Context

We have a big ol google sheet that has evolved organically to contain many sub categories of data, logic, presentation layers (ex. charts and graphs) and is missing any clear navigation.

Goal

re-organize the existing content to make it easier to navigate and maintain (for both engineers contributing to project and all team members interested in the data) as well as being more performant.

Acceptance Criteria

• create a macro google slides deck as a presentation layer, should contain
• create all child sheets listed below
• deprecate original 'data in wbs' sheet

Details

Slide deck

• privacy: obfuscates identifying information (name or url) of the individual data sources
• format
  • a literal google slides deck
  • doesn't need to be pretty
• edit rights should be restricted to sweeties, comment rights should be open to anyone.
• content
  • an index slide
  • section slides (should mirror topic areas listed below, if R&D slides don't make sense at this level then skip it for now)
  • content slides which
    • contain simple (static) tables, graphs and charts copied from child sheets
    • content copied from child sheets should remain linked if google slides offers this option
  • links to each child sheet on both index and individual slide pages. (I recognize this will lead to hidden sheets for the public, im fine with that for now)

Child sheets

• privacy permissions: edit for sweeties, comments for WMDE, hidden for public
• contains
  • individual presentation layer content, ex. charts, graphs and tables (duplicated to slide decK)
  • any logic not already embedded in server-side logic

list of all child sheet topics:

• one macro sheet with a filterable views... equiv to 'latest stats' tab.
  • where possible remove any duplication and prioritize automatically vs manually collected data
• Extensions sheet (with logic hidden but in same file)
• Software versions - mw versions
• Gadgets
• DEI, location, language and categories
• Activity - initial, recent (log data), instance age / year created, user count, editor count (est)
• Quantity/Scale - page counts, data count (items, properties, lexemes, triples, etc), etc
• R&D
  • Log data experiments…
  • Property popularity
  • Knowledge graph connectivity / average distance (hubbiness)