Change Details

//As a Campaigns team member, I want to conduct an audit to determine that all required data points for V0 are included in the schema, so that we can make any necessary changes now rather than later.// **Background:** In a recent Design > Engineering meeting, we realized that V0 prototypes included a timestamp for when a participant registered (but the schema did not yet have this data stored anywhere). For this reason, we will be adding in this data in T308128. But we want to avoid this happening in an unstructured way, so we want to do an audit of V0 and determine whether any other schema changes need to be done ASAP. This way, we can quickly make changes in time for the V0 release. **Resources:** [[ https://www.figma.com/proto/h0iZo5Tj6LHpsFDsInWiG0/Pilot---Event-Registration?node-id=4519%3A232102&scaling=min-zoom&page-id=3542%3A127278&starting-point-node-id=4519%3A232102&show-proto-sidebar=1&hide-ui=1| V0: Create Event Prototype ]] [[ https://bit.ly/3utbFM3 | V0: Register for Event Prototype ]] [[ https://bit.ly/3JJN6AM | V0 Design File ]] **Acceptance Criteria:** * Review current V0 prototype to determine which data points would be needed to represent the information * Consult with Design and Product regarding required data points for V0 * Share findings in a comment in this ticket

//As a Campaigns team member, I want to conduct an audit to determine that all required data points for V0 are included in the schema, so that we can make any necessary changes now rather than later.// **Background:** In a recent Design > Engineering meeting, we realized that V0 prototypes included a timestamp for when a participant registered (but the schema did not yet have this data stored anywhere). For this reason, we will be adding in this data in T308128. But we want to avoid this happening in an unstructured way, so we want to do an audit of V0 and determine whether any other schema changes need to be done ASAP. This way, we can quickly make changes in time for the V0 release. **Resources:** [[ https://www.figma.com/proto/h0iZo5Tj6LHpsFDsInWiG0/Pilot---Event-Registration?node-id=4519%3A232102&scaling=min-zoom&page-id=3542%3A127278&starting-point-node-id=4519%3A232102&show-proto-sidebar=1&hide-ui=1| V0: Create Event Prototype ]] [[ https://bit.ly/3utbFM3 | V0: Register for Event Prototype ]] [[ https://bit.ly/3JJN6AM | V0 Design File ]] **Acceptance Criteria:** * Review current V0 prototype to determine which data points would be needed to represent the information * Consult with Design and Product regarding required data points for V0 * Create updated spreadsheet on which data points we will be collecting

//As a Campaigns team member, I want to conduct an audit to determine that all required data points for V0 are included in the schema, so that we can make any necessary changes now rather than later.// **Background:** In a recent Design > Engineering meeting, we realized that V0 prototypes included a timestamp for when a participant registered (but the schema did not yet have this data stored anywhere). For this reason, we will be adding in this data in T308128. But we want to avoid this happening in an unstructured way, so we want to do an audit of V0 and determine whether any other schema changes need to be done ASAP. This way, we can quickly make changes in time for the V0 release. **Resources:** [[ https://www.figma.com/proto/h0iZo5Tj6LHpsFDsInWiG0/Pilot---Event-Registration?node-id=4519%3A232102&scaling=min-zoom&page-id=3542%3A127278&starting-point-node-id=4519%3A232102&show-proto-sidebar=1&hide-ui=1| V0: Create Event Prototype ]] [[ https://bit.ly/3utbFM3 | V0: Register for Event Prototype ]] [[ https://bit.ly/3JJN6AM | V0 Design File ]] **Acceptance Criteria:** * Review current V0 prototype to determine which data points would be needed to represent the information * Consult with Design and Product regarding required data points for V0 * Share findings in a comment in this ticket* Create updated spreadsheet on which data points we will be collecting