User Details
- User Since
- Apr 16 2015, 4:17 PM (471 w, 1 d)
- Availability
- Available
- LDAP User
- Neil Shah-Quinn (WMF)
- MediaWiki User
- Neil Shah-Quinn (WMF) [ Global Accounts ]
Today
We decided that we would leave both the totals and month-over-month values rather than (a) add a whole new layer to the code in order to keep the totals without displaying them in the "finished" TSV files" or (b) drop the month-over-month values, which would make the spreadsheets a lot less useful.
@Pppery Data-Platform intentionally includes "NEW BUG REPORT" in task titles using their custom form. I believe this is so that new reports catch their attention better. (I agree it does look untidy 😁).
Yesterday
Wed, Apr 24
I just ran into this on MediaWiki.org (that's the permalink, but it's the current version of the page). There are actually several commented-out ranges on the page, which are all displaying incorrectly.
@OSefu-WMF, @mpopov could you approve this access for @Hghani and me?
Tue, Apr 23
Sat, Apr 20
In addition to re-doing the configuration change, @Hghani and I need to get permission to access the deployment server so we can deploy jobs.
Definitely add more potential data quality metrics and other ideas for the dashboard. If it's something beyond creating a dashboard (like, I don't know, using deequ to test our intermediate datasets), it's better to create a new task.
Fri, Apr 19
Okay, sounds like we have broad support, so let's go ahead and create the tag!
FYI, based on the results of T337103, user_is_anonymous and its siblings should be false for temporary users.
Thu, Apr 18
This was actually done a while ago.
Yes, I defintely agree.
One question is how we should handle issues where the data shows spikes or anomalies which are likely related to external factors (e.g. bot users) rather than a clear software bug on our end, like T355143 or T313114. My inclination is that such issues should also be included in this tag (rather than, for example, having a separate tag), but I'm interested in what others think.
Wed, Apr 17
I don't want this created yet. First, I'm looking for feedback on the idea (primarily from Foundation folks involved in the data governance work mentioned in the description, but of course it's open to everyone).
Tue, Apr 16
I'll track the documentation work in each individual task for generating a new table.
I will remove wmf_product.pageviews_corrected as part of T362593.
Since we will be changing the layout and locations of the intermediate tables as part of T333225, we wait and update the documentation afterward.
Mon, Apr 15
Fri, Apr 12
I consulted @Hghani and he agrees with the approach above.
Thu, Apr 11
Wed, Apr 10
The GitHub repo has been updated to point there.
Tue, Apr 9
The last thing I need to do I make arrangements to share the analytics_product Airflow instance while still having team-specific configuration (like the alert email address).