Wikidata-tech

wikidata-tech@lists.wikimedia.org

2 participants
623 discussions

Open tech position
by Rossenova, Lozana 26 Aug '21

26 Aug '21

Dear all, [Apologies for cross-posting] I'm posting here because there is an open devOps position at the Open Science Lab in TIB Hannover where I work, and it might be of interest to people on this list. >> https://www.tib.eu/en/tib/careers-and-apprenticeships/vacancies/details/ job-advertisement-no-62-2021 <https://www.tib.eu/en/tib/careers-and-apprenticeships/vacancies/details /job-advertisement-no-62-2021> We are looking for someone with experience in OSS / Mediawiki / Wikibase software (ideally) hence I'm posting here. Please feel free to spread the word if you know anyone who might be interested and feel free to reach out to me directly at lozana.rossenova(a)tib.eu <mailto:lozana.rossenova@tib.eu> if you have any questions and want to learn more. The position is in Germany, but remote work is also possible. Cheers, Lozana Rossenova -- Research Associate Open Science Lab

1 0

[Breaking change] Languages of entity stubs in RDF output
by Mohammed Sadat Abdulai 24 Aug '21

24 Aug '21

This breaking change is relevant for anyone who consumes Wikidata RDF data through Special:EntityData (rather than the dumps) without using the “dump” flavor. When an Item references other entities (e.g. the statement P31:Q5), the non-dump (?flavor=dump) RDF output of that Item would include the labels and descriptions of the referenced entities (e.g. P31 and Q5) in all languages. That bloats the output drastically and causes performance issues. See Special:EntityData/Q1337.rdf <https://www.wikidata.org/wiki/Special:EntityData/Q1337.rdf> as an example. We will change this so that for referenced entities, only labels and descriptions in the request language (set e.g. via ?uselang=) and its fallback languages are included in the response. For the main entity being requested, labels, descriptions and aliases are still included in all languages available, of course. If you don’t actually need this “stub” data of referenced entities at all, and are only interested in data about the main entity being requested, we encourage you to use the “dump” flavor instead (include flavor=dump in the URL parameters). In that case, this change will not affect you at all, since the dump flavor includes no stub data, regardless of language. This change is currently available for testing at test.wikidata.org. It will be deployed on Wikidata on August 23rd. You are welcome to give us general feedback by leaving a comment in this ticket <https://phabricator.wikimedia.org/T285795>. If you have any questions please do not hesitate to ask. Cheers, -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

2 1

Cirrus Search on Wikidata
by Thad Guidry 22 Aug '21

22 Aug '21

