Context
the team needs a place where we can access reasonably up to date metrics based on the work produced by this broader project.
Story
As PM and UXR (and internal stakeholder) I need easy access to reasonably up to date key metrics re Wikibase Suite.
Goal
Automate syncing our metrics sheet with our metrics database.
Definition of done
this ticket acts as a project container. when the child tickets are complete this ticket's goal should be met.
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T371844 Metrics 1.1 - increase ease of access to data | |||
| Open | Spike | None | T369936 Suite Scraper: Link and automate data transfer between metrics db and spreadsheet | ||
| In Progress | Spike | RickiJay-WMDE | T369963 Create a method to automatically sync data from the database to the sheet | ||
| Open | Spike | None | T369965 Consider google sheets performance in architecting data flow between metrics db and sheet |
I didn't know where to put this exactly because im not quite sure how you'll build this but I found myself wondering at the difference between times when we're basically syncing the raw data (ex. number of properties in an instance) vs syncing the result of some logic (ex. the connectivity score) vs some sort of aggregated stat (total findable triples in ecosystem). certainly we'll want to be able to 'send' all three types from the sheet to the db.
that said, I don't really know if these are basically all the same action in the end or take some different considerations in the api or how the thing is architected. so just sharing as food for thought.
ofc feel free to create additional tickets to describe this work as you see fit :)