Page MenuHomePhabricator

Make “Commons link” constraint configurable
Open, LowestPublic


Currently, CommonsLinkChecker always checks the commonswiki database (except, as a special case, when running the tests). If it doesn’t exist, you get a nasty error. We should support:

  1. configuring a different database name, e. g. the current wiki’s database, and
  2. configuring an API endpoint instead, for non-Wikimedia wikis that also want to reference Wikimedia Commons.

Event Timeline

thiemowmde triaged this task as Lowest priority.Jul 4 2017, 7:27 AM
thiemowmde added subscribers: Lydia_Pintscher, Jonas.
Esc3300 added a subscriber: Esc3300.

It would be good to do away with these string properties.

What do you mean? The commons link constraint is also used (and useful) on “Commons media file” properties.

Is it really needed? I don't think one can add a non-existing file name (not that I tried).

Geoshapes have a special datatype that limits the namespace.

You can’t add it, but that doesn’t help you if the file is later moved or deleted. The constraint also checks if the value is well-formed (forbids certain variation that Wikibase accepts).

Edit: And anyways, this is completely besides the point of this issue. Please open a new task for removing the constraint type if you want to propose that.

Well, it's a factor when trying to determine the priority of this.

Change 501492 had a related patch set uploaded (by Noa wmde; owner: Noa wmde):
[mediawiki/extensions/WikibaseQualityConstraints@master] Make CommonsLinkChecker use the Commons API to asses if page exists

Change 501492 merged by jenkins-bot:
[mediawiki/extensions/WikibaseQualityConstraints@master] Make CommonsLinkChecker use the Commons API to assess if page exists