Confirmed users
1,247
edits
Support/MetricsDashboardPRD: Difference between revisions
Jump to navigation
Jump to search
→Storage
No edit summary |
|||
| Line 37: | Line 37: | ||
=Storage= | =Storage= | ||
* We should figure out how to store this data. It doesn't seem a good idea to query the DB each time the page is generated (even if that's weekly) and have to requery to get old data. Instead, we should save the metrics in some sort of table or database structure that allows easy access. | * We should figure out how to store this data. It doesn't seem a good idea to query the DB each time the page is generated (even if that's weekly) and have to requery to get old data. Instead, we should save the metrics in some sort of table or database structure that allows easy access. | ||
* Having per-article metrics that also have historical data would be a great idea but needs a good database schema to make for easy querying and data extraction. That way if we want to go back and look at top 10 articles in a given metric rather than just top 5, it's doable. | * The exact schema used is pretty important and something we should all agree on first because it's likely that it will be hard to change down the line. | ||
* Having per-article metrics that also have historical data would be a great idea but needs a good database schema to make for easy querying and data extraction. That way if we want to go back and look at top 10 articles in a given metric rather than just top 5, it's doable. This probably needs its own table(s). | |||
* We should (I should) figure out how much data we're talking about here. | |||
* Since none of the data refreshes more than daily, it may also be possible to shunt the current data run into a single static page that updates daily while still preserving the underlying data. | |||