Page MenuHomePhabricator

Add an edit tag parameter and tag the edits made via data bridge with "Data Bridge"
Closed, ResolvedPublic8 Estimated Story Points

Description

As a recent changes patroller on Wikidata I want to see which edits were made with the Wikidata Bridge in order to more easily identify problems with the tool or particular client templates.

All the edits made via Wikidata bridge will be tagged with the tag "Data Bridge".

Example:
edit with several tags

BDD
GIVEN a template is Wikidata Bridge enabled
WHEN an edit is made
THEN an edit tag is added to it on the repository

AC

  • All edits made via the Wikidata Bridge are tagged with an edit tag

Background

Event Timeline

darthmon_wmde renamed this task from Tag edits made via data bridge to Tag the edits made via data bridge.Jul 30 2019, 11:17 AM
darthmon_wmde renamed this task from Tag the edits made via data bridge to Tag the edits made via data bridge with "Data Bridge".
darthmon_wmde renamed this task from Tag the edits made via data bridge with "Data Bridge" to Add an edit tag parameter and tag the edits made via data bridge with "Data Bridge".Jul 30 2019, 11:25 AM
darthmon_wmde updated the task description. (Show Details)

openrefine seems to use versioned tags - that's something I could see us doing.
Also the question of adding the source client was quickly discussed in story writing.

TODO: verify how much there is left to do once T226999: Save Wikidata edit when submitting client edit modal is completed...

As of T230336, ForeignApiWritingRepository supports a tags parameter, but it’s not initialized in createServices:

services.setWritingEntityRepository( new ForeignApiWritingRepository(
	new mwWindow.mw.ForeignApi(
		`${repoConfig.url}${repoConfig.scriptPath}/api.php`,
	),
	mwWindow.mw.config.get( 'wgUserName' ),
	// TODO tags from some config
) );

So as I see it, the following things are left to do:

  • create a (server-side) config setting in Wikibase Client for the tag(s)
  • embed that config variable in the browser-side code
  • use it (browser-side) to initialize the WritingEntityRepository
  • configure it in beta / production

Agreed, thanks! We can copy these to become (sub)tasks of the story once it is picked.
We might want to revise the existing estimation a bit, I think.

This should be working now on Beta, as far as I can tell, but I don’t think it can be tested until T230329: Use header component & save button is done.