- Wikibase Community User Group - lists.wikimedia.org

New extension: Wikibase EDTF
by Jeroen De Dauw 21 Apr '21

21 Apr '21

Dear Wikibase community, You can now use the Extended Date/Time Format inside of your own Wikibase! Announcement post: https://wikibase.consulting/wikibase-edtf/ Demo video: https://www.youtube.com/watch?v=U5ndjtuDPf8 Wikibase EDTF was developed by Professional.Wiki for the Luxembourg Ministry of Culture. Many thanks to the Ministry for funding the work and supporting the open source community. Best -- Jeroen De Dauw | Technical Director Professional.Wiki <https://www.Professional.Wiki> We are MediaWiki, Wikibase and Semantic MediaWiki experts. Professional.Wiki - Jeroen De Dauw & Karsten Hoffmeyer GbR Tieckstraße 24-25, 10115 Berlin | +49 (30) 55 87 42 65 | USt-IdNr. DE322440293

1 0

Re: [Wikibase] [Wikidata-tech] Sunsetting Wikibase 1.35 Docker Images
by Mohammed Sadat Abdulai 14 Apr '21

14 Apr '21

Hello Thad, Thanks for your question; we haven’t precisely defined the exact rules we’ll be using to tag docker images published in the future. For now, we just wanted to make it clear that there are no guarantees that they will stay the same forever. For example, we may want to reuse the ‘1.35’ tag to refer to a different image in the future; and that image might, for example, require different ENV variables to be set or not than the current image. Also, thanks for the link. It’s been read by members of the development team. The feedback from them was that the anticipated “tagging” strategy is more likely to follow a “Unique Tagging” approach as described in that blog post. This is because the main goal of these images is to provide 3rd parties with images they could go ahead and use right away rather than use as a base for building future images from. However, we haven’t quite finalized the details of the release strategy. The main goal is to provide tested services in both docker, and non-docker form that are compatible with one another. Are you using the existing images in FROM statements to build your own custom images? If so we’d be interested in hearing about the alterations you’re making and your use case. Cheers, On Tue, Apr 13, 2021 at 5:22 PM Thad Guidry <thadguidry(a)gmail.com> wrote: > Hi Mohammed & Wikibase Tech team, > > Going forward it sounds like the team has decided to adopt the practice > (not debating best or otherwise, but here only a practice that has been > choosen) of "stable tags" also known as "tagging a servicing release". > > https://stevelasker.blog/2018/03/01/docker-tagging-best-practices-for-taggi… > > I.E. 1.36 is a hypothetical stable tag (a service release). Some small > bugs need to be fixed, and are non-breaking changes. The team pushes an > updated 1.36 service release (the tag remains the same, but the image has > been updated and incorporates the small fixes). A company or service that > uses 1.36 tag can expect not to have to update their FROM line in a > Dockerfile (hopefully) since the expectation is that 1.36 is considered > "stable". > > Is that the practice or strategy that the teams have decided to do going > forward? > > Thad > https://www.linkedin.com/in/thadguidry/ > https://calendly.com/thadguidry/ > > > On Tue, Apr 13, 2021 at 9:58 AM Mohammed Sadat Abdulai < > mohammed.sadat(a)wikimedia.de> wrote: > >> 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. >> _______________________________________________ >> Wikidata-tech mailing list >> Wikidata-tech(a)lists.wikimedia.org >> https://lists.wikimedia.org/mailman/listinfo/wikidata-tech >> > _______________________________________________ > Wikidata-tech mailing list > Wikidata-tech(a)lists.wikimedia.org > https://lists.wikimedia.org/mailman/listinfo/wikidata-tech > -- 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

Upcoming Wikibase Live Session—March 25th, 2021
by Mohammed Sadat Abdulai 23 Mar '21

23 Mar '21

