Analytics/Stories

Editor Engagement Vital Signs (EEVS)

Prioritized Backlog and Current Sprint

We are experimenting using Phabricator. Follow this link!

Stories completed Sprint Ending 4/15/2014

1. user makes report public Mingle #1377
2. user adds scheduled report Mingle #1378

Old user stories (housekeeping needed):

1. CronUser runs report on entire project
2. User runs report for new editor metric
3. Spike on visualization engine
4. Exec visualizes new editor metrics (part 1)
5. Exec visualizes aggregate new editor (part 1)
6. Exec uses UI to select metrics
7. Exec visualizes new editor metrics (final)
8. Exec visualizes newly registered user metrics
9. Exec visualizes productive new editor metrics
10. Devs have revert table
11. Exec visualizes surviving new editor metrics
12. Exec clics link to metric definitions
13. Exec downloads visualized data in TSV

More notes on Epic: https://www.mediawiki.org/wiki/Analytics/Epics/Editor_Engagement_Vital_Signs

Metrics on Mobile Usage

https://www.mediawiki.org/wiki/Analytics/Epics/Metrics_about_Mobile_Usage

Dashboards

Current focus is on Annotations and Discoverability

Secondary Focus on

Limn Dashboard Deployment

https://www.mediawiki.org/wiki/Analytics/Epics/Simplify_Limn_Dashboard_Deployment

EventLogging

Current Focus is on Transition

Unprioritized Backlog

1. HadoopUser uses production-ready geotagging infrastructure
2. Researcher queries geotagging DB for one-off tasks (using R, python, etc)

Metric Definition Standardization

https://www.mediawiki.org/wiki/Analytics/Epics/Metric_Definition_Standardization

Wikipedia Zero Pageviews

Focus on accuracy