Page MenuHomePhabricator

Support ORES for propagated Wikidata edits
Open, NormalPublic

Description

ORES supports Wikidata. You can enable it on wikidata.org and use it on e.g. Special:RecentChanges.

The ORES extension doesn't currently handle these edits on the client-side (e.g. when viewing Wikidata changes relevant to English Wikipedia in Wikipedia RC page).

However, it could (apparently schema changes are required though). It would be useful for the normal reasons ORES and the propagation feature itself are useful (track vandalism, good-faith, etc. to Wikidata content related to the current wiki)

Event Timeline

Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Mattflaschen-WMF renamed this task from Support ORES for propogated Wikidata edits to Support ORES for propagated Wikidata edits.Feb 14 2017, 12:53 AM
Mattflaschen-WMF edited projects, added MediaWiki-extensions-ORES; removed ORES.

As much as I'd like to do this, "we" (you may not have been there) absolutely decided to put it back to next quarter. I know because I spent quite a bit of time taking all the mentions of Wikidata out of the error messages (when we thought the change would be in Q3) and then putting them all back in (when we decided to put it off). So you need to talk to @Catrope about why we did that.

There are a couple issues with this that make it more complicated than I thought:

  1. The Wikidata revision ID is only in rc_params, so it's not joinable. It's also in wb_changes, but that doesn't have the rc_id or anything allowing joining to recentchanges AFAICT.
  2. The ORES tables are per-wiki, so we wouldn't be able to join recentchanges from this DB to the wikidatawiki ORES table.

We could potentially solve 1 by one of:
1a. Putting the real Wikidata revision ID into rc_this_oldid. Not sure if this is a good idea. This is an ID from a totally different wiki in a column that expects one from the current wiki, but you can distinguish based on rc_type.
1b. Adding rc_id to wb_changes.

We could potentially solve 2 by one of:
2a. Fully centralizing the relevant ORES tables, with a 'wiki' column name, then mirroring them everywhere.
2b. Mirroring just the Wikidata ones to the client wikis.

Hmm, if only we had support for ORES scores for non-revision objects (like log entries or RC rows), then this'd be much easier.

Lydia_Pintscher moved this task from incoming to monitoring on the Wikidata board.Jun 11 2017, 6:29 PM

@jmatazzoni There's nothing inherently blocking it, but if this is (potentially) a priority, we should have an architecture discussion. The best solution is not obvious, though @Catrope's approach is worth considering.

Mattflaschen-WMF updated the task description. (Show Details)
Restricted Application added a project: Growth-Team. · View Herald TranscriptFeb 26 2019, 8:41 AM
Harej triaged this task as Normal priority.Apr 3 2019, 5:08 AM