Support/Kitsune/KB Metrics Roadmap

Roadmap for KB Metrics

	THIS PAGE IS A WORKING DRAFT
	The page may be difficult to navigate, and some information on its subject might be incomplete and/or evolving rapidly. If you have any questions or ideas, please add them as a new topic on the discussion page.

NB This is in Draft status because of ongoing user testing that may affect priorities.

• [DONE] Phase 1 - Metrics backend (bug 663234)
  • Determine data required for KB metrics
    • Already has
      • document_id
      • helpful
      • created (datetime)
      • creator_id
      • anonymous_id
      • useragent
    • Needs
      • revision_id
  • Write patch to collect new votes with revision ID
  • Incorporate fallback mechanism to check if user has already votes (check new data, but no results -> check old data)
  • Write migration to convert old votes to new format having revision ID (bug 671405)
    • Converting a large dataset is expensive, so we have to figure out the best way to do it.

• Phase 2 - Metrics front-end
  • Choose a graphing library to create the frontend graphs
    • Highcharts (www.highcharts.com)
  • Make the graph visible only after clicking a view link
    • Not default loading
    • AJAX, so no page reload (bug 663239)
  • Interactive
    • Hover effects to indicate revision

• [in progress] Phase 3 - Admin Panel (bug 672562)
  • Give admin panel to add/remove global dates to all metrics graphs
    • Useful to mark release dates of Firefox, etc, to see important relations between votes and changes.

• Phase 4 - Aggregate Metrics (bug 663244)
  • Show helpful metrics in a single page so that contributors don't have to visit multiple pages and that their attention can be called to where it's needed.
    • Show data from "movers and shakers" (highest change in number of votes)
    • Show least helpful articles (where no > yes votes)
    • Maybe something with useragents?