Page MenuHomePhabricator

Identify options and workflows for filtering RC logs coming from wikidata (😾)
Closed, ResolvedPublic

Description

Users:
All users that may look at wikidata edits (they don't need to already have it turned on)

Acceptance criteria

  • Filter shows up on RC and WL pages
  • Pick the option

There are examples of disjoint and subsample use of filters. I.e. newcommer and registered is a subsample example. However, bot and human are disjoint filters. We should decide if one of them has any benefit over the other.

  • Option 1 (disjoint)
    • Wikidata content changes (i.e. label, description, alias etc.)
    • Sitelink changes in your language [being able to add a language array in preferences?] [SW note: in 'current wiki language' would be clear and much easier to implement than adding array in preferences]
    • Sitelink changes in other languages
  • Option 2 (disjoint)
    • Wikidata content changes (i.e. label, description, alias etc.) and sitelink changes in your language
    • Sitelink changes in other languages
  • 🟩Option 3 (One is a Subset of the other) 🟩- Recommended option, since it is most future proof (opens doors to other unnecessary notifications being excluded) [Popular wikidata edits, All wikidata edits]
    • "Popular" Wikidata edits (refined) [label, description, alias and maybe sitelinks]
    • All Wikidata edits [you get everything] / note that this has sub-parent situation
  • Option 4: (disjoint)
    • Wikidata
    • language links. Combining all language links makes this option simpler than the others for users to understand

Background info on the different categories here:

  • LL: This is the broad category of all language links including all of the below: will not be useful for most users. The breakdown of this is:
    • LL to the language wikipedia you are on: could potentially be useful, unknown
    • LL to the other languages you know as a person: could potentially be useful, unknown + much more complex to implement filter for this
    • Other LL: this is likely to be low usefulness for all users. It is also the largest category of LL
  • All other wikidata changes
  • Decide the filter based on the options. Some ideas:
    • Make another filter group with WD changes. (this is risky because the filters in the same group are mutually exclusive ansd we possibly should thake WD change out from its current group)

image.png (1,476×532 px, 71 KB)

  • If we will keep the current group, we can go with option 2 and add one more "Type of change" for sitelinks in other languages.

image.png (1,438×928 px, 155 KB)

  • Decide if the sitelink for other languages will be off by default - this was decided when discussing the options here to be default off, as it has the highest positive user impact towards "reducing low value notification"

Filter logic table

Example logic table showing how Option 3 would perform filtering. "Y" means the log is visible. Assumes that we will drop non-relevant wikidata changes by default:

active filtersnon-Wikidata changeEU-matching changeLL change for this wikiLL change for another wiki
☐ popular Wikidata edits ☐ all wikidata editsYYYN
☑️ popular Wikidata edits ☐ all wikidata editsNYYN
☐ popular Wikidata edits ☑️ all wikidata editsNYYY
☑️ popular Wikidata edits ☑️ all wikidata editsNYYY

Details

Other Assignee
awight

Event Timeline

Note that the split is not mutually-exclusive, eg. a change could be to site links as well as labels. It is probably rare but we should think about how to support this.

seanleong-WMDE renamed this task from 🧹Add a filter for RC logs coming from wikidata to 🧹Add a filter for RC logs coming from wikidata (😾).Aug 31 2026, 5:33 AM
awight renamed this task from 🧹Add a filter for RC logs coming from wikidata (😾) to 🧹Identify options and workflows for filtering RC logs coming from wikidata (😾).Sep 1 2026, 8:13 AM
SuzanneWood-WMDE renamed this task from 🧹Identify options and workflows for filtering RC logs coming from wikidata (😾) to Identify options and workflows for filtering RC logs coming from wikidata (😾).Sep 3 2026, 11:29 AM

Vi: proposes a sketching session for ideating solutions; begin the prototyping journey.
Adam: (Do we shortlist or finalise a solution and focus on this ideal solution, or broadly sketch different solutions? - logic table)
Danny; At what stage of this process will we present to community for buy-in/validation?

  • Logic table
  • Decide on main idea/solution
  • Sketching (identify interactions, user journey)
  • next?

This is parked for now as we decide whether to instead start with
"Stop sending LL notifications for other langauge wikis"
without filtering, and gather community feedback on that to inform any filtering decisions