Page MenuHomePhabricator

[Analytics] [Request] [WDPE] Wikidata Promotional Editing: Revert Risk Model - Usage Metrics Monitoring
Open, Needs TriagePublic8 Estimated Story Points

Description

WMDE Analytics Request

This task was generated using the WMDE Analytics request form. Please use the task templates linked on our project page to create tasks for the team. Thank you!

Why (Context & Decision)

Background:
Wikidata has always been a target for search engine optimization but it seems to be increasing significantly recently. People seem to be led to Wikidata as the place to anchor their entity to be accessible in generative AI answers etc. To help ensure promotional editing is being spotted and properly acted upon, a revert risk model has been created. The analytics team would like to support this work and provide metric monitoring for the Revert Risk Model usage and impact to this overall topic.

Notes
Draw io

What (Scope & Output)

We would like to understand the usage of the model, by the Patroller group:
Is the new risk model being used?

  • # of (active) UwER who use the API.
  • %of (active) UwER who use the API.

Please note: w will need to check API data availability for calculating this.

  • Task code for metrics
  • Snapshot exported
  • Superset Dashboard (please ensure it is a shared one with other promotional editing work)

By When (Timing & Priority)

Provide a clear deadline, any key milestones (e.g. launch, leadership review), and note if timing is flexible or fixed.

Originally was a tentative 30.09.2026, updated to 31.10.2026


Information below this point is filled out by the analyst.

Sub Tasks

A breakdown of the steps to complete this task.

Data Snapshot Creation
  • Define metric(s) to be derived from the new / updated data pipeline
  • Define output table columns with stakeholder(s)
  • Create process diagrams in query documentation to map out complex flows
  • Write job queries or code
  • Test job queries or code
  • Export data snaphsot / add to wmde hdfs
  • Create Superset dashboard
Finishing Up
  • Required documentation is written
  • The task is moved to Delivered with the stakeholder being assigned and CCed in a comment

Data

The tables that will be referenced in this task and the sample sizes from them that will be used.

  • tbc

Event Timeline

Note from our review planning: This task is prioritized with T435805.

karapayneWMDE set the point value for this task to 8.