Page MenuHomePhabricator

Investigation: Determine that we are collecting all necessary data for V0
Closed, ResolvedPublic3 Estimated Story Points

Description

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:
V0: Create Event Prototype
V0: Register for Event Prototype
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

Event Timeline

ifried renamed this task from Audit to determine that we are collecting all necessary data for V0 to Investigation: Determine that we are collecting all necessary data for V0.May 13 2022, 2:24 PM
ifried updated the task description. (Show Details)

Hi all, this is the link of the new spreadsheet with the fields we currently have for V0, I added some references to where the data will be displayed, so we can check on the wireframes if we are missing some data, it is on the column called "Where do we use this data?":
https://docs.google.com/spreadsheets/d/1nY5ITmFLzFeeh1CUbaCR66rZ3xHV-PuCm6okuaDNQAg/edit#gid=0

This is the link of our schema:
JSON FILE
https://app.dbdesigner.net/designer/schema/0-untitled-4bdd90b6-afb6-45ff-b6af-f0bac3537e85

I think we should add timestamps for the ce_organizers table, like:

  • created_at
  • updated_at
  • deleted_at

This can be useful on v1 when we add the feature to add and remove organizers.

@Daimona , @ifried , @vyuen what do you think?

I'd rather not use that link because it's outdated. Now that it exists, I believe that the JSON file should be the ultimate source of truth.

I think we should add timestamps for the ce_organizers table, like:

  • created_at
  • updated_at
  • deleted_at

This can be useful on v1 when we add the feature to add and remove organizers.

If we plan to use this information, yes.

I'd rather not use that link because it's outdated. Now that it exists, I believe that the JSON file should be the ultimate source of truth.

I think we should add timestamps for the ce_organizers table, like:

  • created_at
  • updated_at
  • deleted_at

This can be useful on v1 when we add the feature to add and remove organizers.

If we plan to use this information, yes.

Thanks, I agree, adding the link to the JSON file is the best option.

The engineers have finished this work, and we have a follow-up task for V1 (T312870), so I'm marking this as Done.