Hi everyone, We have our next Wikibase Live Session on Thursday, March 25th at 1600 UTC (Convert local time <https://zonestamp.toolforge.org/1616688029>). This month we will have team members from Enslaved.org talk to us about how they are using Linked Open Data (LOD) with the help of Wikibase. Everyone is welcome to attend the call. Details about how to participate are below (Add to calendar <https://calendar.google.com/event?action=TEMPLATE&tmeid=MXNkODJuM2ZxbjViOWp…> ): Time: 16:00 UTC, 1 hour, Thursday 25th March 2021 Google Meet: https://meet.google.com/nky-nwdx-tuf Join by phone: https://meet.google.com/tel/nky-nwdx-tuf?pin=4267848269474&hs=1 Notes: https://etherpad.wikimedia.org/p/WBUG_,March_2021 If you have any questions, please do not hesitate to ask. Hope to talk to you soon! -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de

1 1

Message regarding OpenRefine
by Lozana Rossenova 23 Mar '21

23 Mar '21

Dear all, I am sending this message on behalf of fellow Wikimedian Sandra Fauconnier, who is sadly not able to join the Wikibase mailing list due to some bottleneck issue with the manager of the list (I hope this can be solved soon, as it affects everyone here). In any case see message below, it's regarding a new application to Wikimedia for grant support to OpenRefine to develop extensions for media files and structured data. This would of course benefit Wikibase users who plan to use media files like images, etc, and not just data, in their data sets, so I think it's relevant to share here, too. See full details below. Many thanks, Lozana -------------------------------- Hello everyone, Since 2019, it is possible to add structured data to files on Wikimedia Commons [1] (SDC = Structured Data on Commons). But there are no very advanced and user-friendly tools yet to edit the structured data of very large and very diverse batches of files on Commons. And there is no batch upload tool yet that supports SDC. The OpenRefine [2] community wants to fill this gap: in the upcoming year, we would like to build brand new features in the open source OpenRefine tool, allowing batch editing and batch uploading SDC :-) As these are major new functionalities in OpenRefine, we have applied for a Project Grant [3]. Your feedback [4] and (if you support this plan) endorsements are very welcome. Thanks in advance, and many greetings, Sandra (User:Spinster / User:SFauconnier) as member of the OpenRefine steering committee Antonin (User:Pintoch) as OpenRefine developer [1] https://commons.wikimedia.org/wiki/Commons:Structured_data [2] https://www.wikidata.org/wiki/Wikidata:Tools/OpenRefine [3]https://meta.wikimedia.org/wiki/Grants:Project/Structured_Data_on_Wikimed… [4]https://meta.wikimedia.org/wiki/Grants_talk:Project/Structured_Data_on_Wi… -- Lozana Rossenova PhD Researcher in Digital Archives Curation London South Bank University / Rhizome centreforthestudyof.net <http://www.centreforthestudyof.net/> / rhizome.org

1 0

Upcoming Wikibase Live Session—February 11th, 2021
by Mohammed Sadat Abdulai 07 Feb '21

07 Feb '21

