Right now, we have an intermediate pageviews_corrected table which we use to apply to a single correction to the page view data (relating to Internet Explorer traffic from Pakistan).
We also apply corrections in Wikicharts for the traffic data loss and unique devices data loss.
We should adopt a standard approach for handling these corrections.
Options:
- use an intermediate table.
- integrate it into the SQL queries. Simpler to maintain, but the data won't be available for other uses (e.g. Superset dashboard?)
just give up on the corrections altogether and go back to using unmodified page view data. That isn't workable given the importance of correcting for the traffic and unique devices data loss.