FYI please see also T177539, "Provide an RDF mapping for external identifiers with third party URIs"

Thank you, @Ramsey-WMF, that makes sense.

In T91928#3555132, @EddieGP wrote:

In T91928#1382241, @Pigsonthewing wrote:

Reopened, as this is not about Flickr2Commons (despite the edit someone made to the title), which was mentioned only as one example of the issue.

In T175827#3615526, @Ramsey-WMF wrote:

This should be addressed as part of future work on "structured licenses" for the Structured Data on Commons project.

Example of error message (since fixed):

In T147199#3508328, @MaxSem wrote:

If a corporation is insane enough to still run XP and force their users to run IE, we can only hope that yet another site they can't use will be the final straw forcing them to do something.

This is orthogonal to the property proposal cited (which I submitted).

Users which cannot move off of the underlying Windows XP operating system can install the latest Firefox easily

Although this is marked "closed", no such headers are currently in the source of, for example:

Who said this was /only/ about Flickr2Commons?

en.Wikipedia import seems to be working now, thank you.

Please add en.Wikipedia; I have several template imports waiting for this.

Maybe we could also combine domains; e.g. http://www.biodiversitylibrary.org and http://biodiversitylibrary.org are really equivalent to each other; as are http://books.google.com and http://books.google.co.uk

While we wait for James' grant proposal to succeed, any chance of updating this as a one-off please?

While we wait for James' grant proposal to succeed, any chance of updating this as a one-off please?

To repeat my reply to your post on Wikidata's 'Project chat' page:

Waiting for more information on tool used.

In T169641#3412486, @debt wrote:

In T169641#3407564, @CKoerner_WMF wrote:

Is this specific to advanced search or Special:Search in general?

@Lucas_Werkmeister_WMDE then we need to fork this ticket for constraint violation reports of the kind I linked to.

did you notice this problem on any particular item which had a “single value” violation, or was it more of a general concern?

Given that this is fundamentally possible, I think we can close this task?

It seems that:

{{DISPLAYTITLE:''<span lang="fr>L'esprit de l'escalier</span>''}}

In T166491#3345659, @Smalyshev wrote:

Also discussed in: https://www.wikidata.org/wiki/Wikidata:Project_chat/Archive/2017/05#Query_service_URLs

...and likewise for categories

In T138371#2794282, @abian wrote:

In T162378#3241478, @Cyberpower678 wrote:

I'm going to need the page to get bot approvals going.

At your next event, as soon as possible, ideally one at least week beforehand, you can open a task on Phabricator for that (we need outgoing IPv4/IPv6).

See also T157897

Or the upload tool(s) could just resolve the short URL to the full one. Or issue a "shall I convert URLs, or abort" warning.

Removing the Firefox add-on fixed this for me.

Original report at:

See also this property proposal:

This is a response (but not is mutually exclusive) to the property proposal I made at:

Relevant "oldid" URLs:

region:GB

(for example) causes a set of links to GB specific maps to be at the top of the GeoHack page.

What if the creator is none of these? For example, a non notable individual who puts images on their own website, with a CC licence?

Has anyone considered the alternative of having a "creator type" property, qualified by one of the three kinds of ID discussed above?

The "account creator" right (which I hold, for en.WP) does not do the same thing.

It would be handy if an item's URL - e.g. https://www.wikidata.org/wiki/Q123 - could also be parsed.

In T112378#1633919, @Rjwilmsi wrote:

Needs to be clearly stated on https://en.wikipedia.org/wiki/Template:Authority_control

This seems to have been done without the consensus of the editing (and image uploading) community. Please restore the import of time from EXIF, ASAP. Even if it is wrong, such data is useful for sequencing sets of images correctly, where image names do not facilitate this (perhaps Task T109589 is related?) It has always been editable.

Please credit me with some intelligence. This has nothing to do with "deployment to WMF sites". The proposed solution /when deployed/ will not not resolve the issue described.

Reopened - this is not resolved by "throttleoverride", according to https://lists.wikimedia.org/pipermail/wikimedia-l/2015-June/078309.html

Edit conflict as I modified my last comment; sorry Bene ;-)

Thank you for the notification. Having looked at the examples produced by the query shown above, I am concerned that removing some my impact usability for people editing or adding to Wikidata manually.

Are we planning a party for this bug's *sixth* birthday?

In T97566#1265567, @Lydia_Pintscher wrote:

either way we need to have a discussion in the community to agree that "anything in brackets can be stripped" is ok

How would "throttleoveride" be of use to event organisers, trainers, Wikimedians in Residence, etc, who are not sysops?

This would be very useful; and in training sessions run in-house by Wikimedians in Residence, too. I've had a lot of valuable training-time wasted dealing with the issues described.