Hi everyone, We have our next Wikibase Live Session on Thursday, February 11th at 1600 UTC (Convert local time <https://zonestamp.toolforge.org/1613059230>). This month we will have a team member from Enslaved.org talk to us briefly about how they are using Linked Open Data (LOD) with the help of Wikibase. Everyone is welcome to attend the call and share-out about their project or what they have been working on recently around Wikibase. Details about how to participate are below (Add to calendar <https://calendar.google.com/event?action=TEMPLATE&tmeid=MXNkODJuM2ZxbjViOWp…> ): Time: 16:00 UTC, 1 hour, Thursday 11th February 2021 Google Meet: https://meet.google.com/nky-nwdx-tuf Join by phone: https://meet.google.com/tel/nky-nwdx-tuf?pin=4267848269474&hs=1 Notes: https://etherpad.wikimedia.org/p/WBUG_February_2021 If you have any questions, please do not hesitate to ask. Hope to talk to you soon! -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de

1 0

New development roadmap for Wikidata and Wikibase for 2021
by Mohammed Sadat Abdulai 04 Feb '21

04 Feb '21

Hi everyone, I’m excited to announce the new roadmap of the Wikidata development team for Wikidata and Wikibase for the year 2021! In 2021 we will continue developments to increase data quality and trust in Wikidata. Among the initiatives are to find more ways for people to find biases and gaps in the data and compare Wikidata’s data against other databases to find mismatches. We will also finish up the work from last year on a visual query builder to simplify querying. We will be releasing the first version of the new REST API to make it easier for 3rd-party developers to build applications using data from Wikidata. We will also work on making interface improvements for lexicographical data to make it more usable and attractive for contributors. On the Wikibase side of things, we will officially release the lightweight, first version of Wikidata-Wikibase Federation that allows accessing remote Wikidata properties in a custom Wikibase instance. We will then develop and release an enhanced version of this feature after incorporating feedback from users. We will also: 1. Implement a new release strategy and infrastructure for Wikibase packages and create user documentation for the Wikibase Docker update process 2. Investigate how to give Wikibase admins the option to change certain configuration options through a UI without directly editing localsettings.php. 3. Develop a web service for users to instantly create a temporary Wikibase sandbox so they can quickly and easily evaluate if the software is a fit for their project. 4. Continue to collaborate with OPEN!NEXT <https://opennext.eu/> to provide support for partners including set up of Wikibase instances, data modelling, maintenance, and API development. The most up-to-date versions of the roadmap can be found here: - Wikidata <https://eu-rm.roadmunk.com/publish/f247f2e06ee338c9997893bd1f9a696fbf2a40ed> - Wikibase <https://eu-rm.roadmunk.com/publish/695c6bc0060b5a1a0b4a74131acd35137db8b97a> You can click on the different items to see further information, like a description or planned start date. In addition, we’re also presenting status updates <https://www.wikidata.org/wiki/Wikidata:Development_plan/archive2020/status_…> on what was achieved for each of the 2020 goals. Please note that the roadmap only presents the main projects that the development team will work on during 2021. Critical and ongoing tasks (e.g. maintenance of the software and fixing pressing bugs) are not mentioned in the roadmap, but will be included in the workflow over the year. The roadmap is based on estimations and will evolve during the year. The roadmap does not contain events we are attending or organizing. If you have any questions or feedback, feel free to add them on this talk page <https://www.wikidata.org/wiki/Wikidata_talk:Development_plan>. Cheers, -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de

3 2

creating new items in Wikibase with a supplied ID
by Erik Paulson 29 Jan '21

29 Jan '21

Hello - Sorry for the crosspost/repeat - I sent a version of this to the wikidata mailing list, but it was right in the peak of the holidays. This list is probably more appropriate for it and hopefully by now the wikibase developers are back from their holidays and all caught up on email/year end/new year tasks, and can help provide some guidance. The tl;dr version of this post: On a blank Wikibase instance, I want to be able to do: api.php?action=wbeditentity&*new=item&id=Q42*&data={"labels":{"en":{"language":"en","value":"Douglas Adams"}}} I do not want to do this on wikidata.org - I understand why it makes no sense in that context. But I would like to be able to do this on my own Wikibase instance. Beyond the whimsical like ensuring Doug Adams gets to be Q42, the main reason for this is data portability and identifier stability. As more hosted Wikibase providers come online and start offering services, I want to know that I have data portability if I need to change to a different provider. Anyone who queries my Wikibase needs to know the identifiers my Wikibase uses for instances and more importantly for classes, and if I change providers, those identifiers cannot change without breaking those queries. I do not think that MySQL backups are a reliable way to be able to transition between providers. I am not confident that all providers will want to offer a service where they accept a MySQL backup to load into their Wikibase backend, and there are additional challenges moving between Wikibase versions. (Though some may - I programmatically create the contents of my Wikibase so I don't care about edit history, but if one were to care about that history and other things like wikiusers I imagine the MySQL dumps would be the preferred way to migrate?) One possible solution is to simply create blank items in a new Wikibase, from 1 to the maximum identifier used in my old wikibase, and then repopulate each item with the claims from my old Wikibase instance. Unfortunately this is not a reliable solution because while Wikibase guarantees that item IDs will not be reused, it does not guarantee that every ID in the sequence will be created, e.g. in rare cases Wikibase may go from Q41 to Q43 and skip/never create Q42. I don't mind that the identifier needs to be prefixed with a 'Q' or a 'P' for a particular type, I just want to be able to set the same identifier if I set up a new wikibase instance. I think Wikibase is awesome, but it is an odd database that does not allow you to set the keys for the data you are managing :) In reading through the Wikibase Repo code, it seems like this scenario was considered though perhaps isn't fully implemented (or has been disabled?). The code in EntitySavingHelper.php looks like there are/were ways to call it by providing an ID while still asking for a new entity, though there is logic earlier in the ModifyEntity code to look for and explicitly reject the case where the API asks for 'new' and also provides an ID, so I'm not sure how this code path would get called. There is also code to ask the entityStores if they 'canCreateWithCustomId', but those all appear to just return 'false'? However, if that logic was skipped in the API handler and a bit of code reworked in ModifyEntity and EntitySavingHelper, along with ensuring that that the next available ID is kept up to date in the wb_id_counters table to always be 1 beyond the maximum ID in use, it looks like it might not be that hard to enable creating entities with specific IDs? So three questions: Would the Wikibase development team ever be open to supporting something like this, behind a flag like $wgWBRepoSettings['allowUserProvidedIds'] that defaulted to false? Are there more complicated implications from allowing a change like this that would need to be considered? I understand why the Wikidata.org repo needs this codepath fast and can't allow users to provide IDs for new entities anyway, but are there other reasons this isn't supported beyond "Wikidata doesn't need it?" Is this all moot with the eventual REST API? I see that there's a PUT envisioned, could I use that to directly create an item or property and give it an ID then, or does the ID have to already exist to replace it? I am happy to try to tackle creating a patch for this, but I'd like to get some feedback if there's any big lurking issues that I should know about before starting on the work - I'd rather not get deep into it only to find out it will never work or never be accepted. I'm also happy to shift this to phabricator if that's more appropriate. Thank you all for your work on Wikibase! Thanks, -Erik

4 4

wikibase-docker does not start anymore
by Jesper Zedlitz 06 Jan '21

06 Jan '21

Hi everyone, the Wikibase docker installation https://github.com/wmde/wikibase-docker does not start anymore error free. Since there is no issue list for the Github repository I try my luck with the mailing list. The problem occurs related to Elasticsearch and CirrusSearch: wikibase_1 | Validating my_wiki_general alias...alias is free...corrected wikibase_1 | Validating my_wiki alias...alias not already assigned to this index...corrected wikibase_1 | Updating tracking indexes... wikibase_1 | Unexpected Elasticsearch failure. wikibase_1 | Elasticsearch failed in an unexpected way. This is always a bug in CirrusSearch. wikibase_1 | Error type: Elastica\Exception\Bulk\ResponseException wikibase_1 | Message: unknown: Error in one or more bulk request actions: wikibase_1 | wikibase_1 | index: /mw_cirrus_metastore_first/mw_cirrus_metastore/version-my_wiki_content caused blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; wikibase_1 | index: /mw_cirrus_metastore_first/mw_cirrus_metastore/version-my_wiki_general caused blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; wikibase_1 | index: /mw_cirrus_metastore_first/mw_cirrus_metastore/version-my_wiki_archive caused blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; wikibase_1 | wikibase_1 | Trace: wikibase_1 | #0 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Bulk.php(359): Elastica\Bulk->_processResponse(Object(Elastica\Response)) wikibase_1 | #1 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Client.php(361): Elastica\Bulk->send() wikibase_1 | #2 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Index.php(182): Elastica\Client->addDocuments(Array, Array) wikibase_1 | #3 /var/www/html/extensions/Elastica/vendor/ruflin/elastica/lib/Elastica/Type.php(202): Elastica\Index->addDocuments(Array, Array) wikibase_1 | #4 /var/www/html/extensions/CirrusSearch/includes/MetaStore/MetaVersionStore.php(70): Elastica\Type->addDocuments(Array) wikibase_1 | #5 /var/www/html/extensions/CirrusSearch/maintenance/metastore.php(133): CirrusSearch\MetaStore\MetaVersionStore->updateAll('my_wiki') wikibase_1 | #6 /var/www/html/extensions/CirrusSearch/maintenance/metastore.php(95): CirrusSearch\Maintenance\Metastore->updateIndexVersion('my_wiki') wikibase_1 | #7 /var/www/html/extensions/CirrusSearch/maintenance/updateOneSearchIndexConfig.php(301): CirrusSearch\Maintenance\Metastore->execute() wikibase_1 | #8 /var/www/html/extensions/CirrusSearch/maintenance/updateOneSearchIndexConfig.php(270): CirrusSearch\Maintenance\UpdateOneSearchIndexConfig->updateVersions() wikibase_1 | #9 /var/www/html/extensions/CirrusSearch/maintenance/updateSearchIndexConfig.php(61): CirrusSearch\Maintenance\UpdateOneSearchIndexConfig->execute() wikibase_1 | #10 /var/www/html/maintenance/doMaintenance.php(99): CirrusSearch\Maintenance\UpdateSearchIndexConfig->execute() wikibase_1 | #11 /var/www/html/extensions/CirrusSearch/maintenance/updateSearchIndexConfig.php(70): require_once('/var/www/html/m...') wikibase_1 | #12 {main} I have tried version 1.34 as well as 1.35 - always the same problem. The error occurs only the first time you start Wikibase. Unfortunately, automatic tests always fail due to this error. Best wishes Jesper

2 1

Upcoming Wikibase Live Session—December 17th, 2020
by Mohammed Sadat Abdulai 14 Dec '20

14 Dec '20

Hi everyone, Our next Wikibase Live Session is Thursday, December 17th at 1600 UTC (time converter <https://www.timeanddate.com/worldclock/converter.html?iso=20201217T160000&p…> ). We will have a few people share out about their project in the first half of the call and then continue our conversation from the last session about what will be a better platform for community discussions. Everyone is welcome to attend the call. Details about how to participate are below (Add to calendar <https://calendar.google.com/event?action=TEMPLATE&tmeid=NnM5bWhxYTA5cmg1czM…> ): Time: 16:00 UTC, 1 hour, Thursday 17th December 2020 Google Meet: https://meet.google.com/nky-nwdx-tuf Join by phone: https://meet.google.com/tel/nky-nwdx-tuf?pin=4267848269474&hs=1 Notes: https://etherpad.wikimedia.org/p/WBUG_December_2020 If you have any questions, please do not hesitate to ask. Hope to talk to you soon! -- Mohammed Sadat *Community Communications Manager for Wikidata/Wikibase* Wikimedia Deutschland e.V. Tempelhofer Ufer 23-24 10963 Berlin www.wikimedia.de

1 0

Looking for tutorials on Entity Schema creation.
by Troy, Joseph M 20 Nov '20

20 Nov '20

Greetings Wikibase community from Urbana, IL, USA I have installed wikiba.se docker on a virtual machine, and now I’m looking for user guides or tutorials on how to use the software to create items and Entities. I especially want to know how to use “Shape Expressions Code” on the Entity Schema creation page. So if anyone can recommend any guide or tutorial for someone very new to wikibase usage, that would be wonderful. Thank you. JOSEPH M TROY Web Applications Developer / Architect, PhD Candidate in Informatics University of Illinois at Urbana-Champaign Library Administration 424 Main Library, UIUC | M/C 522 Urbana, IL 61801 217.300.0456 | jmtroy2(a)illinois.edu<mailto:jmtroy2@illinois.edu> www.library.illinois.edu<http://www.library.illinois.edu> [/var/folders/98/g5_f7ykx4gv81_xk4rpw64xx51wn9r/T/com.microsoft.Outlook/WebArchiveCopyPasteTempFiles/signature_logo.png]<http://illinois.edu/> Under the Illinois Freedom of Information Act any written communication to or from university employees regarding university business is a public record and may be subject to public disclosure.

1 0

2024

2023

2022

2021

2020

2019

2018

Wikibase Community User Group