The dashboarding problem
1 like615 views
The Wikimedia Foundation's analytics team aims to improve editor engagement visualization across its projects by addressing data accessibility, visualization, and information architecture. They prioritize public access to data, utilize server-less technology to simplify development, and leverage a micro-library stack for dashboard creation. Key lessons learned emphasize reducing complexity and the benefits of a server-less approach for easier deployment.
![https://metrics.wmflabs.org/static/public/dash/
{
"defaultProjects": [
"enwiki", "eswiki", "dewiki", "frwiki", "ruwiki",
"jawiki", "itwiki"
],
"defaultMetrics": [
"RollingActiveEditor", "NewlyRegistered"
]
}](https://image.slidesharecdn.com/thedashboardingproblem-141023143638-conversion-gate02/85/The-dashboarding-problem-39-320.jpg)
The dashboarding problem
- 2. Analytics team at Wikimedia Foundation
- 3. Easily Visualize Editor Engagement for all Wikimedia projects Goal:
- 4. Explore Side Goal: Dashboarding Technologies
- 5. Date project pages created 20140101 arwiki 50 20140102 arwiki 40 … 20140101 dewiki 100 20140102 dewiki 200
- 6. Problem #1
- 7. Problem #1 Access to Data
- 8. Everyone should have access! Easily Visualize Editor Engagement for all Wikimedia projects
- 9. Problem #1 Public Access to Data
- 13. Visualization is an easier problem than data access
- 18. Problem #3
- 19. Problem #3 Information Architecture
- 20. How do you explore data for more than 800 projects?
- 24. #1 Access to Data #2 Visualization #3 Information Architecture
- 25. #1 Access to Data #2 Visualization #3 Information engineering Architecture design
- 26. #3 Information Architecture Design knows best
- 28. #1 Access to Data
- 29. Tech Decision: Make all data available via HTTP
- 31. Data is available in JSON format
- 32. { "result": { "Sum": { "newly_registered": { "2014-08-26 00:00:00": 364.0, "2014-08-24 00:00:00": 331.0, "2014-08-21 00:00:00": 382.0, "2014-08-30 00:00:00": 383.0, "2014-09-25 00:00:00": 372.0, "2014-08-22 00:00:00": 367.0, "2014-09-24 00:00:00": 410.0, "2014-09-06 00:00:00": 370.0, "2014-09-09 00:00:00": 370.0, "2014-09-27 00:00:00": 321.0, "2014-09-05 00:00:00": 317.0 } } }, "parameters": { "Cohort": "arwiki", "Created On": "2014-09-13 00:00:00", "Metric_end_date": "2014-09-13 00:00:00", "Metric_start_date": "2014-09-12 00:00:00", "Cohort Size": 0, "Metric": "NewlyRegistered" } } Includes metadata
- 33. Data is available to everyone.
- 35. Why not?... Server-less What is the middle tier for anyways?
- 36. Decouples visualization piece from data gathering piece No authentication needed Server-less
- 38. We are server-less, we need to store the bootstrap state of the dashboard somewhere
- 39. https://metrics.wmflabs.org/static/public/dash/ { "defaultProjects": [ "enwiki", "eswiki", "dewiki", "frwiki", "ruwiki", "jawiki", "itwiki" ], "defaultMetrics": [ "RollingActiveEditor", "NewlyRegistered" ] }
- 40. Any other data store. Yours?
- 41. Technology Stack
- 42. Must Haves: Package Manager Dependency Loading Data Binding Library DOM manipulation and ajax Testing
- 43. Technology Stack Micro libraries: “each library does 1 thing well”
- 44. > Bower install
- 48. The Of Knockout Components
- 49. Knockout is not Polymer
- 50. Reusable pieces
- 52. Show me the code….
- 55. Dashiki: a thin wrapper on top of OS technology + information architecture. We can use dashiki to build other dashboards.
- 57. Lessons: Server-less = Reduced complexity Easy(est) to deploy CORS No error log for now Bootstrap default state Keep things simple. No authentication.
- 58. Questions?