== Requirements ==
In order to have a final draft of the Content Translation schema, we need to do the following.
* Finish deciding exactly which events we want to track and how that will change across the different modes (desktop article translation, desktop section translation, and mobile section translation).
* Decide what ancillary fields are necessary so that the events are properly contextualized
* Review the schema against key research questions to ensure that the data is structured in a way that will make the analysis of those questions as easy as possible.
* Consult Mikhail to make sure our use of fragments and naming conventions match up with Event Platform conventions (or came become Event Platform conventions)
* Consult Language team members to ensure that the selection of events is logical and that they are feasible to instrument.
* Describe in the draft the meaning of each event in enough detail that the implementers know exactly when each event should fire.
* Keep the diagram of the relationships between the events up to date to ensure that nothing important is missed and as a future documentation resource.
== Current schema draft ==
* [Schema draft](https://docs.google.com/document/d/1vebKoKfWoVyyS0fWZOeyK_-eaN_gaiT-Bzm05X-l6ho/edit#)
== Current schema diagram ==
{F33939728, size=full}
Previous schema diagrams:
* v3: {F32414649}
* v2: {F32414654}
* v1: {F32383118}
* Pau's initial draft (apparently Phab can't turn it into a thumbnail, so click "it is a mystery" to view): {F31786984}