To make a final decision on the standard base schema for v1, we need to dig into the preliminary list of fields in the code to check for feasibility, triage, and prioritize.
Working list: https://docs.google.com/document/d/1Z_KRHWw7hNXldePxJP1YTvxJHOtKzZ3kSTo7YPkdp4k
Feasabilty assessment for items in the working list: https://docs.google.com/spreadsheets/d/1fmAtvRsXltMOzBJ8Br9QxCdBaPHDT0ygrXXZ1CGASq8
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | phuedx | T276378 EPIC: Release Metrics Platform v1 | |||
| Resolved | Ottomata | T281999 Metrics Platform Schema: Define & Model Event Level Fields | |||
| Duplicate | • jlinehan | T277092 [Metrics Platform] Standard base schema | |||
| Resolved | • jlinehan | T276379 [Metrics Platform] Create Metrics Platform Schema | |||
| Resolved | • DAbad | T275420 [Metrics Platform] Define first set of standard fields for metrics platform | |||
| Duplicate | kzimmerman | T278595 [Metrics Platform] Evaluate preliminary list of standard fields for feasibility | |||
| Resolved | • Mholloway | T280195 Create a device detection strategy for the device_type context field | |||
| Resolved | phuedx | T277090 [Metrics Platform] Standard base schema should include a 'test' or 'debug' field for QA and other purposes |
I think this is done, considering the task is scoped to the preliminary list? The preliminary list is essentially the green portion of the spreadsheet.
But, there is a subtask to be created shortly about device detection strategies. That probably precludes closing this one for now.