Resolving as this presentation was completed at the June 6 Staff Meeting.

I've created a dashboard to explore how edit sizes vary by the specified dimensions. The dashboard includes data on median edit size and the proportion of edits by size.

Thank you for the clarification. See some responses below:

I've taken an initial pass at draft slides for the June 4 staff meeting for review and iteration.

@ppelberg I finished reviewing and just made a few small corrections to fix typos and a broken link. The content looks good to me. This should be ready to now publish.

I'd also recommend making sure there are definitions documented for contextual attributes where it may be unclear.

Would it be accurate for me to understand the columns below as meaning...?

num_domain_occurrences: the number of references that cite a given domain across all pages in the main namespace at a given project

The num_domain_occurrences comes from the external links table and indicates the number of times that domain appears across all pages on a given project.

Thanks for following up. See responses inline below and let me know if any additional information would be helpful:

I've completed QA of the new event.mediawiki_product_metrics_wikifunctions_ui table and confirmed that all events are logging as expected with minimal variance in counts. I've noted a few questions below primarily for clarification. See summary of checks noted below and full QA report for details.

@VirginiaPoundstone
I've completed some initial QA checks and confirmed that there are no significant issues or discrepancies with the new instrumentation (all new and previous fields are logging as expected and there are no large discrepancies in total event counts between the two instruments).

@Trizek-WMF I've drafted a summary of the Reference Check results on my sandbox page that can be published on mediawiki. Feel free to edit as needed and let me know if you have any questions or if there is additional text I can help provide.

Revert rate of new content edits with a reference by experience level and wiki

Using data contained in mediawiki_history, I also queried other data associated with the new content edit including wiki, user experience level, and if it was reverted within 48 hours. I also added in if reference check was shown during the edit (the first iteration of edit check, which prompts a user to add a citation if they have not done so already prior to publishing).

Review the sources people are citing when they add new content that includes a reference. Note: The analysis I completed in T346982 can be re-used to help complete this task.

All results and methodology are now summarized in the final report. Please let me know if you have any questions or suggested additions/changes.

The final draft is ready for review.

I did a quick check and confirmed that the missing daily data issue appears to be isolated to druid. The unique device tables in hive included the expected daily data for March and April.

I've completed the retention rate analysis (Curioisity #2) now that we have two full months of data. Findings are summarized on slides 20-28 of the slide deck.

I've completed the analysis of all the identified metrics, which are summarized in the report.

QA is currently pending deployment of a patch to add the stream to $wgEventLoggingStreamNames. The patch is expected to be deployed tomorrow and then data should start to be available in event.mediawiki_product_metrics_wikifunctions_ui for QA

I reviewed data logged for this new event in wikifunctions_ui and confirmed the data appears as expected. See summary of checks below:

Completed review of guardrails #4-5. Findings are summarized on slides 35-45 of the slide deck.

Resolving this task as we've confirmed we have instrumentation to track the language settings of users and I was able to use this instrumentation to pull all needed data for the Audience research work.

I've confirmed that the new instrumentation added to track this feature appears to be logging as expected. See summary of QA checks and some initial data findings below:

I've completed an initial analysis exploring user's interface languages, geographical distribution and community engagement. Findings are summarized in a google doc.

I've completed an initial analysis of the Edit Check AB test results including review of the KPI, Curiosity #1, and Guardrails 1-3. Results are summarized in this slide deck which was presented to the team on 12 March 2024.

I agree that the webuisactionstracking schema is probably the best fit for this but there are a few limitations this will introduce including per wiki sampling rates and data retention periods that will impact how the metrics in T359489 are calculated. See notes below: