This is a parent task for the work to be done for the Better Use of Data Program, which was started in FY2018/19.
NOTE: This task is a working draft and subject to change.
# Roadmap FY2019-2020
##### Q1 (July - September)
##### Data Engineering
[] **Common Instrumentation Development Kit (prototype)**
[] Develop JavaScript client
[] Develop Swift client
[] Develop Java client
[] Document API and behavior specification on-wiki
[] Document examples, usage, and best practices on-wiki
[] **Cross-platform datasets**
[] Research and architect "unique devices" dataset
[] Research and architect "session length" dataset
##### Data Access
[] Automated dashboard for Audiences Core Metrics (Readers & Contributors)
[] Internal production release of edits_hourly and editors_monthly Druid datasets (for use in Superset and Turnilo)
##### Data Training
[] Product team trainings: best practices for working with data in the product development lifecycle
[] Product team trainings for core metrics: data exploration and reports
##### Tracking
- MEP stream configuration service planning
- MEP schema registry deployment
- Client-side error logging working group
---
##### Q2 (October - December)
##### Data Engineering
[] **MEP for Audiences**
[] Develop schema registry UI
[] Develop stream configuration service UI
[] Develop CI and commit hooks
[] Develop stream configuration service metadata
[] Cross-platform client-side error logging
[] Evaluate analytics systems capacity
[] Evaluate incremental back-off / rate limiting solutions
##### Tracking
- MEP engineering sync
- Client-side error logging working group
---
##### Q3 (January - March)
##### Data Engineering
[] **Common Instrumentation Development Kit (final production form)**
[] Develop production version of Sampling Controller
[] Develop production version of Association Controller
[] **Complex analytics guidance**
[] Document A/B testing procedures
[] Document funnel analysis procedures
##### Tracking
- TBD
---
##### Q4 (April - June)
##### Data Engineering
[] Advise all newly-created schema use EventGate-style JSONSchema
[] Port select EventLogging schema to EventGate-style JSONSchema
[] Evaluate feasibility of cross-schema joins
[] Develop automated ingestion pipeline and dashboard defaults
##### Tracking
- TBD