I thought that "," comma was being added to the Elasticsearch token filter as a stopword and excluded from simple search now? Or did I miss something? [image: image.png] Or NO and U+002C comma was decided against being added, and we must use the Advanced Search on Wikidata or the API ? I noticed that the string "foot locker inc" will not show the entity in the dropdown, but only "foot locker, inc." ? (I've since added the full legal name into the alias to improve searchability, but still would like to know the stopword decision) Thad https://www.linkedin.com/in/thadguidry/ https://calendly.com/thadguidry/

3 5

[Breaking change] Wikidata forms without statements use empty JSON array instead of empty JSON object
by Mohammed Sadat Abdulai 27 May '21

27 May '21

Hi everyone, This change is relevant for everyone who uses the JSON serialization of Lexeme, Form or Sense entities. Currently, when a Lexeme Form or Sense has no statements stored, it is rendered as an empty array [] in JSON. (Example < https://www.wikidata.org/w/api.php?action=wbgetentities&format=json&ids=L38…>). We want to serialize it as an empty object {} instead. This change will ease the deserialization process and bring more consistency in our code as nonempty statements are already serialized as objects, not arrays. The impact of this change will be in the output of wbgetentities and editing APIs, as well as Special:EntityData and the Lexeme JSON dumps. If you’re maintaining tools that use lexicographical data, you may want to check your code to make sure that it reflects this change, e.g. lexeme forms or senses with no statements are properly deserialized by your tool. This change is available for testing at test.wikidata.org before deployment to www.wikidata.org. You are welcome to give us general feedback by leaving a comment in this ticket <https://phabricator.wikimedia.org/T241422>. If you have any questions please do not hesitate to ask. Cheers, -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

The Wikibase Spring Release is now available!
by Mohammed Sadat Abdulai 07 May '21

07 May '21

We hereby announce that the Wikibase Spring Release has been published <https://releases.wikimedia.org/wikibase/1.35/>. Here are links to important documentation related to the release: - The full release notes <https://gerrit.wikimedia.org/r/plugins/gitiles/mediawiki/extensions/Wikibas…> - Installation instructions <https://www.mediawiki.org/wiki/Wikibase/Suite> (manual installation) - Installation instructions <https://www.mediawiki.org/wiki/Wikibase/Docker> (Docker) - Updating your Wikibase <https://github.com/wmde/wikibase-release-pipeline/blob/main/docs/topics/upg…> (Docker) As previously mentioned, this new release is compatible with MediaWiki 1.35 and contains new Wikibase features: - Federated Properties <https://doc.wikimedia.org/Wikibase/master/php/md_docs_components_repo-feder…> : a feature that allows a newly created Wikibase instance to use the existing Properties of Wikidata or another Wikibase. Please note that this feature has some limitations: once you’ve enabled federation mode, you can no longer create local properties. We recommend not enabling it in Wikibase instances that already contain properties. - WikibaseManifest <https://www.mediawiki.org/wiki/Extension:WikibaseManifest>: the new release is compatible with this extension made by Wikimedia Deutschland which exposes automatically discovered configuration information about your local Wikibase for use by external tools. - Wikibase Pingback: <https://doc.wikimedia.org/Wikibase/master/php/md_docs_topics_pingback.html> a feature that allows Wikibase operators to opt in to sharing anonymized data about their Wikibase instance with Wikimedia. This completely optional feature helps us to understand the usage of Wikibase by collecting which versions of MediaWiki are in use, on what platforms, and which Wikibase features and extensions are enabled. The Pingback Privacy Statement <https://www.mediawiki.org/wiki/WMDE_Engineering/Wikibase/Pingback_Privacy_S…>contains the full disclosure about what information is being collected. We would also like to highlight that the new and improved Docker images now contain even more useful components <https://hub.docker.com/u/wikibase>, such as extensions that were requested for inclusion by the community. If you have any questions, please don’t hesitate to ask. Cheers, -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

The Wikibase Spring Release will be published on/before May 15th
by Mohammed Sadat Abdulai 30 Apr '21

30 Apr '21

Hello, This is to announce that we are in the final days of preparing the Wikibase Spring Release. We anticipate publishing the new release on or before May 15, 2021. An official release announcement will be made on the day we publish. The upcoming tarball and Docker releases will be compatible with MediaWiki 1.35 and will contain a two new Wikibase features: - Federated Properties <https://doc.wikimedia.org/Wikibase/master/php/md_docs_components_repo-feder…> : a feature that allows a newly created Wikibase instance to use the existing Properties of Wikidata or another Wikibase. Please note that this feature has some limitations, namely that you cannot use local properties once you’ve enabled federation mode. - WikibaseManifest <https://www.mediawiki.org/wiki/Extension:WikibaseManifest>: the new release is compatible with Wikimedia Deutschland’s extension that exposes automatically discovered configuration information about your local Wikibase for use by external tools. We would also like to highlight that the new-and-improved Docker images will now contain even more useful components <https://phabricator.wikimedia.org/T266779>, such as extensions that were requested for inclusion by the community. Finally, the release announcement will provide the location of detailed release notes, improved Wikibase installation documentation, instructions for upgrading your Wikibase to the new version, and instructions for enabling/configuring new features. If you have any questions please do not hesitate to ask. Cheers, -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

How to increase character lenght of a String Property
by Claudio Prandoni 20 Apr '21

20 Apr '21

Hello and nice to meet you! I have a (hopefully) simple question ... In my MediaWiki / Wikibase instance [1] I have a set of Properties whose data type is String, which are used to store the translations of the text of epigraphs, see eg. [2]. These fields appear to have a length limit of 400 characters. Is there any way to increase that limit? Thank you very much! Claudio [1] https://wiki.eagle-network.eu/ [2] https://wiki.eagle-network.eu/wiki/Item:Q9529 -- Questa email è stata esaminata alla ricerca di virus da AVG. http://www.avg.com

2 4

Sunsetting Wikibase 1.35 Docker Images
by Mohammed Sadat Abdulai 14 Apr '21

14 Apr '21

Hello, This is to announce that the existing Wikibase Docker images will be sunset and that the most recently released Docker 1.35 images are the last versions that we will publish from the wikibase-docker github repository <https://github.com/wmde/wikibase-docker>. If for some reason you need them, these previous Docker images will remain available for a period of approximately 6 months, officially sunsetting on September 30, 2021. Please note that tags for these docker images have always been, and remain, mutable. This means if you want to be sure that you’re getting the same image you should specify the exact image hash. This is a result of the ongoing “Release Strategy and Infrastructure” initiative which will culminate in a Spring release with new 1.35 Docker images which should be used going forward. We will make another announcement shortly with the exact date of this new release and all relevant information. If you have any questions please do not hesitate to let us know. Cheers, -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now <https://www.wikimedia.de/newsletter/>. Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland – Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

2 3

Is updater script really updating the set of properties?
by Victor Agroskin 10 Feb '21

10 Feb '21

Dear colleagues, I'm running a custom instance of Wikibase with SPARQL service and I'd noticed that updater service (runUpdate.sh) doesn't really update triplestore with new properties created in my Wikibase instance. As well as I can see, newly created P-item names aren't even returned by API call for "recentchanges". So new properties with their names and other attributes never appear in the triplestore after their creation. Once the property is used in some statement or qualifier, corresponding triples are put into the triplestore immediately, but the property remains without names or descriptions. Is it because properties are managed centrally in Wikidata? Is it assumed that I should reload a full snapshot each time I create a new property? Or is it some bug on my side? Thank you for your help! Victor Agroskin

2 3

BREAKING / SIGNIFICANT CHANGE: wbeditentity response to use standard JSON serialization
by Lucas Werkmeister 08 Feb '21

08 Feb '21

Hi folks! This is an announcement for a change to the response of the wbeditentity API module, which is a breaking change for MediaInfo entities (Structured Data on Commons), a significant change for Lexeme entities (lexicographical data), a minor change for Property entities, and a no-op for Item entities. The wbeditentity API module, which can be used to edit any part of a Wikibase Entity, has long included a part of the edited data in its response. However, this response data was incomplete: it included e.g. Labels, Statements, Sitelinks, but not the datatype of a Property or the Lemmas of a Lexeme. Additionally, Statements were always returned under the key "claims", even though MediaInfo entities generally use the key "statements". On or around February 10, we will deploy a code change that will make wbeditentity return the entity data using the standard serialization format of an entity type, the same that is used by wbgetentities and Special:EntityData. This means that the response will now contain all the parts of an Entity, and also that, for MediaInfo entities, the Statements will now be returned under "statements". (These Statements will also be missing the "datatype", just like the MediaInfo data from wbgetentities and Special:EntityData – see T246809 <https://phabricator.wikimedia.org/T246809>.) To avoid breaking MediaInfo API users immediately, we are temporarily adding Statements under the key "claims" as well – that is, the change on February 10 is only significant, not yet breaking, and MediaInfo API users can use either the "claims" or the "statements". On or around March 3, we will remove this compatibility code, and MediaInfo API users will have to use "statements" if they want to look at the Statements of the returned entity data. It’s also worth mentioning here what the wbeditentity response data represents. The API returns the Entity data as edited by your API request, and the revision ID of the page that the change was saved under. This is *not* necessarily the Entity data of that revision ID: if Wikibase patched any edit conflicts between the base revision ID that your request specified (baserevid parameter) and the actual latest revision ID, then those changes are not included in the response. For example, if you load an Item with revision ID *X* and labels “a” and “b” in different languages, and make a wbeditentity request with baserevid=*X* to change the label “a” to “A”, but in the meantime someone else had already changed the label “b” to “B” and saved this as revision *Y*, then the API response for your request will have a last revision ID ("lastrevid") of *Z*, and this revision *Z* will have labels “A” and “B” if you get it from Special:EntityData, but the API response for your request will have labels “A” and “b” (the result of applying your edit to the base revision). If you need the actual latest Entity data after your edit, make a separate request to Special:EntityData or wbgetentities. (This is nothing new, and unaffected by the change being announced here, but we thought it was still worth mentioning.) If you have any issue or question, feel free to leave a comment at T271105 <https://phabricator.wikimedia.org/T271105>. Cheers, Lucas -- Lucas Werkmeister (he/er) Full Stack Developer Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30 219 158 26-0 https://wikimedia.de Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207.

1 0

← Newer
1
2
3
4
5
6
7
8
...
63
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

Wikidata-tech