User Details
- User Since
- Jul 8 2019, 8:14 PM (268 w, 1 d)
- Availability
- Available
- LDAP User
- Unknown
- MediaWiki User
- MKampurath (WMF) [ Global Accounts ]
Sat, Aug 17
Aug 16, 2024
Progress update for the week
- Calculated July metrics and started analysis and information gathering for narrative
- Continued editing the Q4 quarterly metrics on the Sandbox
Fri, Aug 9
Aug 9, 2024
Progress update for the week
- Reviewed the Q4 quarterly report with Caroline Myrick.
- Started editing it on the Sandbox
- Reached out to folks, with additional questions about the quarterly report.
What are your priorities for next week
- Apply for schengen visa
- Calculate July monthly metrics
Any emerging blockers or risks ? or unresolved dependencies?
- no
Have there been any new learnings?
- no
Have there been any changes to the scope or timeline?
- no
Are you working on anything else that is not captured in any other reports?
- No
Fri, Aug 2
Aug 2, 2024
Progress update for the week
- Quarterly Reporting
- Reviewed and Summarized Q4 Content gap and Relevance metric initiatives
- Discussed QLS and Annual plan metrics presentation plan with Selena, Amanda, Kate and Omari
- Temporary Accounts Initiative - discussed internally with the team and communicated decisions on data changes needed for the project to the data engineering team
- Slow progress this week as Ive been OOO most of this week.
What are your priorities for next week
- Reach out and make connections with folks that I gathered from my initial discussions with Caroline,Omari and Kate
- Deliver Q4 report for publishing on meta
Any emerging blockers or risks ? or unresolved dependencies?
- no
Have there been any new learnings?
- Yes we’re looking into the possibility of connecting dots outside of P&T to be able to incorporate them into monthly metrics updates
Have there been any changes to the scope or timeline?
- no
Are you working on anything else that is not captured in any other reports?
- no
Thu, Aug 1
Also, I'd suggest making the field user_is_temporary rather than user_is_temp. That would be in line with our usual practice of spelling things out fully, and also probably slightly more accessible.
@nshahquinn-wmf and I discussed this further today for answering a few questions in @Milimetric 's document and we would prefer that every table which has the column user_is_anonymous should have a new corresponding column user_is_temp (not _temporary, to keep the naming consistent with mediawiki)
Wed, Jul 31
Tue, Jul 30
Hi @VirginiaPoundstone , not aware of any other edge cases. I spot checked a few pages from the list of 140 and found that many of the articles were created in July 2024 and I found pageviews using the AQS API, as well as the pageviews tool (example page). I think we should vet the list to understand true impact of this problem.
Jul 26 2024
Jul 26, 2024
Progress update for the week
- Quarterly reporting
- Followed up with PMs and folks to collect information about initiatives that may have impacted Q4 high level metrics
- Summarized Q4 Content gap and Relevance metric initiatives
- Slow progress this week as Ive been OOO most of this week.
What are your priorities for next week
- Reach out and make connections with folks that I gathered from my initial discussions with Caroline,Omari and Kate
Any emerging blockers or risks ? or unresolved dependencies?
- no
Have there been any new learnings?
- Yes we’re looking into the possibility of connecting dots outside of P&T to be able to incorporate them into monthly metrics updates
Have there been any changes to the scope or timeline?
- no
Are you working on anything else that is not captured in any other reports?
- No
Jul 23 2024
Jul 19 2024
Progress update for the week
- Met with Omari and Kate this week to understand their takeways and learnings from last year’s SDS 1.4 work, and opportunities for improvement. Mapped the information gathered from them and made action items to focus on next steps.
- Monthly reporting - reviewed the summary for publishing
- Quarterly reporting
- Followed up with PMs and folks to collect information about initiatives that may have impacted Q4 high level metrics
- Created a summary of the Q4 Contributors metric initiatives
What are your priorities for next week
- Add Q4 metric initiatives and Finalize Quarterly metrics reporting
- Planning and reaching out for Infographics POC
- Planning for focus group and reaching out to stakeholders
- OOO 7/25 and 7/26
Any emerging blockers or risks ? or unresolved dependencies?
- no
Have there been any new learnings?
- Yes. learnings on what narrative driven metric report could look like.
Have there been any changes to the scope or timeline?
- no
Are you working on anything else that is not captured in any other reports?
- Debugging https://phabricator.wikimedia.org/T364872 with Mikhail and Dan
Jul 18 2024
Ohh ok. got it. thanks @lbowmaker
will this enable us to get dashboards info as well, more regularly ?
One additional request - can we please update the description of this task so its clear what is being done here.
IIUC isn't Superset already integrated with Datahub? I can see the list of charts (but not dashboards) created on superset. what will this pipeline help to do exactly?
Jul 11 2024
Jul 12, 2024
Progress update for the week
- Read thru 'How-to' Guide: Quarterly Core Metrics Reports
- Met with Caroline and got a lot of information about metrics reporting including background documentation on past FY’s discussions on community feedback
- Started planning for identifying stakeholders and solicit feedback from individuals/group on improving our reporting
What are your priorities for next week
- Meet with Kate and Omari, who have laid a good foundation for the work previously done for metrics reporting, and build some ideas together.
- External search engine referrer pageviews analysis
Any emerging blockers or risks ? or unresolved dependencies?
- no
Have there been any new learnings?
- Yes! Lots of learnings and takeaways from the last 3 quarters of core metrics reporting, things we would like to stop and things we would like to do more of.
Have there been any changes to the scope or timeline?
- no
Are you working on anything else that is not captured in any other reports?
- Provided feedback for Essential metric documentation
- Helped in finalizing the last Asana report for WE 1.3
Jul 9 2024
Hey @YLiou_WMF I do believe it would be worthwhile adding the missing sub topics within Accessibility and Relevance as mentioned in my previous comment. We have added a lot of content in these sections in our review of core metrics and found it useful in getting a comprehensive understanding of our metrics.
example, Effectiveness
Adding some points discussed in the Council meeting today
- Stewardship Scope: review list of duties, develop a minimal set of responsibilities
- Need to adjust due to move from individual-based stewardship to team-based stewardship
- OD: Effectiveness metric stewardship
- KZ: external audit for F&A.
- Internally, we know James Baldwin & Shelby Langan are the go-to, but this is not well-documented
Jul 3 2024
Hi @YLiou_WMF , I did a quick scan and the following seem to be missing from the detailed explanation
- Accessibility
- Documentation/ Openness
- Relevance
- Impact
- Baselines, Benchmarks, historical data
This task is done and was closed on June 14. See Asana for details
Yes! this is officially completed!
Individual Close out reports for the hypotheses are available on this KR list
Jul 1 2024
Hi @YLiou_WMF , aren't we planning to expand on the Essential_metrics#Definitions to provide explanation on each of the dimensions and what they mean based on the proposal ?
Jun 27 2024
I wanted to chime in that this data will be very useful for us as we look at high level metrics in the upcoming FY. Thank you Research team for prioritizing and completing this!
I wanted to add that having this data in a Hive table would be very helpful in making it user friendly. It would be very convenient if we could run SQL queries directly on it and use it to make charts in Superset, to analyze the topics that engage readers and editors.
Yes! this is complete for our first set of data stewards.
Ive followed up with the program manager. Will update here as soon as I hear from them.
Jun 26 2024
thanks @Isaac ! I will keep an eye on this task.
Pls reach out to Movement-Insights team if you need help or support with use cases, or to chime in on prioritization.
Jun 25 2024
This is not in scope for SDS1.1 KR, so we have decided to take this on as Essential work and will be decided by the movement insights team.
Jun 19 2024
Jun 18 2024
will this have an impact, or help improve our existing way of measuring content gaps? if yes, then I would be happy to weigh in on some questions - like providing use-cases associated with this model.
Jun 17 2024
While we can deprecate the superset section, we need to verify if Turnilo section is still relevant or not, since datahub is not synced with Turnilo?
thanks @TBurmeister for your inputs . We will park it in meta wiki, per the other suggestions.
Also https://www.mediawiki.org/wiki/Wikimedia_Product/Data_dictionary should be deprecated since we have Datahub now, and this information was pre-datahub. I'll create a task for deprecating, after conferring with other data users. thanks for bringing it up !
Jun 16 2024
@kzimmerman : This topic came up in our steering committee meeting last week. Do you have any suggestions? or preferences?
Jun 13 2024
Jun 12 2024
Jun 7 2024
Dan and I looked at this a bit more in our data operating theater and have a strong suspicion that this is indeed caused by re-direct requests. We compared April 19 which was akin to previous trends and Apr 26 which saw spikes and you can see the difference in 301 requests between the two days.
Jun 4 2024
I have created this basic chart on Superset, which needs few more enhancements.
May 29 2024
May 28 2024
As a part of SDS1.1.2, I have created a high level requirements doc which we can expand to implement data quality measures for Unique Devices.
I adopted it from the work DPE had done earlier this year for SDS3.3. In the next quarter, we can dive deep to work out details such as the data quality measure name, superset dashboard/chart, etc. and other details with the Data Engineering team.
May 24 2024
Thanks @MNeisler for the response. While the contribution of wikifunctions is less to overall unique devices, this does seem like a big problem for the team as they are unable to to look at a key metric.
As a first step to investigating if this is connected to T344381, I tried looking at the Central Notice calendar to see if any banners have been running that may have been causing incorrect redirect requests. I don't see any banner campaigns running in HK so this doesn't give us much.
@TAndic, do you know if there are banners or campaigns running in Hong Kong or Singapore? I checked the calendar and the archive, but didn't see anything. Martin asked me to reach out to you for help with the central notice and campaigns.
May 17 2024
May 15 2024
Disable Chrome Private Prefetch Proxy - Monitoring Plan lays out some low-lift monitoring activities that we could do over the next 7, 30, 90 days to make sure we catch any abnormalities.
Today Movement-Insights spoke about doing some preliminary impact analysis.
We have a report Temporary Accounts Initiative aka IP Masking Impact Report (Data) and it has ‘what’ will be impacted, we need to understand ‘by how much’ it will be impacted, and update that report.
PS: timeline - testwiki deployment will happen before the end of June 2024.
@MNeisler : Can you provide impact of this issue. I would like to know
- proportion of wikifunctions unique devices to overall unique devices (now as well as prior to this bug)
- how is this impacting the work you're doing for Abstract wp team ?
- how often are the superset dashboards monitored? by whom?
- what kind of decisions are the Abstract team making from knowing the unique devices that access wikifunctions.
- any community involvement?
- anything else that you would like to add
May 14 2024
Apr 29 2024
Apr 24 2024
In today's team meeting we spoke about approach, creating a prototype table with the corrections and lowering the scope to phase it out for each metric area, starting with pageviews or unique devices.
Apr 23 2024
We are leaning towards switching off the Prefetch feature since the fraction of requests with no-cookies is 17.5% . numbers in the notebook (last cell)
Apr 22 2024
I think classifying the issues by data domain will definitely be useful. As a start, we can use workboard columns to do this, unless we decide it would be more useful to use columns for status (e.g. backlog, investigation, fixing...).
Yes! lets start with that.
@nshahquinn-wmf , do you have permission to create the yellow project tags? or can we request to have that created in this task ?
Apr 18 2024
Ty @nshahquinn-wmf for opening this task. Sharing my initial thoughts below:
- Agree that we should tag all the tasks that reports data anomalies with this tag, for now. Once we use this method and find that the proportion of bot issues surpasses software bugs, or vice versa, we can think about splitting it out.
- I would like us to use this tag for data issues reported Community as well. Not sure if you already intended that but in the examples I saw tasks opened by WMF staff so wanted to make it explicit here
- I'm wondering if instead of one data-problem tag, we should instead have functional area tags like data-problem-traffic, data-problem-readership, data-problem-contributors, data-problem-content to keep track of the areas where we have data problems. But this would mean not having tags for tables that fall outside of functional areas (if we have any). And the quintessential problem of too many tags!
Similar to T307883, Im inclined towards declining this task since -
- they've been open for a while
- we are re-thinking our strategy for Contributors metric since it is now a core annual plan metric. @OSefu-WMF is there a task I can link here for the work you are doing?
Im inclined towards declining this task since -
- they've been open for a while
- we are re-thinking our strategy for Contributors metric since it is now a core annual plan metric. @OSefu-WMF is there a task I can link here for the work you are doing?
Apr 17 2024
Apr 12 2024
Observed results:
Querying the daily sum of unique devices across all domains using druid.unique_devices_per_domain_daily or all project families using druid.unique_devices_per_project_family_daily shows no daily data logged for January 2024 and February 2024. There is only one data point logged for both datasets 2024-01-01 and 2024-02-01. It appears this impacts all project families and domains. Daily data returns to expected values as of March 2024.
Apr 11 2024
I got the below error when upgraded to Pandas 2.2.2
Apr 10 2024
Can I add more scope to this?
Apr 9 2024
@nshahquinn-wmf can you share the timeline you have planned for removing them from the repo?
Apr 5 2024
- Dig into our data on user traffic and how we’re segmenting traffic
Mar 18 2024
Hi @VirginiaPoundstone this work supports the Essential Work we have to perform of providing movement metrics each month to inform internal staff as well as share externally.
As a part of the monthly movement metrics, we need to analyze trends and investigate anomalies, to inform executive leadership as well as engage various teams to resolve potential issues. This view of the editor data will help us do that.
Mar 14 2024
Summary
We have decided to close out the hypothesis.
Mar 13 2024
Hi @lbowmaker , Since the Contributors metric in SDS1.1.1 was rejected and the hypothesis was disproven, we didn’t go ahead with implementing data stewardship even though data stewards were selected.