The idea is that schemas across our many products should be consistent between each other by having a set of commonly-used fields defined in the same schema fragment which can be referenced by specific schemas. For example, we want to standardize identifier names and meanings. This enables cross-schema analysis, reusable instrumentation snippets, and portability between analysts.
Draft on wiki: mw:Wikimedia Product/Analytics Infrastructure/Schema fragments
Change 605303 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] [WIP] Add product analytics fragment
Hm… maybe user, page, and ui would be better as separate fragments, rather than together in one fragment
Change 605303 abandoned by Bearloga:
[schemas/event/secondary@master] [WIP] Add product analytics fragments
Reason:
Splitting up into smaller patches (one patch per fragment)
Change 615559 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] Add identifiers fragment
Change 615560 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] Add activity sequence fragment
Change 615561 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] Add user fragment
Change 615562 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] Add page fragment
Change 615563 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] Add UTM parameters fragment
Change 615565 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] Add UI fragment
Change 615566 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] Add A/B testing fragment
Change 615559 merged by Bearloga:
[schemas/event/secondary@master] Add identifiers fragments
Change 622183 had a related patch set uploaded (by Bearloga; owner: Bearloga):
[schemas/event/secondary@master] [WIP] Create mediawiki_common fragment
Change 615563 merged by Bearloga:
[schemas/event/secondary@master] Add UTM parameters fragment
Change 615560 abandoned by Bearloga:
[schemas/event/secondary@master] Add activity sequence fragment
Reason:
Abandoning the notion of generic activity/sequence IDs in a fragment in favor of including these in best practices and letting schema developers create them manually in their schemas.
Change 615562 abandoned by Bearloga:
[schemas/event/secondary@master] [WIP] Create mediawiki_page fragment
Reason:
Abandoning in favor of grander discussion and planning of standard dimensions and schema field conventions (refer to https://phabricator.wikimedia.org/T275420)
Change 622183 abandoned by Bearloga:
[schemas/event/secondary@master] [WIP] Create mediawiki_common fragment
Reason:
Abandoning in favor of grander discussion and planning of standard dimensions and schema field conventions (refer to https://phabricator.wikimedia.org/T275420)
Change 615561 abandoned by Bearloga:
[schemas/event/secondary@master] [WIP] Create mediawiki_user fragment
Reason:
Abandoning in favor of grander discussion and planning of standard dimensions and schema field conventions (refer to https://phabricator.wikimedia.org/T275420)
Change 615565 abandoned by Bearloga:
[schemas/event/secondary@master] Add web user interface fragment
Reason:
Abandoning in favor of grander discussion and planning of standard dimensions and schema field conventions (refer to https://phabricator.wikimedia.org/T275420)
Change 615566 abandoned by Bearloga:
[schemas/event/secondary@master] Add A/B testing fragment
Reason:
Abandoning in favor of grander discussion and planning of standard dimensions and schema field conventions (refer to https://phabricator.wikimedia.org/T275420)
Abandoning in favor of grander discussion and planning of standard dimensions and schema field conventions (T275420).
We may decide to not do the fields as fragments but in a "universal" schema. May re-open this ticket, if needed.