Resolving this task but please reach out if you have any questions.

I've added new charts to the wikifunctions superset dashboard to track API metrics stored in the mediawiki_product_metrics_wikilambda_api table. These are all currently stored under the "API metrics" tab.

Resolving this task as I've addressed all comments in the doc but please reach out if you have any questions. Any additional analysis requests about the current user base can be filed under separate tickets.

I've updated the "Interactions tab" of the wikifunctions superset dashboard to reference event.mediawiki_product_metrics_wikifunctions_ui.

Thanks for confirming @Esanders. With that clarification, all data logged for this event in mediawiki_web_ui_actions looks good to me. Reassigning to @ppelberg for sign-off/any next steps.

I've completed QA of the data logged for the new event instrumented in https://gerrit.wikimedia.org/r/1008929 to track clicks to permalink timestamps.

@DMartin-WMF
I've completed an initial QA of the data logged in the new event.mediawiki_product_metrics_wikilambda_api. We started recording events in this table following the deployment of this fix on 20 June 2024.

we'd value knowing of the edits newcomers publish >100 bytes, how those edits are distributed by byte size.

Just following up to confirm that the patch to add change events for function editing was deployed. I checked the data logged in event.mediawiki_product_metrics_wikifunctions_ui and confirmed that the new change event is logging as expected.

@ppelberg
I've completed an initial analysis of the baseline for constructive activation per the definition documented in DRAFT APP FY24-25: OKRs sheet and defined below.

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