Thank you very much!

On a similar note, we also have some properties whose value is expected to be the subject entity id:

• https://www.wikidata.org/wiki/Property:P6482
• https://www.wikidata.org/wiki/Property:P6413

That's great! Is there a list of the supported external ids?

Is this the same thing as T223803?

@LucasWerkmeister has allocated a machine for that. There are a number of changes that we would like to make to OpenRefine in order to make it more suitable to be hosted online (such as connecting to Wikidata by OAuth). None of them should be blocking for a proof of concept though (especially since you will probably not use Wikidata editing from OpenRefine in the scope of Mortar).

We have some tutorials for OpenRefine and Wikidata, although not targeted for Commons users

• https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine/Editing/Tutorials/Basic_editing
• https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine/Editing/Tutorials/Video
• WikiCite 2018 tutorial session: https://www.youtube.com/watch?v=xORXSkE0yCE
• Demo at WikidataCon 2017: https://www.youtube.com/watch?v=kIpPZyZp1kI
• Screencast about reconciliation in OpenRefine: https://www.youtube.com/playlist?list=PL_0jeq3PjvtADzbovAgHNzOFvOlyF6uL1

Ah nevermind there is already a link, I just did not look on the right-hand side.

The EditGroups external tool now has documentation for developers, explaining the current infrastructure: https://editgroups.readthedocs.io/en/latest/architecture.html.
I would be happy to expand on the points that are unclear or missing.

Thank you so much @Lucas_Werkmeister_WMDE for working on this!

Thanks all for your patience for this! Excited to see my first commit making it into Wikibase \o/

Thanks for the ping! I am not using wb_terms in any of my projects. Good luck with the migration, it looks epic.

Let me spell out my use case in more detail then.

Ok great! I'll move the field to the end and try to make Jenkins happy then.

Sure, it also makes sense to add full text URLs.

@Lydia_Pintscher we would need your thoughts about this.

This is nice! However, when visualizing properties by category, it seems that subclasses are not taken into account: only the properties bearing that exact category as P31 value are listed. This gives a pretty inaccurate view: it is crucial to respect this hierarchy, just like the prop-explorer tool does:
https://tools.wmflabs.org/prop-explorer/

I agree with @Nicolastorzec above.

@Smalyshev okay! Sorry if this is not the right place: I would be happy to migrate the patch to another ticket. Indeed the patch only adds entity-level metadata, not dump-level metadata. I think this would be less of a breaking change, given that it does not require changing the dump structure (and of course it is more useful to me, haha!)

I think Wikidata-Toolkit could be used for that:
https://github.com/Wikidata/Wikidata-Toolkit/blob/master/wdtk-rdf/src/main/java/org/wikidata/wdtk/rdf/RdfSerializer.java
Obviously it would mean making sure the RDF serialization produced by it is consistent with what is being fed in WDQS at the moment.

I am wondering what is the status of this: is more discussion needed about what version information to include, or are we simply waiting for a patch?

Concerning the dumps, it should be possible to add versioning information on a per-entity basis, for instance by adding the revision id in the JSON serialization of the entity, as is currently done in Special:EntityData. This would arguably be more useful than a per-dump versioning, given that the dump generation process is not atomic. It would also be less of a breaking change: it would just amount to make JSON serialization of entities more uniform. This is debated in T87283.

Just confirming that the bug has occurred today again and the proposed fix worked perfectly. Thanks again!

Woaw, thanks for the very thorough analysis! I cannot reproduce this anymore. Thanks for the GOMAXPROCS trick! I will add it to the docs.

@Lydia_Pintscher Sure! I have just deployed a demonstration of this use case on EditGroups.

I would also be interested in this, spcifically for Wikidata where the diff structure could be exploited even further as suggested by @Yair_rand.

If you need a mapping from ISO language codes to Wikimedia ones, Wikidata-Toolkit has such a mapping: https://github.com/Wikidata/Wikidata-Toolkit/blob/3e62f93b137c25961c5a12172c7f213a720ecb67/wdtk-datamodel/src/main/java/org/wikidata/wdtk/datamodel/interfaces/WikimediaLanguageCodes.java

What exactly would you do with this information? i.e. what's the actual use case that makes you file this request?

What is the protocol to go forward on this? Should we hold a RFC on-wiki to let people choose among the possible solutions above?

We have this problem in https://dissem.in/ . This project is set up on Translatewiki, the code is hosted on GitHub and uses Travis for CI. We use Django's localization system which is based on gettext. We compile messages in the CI to check that they are valid. Sometimes translators add incorrect translations (such as translations not reusing the same variables as the msgid, or in a different format). This breaks our build as any incorrect translation will stop the entire compilation process. It is not clear if and how it would be possible to configure the translation compilation process to ignore invalid messages.

Any help with finishing the migration is welcome of course, I am currently busy with dissemin but I will try to come back to this at some point.

@Samwalton9 yes that is due to me starting the migration… and not completing it yet!

I have updated the Wikibase data model docs, which incorrectly mentioned precisions of hours, minutes and seconds. I assume that they were there because they were part of an earlier design?

Useful solution from Nikki: add in your common.css:

I have pinged a few interface admins on wiki to enable this.

Oh can they? Sorry I had no idea! Thanks, I will try to enable it myself.

I currently use my own custom hacky script to create properties, but having something stable and usable by anyone would be highly beneficial.

@Lucas_Werkmeister_WMDE thank you very much for that!

I have taken the liberty to remove "Cloud Services" as a subscriber to this ticket as I do not think every toollabs user wants to receive notifications about this.

As explained in T164152 I am happy to mentor anyone for this.

@Daniel_Mietchen regarding https://twitter.com/EvoMRI/status/1055785761574813696 (I do not read Twitter notifications - but happily interact on open platforms such as Mastodon):

The search interface can also be used for that thanks to the haswbstatement command. That only gets you one id per query, so it might not be suited for all tools. I don't know if the lag is lower in this interface.
Retrieving items by identifiers is quite crucial in many tools so it would be useful to have a solid interface for that instead of relying on SPARQL (which feels indeed like using a sledgehammer to crack a nut).

@Gehel my service has been quite unstable for some time, but I haven't found the time yet to find out exactly where the problem is coming from - it could be SPARQL, the Wikidata API, redis or the webservice itself. I will add a few more metrics to understand what is going on and report back here.

@Criscod yes that would be a great idea.