User talk:Daniel Mietchen/Archive/2022

From Wikidata
Jump to navigation Jump to search

Wikidata weekly summary #501

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • The next Wikidata+Wikibase office hours will take place on Wednesday, January 19th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group.
      • SPARQL queries live on Twitch and in French by Vigneron, January 4 at 19:00 CEST
    • Ongoing:
    • Past:
      • Wikibase live session (December 2021) - log
  • Tool of the week
    • Wikidata's Q item explorer: Show claims where the item is the subject of the statement but doesn't show statements where the item is the target value.
  • Development
    • Due to the winter holidays, no development has happened for Wikidata in the last two weeks.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #502

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • OneZoom "tree of life explorer" is an interactive map of the evolutionary links between all living things known to science using Wikidata.
  • Development
    • Getting the Wikidata:Mismatch Finder ready for release. Focusing on adding statistics.
    • Fixed an issue where statement editing was broken in some older browser (phab:T298001)
    • Made it so that grammatical features on a Form of a Lexeme can be ordered consistently across all Lexemes (phab:T232557)
    • Working on an issue where changes from Wikidata don't get sent to the other wikis for the initial adding of the sitelink to an Item (phab:T233520)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

  • Looking back at 2021
    • Developments rolled out in 2021:
      • New updater for the Wikidata Query Service to help it keep up with the large number of edits on Wikidata
      • Query Builder to make it easier for people to create SPARQL queries without having to know SPARQL
      • Item Quality Evaluator to make it easy to find the highest and lowest quality Items in a topic area
      • Constraints Violations Checker is a small command-line tool that gives constraint violation statistics for a set of Items to make it easier to find the Items that need more work
      • Curious Facts finds anomalies in the data in Wikidata and offers them up for review and amusement
      • Wikidata Map to see the distribution of Wikidata's Items across the world and the connections between them
      • Current Events to make it easy to see what's currently a hot topic in the world and being edited a lot on Wikidata
    • New entities in 2021:

missing authors in paper Q27349821

Hello Daniel, I am writing you since you are the creator of https://www.wikidata.org/wiki/Q27349821, but I guess many others. If you look at the "author" property of the entry you can see that all the authors surnames starts by A,B or C. In fact many are missing (e.g. myself). Do you know why? I guess this kind of entries are imported automatically, so I guess there is a bug somewhere. --Wiso (talk) 12:52, 5 January 2022 (UTC)

@Wiso: Thanks for checking. I tried to fix this but at that scale, our usual author curation workflows tend to break down. So for now, we have the author (P50) information in Measurement of the Higgs boson mass from the H → γ γ and H → Z Z * → 4 ℓ channels in p p collisions at center-of-mass energies of 7 and 8 TeV with the ATLAS detector (Q27349821) and the author name string (P2093) information in Q110449462, and merging them did not work (more details here and here). While we are in touch, I would like to have a chat with you about what the best way would be to handle such cases with thousands of authors and how to leverage information from places like INSPIRE-HEP (Q5972440) for author disambiguation. Would you have time for that over the weekend? --Daniel Mietchen (talk) 23:45, 6 January 2022 (UTC)
Hello @Daniel Mietchen, thanks for the reply. If I have understood correctly Q27349821 and Q110449462 are duplicated, created when trying to move from author name string to author. I guess author is more correct. I am not expert of wikidata, for example no idea how to merge items. I have worked with INSPIRE-HEP api in the past, with some python scripts, it is not complicated. I would say that the main one to resolve author disambiguation is with the orchid-id, which is available by inspire-hep. Chatting is extremely complicated, impossible in the week end. Is there any way to create entries in a sandbox in wikidata? I can try to write a script to import papers from my experiment (ATLAS). Wiso (talk) 14:22, 7 January 2022 (UTC)
@Wiso Just curious: did you write any parts of the paper? (I don't ask which ones) How do the deceased authors contribute? There was some discussion with Daniel at MediaWiki_talk:Gadget-Merge.js#What_to_do_in_case_of_EntityContentTooBigException?. --- Jura 15:08, 7 January 2022 (UTC)
Yes, I am an author. The author list for each paper is frozen at a certain point of the analysis, very close to its release. All the qualified ATLAS authors are included, plus special request (e.g. new student who are not author but who worked on the analysis, ...). Then the document is realeased on arxiv and at the same time it is submitted to the journal. The iteration with the journal take some time (few months). After the iteration, if the paper is accepted by the journal, it is published by the journal. "Deceased authors" are the ones who died between then creation of the author list (so they contributed to the paper) and the publication on the journal. Wiso (talk) 08:59, 11 January 2022 (UTC)

Wikidata weekly summary #503

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: MSGJ (RfP scheduled to end after 20 January 2022 17:45 UTC)
  • Development
    • Fixed an issue where making changes with sitelinks were not fully dispatched to the clients (phab:T233520)
    • Mismatch Finder: Improved the texts in the tool to be more understandable after testing
    • Mismatch Finder: added a way to get statistics about all the reviews that have been done in the tool and what is still awaiting review
    • Special:NewLexeme: kicked off the development work to improve the page in order to make it more understandable

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #504

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship: MSGJ (Successful). Welcome onboard \o/
  • Tool of the week
    • Comparator compare the list of cited entities across two different wikipedia articles using Wikidata and SPARQL
  • Development
    • Enabling usage tracking specifically for statements on Waray, Armenian and Cebuano Wikipedias (phab:T296383, phab:T296382, phab:T296384)
    • Implementing basic version of mul language code and deploying it to Test Wikidata (phab:T297393)
    • Preparing an event centered on reusing Wikidata's data
    • Mismatch Finder: Been in touch with people who can potentially provide the first mismatches to load into the new tool for the launch. Finalized the statistics part.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #505

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Basque version of Wordle using Wikidata's lexicographic data. Check it out!
  • Other Noteworthy Stuff
    • WDQS scaling update for Jan 2022 available here. We will be trying to do monthly updates starting this month.
  • Development
    • Continuing work on adding the mul language code for labels, descriptions and aliases. (phab:T297393)
    • Enabled statement usage tracking for Cebuano, Armenian and Warai Warai to ensure fine-grained notifications about edits on Wikidata on those Wikipedias (phab:T296383, phab:T296382, phab:T296384)
    • Continuing work on fixing a bug where Wikidata changes do not get sent to Wikipedia and co for the first sitelink adding leading to missing information in the page_props table (phab:T233520)
    • Continuing work on making sure the Wikidata search box works with the new Vector skin improvements (phab:T296202)
    • Mismatch Finder: Debugging some issues with the first files we got with mismatches that we can load into the Mismatch Finder


You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #506

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • The Data Reuse Days will bring together Wikidata editors and data reusers on March 14-24 - we're currently building the schedule. Join us and discover many cool projects!
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Andy Mabbett on the "Cite Q" template that uses data from Wikidata in Wikipedia citations and Crystal Clements on setting the framework for a future discussion on addressing ethical concerns surrounding representation of gender for living persons in Wikidata, February 8th. Agenda
      • Wikidata Query Service scaling: You can join 2 calls and provide feedback at the 2 WDQS scaling community meetings on Thursday, 17 Feb 2022 18:00 UTC, and Monday 21 Feb 2022 18:00 UTC. Full details here.
      • Live on Twitch and in French about Academic bibliographical data and Scholia by Vigneron and Jsamwrites, February 8 at 19:00 CET (UTC+1)
      • LIVE Wikidata editing #70 - YouTube, Facebook, February 12 at 19:00 UTC
      • Online Wikidata meetup in Swedish #95, February 13 at 13.00 UTC
    • Ongoing:
    • Past:
  • Tool of the week
  • Other Noteworthy Stuff
    • January 1st as date
    • Wikidata has 2,540,891 items for people with both date of birth and date of death. There are 9 redirects for every 100 such items. (source). 2000 people share dates of birth and death with another person.
  • Development
    • Mismatch Finder: Tracking down one last issue with the upload of mismatch files. Once that is fixed we are ready to release the tool.
    • Lexicographical data: Started coding on the rewrite of Special:NewLexeme to make it easier to understand and use.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #507

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Other Noteworthy Stuff
  • Development
    • Continuing work on the basics of the new Special:NewLexeme page. Nothing to see yet though.
    • Fixed a bug where sitelinks where added for wikis that shouldn't get them. (phab:T301247)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #508

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Call for Mentors: Wiki Mentor Africa is a mentorship project for tool creators/contributors. Interested to become a mentor (experienced tool creators/contributors), please visit this page!
  • Development
    • We started coding on the Wikibase Rest API based on the proposal we published a while ago.
    • We are continuing to work on the new Special:NewLexeme page. The first input fields are in place but not pretty or usable yet.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #509

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Lexicographical data: work is continuing on the new Special:NewLexeme page. We are working on the basic input fields and permission handling.
    • Mismatch Finder: Released the tool and working through feedback now and getting additional mismatches from organizations using our data.
    • REST API: Starting to build the initial Wikibase REST API. We are starting with the endpoint to read Item data first.
    • Data Reuse Days: Continuing event preparation
    • Published new security release updates for Wikibase suite wmde.6 (1.35)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Item International Society for Therapeutic Ultrasound Conference 2016: Tel Aviv, Israel. 14-18 March, 2016. (Q50025596) author problems

Hi,

You and you bot created and edited International Society for Therapeutic Ultrasound Conference 2016: Tel Aviv, Israel. 14-18 March, 2016. (Q50025596) extensively. In author (P50) there seem to be several authors listed several times (Kullervo Hynynen X 3, Elisa E. Konofagou X 6, Nathan McDannold X 3, Natalia Vykhodtseva X2 , Hao-Li Liu X 2, Cyril Lafon X 6, Vera Khokhlova X 6 etc.). Could you check this issue? Thanks, DGtal (talk) 07:35, 27 February 2022 (UTC)

@DGtal: Thanks for checking. This actually appears to be correct in the sense that every author of a contribution (poster, oral etc.) to this conference is listed as an author of this publication, and if people like the ones you listed appear on multiple such contributions, they are listed multiple times at the source. I do not like this practice very much myself, but there are quite a few conference-related publications that use this style of authorship that can result in multiple occurrences of the same author on the same paper. --Daniel Mietchen (talk) 19:16, 6 March 2022 (UTC)
I think I understand. So the item doesn't really deal with a scholarly article (Q13442814) but rather is a Conference Summary that should ideally be split up into it's components? DGtal (talk) 07:48, 7 March 2022 (UTC)

Wikidata weekly summary #510

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot: EnvlhBot 3. Task/s: add dictionaries IDs to French lexemes
    • Closed request for permissions/Bot: IndoBot (Approved). Task/s: I would like to import all Indonesian schools, more than 100000. The data includes school type, location, and coordinates as well as external identifiers
  • Tool of the week
    • Wikxhibit is a tool that allows anyone, even non-programmers, to create cool presentations of Wikidata, and other sources of data on the web, only using HTML and without any additional programming. Are you interested in creating presentations of Wikidata? We would like to understand your experience with Wikidata to better improve our tool. It would help if you can fill out our survey https://mit.co1.qualtrics.com/jfe/form/SV_cvZKKlRu2S7C9Fk
  • Other Noteworthy Stuff
    • Wikidata dumps: Due to technical issues the JSON and RDF dumps for the week of March 1st couldn't be properly generated (phab:T300255#7746418). The situation is expected to get back to normal this week.
    • Item with QID 111,111,111 was created
    • Job openings:
      • The development team at WMDE is looking for a Senior Software Engineer to develop and improve the software behind the Wikidata project. Apply here!
      • The WMF Search Platform team is looking for someone to maintain and develop Wikidata Query Service. Apply here!
      • Natural History Museum, Berlin (Q233098) is looking for someone for project- and data management especially for Wikidata related stuff about the museums collections Job Description (German)
  • Development
    • Data Reuse Days: Preparing for the upcoming Data Reuse Days. Join us! A lot of exciting sessions are coming together.
    • Lexicographical data: Continued work on the new Special:NewLexeme page. We are getting close to the point where it can create a Lexeme.
    • REST API: Continuing to work on the first endpoint to read Item data.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #511

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • WDQS outage on 06 March: users may have unexpectedly had requests blocked. Incident report here.
  • Development
    • Getting ready for Data Reuse Days
    • Mismatch Finder: Discussing the next batches of potential mismatches with MusicBrainz data and some remaining Freebase data
    • Lexicographical data: Continuing work on the basic version of the new Special:NewLexeme page, focusing on putting in the base data about the new Lexeme
    • REST API: Continuing coding on the basic version of the GET Item endpoint

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #512

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • PodcastBot. Task/s: Upload new podcast episodes, extract: title, part of the series, has quality (explicit episode), full work available at (mp3), production code, apple podcast episode id, spotify episode ID. Regex extraction: talk show guest, recording date (from description)
      • AradglBot. Task/s: Create between 100,000 and 200,000 new lexemes in Aragonese language Q8765
    • Closed request for permissions/Bot: EnvlhBot 3 (approved). Task/s: add dictionaries IDs to French lexemes
  • Tool of the week
    • Linked People project let's you explore the family trees of all known people at Wikipedia/Wikidata.
    • Gene of the Day (gene-wordle) uses Wikidata for gene names and crafting an answer list by number of sitelinks.
  • Development
    • Lexicographical data: We're continuing with the work on the new Special:NewLexeme page. We worked on saving a valid new Lexeme with the new page. We are now focusing on the suggesters for language and lexical category so editors can select the right Item for them.
    • Data Reuse Days: We ran sessions on how to use Wikidata's data programmatically and the best practices around it. Slides and videos are available already (see above).
    • REST API: Continuing coding on the basic version of the GET Item endpoint. We have the very initial version of the get item endpoint ready and are now adding more parameters to it.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #513

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Scribe is a keyboard extension based on lexicographical data that can help users remember grammar rules (see blogpost above).
    • WorldlEH is a wordle clone in Basque.
  • Development
    • [Significant Change]: wbsearchentities changed to explicitly return display terms and matched term
    • Lexicographical data: Working on the lookup for language and lexical category and displaying potential errors during Lexeme creation
    • Improved the API response of the wbsearchentities endpoint by adding the language to the labels and descriptions in the API response (phab:T104344)
    • Data Reuse Days: Second and final week - organized, attended and held a few sessions incl. bug triage hour and pink pony session
    • REST API: Continuing work on getting the the data of an Item, we almost have filtering of the data returned by the API and basic error handling is in place. Next up: not returning the data if the client already has the most recent data, and authentication

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Scholia use profiles

Hi Daniel! I hope you are well. Thanks for your recent comment about Jupyter notebook. Could you please tell me more about your work "improving the Scholia /use profiles"? The test case you mentioned looks amazing. -- Oa01 (talk) 08:06, 25 March 2022 (UTC)

@Oa01:, In essence, the underlying info stems from mining PubMed Central for mentions of Jupyter notebooks AND GitHub and then checking whether said notebooks can actually be found on GitHub. If that was the case, I tagged the paper as describing a project that uses Jupyter notebooks. For some other test cases, see the bottom panel at toolforge:scholia/P4510. --Daniel Mietchen (talk) 17:34, 1 April 2022 (UTC)
Thanks, Daniel. Very cool. Oa01 (talk) 19:33, 1 April 2022 (UTC)

Open Definition conformant license

Hi Daniel, this edit is incorrect. reference URL (P854) should never be used as a qualifier. Probably best to revert this batch. I wonder if instance of (P31) is really the right property to put open license (Q30939938) in. Is this really the identity of the item? I would move it to complies with (P5009) which is a dedicated property to store this kind of data. Multichill (talk) 15:24, 2 April 2022 (UTC)

@Multichill: Thanks for the check, the fix and the suggestion. I am aware that P854 is not to be used as a qualifier, but I was distracted when I set up the batch, so mistyped an S as a P. When I noticed that the batch had mixed up the reference and qualifier tagging, I triggered a batch revert immediately, but this has not finished, and I do not know how I would get it to finish. So I will check the remnants and fix as much as possible. I share your concern about the use of P31 for tagging "Open Definition conformant license" and agree that P5009 (of which I hadn't been aware) could play a role here, but the combination "complies with" "Open Definition conformant license" still seems odd. I would say that this particular license is compliant with the Open Definition, and the nature of this compliance has something to do with "Open Definition conformant license" but I am not sure yet what the best way to model this would be. Also, my reasoning here is for now just based on the English labels. Maybe it makes some more sense in some of the other languages, which I have not checked yet. --Daniel Mietchen (talk) 13:43, 3 April 2022 (UTC)
@Multichill: Turns out that DeltaBot has fixed the remaining cases. --Daniel Mietchen (talk) 15:26, 3 April 2022 (UTC)
@Multichill: In terms of how to model the compliance, what about this way? --Daniel Mietchen (talk) 15:31, 3 April 2022 (UTC)
That looks like a nice solution. Multichill (talk) 16:28, 3 April 2022 (UTC)

Wikidata weekly summary #514

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot: APSbot 4: Task/s: Regularly create organizations from the Research Organization Registry (ROR - https://ror.org/) that are missing in Wikidata.
  • Tool of the week
    • Kyrksok.se is an app about Swedish churches based on Wikidata.
    • QAnswer is a question answering system based on Wikidata and other projects. Who was the first to create liquid helium? Try it!
  • Development
    • Lexicographical data: Continued work on the new Special:NewLexeme page and focused on displaying sensible error messages if an error occurs during Lexeme creation. We're also working on adding a dropdown for the language variant.
    • REST API: Continued work on conditional requests and authorization
    • Made use of the new fields added in the wbsearchentities API and added language information to the markup of entity searches that you see when editing a statement or searching with the little searchbox at the top of the page on Wikidata. Now these search results should make a bit more sense to people who use screen readers.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #515

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • Glitter another R package to write SPARQL queries and query Wikidata and other SPARQL endpoints. This package provides a domain specific language to write queries directly from R.
    • Conzept is a topic-exploration tool based on Wikidata and other information sources.
  • Development
    • Lexicographical data: Continued work on the new Special:NewLexeme page. We worked on displaying error messages and inferring the spelling variant from the language. We also looked into the non-JavaScript version of the page.
    • REST API: Worked on conditional requests (do not return data the client already has) and authorization.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Oberholser

@Daniel Mietchen: there is a (Harry C. Oberholser (Q67349028)) and a Harry C. Oberholser (Harry C. Oberholser (Q39626)). Wonder if you could take a look at this. Thank you for your time. Lotje (talk) 11:16, 13 April 2022 (UTC)

@Lotje: Thanks for the ping. I merged these two items. --Daniel Mietchen (talk) 01:21, 16 April 2022 (UTC)

Wikidata weekly summary #516

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: Pi admin bot (RfP scheduled to end after 20 April 2022 17:58 UTC)
    • Closed request for adminship: Stang (successful)
    • New requests for permissions/Bot:
  • Tool of the week
    • Bird O'Clock! is a tool based on Wikidata and other data sources that shows pictures and numbers from actual people counting actual birds in the actual world!
    • Tiago's Coin Herbarium is a coin collection depicting different plant information displayed via Wikidata SPARQL queries.
  • Development
    • Lexicographical data: Worked on inferring the spelling variant from the language's Item on the new Special:NewLexeme page and started building a little help box on the special page to explain what lex. data is.
    • REST API: Getting closer to having a first version of the REST API that returns Item data.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #517

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for adminship:
    • New requests for permissions/Bot:
  • Tool of the week
    • Wikitaxa is a software of taxonomy data written in R.
    • User:So9q/fatcat-link.jsscrip is a userscript for looking up fatcat! DOIs. It adds a link to the fatcat! database in the Tools' section on items.
  • Development
    • Lexicographical data: Worked on showing the name of language variants in the language variant selector and added the new information box to help people get a better understanding of lex. data.
    • REST API: Finished the initial implementation of the endpoint for getting data for a full Item and discussed feedback, testing and roll-out plans.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #518

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • The new "mul" term language code is now available on Test Wikidata
    • Lexicographical data: We are finishing up the information box that should help new users understand quickly what lexicographical data is. We also added the help text to encourage people to check if the Lexeme already exists before creating one.
    • REST API: We started working on the REST routes to get all statements of an Item and retrieve a single statement from an Item.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #519

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Closed request for permissions/Bot:
      • PangolinBot. Task/s: Automatically replace one property value with another (Approved)
  • Development
    • REST API: We are continuing to implement the REST routes to get all statements of an Item and retrieve a single statement from an Item (phab:T305988, phab:T307087, phab:T307088)
    • Lexicographical data: We are finishing the version of the page for browsers without JavaScript support (phab:T298160). We started working on the feature to pre-fill the input fields by URL parameter (phab:T298154). And we started working on better suggestions for lexical categories so commonly-used ones can more easily be added to avoid mistakes (phab:T298150).
    • We fixed an issue with recently added new language codes not being usable for Lexemes and not being sorted correctly on Special:NewItem (phab:T277836).

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

quickstatements; temporary_batch_1633294882827

Hi Daniel! Can you please check to see what did go wrong with this batch? For example: [2] -- Meisam (talk) 07:41, 3 May 2022 (UTC)

Thanks for checking, Meisam, and for the ping. That batch made only a single edit, which was to create that page. This seems to be correct to me. However, I agree that the item would benefit from further annotation, so I added a bit more. Note that the item was originally created for author (P50) statements, the result of which you can explore, for instance, via their Scholia profile. --Daniel Mietchen (talk) 19:56, 5 May 2022 (UTC)
Thank you for taking care of it. I think for these type of items, having a claim like occupation:researcher or a similar thing would have helped a lot. Cheers! -- Meisam (talk) 09:33, 7 May 2022 (UTC)
@Meisam: I opted for occupation: author and did a few batches (example). --Daniel Mietchen (talk) 00:23, 11 May 2022 (UTC)

Wikidata weekly summary #520

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

author vs researcher

Hi Daniel,

I wonder if this is correct to add author (Q482980) for occupation (P106) for example Katarzyna Danis-Wlodarczyk (Q71100537). author (Q482980) is described as "author or intellectual author of a linguistic work". The reference for this claim is stated in (P248) and a scholarly article. Kpjas (talk) 08:20, 14 May 2022 (UTC)

@Kpjas: Thanks for sharing your thoughts about this. I am not sure either whether this is the way to go, but these edits were triggered by the discussion with @Meisam: above, whose opinion would be welcome here too. --Daniel Mietchen (talk) 20:05, 20 May 2022 (UTC)
@Sic19: used to add researcher (Q1650915) to this kind of items which I find it quite reasonable. -- Meisam (talk) 08:04, 22 May 2022 (UTC)

Wikidata weekly summary #521

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • 6 and 8 June: Scholia hackathon with focus on software-related visualizations and curation workflows
      • 29 July 2022: The submission deadline for the Wikidata Workshop 2022 that will be co-located with the 21st International Conference on Semantic Web (ISWC 2022).
    • Ongoing:
  • Tool of the week
    • LOD4Culture is a web application for exploring world-wide cultural heritage.
  • Other Noteworthy Stuff
    • UNLOCK, a Wikimedia Deutschland program, is looking for your project ideas. These could be the development of tools building on top of Wikidata's data, of applications for social and public good or related to civic tech. Apply until May 29th, 2022!
    • Job opening: Community Communications Manager - Wikibase at Wikimedia Deutschland.
  • Development
    • Wikibase REST API: Initial implementation of a route providing all statements of an item (phab:T305988), an a route to retrieve a single statement (phab:T307087) completed.
    • First batch of WBstack.com accounts successfully migrated to Wikibase.cloud. You can keep track of our progress on this phabricator ticket phab:T303852.
    • Lexicographical data: We updated the input placeholders on the new version of the NewLexeme special page (T302877, T307443). We finished the feature to prefill the inputs from URL parameters if present (T298154) and to suggest common lexical category items (T298150). We are working on some accessibility improvements (T303806, T290733, T305359) and improving validation / error messages (T305854).

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #522

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • Want to know more about Abstract Wikipedia & Wikifunctions? You can now subscribe to the weekly newsletter and get a friendly reminder every time a new issue is published!
    • Radioactivity map: Mind map about radioactive radiation built by importing from Wikidata with InfoRapid KnowledgeBase Builder
  • Development
    • Wikibase REST API: Expanding statement reading routes (a single statement specified by ID (phab:T307087), all statements of an item (phab:T305988), a single statement for a specific item (phab:T307088))
    • Fetch revision metadata and entity data separately in all use cases (phab:T307915, decision)
    • Update installation instructions in WikibaseLexeme.git readme file (phab:T306008)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #523

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development
    • Lexicographical data: We finished work on input validation and displaying errors for faulty input (phab:T305854) and are continuing work on accessibility improvements such as screen reader support and keyboard navigation (phab:T290733, phab:T30535).
    • REST API: We finished implementation of conditional statement requests (phab:T307031, phab:T307032) and published the OpenAPI specification document (still subject to change as the API develops). We started working on the write part of the API with adding statements to an Item (phab:T306667).

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

A new Abstract Wikipedia and Wikifunctions update is out

The new Abstract Wikipedia and Wikifunctions Update is out! Please, come and read it! In this issue: an essay from Denny, development updates.

Subscribe · Translate this message


--MediaWiki message delivery (talk) 13:35, 8 June 2022 (UTC)

Wikidata weekly summary #524

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call June 14, 2022: Will Kent (Wikidata Program Manager at Wiki Education) and Rosie Stephenson-Goodknight (Wikimedia Foundation Trustee; Visiting Scholar at Northeastern University; co-founder of Wiki Women in Red) will present on Leveraging Wikidata for Wikipedia – running a multi-language wiki project and the role of Wikidata in improving Wikipedia's content gender gap. Agenda
      • Live editing session on Twitch, in French, by Vigneron, June 14 at 19:00 CEST (UTC+2)
    • Ongoing
    • Past
  • Tool of the week
    • ExtraInterwiki. Some language links will never show up in your favorite Wikipedia, those who don’t have a corresponding article in this Wikipedia. This new tool aims to give them more visibility by searching topics closed to the one on an article with no article on your wiki.
  • Development
    • Fixed a bug where Item IDs where shown instead of the label after selecting an Item in an Item selector (phab:T306214)
    • Lexicographical data: finished accessibility improvement for the new Special:New Lexeme page (phab:T290733), improving error messages for the new page (phab:T310134) and worked on a new search profile to make selecting languages easier (phab:T307869)
    • REST API: continued work on creating statements (phab:T306667)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Lack of information

You've created Jennifer Couzin-Frankel (Q64692845) which is totally lacking information.--Lovehansa (talk) 09:39, 14 June 2022 (UTC)

@Lovehansa: Thanks for reviewing that item. I agree it could be expanded a lot (and I added a bit), but there is quite a bit of information in items linked to it, as can be explored via WhatLinksHere or via tools like Reasonator or Scholia. --Daniel Mietchen (talk) 01:21, 19 June 2022 (UTC)

Wikidata weekly summary #425

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Lexicographical data:
      • Enabled Lua access to Lexemes for all Wikimedia projects
      • Continued work on improving the language search for Lexeme languages on the new Special:NewLexeme page (phab:T307869)
      • Improving the accessibility of a design system component and the new Special:NewLexeme page (phab:T290733)
      • Making it easier to understand what to do when the spelling variant isn't available on the new Special:NewLexeme page (phab:T298146)
    • REST API: Continuing work on making it possible to add a statement to an Item

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #426

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • William Avery Bot 7. Task/s: Merge multiple references on the same claim citing Accademia delle Scienze di Torino.
  • Tool of the week
    • IsisCB Explore - is a research tool for the history of science whose books and subjects use imagery from Wikidata.
  • Other Noteworthy Stuff
    • Template Item documentation now includes a query to the corresponding lexemes. This is an attempt to make navigation between lexemes and items easier. For the record, Item documentation is available in the header of the talk page for each item.
  • Development
    • Lexicographical data: We are wrapping up the coding on the new Special:NewLexeme page. Testing and rolll-out will follow soon. We are still working on making it easier to find languages in the language selector on the Special:NewLexeme page. (phab:T307869)
    • REST API: We are continuing to code on the ability to create statements on an Item (phab:T306667)
    • Investigating an issue with labels not being shown after merges (phab:T309445)
    • Preparation for upcoming work: We are planning the next work on the Mismatch Finder to address feedback we have received so far as well as EntitySchemas to make them more integrated with other areas of Wikidata.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On June 10, an update regarding Wikifunctions usability tests has been published (the full report is also available).

On June 21, an update regarding manually-written articles in Abstract Wikipedia has been published (for how AW will deal with model articles, read the earlier update).

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 16:21, 30 June 2022 (UTC)

A new Abstract Wikipedia and Wikifunctions update is out

The new Abstract Wikipedia and Wikifunctions Update is out! Please, come and read it! In this issue: development updates, team updates.

Subscribe · Translate this message


--MediaWiki message delivery (talk) 16:38, 1 July 2022 (UTC)

A new Abstract Wikipedia and Wikifunctions update is out

The new Abstract Wikipedia and Wikifunctions Update is out! Please, come and read it! In this issue: development updates, team updates.

Subscribe · Translate this message


--MediaWiki message delivery (talk) 16:38, 1 July 2022 (UTC)

Wikidata weekly summary #522

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • ListedBuildingsUKBot. Task/s: Add wikidata site links to appropriate wiki commons category pages for listed buildings with matching ID numbers. I've identified about 1000 entities that can be updated. e.g. [3] should have a wiki commons link to [4] since they both refer to [5].
  • Development
    • Lexicographical data:
      • We have finished most of the development on the new Special:NewLexeme page. You can try it at https://wikidata.beta.wmflabs.org/wiki/Special:NewLexemeAlpha. We will make this available on Wikidata for testing with real-world data on July 14th.
      • We are continuing to work on the new search profile for languages to make setting the language of a new Lexeme easier (phab:T307869)
    • REST API: We are putting finishing touches on the first version of the API route to add statements to an Item. It is still lacking support for automated edit summaries.
    • We are working on word-level diffs to make it easier to see what changed in an edit (phab:T303317)
    • We are investigating the issue of labels not being shown after some merges (phab:T309445)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #528

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • The next Wikidata+Wikibase office hours will take place on Wednesday, July 27th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call July 12, 2022: Houcemeddine Turki will speak on "Enriching and Validating Wikidata from Large Bibliographic Databases." This call will be part of the 2022 LD4 Conference on Linked Data, “Linking Global Knowledge.” While you can attend the call directly via the links below without registering for the conference, we encourage everyone to check out the full conference program and all the excellent sessions on Sched at Agenda
      • 7/30 OpenStreetMap x Wikidata @ COSCUP 2022
      • 2022 LD4 Conference on Linked data. July 11th through July 15th, 2022
    • Ongoing
    • Past:
  • Development
    • Data Quality Days!
    • Making plans for improving EntitySchemas and integrate them more into editing and maintenance workflows
    • Implemented word-level diffs of labels, descriptions, aliases and sitelinks (phab:T303317)
    • Continuing the investigation about labels not being shown after some merges (phab:T309445)
    • Lexicographical data:
      • Continuing work on making it easier to pick the right language for a new Lexeme (phab:T298140)
      • Fixing a bug where `[object Object]` was shown in the gramatical feature field (phab:T239208)
      • Fixing a number of places where labels for redirected Items were not shown even though the redirect target had labels (phab:T305032)
    • REST API:
      • Finished the first version of the API route for creating statements on an Item (excluding autosummaries so far)
      • Started work on the API route for removing a statement from an Item

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On July 12, an update regarding the latest team and development news has been published.

On July 15, an essay regarding the potential of Abstract Wikipedia, written by Denny, has been published.

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 10:40, 17 July 2022 (UTC)

Wikidata weekly summary #529

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • The next Wikidata+Wikibase office hours will take place on Wednesday, July 27th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • Next Linked Data for Libraries Wikidata Working Hour July 18, 2022: Working with diverse children's book metadata. The second Wikidata Working Hour in the series will cover reconciliation in OpenRefine, so we can identify which authors from our spreadsheet of children's book metadata already exist and/or need to be created in Wikidata. You are, as always, welcome to bring your own data to work on. Event page
      • Assessing the Quality of Sources in Wikidata Across Languages - Wikimedia Research Showcase, Wednesday, July 20, at 9:30 AM PST/16:30 UTC
      • Mark your calendars for the Wikimania Hackathon! The free, online, public event will take place from 16- 22 UTC August 12 and 12-17 UTC August 13, and include a final showcase on August 14.
    • Ongoing
    • Past
  • Development
    • Lexicographical data:
    • REST API: Continued working on the API route to replace or remove a statement of an Item
    • We are making Wikibase resolve redirects when showing Item labels and descriptions in a lot more places; notably, this includes the wbsearchentities API. (phab:T312223)
    • Mismatch Finder: We are discussing options for how to improve its handling of dates, specifically calendar model and precision.
    • EntitySchemas: We are trying to figure out how to best technically go about implementing some of the most-needed features for version 2.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #530

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • The next Wikidata+Wikibase office hours will take place on Wednesday, July 27th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
      • [Small wiki toolkits] [Upcoming bots & scripts workshop. "How to maintain bots" is coming up on Friday, July 29th, 16:00 UTC
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call July 26, 2022: Clair Kronk, Crystal Clements, and Alex Jung will be providing an update to Wikidata/gender discussions from the February 8 call with a focus on pronouns. Clair will introduce us to LGBTdb, a Wikibase instance created for and by LGBTQIA+ people from which we draw insight in Wikidata-related discussions. We also hope to discuss current pain points and share action items for future collaboration. Input from community members who are familiar with lexicographical data would be greatly appreciated. Agenda
      • Wikimedia Indonesia Wikidata meetup. 1300 WIB, July 30, 2022.
    • Ongoing:
      • Weekly Lexemes Challenge #51, Plants
  • Tool of the week
    • User:Magnus Manske/referee.js - is a userscript that automatically checks external IDs and URLs of a Wikidata item as potential references, and adds them with a single click.
  • Development
    • Lexicographical data: We went over all the feedback we received for teh testing of the new Special:NewLexeme page and started addressing it and fixing the uncovered issues. One issue already fixed is a bug that prevented it from working on mobile view. (phab:T313116)
    • Mismatch Finder: investigated how we can make it work for mismatches in qualifiers instead of the main statement (phab:T313467)
    • REST API: Continued working on making it possible to replace and remove a statement of an Item
    • We enabled the profile parameter to the wbsearchentities API on Test Wikidata (phab:T307869)
    • We continued making Wikibase resolve redirects when showing Item labels and descriptions in more places (phab:T312223)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Research bot

Hi Daniel, Your research bot has recently marked (last 48 hours) on wikidata several Australian native plant taxa as invasive to Australia . Why is it doing this, and can you please halt it? Junglenut (talk) 11:17, 21 July 2022 (UTC)

@Junglenut: Thanks for your note. The bot has added invasive to (P5588) statements (example) based on entries in the database SInAS database of alien species occurrences (Q112339024), and the file "SInAS_AlienSpeciesDB_2.4.1.csv" in particular. Can you give some examples where you think these statements would be wrong? Like with any database, some entries are likely to be problematic, and I hope we can help address at least part of such problems. --Daniel Mietchen (talk) 11:47, 26 July 2022 (UTC)
The ones that I am aware of are Ptychosperma elegans, Ptychosperma macarthurii, Eupomatia laurina, Pseuderanthemum variabile, Angiopteris evecta, Ficus drupacea, Ficus platypoda, Toona ciliata, and Pipturus argenteus. All of these are valid Australian natives, and two of them are endemic.
There may be others as well, given that I'm not subscribed to every Australian taxon. But whatever the source your bot is using it seems fairly obvious that either the database itself or the data extraction is inaccurate, and the bot should be halted while the issue is sorted out. — Junglenut (talk) 11:58, 28 July 2022 (UTC)
Apologies - the list I gave you just now was a full list of the ones for which I received notifications about edits by the bot, but not necessarily marked as invasive to AU. Only the following were incorrectly edited by the bot: Eupomatia laurina, Pseuderanthemum variabile, Toona ciliata and Pipturus argenteus, I have removed those statements on the relevant pages, however there still exists the possibility of other taxons being incorrectly labelled. Junglenut (talk) 12:59, 28 July 2022 (UTC)
@Junglenut: Thanks for checking and for the fix. As just stated in the other thread above, I'm reviewing the workflows, but I think marking the problematic statements as deprecated is the best we can do for now. Thanks again for curating in this area. --Daniel Mietchen (talk) 12:11, 29 July 2022 (UTC)

Wikidata weekly summary #531

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Invasive to its native place?

Hi Daniel, your bot just added a bunch of invasive to (P5588) values to Dracaena draco (Q157952), including Canary Islands (Q5813). That can't be right - it's a native (and endangered) plant here, not an invasive one! Can you double-check please? Thanks. Mike Peel (talk) 06:08, 18 July 2022 (UTC)

Just to ping you again about this? Thanks. Mike Peel (talk) 14:56, 26 July 2022 (UTC)
Hi Mike, thanks for the note and the additional ping. I'll look into this and fix as needed. For background, see here. --Daniel Mietchen (talk) 01:24, 28 July 2022 (UTC)
@Mike Peel:. I am still checking the workflows, but in the meantime, I have marked this one as deprecated for now. Thanks again for the quality check. --Daniel Mietchen (talk) 12:08, 29 July 2022 (UTC)
Thanks! I see the bot has now removed the values - except for the deprecated one! So it now looks odder. :-) I've just removed the deprecated value, just mentioning this in case it would have happened elsewhere too. Thanks. Mike Peel (talk) 18:43, 5 August 2022 (UTC)

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On July 20, an update regarding the latest additions to the team has been published.

On July 29, an essay regarding long typed lists and how to deal with them, written by Denny, has been published.

On August 5, an essay regarding a proposed launch plan for Wikifunctions, written by Denny, has been published.

Enjoy the reading!

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 09:16, 5 August 2022 (UTC)

Wikidata weekly summary #532

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Wikimania 2022, August 11 to 14, online event. The Hackathon will take place August 12-14. On this page you can find a summary of sessions and community gatherings related to Wikidata and Wikibase.
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call August 9, 2022: Pieter Vander Vennet on MapComplete, a thematic OpenStreetMap viewer and editor which uses species, language, and image data from Wikidata. Agenda.
      • The Wikimania Hackathon starts next Friday, August 16-22! There are still lots of spots in the schedule to add your Wikidata related sessions or project ideas (anyone can present a session)
    • Ongoing
      • Wikimedia Indonesia's Wikidata edit-a-thon (datathon) for the 77th anniversary of the Indnesian Independence Day started on 5th August and will be held until 12th August. Participants are instructed to edit items containing the statement country of origin (P495): Indonesia (Q252).
      • Toolhub is a catalog of 1500+ tools used every day in a wide variety of workflows across many Wiki projects. We are currently improving the search functionality and need your input – whether you are already familiar with Toolhub or not. Please take 5-10 minutes to leave feedback.
    • Ongoing
      • Weekly Lexemes Challenge #53, Sheep
    • Past
      • First online meet-up fully organized by volunteers of the Indonesian Wikidata Community has been held on 30th July where we edited items on Indonesian ethnic groups.
  • Tool of the week
    • Wiki tools - adds dozens of Wikipedia and Wikidata functions to your Google sheets.
  • Development
    • Lexicographical data:
      • Continuing to address feedback from the testing (e.g. phab:T312292, phab:T313113, phab:T313466)
      • We have pushed back replacing Special:NewLexeme with the new Special:NewLexemeAlpha a bit to address more of the testing feedback.
    • Continuing to tackle allowing sitelinks to redirects under some circumstances (phab:T278962)
    • REST API:
      • Finishing up the endpoints for removing and replacing statements and adding authentication and authorization to them
      • Looking into feedback from first testing

You can see all open tickets related to Wikidata here. If you want to help out, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #533

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship:
      • Estopedist1 (RfP scheduled to end after 21 August 2022 12:36 UTC)
  • Events
    • Upcoming:
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour August 15, 2022: Fourth session of our summer/fall project working with diverse children's book metadata. We'll be covering manually creating publisher items: showing how to create items, add statements to items, add references, and use gadgets. You are, as always, welcome to bring your own data to work on. All sessions in our project series will be recorded for those who cannot attend. Links will be added to the event page when available. Event page
    • Ongoing:
  • Tool of the week
    • KnolCase is a case-based knowledge management tool for gathering information about subjects of interest and organizing these into case files.
  • Development
    • Took part in Wikimania and the Wikimania hackathon
    • Continuing work on making it possible to add sitelinks to redirects under some special conditions (phab:T278962)
    • Lexicographical data: continuing to address the feedback from testing
    • REST API:

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #534

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
    • List of created Wikidata items - a tool which combines Xtools pages created API with Wikidata API to get the list of items created by a user with their label.
  • Development
    • Lexicographical data: continuing to address feedback from testing. We are almost done now.
    • REST API: continued investigating the use of PATCH and JSON Patch and worked on a proof-of-concept
    • Birthday planning and prepping is in full swing

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Call for participation in the interview study with Wikidata editors

Dear Daniel Mietchen,

I hope you are doing good,

I am Kholoud, a researcher at King’s College London, and I work on a project as part of my PhD research that develops a personalized recommendation system to suggest Wikidata items for the editors based on their interests and preferences. I am collaborating on this project with Elena Simperl and Miaojing Shi.

I would love to talk with you to know about your current ways to choose the items you work on in Wikidata and understand the factors that might influence such a decision. Your cooperation will give us valuable insights into building a recommender system that can help improve your editing experience.

Participation is completely voluntary. You have the option to withdraw at any time. Your data will be processed under the terms of UK data protection law (including the UK General Data Protection Regulation (UK GDPR) and the Data Protection Act 2018). The information and data that you provide will remain confidential; it will only be stored on the password-protected computer of the researchers. We will use the results anonymized (?) to provide insights into the practices of the editors in item selection processes for editing and publish the results of the study to a research venue. If you decide to take part, we will ask you to sign a consent form, and you will be given a copy of this consent form to keep.

If you’re interested in participating and have 15-20 minutes to chat (I promise to keep the time!), please either contact me at kholoudsaa@gmail.com or use this form https://docs.google.com/forms/d/e/1FAIpQLSdmmFHaiB20nK14wrQJgfrA18PtmdagyeRib3xGtvzkdn3Lgw/viewform?usp=sf_link with your choice of the times that work for you.

I’ll follow up with you to figure out what method is the best way for us to connect.

Please contact me using the email mentioned above if you have any questions or require more information about this project.

Thank you for considering taking part in this research.

Regards

Kholoud

Not sure what came out of that interview, but I guess this can be archived by now. --Daniel Mietchen (talk) 15:56, 25 August 2022 (UTC)

Joseph Lau (Q107974859)

Hi Daniel, is he distinct from Joseph Lau (Q85265213)?-- Culinary Specialist (talk) 16:23, 11 August 2022 (UTC)

@Culinary Specialist: not sure yet, but I've been sing the Author Disambiguator to try and sort this out a bit better. --Daniel Mietchen (talk) 15:55, 25 August 2022 (UTC)

ambiguous items

Hello. Just a friendly reminder to add a couple identifying properties, labels, and/or external identifiers to human items such as Brittany Rohl (Q112118368), so that they can be identified and distinguished more easily, and don't get mistakenly merged with other items (especially important in biomedical articles where there may be hundreds of authors in the same field with similar names). I added a Google Scholar ID to Kathleen M. Collins (Q112118365) to aid in disambiguation. Cheers. -Animalparty (talk) 23:41, 15 August 2022 (UTC)

Thanks for the reminder. I am aware of this and usually add multiple links to such items when I create them, and for a while, those bare items have also been enriched with a third statement (details). In any case, I made some edits to Brittany Rohl (Q112118368). --Daniel Mietchen (talk) 15:26, 25 August 2022 (UTC)

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On August 9, an update regarding the launch of Wikifunctions Beta has been published.

On August 19, an update regarding the proposed template language syntax for Wikifunctions and the Wikimania 2022 sessions dedicated to Wikifunctions and Ninai-Udiron has been published.

Enjoy the reading!

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 18:06, 29 August 2022 (UTC)

Wikidata weekly summary #535

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development
    • REST API: working on the ability to change existing statements on an Item (phab:T306934)
    • Lexicographical data: Finishing up the remaining pieces of the new Special:NewLexeme page based on the testing feedback (subtickets of phab:T307866)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wrong date imported by Research bot

Hi! I have noticed a few time already that ResearchBot import a publication date that isn't the correct one. See e.g. Q113203530, which I'll leave uncorrected as a case study. I'm not sure what is causing it but I would appreciate if you could have a look. Thanks! --Jahl de Vautban (talk) 10:14, 31 August 2022 (UTC)

Thanks for the quality check, Jahl de Vautban! The problem has been identified and likely fixed in the code (we're still doing some tests), but it will take some time to fix the corresponding statements (we're looking into this too). In any case, from now on, future imports should not have this problem any more. --Daniel Mietchen (talk) 22:07, 1 September 2022 (UTC)

Wikidata weekly summary #536

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • MsynBot 9. Task/s: manage existing GND ID (P227) identifier claims
      • DL2204bot. Task/s: Add ExternalID values, edit/create items, add/edit lexemes, senses, forms
  • Events
    • Upcoming:
      • Wikidata's 10th birthday is coming up soon: you can contribute to the celebration video, prepare an event or a birthday present.
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call September 6, 2022: Dominic Byrd-McDevitt will talk about the Digital Public Library's Wikimedia program, an effort to provide national leadership around access and discoverability of digital collections by leveraging Wikipedia and its sister projects. 2 years ago, DPLA launched a digital asset pipeline to enable participating institutions in the DPLA network to share their collections with Wikimedia Commons. DPLA is continuing to innovate by taking advantage of Wikidata entities and Structured Data on Commons to continually synchronize data and improve discoverability. We'll discuss issues around large datasets, aggregation, reconciliation, and other challenges DPLA has faced. Agenda
      • Talk to the Search Platform / Query Service Team—September 7th, 2022 Date: Wednesday, September 7th, 2022. Time: 15:00-16:00 UTC / 08:00 PDT / 11:00 EDT / 17:00 CEST / 19:00 GST
    • Ongoing:
  • Development
    • REST API:
      • We are continuing to work on the PATCH endpoint to make it possible to edit existing statements (phab:T306934)
      • We started the security review process for one of the libraries we are using. Until that is finished this part of the REST API can unfortunately not be tested on beta Wikidata. (phab:T316523)
      • For anything but the PATCH endpoint, you can follow along development on beta Wikidata and see the latest docs. More details at Wikidata:REST API feedback round.
    • Lexicographical data: Continued addressing remaining issues found during testing (phab:T314064, phab:T312633, phab:T312652)
    • Continuing work on supporting sitelinks to redirects under some special conditions (phab:T278962)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

ResearchBot adding references to articles

Thanks for your work on this. We know this is a gigantic task, as I'm doing the same semi-automatically for specific topics. So I noticed it is very useful to have all references from review articles (P31 Q7318358).

My suggestion would be that you prioritize your work to add refs to review articles first. SCIdude (talk) 07:55, 8 September 2022 (UTC)

Hi SCIdude — thanks for thinking and editing along. Can you provide some more details and/ or examples? "add refs to review articles first" can be interpreted in multiple ways, and I'm not sure I can be of much help with any of them at this point. --Daniel Mietchen (talk) 20:52, 10 September 2022 (UTC)
I'm assuming your bot adds P2860 statements to article items (P31 Q13442814).. Review article items (P31 Q7318358) are a subset. My suggestion is to work on this subset first. SCIdude (talk) 06:50, 11 September 2022 (UTC)
SCIdude: The bot rarely does cites work (P2860) edits but if it does, I will try to give special attention to review articles. --Daniel Mietchen (talk) 21:41, 11 September 2022 (UTC)
Thanks.

Wikidata weekly summary #537

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour September 12, 2022: Sixth session of our summer/fall project working with diverse children's book metadata. We'll be creating items for books (works and editions) in Wikidata. You are, as always, welcome to bring your own data to work on. All sessions in our project series will be recorded for those who cannot attend. Links will be added to the event page when available. Wikidata Working Hour Event page
      • Webinar: Querying Wikidata: All the Knowledge in the World. Sep 15, 2022 5:00 PM Central European Summer Time
    • Ongoing:
      • Weekly Lexemes Challenge #58, City
  • Tool of the week
    • View it! Tool - (based on Wikidata) allows viewing a multitude of images that depicts a given topic on Wikipedia.
  • Development
    • REST API: Continued work on the endpoint for changing a statement (phab:T306934)
    • Lexicographical data: Made sure that the new Lexeme creation page also is shown in older browsers (phab:T311157), which was one of the last remaining issues before we can switch out the existing page (phab:T307866)
    • Continued work on enabling sitelinks for redirects under certain conditions (phab:T278962)
    • Spend a few days with people from Wikimedia Indonesia to discuss our partnership

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #538

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • New requests for permissions/Bot:
      • بوٹ دا عثمان
        • Task/s:
          • Dual script support for Punjabi Wikidata labels and descriptions in Gurmukhi (pa) and Shahmukhi (pnb), taking a conservative approach (only making "obvious" transliterations).
          • Addition of labels and descriptions entirely consistent of information which can be inferred from other language labels (again, only for "obvious" cases).
  • Tool of the week
    • WD-FIST is a userscript that checks Wikipedia pages for available images if the item doesn't have one (automatically or manually via sidebar link).
  • Development
    • REST API:
      • Finished the endpoint for editing statements (phab:T306934)
      • Working on automated edit summaries (phab:T312811)
      • Making small modifications to the response format for statements (phab:T317866)
    • Lexicographical data:
      • Special:NewLexemeAlpha now uses the new search profile for languages, which makes it easier to select a language Item for the language of the new Lexeme (phab:T312853)
      • Finished the work on making sure that the example Lexeme falls back to other locally defined examples for languages other than English instead of the pre-set example Lexeme (phab:T313599)
      • Working on making sure that only *-x-Q123, not *-x-q123, can be used as a Lexeme language code (phab:T317863)
    • Sitelinks to Redirects are now available for testing on test.wikidata.org
    • Improved the wrapping and selection behavior of aliases in the header of an Item (phab:T315991) Thanks Fomafix for the patch!
    • Improved the translations of the Lexeme and EntitySchema namespaces (phab:T316770) Thanks to Amire80 for the patch!
    • Started supporting Codex work for some Wikidata-specific work needed in the new design system (phab:T306932)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #539

Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🧵 Discussions
    • New requests for permissions/Bot:
      • JhsBot 6
        • Task/s: Add sitelinks to newly created wikis after wikis have been created and exported from the Wikimedia Incubator.
  • 🎊 Events
    • Upcoming
      • Live editing session on Twitch, in French, by Vigneron, September 26 at 18:00 CEST (UTC+2)
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour September 30, 2022: the seventh Wikidata Working Hour in the series will be a review session of creating contributor and publisher items in Wikidata. The primary goal of this session is to generate as many contributor and publisher items as we can in advance of the two following sessions which have to do with batch editing -- we want enough to make a good batch! We will review how to add items, but then reserve the bulk of the session for open editing, kind of like a mini-editathon! Naturally, participants can ask questions and share thoughts at any point during the editing! You are, as always, welcome to bring your own data to work on. All sessions in the project series will be recorded. Links will be added when available. Event page
    • Ongoing
      • Weekly Lexemes Challenge #60, Cows
  • 🧰 Tool of the week
    • User:Bovlb/notability.js is a userscript that adds a small notability indicator to the top right of an item showing how well the item satisfies the three notability criteria. Left to right, the three columns indicate sitelinks, identifiers and references, and structural need.
  • 🧑🏿‍💻 Development
    • Continuing work on making the mul language code work.
    • Continuing work on making Special:UnconnectedPages scale (phab:T300770)
    • Ensuring that Lexeme language codes using mis use uppercase Q consistently in the Item IDs (phab:T317863)
    • REST API: Working on automated edit summaries (phab:T312811)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On September 23, an update regarding the state of Abstract Wikipedia's Natural Language Generation workstream has been published. This entry is also available as a Wikimedia Diff blog post.

On September 27, an update regarding how to create a Wikifunctions guideline for staff contribution has been published. Please, take some time to contribute to the discussion.

Enjoy the reading!

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 10:53, 29 September 2022 (UTC)

Wikidata weekly summary #540

Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🎊 Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call
        • October 4, 2022: Lana Soglasnova and Roman Tashlitskyy will talk about their preliminary work in creating and editing items for Slavic people and some of the complications involved in this work, especially around transliterating names in various languages. Agenda
        • Wikibase Working Hour! 25 October 2022, 2pm Eastern (Time zone converter) Amy Ruskin of Northeastern University Library, will speak on the topic of Wikidata vs. custom Wikibases: Community history case studies, Boston’s Chinatown. The Boston Research Center (BRC) is a digital community history and archives lab based in the Northeastern University Library. One of our current projects involves taking an inventory of historical materials related to Boston’s Chinatown, and we have been using Wikibase to store multilingual data about the linked collections, organizations, and people. In this presentation, we will discuss our experience of getting started with a custom Wikibase and give an overview of our progress so far on the Chinatown Collections project. Amy Ruskin is the Data Engineer in the Digital Scholarship Group in the Northeastern University Library. She has a Master's degree in Information Studies from McGill University and a background in computer science and statistics. Registration link
      • Live editing session on Twitch, in French, by Vigneron, October 4 at 18:00 CEST (UTC+2)
      • [Small wiki toolkits] Upcoming "How to interact with Wikidata via Pywikibot" workshop on Friday, October 7th, 16:00 UTC
      • The State of Wikidata and Cultural Heritage: 10 Years In. Oct 4, 2022 08:00 AM in Pacific Time (US and Canada)
      • Talk to the Search Platform / Query Service Team—October 5th, 2022
      • Wikidata Office Hour GLAM-Hack − online meet-up about the "library world" with Wikidata. October 5th, 12.00 UTC (online via Zoom)
    • Ongoing
      • Wikimedia Österreich, in cooperation with Wikimedia Deutschland, started the DACH Culture Contest as a Börthday present for Wikidata 10th anniversary! It features two categories: "libraries in Austria, Germany and Switzerland" and "Culture in Austria, Germany and Switzerland". So if you would like to improve data about libraries, books, music, art, video games, cinema etc as a börthday treat, join us and get the chance to win some nice prizes! The contest will last until October 16, 2022.
      • Weekly Lexemes Challenge #61, Time
  • 🧑🏿‍💻 Development


You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Duplicate item for scholarly article?

I happened to notice that A case study of the Hirsch index for 26 non‐prominent physicists (Q114267509) and A case study of the Hirsch index for 26 non-prominent physicists (Q114267510) had the same title, and after digging a bit I discovered that Q114267510 has a DOI pointing to https://onlinelibrary.wiley.com/doi/10.1002/andp.20075190903, which has the title "A more direct representation for complex relativity". I think Research Bot somehow has a bug here that caused the second item to end up with the same name as the first, despite intending to represent a different article entirely?

Also, thank you for running Research Bot, I've been following it since I've been hoping we can hit 100 million items in time for Wikidata's 10th birthday :) Just want to make sure we do so without adding bad data.

Best, Nicereddy (talk) 13:54, 28 September 2022 (UTC)

@Nicereddy: This one was a bit complicated, but here is what I think happened under the hood: in short, it's again (just as with the HTML tags discussed in the thread below) a problem originating at from the Crossref record, and I do not see an automated way to handle such cases at the moment while reusing their metadata. I'll think about it, though, and leave the two items alone for the moment. I did leave a comment at Talk:Q114267510, though. --Daniel Mietchen (talk) 21:40, 9 October 2022 (UTC)

Wikidata weekly summary #541

Here's your quick overview of what has been happening around Wikidata over the last week.
  • ✨ Other Noteworthy Stuff
    • The fourth edition of the Coolest Tool Award is looking for nominations. Please submit your favorite tools by October 12, 2022. The awarded projects will be announced and showcased in a virtual ceremony in December.
    • The September 2022 summary for the Wikidata Query Service backend update is out.
  • 🧑🏿‍💻 Development
    • MUL language code: fixed the order of languages shown in the termbox on desktop, especially when mul is used (phab:T311617)
    • Lexicographical data:
      • Made Special:NewLexemeAlpha use the same font as the rest of the wiki (phab:T313166) – this should be the last blocker for replacing the old special page
      • Disallowed *-x-qid with lowercase Q as Lexeme language codes in favor of *-x-Qid (phab:T317863)
    • REST API: worked on handling conditional HTTP request headers
    • Changed the unexpectedUnconnectedPage page prop so that Special:UnconnectedPages can show the latest pages first, which should finally resolve this old security task in production (phab:T300770)
    • Cleaned up the Wikibase and WikibaseLexeme ontology files (phab:T314360)
    • Added a few more globes for geocoordinates (phab:T314611) - Thanks, Mike!

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On September 30, an update regarding Cory Massaro's arts residency in Istanbul has been published.

On October 5, a comprehensive update about the last two months of Abstract Wikipedia and Wikifunctions technical developments has been published.

Enjoy the reading!

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 10:59, 13 October 2022 (UTC)

adding references

Up to now, to find articles missing references, I just excluded any article with any number of references. But recently seeing articles with very few refs added by you (Q91562400, Q22809915) I have to reconsider. Out of curiousity, why don't you use crossref, scholar or semanticscholar? SCIdude (talk) 10:28, 16 October 2022 (UTC)

@SCIdude: Sometimes, I am just working on citations to a particular set of items rather than citations from them, which might explain the patchiness in cases like these. Another thing to keep in mind is that the references cited from a particular item may well not all be in Wikidata at a a given time. That said, I have not used wd-cli much but would be happy to give it a try for handling citations. Can you point me to the code underlying some of your relevant sample edits? Apart from that, perhaps it's time for us to have some synchronous exchanges to coordinate our respective Wikidata activities. --Daniel Mietchen (talk) 14:01, 16 October 2022 (UTC)
Actually most what I'm doing in general is semi-automatic. For example the script [6] needs manual creation of missing articles (e.g. run, copy DOIs into sourcemd, wait, continue) before writing the commands with all citations, which then can be used as input for `wd ee`. In general I see no other way than that. Using the Unix command line, where previous commands can be easily edited and run helps tremendously. If you browse the repo given above you'll see that small scripts as parts of workflows are doing everything. The modular workflow paradigm is unavoidable with complex tasks, in my opinion. Monolithic software will get you in a cul-de-sac. SCIdude (talk) 14:33, 16 October 2022 (UTC)

Wikidata weekly summary #542

Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🧑🏿‍💻 Development
    • REST API:
      • Finished work on handling conditional HTTP request headers (If-Match, If-None-Match, etc)
      • Working on providing more clear error reports to PATCH route errors
    • Mismatch Finder: Implementing a new random mismatch feature (phab:T302289)
    • The text in the namespace tabs for Lexeme: and EntitySchema: pages can now be easily translated (phab:T316770) - thanks Amir!
    • Made the Wikibase error message "Malformed input" more meaningful (phab:T304943)
    • Continued working on the deployment of a patch to improve the Query Service lag integration in MediaWiki API's maxlag (phab:T315423)
    • Fixed a bug where the Kartographer map preview is erroneously closed, when clicking on zoom actions (+/-) (phab:T303103)
    • Still working on fixing a mobile termbox issue related to the "mul" language code (phab:T318137)
    • Added ircs as an allowed protocol for the URL datatype (phab:T320643) - thanks Lectrician1!

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #543

Here's your quick overview of what has been happening around Wikidata over the last week.
Wikidata passed another milestone on October 19.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Italics in paper names

Anastasia Denisova. Internet Memes and Society: Social, Cultural and Political Contexts (Q114394609), Fossil Folklore from India: The Siwalik Hills and the Mahâbhârata (Q114394606), and H.M. ARMED SHIP VIGILANT, 1777–1780 (Q114394603) all were imported with "i" HTML tags in their titles. These should probably be fixed, along with any others that were created recently with this problem (there are a few I saw that I didn't link here). Nicereddy (talk) 02:07, 4 October 2022 (UTC)

And a similar problem with Multilayer nanogranular films (Co40Fe40B20)50(SiO2)50/α-Si:H and (Co40Fe40B20)50(SiO2)50/SiO2: Magnetic properties (Q114394646). Nicereddy (talk) 02:10, 4 October 2022 (UTC)
For me it looks more like a limitation of MediaWiki, not a problem of item. But I've seen a lot of similar problems and I wonder if it is even technically possible to convert all current cases into en:Unicode subscripts and superscripts. Lockal (talk) 03:09, 4 October 2022 (UTC)
@Nicereddy, Lockal: Thanks both for looking into this. It is a problem I have on my radar, though it is not specific to my bot (for examples from other bots, see Tripfordines A−C, Sesquiterpene Pyridine Alkaloids from Tripterygium wilfordii, and Structure Anti-HIV Activity Relationships of Tripterygium Alkaloids (Q113960369), Functional Characterization of the Lin28/let-7 Circuit During Forelimb Regeneration in Ambystoma mexicanum and Its Influence on Metabolic Reprogramming (Q104488932) or Taxonomy, ecology, and conservation status of Philippine Rafflesia (Rafflesiaceae) (Q54250206)), as the titles are actually stated with the Markup in the databases queried, be that Crossref (example) or Europe PMC (example). A fix is not straightforward, since there are a number of edge cases that complicate things, and I am using Wikidata Integrator (Q31743627), which does the heavy lifting. There is also the issue of how best to handle such corrections in terms of deprecations or preferred statements and the suitability of the cited source (see my notes). In any case, I am doing regular rounds of cleanups for titles containing HTML tags like italics, bold or line breaks and others for which title (P1476) has constraint statements. This is not the case for <sub> and <sup> yet, so we should probably add them there too, especially since there are much higher numbers of them (currently 3k for sup and 2k for sub). Help with any of that would be appreciated. --Daniel Mietchen (talk) 11:20, 9 October 2022 (UTC)
@Nicereddy, Lockal: I wrote a maintenance query that produces QuickStatements (V1) commands that do the following (sample edits):
  • search for articles with <sub> or </sub> tags in their title
  • create a new title and English label in which the tags are replaced with single spaces
  • move the old titles to title in HTML (P6833) (qualifier) statements
Some of the things I am not sure:
  • whether <sub> or </sub> tags should be replaced by nothing or by single spaces (I went for single spaces here but this may actually be more appropriate for <i> or </i> tags)
  • how to expand this to automatically detect and cover all languages in which the titles and/ or labels contain the respective target tags
  • whether the references under the title statements should be kept, given that they state the title with tags, while we then use it without
  • whether we should not delete the old title and instead better use deprecated/ preferred ranks, which I think QuickStatements cannot currently handle
Apart from that, the approach seems applicable for other HTML tags too.
--Daniel Mietchen (talk) 21:03, 9 October 2022 (UTC)
I think it would be much better to use unicode subscripts and superscripts instead of just removing all tags, e. g.: Multilayer nanogranular films (Co₄₀Fe₄₀B₂₀)₅₀(SiO₂)₅₀/α-Si:H and (Co₄₀Fe₄₀B₂₀)₅₀(SiO₂)₅₀/SiO₂: Magnetic properties. At least for numbers and some basic Latin characters. I bet it would cover 99% of titles with subscripts and superscripts. And for the rest decide case by case. Lockal (talk) 02:54, 10 October 2022 (UTC)
There are 66k labels with HTML tags at this moment: https://quarry.wmcloud.org/query/67990 Lockal (talk) 04:28, 10 October 2022 (UTC)
Came across this thread as I am facing similar issue (https://www.wikidata.org/wiki/Topic:X5q2qm0bxy8mujam), if there is a consensus on how to best handle html tags (not being limited to sub/supscript numbers), happy to learn! AdrianoRutz (talk) 17:24, 26 October 2022 (UTC)

Research Bot is adding a written language to paintings

This edit doesn't make sense: Eenglish added to painting. Jane023 (talk) 18:45, 26 October 2022 (UTC)

@Jane023:: Thanks for the hint. Fixed. --Daniel Mietchen (talk) 02:24, 28 October 2022 (UTC)

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On October 14, we welcomed Stef Dunlap in our team as Quality and Test Engineer.

On October 20, an update regarding a new Wikifunctions demo (also available here) has been published.

On October 27, we shared a summary of what we achieved thanks to the efforts of six Google Fellows, whose fellowship has come to an end.

Enjoy the reading!

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 11:17, 28 October 2022 (UTC)

empty items

It would be nice if you would add at least one statement to items that you create. Like you made hydraulic trait (Q113024585) and linked a ton of things to it but you didn't add any statements. Generally items without statements aren't desired. BrokenSegue (talk) 17:43, 26 September 2022 (UTC)

Thanks for the note, BrokenSegue. I completely agree that items should have at least one statement. Not sure why I left out this one — thanks for the fix. --Daniel Mietchen (talk) 11:20, 27 September 2022 (UTC)

This happened again with impact of disasters on cultural heritage (Q108829176). It's not helpful to have items with no statements. BrokenSegue (talk) 16:44, 31 October 2022 (UTC)

Wikidata weekly summary #544

Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🧰 Tool of the week
    • sparklis (source) : query builder in natural language that allows people to explore and query SPARQL endpoints with all the power of SPARQL and without any knowledge of SPARQL, nor of the endpoint vocabulary.
  • ✨ Other Noteworthy Stuff
    • Word Finder is a tool based on Wikidata Lexemes that solves anagrams and find missing letters in crosswords.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

wrong main subject (P921) statement

Hi Daniel, this edit is wrong, please fix. Hint: the membranes that are fused here are different from those at viral entry. SCIdude (talk) 07:16, 22 October 2022 (UTC)

Here is another: 2

@SCIdude: Thanks for catching that. I see what you mean and will think about a fix. --Daniel Mietchen (talk) 14:59, 4 November 2022 (UTC)

John Cupitt

Hi Daniel,

John R. Cupitt (Q110741611) has no information – maybe it's a duplicate to John R. Cupitt (Q102256335)? Jørund Viktoria Alme (talk) 11:04, 3 November 2022 (UTC)

@Jørund Viktoria Alme: Thanks for the pointer. After taking a closer look, the two turned out to be indeed about the same person. Note that each page here also has a "What links here" link in the sidebar, which may well provide additional information relevant to improving the item at hand. For people specifically, it is also often worthwhile to check out their Scholia profiles, in this case toolforge:scholia/author/Q102256335. --Daniel Mietchen (talk) 14:58, 4 November 2022 (UTC)

Empty item

Hello,

may you give more information on Xiangguo Qiu (Q66680131)?-- Aunty Gormint (talk) 20:20, 6 November 2022 (UTC)

@Aunty Gormint: Done. See also their Scholia profile at toolforge:scholia/author/Q66680131. --Daniel Mietchen (talk) 23:16, 6 November 2022 (UTC)

Wikidata weekly summary #545

Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🎊 Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Wikidata Working Hour November 7, 2022: tenth and final Wikidata Working Hour in the series will be using SPARQL to query and visualize the data we’ve added to Wikidata during our series. You are, as always, welcome to bring your own data to work on. All sessions in our project series will be recorded for those who cannot attend. Links will be added to the event page when available. Event page
      • Live querying session on Twitch, in French, by Vigneron, November 8 at 18:00 CET (UTC+1)
      • Wikidata and Wikibase office hour, taking place online on November 9th at 17:00 UTC (more details here)
      • Raising an Artist Profile with Wikidata: Thursday November 10, 2022 at 20:00 UTC (Session A) and 23:00 UTC (Session B). This free, step-by-step Wikidata workshop will focus mainly on Indigenous artists. Participants may choose to attend either Session A or Session B: both will cover the exact same material.
      • Wikidata editathon in Swedish with focus on climate politics and COP27, online and in Stockholm, 11 November 13.00-18.00 UTC
      • A Hands-On Introduction to Wikidata: Thursday December 1, 2022 at 17:00 UTC. By the end of this session, you will be able to edit Wikidata records about the cultural venues that matter most to you.
  • 🧰 Tool of the week
    • WikibaseEcho.js: Userscript that shows the labels of entities in your notifications. Currently only works on Firefox.
  • 🧑🏿‍💻 Development
    • Lexicographical data: Replaced the old Special:NewLexeme page with the new one (phab:T307866) - a few remaining issues will still be fixed
    • Vue 3: Almost finished the Vue 3 migration in Wikibase and WikibaseLexeme (phab:T321595 and (phab:T304534) - this is needed for finalizing the migration in MediaWiki overall
    • Mismatch Finder: Worked on improving the handling of dates (phab:T288511)
    • Search: Working with the WMF on making the new Vue-based Vector search understand Wikidata (phab:T316093)), especially regarding “load more” behavior
    • REST API:
      • Continued improving error reporting for PATCH routes (phab:T320358)
      • Ensuring that the API correctly marks bot edits as bot edits and treats them as such in various other places

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Research Bot adds number of pages twice

Hi! I noticed that in some cases Research Bot adds twice the number of pages, once with and the other without a reference ; see e.g. Q64368710#P1104. Could you have a look at it ? Thanks ! --Jahl de Vautban (talk) 17:44, 10 November 2022 (UTC)

@Jahl de Vautban: Thanks for the hint. This was due to a missing "DISTINCT" in the query I used to generate the edit commands. This is now fixed, and I will look into cleaning up the leftovers. --Daniel Mietchen (talk) 19:48, 10 November 2022 (UTC)

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On November 4, an essay from Denny about the possible evolutions of natural language generation tasks on Wikifunctions was published.

On November 9, an update about a new browser-based tool, Form Checker, was published (instructional video available here).

Also, we have a new channel on IRC, called "wikipedia-abstract-tech", which is also bridged with Telegram. Find out more about (and maybe join) our official channels here.

Enjoy the reading!

Subscribe · Translate this message

--MediaWiki message delivery (talk) 10:19, 11 November 2022 (UTC)

Wikidata weekly summary #546

Here's your quick overview of what has been happening around Wikidata over the last week.
  • 🎊 Events
    • Upcoming:
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group call November 15, 2022: We will be discussing the first Wikidata Affinity Group Working Hour series, which ran from July to early November of this year. We will offer visualizations based on our data, listen to some of our volunteers talk about their experience helping to build the series, and discuss the results of our participant survey. We want to hear your questions and suggestions for future series! Agenda
      • Enrichissement des données sur la danse: Wednesday 16 November at 6:30 pm UTC (Session A) and Thursday 17 November at 6:30 pm UTC (Session B). Join the Regroupement québécois de la danse (RQD) and the Linked Digital Future Initiative (LDFI) for two dynamic sessions focusing on dance data. Session A will focus on artists, while Session B will focus on organizations and dance companies. Note: These sessions are offered in French only.
    • Ongoing:
    • Past:
      • Wikidata/Wikibase Telegram office hours log (2022-11-09)
  • 🧰 Tool of the week
    • QLever - Alternative instance for SPARQL queries.
    • Discuss.js - Adds a link to a diff when clicked will open a new topic on the talk page that mentions the revision and the user.
  • 🧑🏿‍💻 Development
    • REST API:
      • Finished work on improved error reporting of the PATCH routes (phab:T320358)
      • Finished work on properly handling bot user right and marking bot edits as such
      • Adjusting statement data structure in Wikibase REST API responses and requests (phab:T321459)
    • Mismatch Finder: continuing work om improving the handling of dates in the Mismatch Finder (phab:T288511)
    • New Vector skin: continuing work with the WMF on making the new Vue-based Vector search understand Wikidata (phab:T316093, phab:T317682)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikidata weekly summary #547

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • Online Wikidata meetup in Swedish #130, November 27 at 13.00 UTC
      • Wiki <3 Data - How to use Wikidata for data visualization. Join us on Monday 28 Nov. from 13:15 - 17:00 at Aalto University in Espoo, Finland or online! - Hosted by Visual Communication Design programme at Aalto Arts, workshop by Yamen Bousrih.
      • Next Wikidata Bug Triage Hour about Entity Schemas and other topics, on December 6th at 17:00 on Jitsi
    • Ongoing:
  • Development
    • REST API: continuing work on adjusting JSON request and response format (phab:T321459)
    • Lexicographical data:
      • Added separation between identifiers and other statements on Lexemes (phab:T318310)
      • Fixed the case where language fallback indicators where shown on Special:NewLexeme when they should not be (phab:T322687)
      • Adjusted the help link for the spelling variant input field (phab:T315161)
    • Mismatch Finder:
      • Finished work on better handling of dates (phab:T288511)
      • Finished work on allowing mismatches with empty Wikidata values to make it possible to use the Mismatch Finder also for suggesting missing data (phab:T313468)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

New Abstract Wikipedia and Wikifunctions updates are out

There are new updates for Abstract Wikipedia and Wikifunctions! Please, come and read them!

On November 17, we announced the beginning of the consultation about Wikifunctions' Code of Conduct. You are invited to express your opinions in the talk page.

On November 23, we posted a brief newsletter announcing the interview to former Google Fellow and returning Wikipedian Ori Livneh. You can read his full interview on the Diff blog.

Also, we remind you that we have a new channel on IRC, called "wikipedia-abstract-tech", which is also bridged with Telegram. Find out more about (and maybe join) our official channels here.

Enjoy the reading!

Subscribe · Translate this message

-- MediaWiki message delivery (talk) 10:11, 28 November 2022 (UTC)

Wikidata weekly summary #548

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • Save the date! The next WikidataCon will take place on October 28-29, 2023, and will be organized by Wikimedia Taiwan and Wikimedia Germany. The hybrid event will be streamed from Taipei and accessible for everyone online. More information and updates on d:Wikidata:WikidataCon_2023
      • Next LD4 Wikidata Affinity Group call November 29, 2022: We will be discussing openly managed data gathering and management with Holly Little (Smithsonian), Sabine von Mering (Museum für Naturkunde), Erica Krimmel (Florida State University), and Debra Paul (University of Illinois)! Agenda
      • A Hands-On Introduction to Wikidata: Thursday December 1, 2022 at 17:00 UTC. By the end of this session, you will be able to edit Wikidata records about the cultural venues that matter most to you.
      • Online Wikidata meetup in Swedish #131, December 4 at 13.00 UTC
    • Past:
      • Wikibase live session (November 2022) log
  • Development
    • REST API:
      • Finished the adjusted statement data structure (phab:T321459)
      • Simplifying the structure of sitelinks in Item data (phab:T321483)
      • Simplifying the value format for entity ID, time and globecoordinate value types (phab:T322734)
      • Investigating the way forward for rate limiting (phab:T322746)
    • Ontology issues: Preparing a survey for re-users of Wikidata's data about the different types of ontology issues and which ones are causing the most issues for application builders
    • Mismatch Finder:
      • Finishing the work on making it possible to provide mismatches with an empty Wikidata value so the tool can also be used to suggest new data (phab:T313468)
      • Finishing the work on better handling of calendar models and precision for dates (phab:T288511)
    • Lexicographical data: Fixing bugs:

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Wikimedians for Sustainable Development - November 2022 Newsletter

This is our twentyfirst newsletter, covering November 2022. This issue has news related to SDGs 3, 5, 11, 13, 14, 15, 16 and 17.

Activities

  • Current: Women in Climate Change editathon in various languages (1 December 2022 - 31 January 2023) (SDG 5 & 13) [17]
  • Past: Wikipedia and sustainability, how to increase knowledge on climate change? (SDG all) [1]
  • Past: Wikidata editathon in Swedish during COP 27 (SDG 13) [2]

News

  • Wikimedia Nederland signed the Wikimedia Affiliates Environmental Sustainability Covenant (SDG all) [3]
  • WikiProject Govdirectory was featured as Digital Public Goods (SDG 16) [11]
  • The theme for Wiki Loves Africa 2023 has been revealed: Climate and weather (SDG 13) [16]

Resources

  • Let's Connect learning report - pilot phase 2022 (SDG 17) [15]

Research

  • Recommendations for use of annotations and persistent identifiers in taxonomy and biodiversity publishing [SDG 15) [7]
  • A longitudinal analysis of gender diversity in Wikipedia articles (SDG 5) [13]

Videos

  • 10 Anos de Wikidata: Wikidata for Open Access to Cultural Heritage, por Susanna Ånäs (AvoinGLAM) (SDG 11) [14]

New WikiProjects

  • Myosotis Pilot (SDG 15) [12]

New Wikidata properties

  • Bank of information on the historical and cultural heritage of the Republic of Belarus (SDG 11) [4]
  • Louisiana Plant ID (SDG 15) [5]
  • DrugCentral ID (SDG 3) [8]
  • Probes And Drugs ID (SDG 3) [9]

New Wikidata query examples

  • Map of water bodies in France (SDG 14) [6]
  • Gender balances of winners of literary awards (SDG 5) [10]

Links

This message was sent with Global message delivery by Ainali (talk) 22:05, 1 December 2022 (UTC) • Contribute • Manage subscription

A new Abstract Wikipedia and Wikifunctions update is out

There is a new update for Abstract Wikipedia and Wikifunctions. Please, come and read it!

In this issue: news about Natural Language Generation (NLG) meetings, a new Mastodon account for the project, and the latest development updates.

Also, we remind you that:

Enjoy the reading! -- MediaWiki message delivery (talk) 10:11, 3 December 2022 (UTC)

Subscribe to the newsletter

ResearchBot: Book review items

Hello, the bot created several items with corrupted DOI codes:

The items do not have some links or names that allow clearly identify the entities. instance of (P31) is looked wrong also. Could you fix or delete the items? — Ivan A. Krestinin (talk) 11:10, 3 December 2022 (UTC)

@Ivan A. Krestinin: Thanks for the checking and notification. I slightly reformatted your list and am looking into the matter. --Daniel Mietchen (talk) 13:52, 3 December 2022 (UTC)
Looks like the journal changed ownership, and the new owners discarded the original DOIs in favour of new ones. --Daniel Mietchen (talk) 15:19, 3 December 2022 (UTC)
Thank you! Usually DOI codes do not use "&" symbol. Most probably the values are incorrect, not deprecated. — Ivan A. Krestinin (talk) 15:47, 3 December 2022 (UTC)

Wikidata weekly summary #549

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • Next Linked Data for Libraries LD4 Wikidata Affinity Group Working Hour on December 5. We will be working on Structured Data on Commons with a WINTER FUN theme, adding depicts statements to images and playing with some tools. You are, as always, welcome to bring your own data to work on. This will be our last scheduled Working Hour for 2022. Please join us for a relaxing and enjoyable session to wrap up a year of excellent work together. Event page
      • Bug Triage Hour on December 6 at 17:00 UTC, on the topic of Entity Schemas (other topics also welcome). Come with your favorite Phabricator ticket so we can improve its description together!
      • Save the date! The next WikidataCon will take place on October 28-29, 2023, and will be organized by Wikimedia Taiwan and Wikimedia Germany. The hybrid event will be streamed from Taipei and accessible for everyone online. More information and updates on the WikidataCon 2023 page.
    • Ongoing
      • Weekly Lexemes Challenge #69, Cycles
  • Tool of the week
    • How many edits does Wikidata get per second? listen.hatnote.com/#wikidata is a tool that allows you to listen to the sound of Wikidata's recent changes feed.
  • Development
    • Improved the error message for sitelinks to redirects (phab:T320490)
    • Made the Property namespace a content namespace (phab:T321282)
    • Lexicographical data: Added a better link for a help message (phab:T315161)
    • Mismatch Finder:
      • Linked the header to make it easier to get back to the main page (phab:T323680)
      • Made the layout more compact (phab:T323678)
      • Fixed an issue where the whole header of a mismatch results table was a link instead of just the Item ID (phab:T323823)
      • Improved the text on a button (phab:T323682)
      • Finished better support for dates with calendar model and precision (phab:T288511)
      • Ordered the columns in the results page better so they make more sense (phab:T323819)
    • Fixed a bug where a large horizontal scrollbar appeared on RTL interface languages (phab:T321441)
    • Fixed a bug in the search in the new Vector skin (phab:T324148)
    • Query Service:
    • mul language code: continuing investigation for language fallbacks on mobile that is currently blocking it (phab:T323098)
    • REST API:

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.


Wikidata weekly summary #550

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Tool of the week
  • Development
    • REST API:
    • Vektor 2022: Finished work on making Vector’s new Search work with Wikidata. The changes roll out for testing on test.wikidata.org next week (phab:T275251)
    • Query Service:
      • Getting a link to the query is now possible in the same place as getting a link to the result of the query (phab:T324218)
      • Removed the gif that showed on hover over the button that advertises the Query Builder to make it less annoying (phab:T296135)
      • Added wikibase:identifiers to the autocomplete feature (phab:T302057)
      • Adjusted the layout of the Query Builder header to be more in line with other application (phab:T288939)
    • Constraint violations: When a language name is mentioned in the constraint it will now show the name of the language in the interface language instead of the language itself to make it easier to understand (phab:T316936)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Please respond

Please respond to the comments at Wikidata:Administrators'_noticeboard#Lexeme_creations_by_Daniel_Mietchen. Thank you. BrokenSegue (talk) 21:50, 16 December 2022 (UTC)

@BrokenSegue: Thanks for the notification - will do. --Daniel Mietchen (talk) 09:29, 17 December 2022 (UTC)

Wikidata weekly summary #551

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • You can now register for the Wikimedia Hackathon 2023, taking place on May 19-21 in Athens, Greece. You can also apply for a scholarship until January 14th. More information: Wikimedia Hackathon 2023/Participate
      • digital@IANLS: online Wikidata workshop for Neo-Latinists in February 2023
      • Call for Papers on Linked Open Data on Journal BiD: Deadline: Sun, 04/09/2023. Some of the ideas and issues to be included in this issue: Creation and exploitation of knowledge graphs, Information services based on linked open data and knowledge graphs, Artificial intelligence and linked open data, Textual corpora and linked open data, Textual corpora and knowledge graphs, Application of bots in linked open data, Application of bots in knowledge graphs, Linked open data and diversity of genres, Graphs of knowledge and diversity of genres, FAIR and linked open data, FAIR and knowledge graphs, Ontologies and linked open data, Ontologies and knowledge graphs, Application of ontologies in information services.
    • Ongoing:
  • Tool of the week
    • Wikidata Atlas is a system allows the user to search for different types of entities (with geo-coordinates) on Wikidata and visualize them on a world map. (Feedback is very welcome to help evaluate and improve the tool.)
    • Check out a similar tool: wiki-atlas
  • Development
    • REST API: We are getting ready for a release in January and would really love more people to test the current state on beta. You can find details for testing at Wikidata:REST API feedback round.
    • Vector 2022 search: We have worked on making the new search in the Vector 2022 skin work for Wikidata. You can now test it on test.wikidata.org and soon on Wikidata.
    • Query Service:
      • Removed the SVG download options for result views where SVG downloads are not supported, such as Map (phab:T311594)
      • Fixed the indentation of autocompletion suggestions (phab:T291695)
      • Fixed downloading query results in the Query Builder (phab:T323451)
    • Lexicographical data:
      • Working on showing the Lexeme lemmas when you look at a Lexeme’s history (phab:T312660)
      • Fixing a keyboard navigation issue in the lookups on Special:NewLexeme (phab:T324743)
    • mul language code:
      • Continuing to investigate how to implement language fallbacks on mobile termbox (phab:T323098)
      • Investigating how to disallow `mul` descriptions (phab:T313027)
    • Improving and harmonizing the footers in the Query Builder (phab:T324356) and Mismatch Finder (phab:T324366)
    • Preparing for showing constraint violations to visitors who aren’t logged in (phab:T272132)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Austin L. Hughes (Q107333432)

Hi Daniel,

are the obituaries correctly placed? Seditious Joe (talk) 17:20, 20 December 2022 (UTC)

@Seditious Joe: Yes, I think adding a described by source (P1343) statement to the person's item and using the item for the obituary as value of that statement seems correct. You can also add a main subject (P921) statement to the obituary's item, linking back to the person, and the obituary's item can be marked as an instance of an obituary. --Daniel Mietchen (talk) 20:14, 20 December 2022 (UTC)
PS: For Australians, there is also Obituaries Australia ID (P9232). --Daniel Mietchen (talk) 20:43, 20 December 2022 (UTC)

Undefined lexemes

Please improve the quality of the lexemes you're adding. Adding lexemes with only forms, and no senses, identifiers or even backlinks to help people understand the meaning of the lexeme and then leaving them for other people to fill in for you is not fair on other editors, particularly when done repeatedly and/or in large numbers. - Nikki (talk) 02:38, 2 December 2022 (UTC)

@Nikki: Saw this only now by way of this comment. Will address things over there first and then come back here for anything else that may need addressing. --Daniel Mietchen (talk) 09:34, 17 December 2022 (UTC)
@Nikki: I am moving my lexeme-related comments from there to here, so that we can work out next steps here too.
  • I agree that lexemes should be linked to structured information as much as possible. If you follow my edits in the lexeme namespace, then you will have noticed that I am doing senses, etymology, compounds, pronunciation and similar on a regular basis. Not sure how best to give an overview here (the contributions in the lexeme namespace currently times out), but perhaps things like the NavelGazer for P5137 might serve as an indication. I am not doing much in terms of identifiers, simply because I am not aware of good workflows for that — pointers appreciated.
  • When I am adding structured information to lexemes, I do not pay much attention to who created the respective pages, other than sending an occasional "Thank you" to contributors that are new to me in lexeme contexts. This is partly because I work on lexemes as I come across them in other contexts (e.g. while reading a paper or working on a Wikipedia article), rather than systematically, and partly because my workflows for creating lexemes (e.g. via Ordia's text to lexemes) are different than those for annotating lexemes (e.g. via MachtSinn), and when I am doing one, I concentrate on that.
  • For lots of lexemes, it is not immediately possible to link them to a sense (e.g. verbs, or nouns with a meaning more granular than the Wikidata items in this space), compound, etymology or so, and immediately going off to create these would again disrupt the lexeme creation workflows, so I leave that for later. This seems to be the core of Nikki's criticism, and having cleaned up or annotated lots of entities set up by others in the various namespaces myself, I have an idea about the frustration that this can cause. However, I think it is important for the project to allow this kind of incompleteness as an entry point for contributions and contributors. There may well be people who prefer to annotate existing lexeme entries rather than creating new ones (verbs have many forms in many languages, and nouns or adjectives in many languages can have many forms too, or a user's knowledge of the language in question might not be sufficient to get all the forms right), and we should be open to this way of contributing, which rests on complimentary contribution pathways, e.g. "simply" creating the lexemes and their respective forms.
  • Working on automation myself both on Wikidata and beyond, I am aware of the benefits of using identifiers and other aspects of structured data, but as stated above, I am not aware of relevant workflows for lexemes. Via things like Scholia's curation pages (example), I help build curation workflows, and closer integration with lexemes (both missing and existing) is being considered. While that has not seen much progress lately, I am planning to get back to this in the new year, and testing the existing workflows that I know is part of that, so that they can be more closely integrated with the new ones.
  • I am aware of some bots active in the lexeme space (e.g. User:Elhuyar Fundazioa bot or User:Uzielbot) but not for German, and I am not sure what the workflows are that Nikki uses to add, say, Duden lexeme ID (P8376) statements to lexeme entries. In any case, I would welcome more bot jobs that assist in curating lexeme entries, both existing and missing, and ideally in ways that work across languages.
  • As an aside, I think the lexeme equivalent of an empty item is a lexeme without forms, and while I do not like empty items either, I think it's better to have them than having no entry for a given concept, since queries allow to list all entities with no statements at all but not all entities that have no entry.
To sum up, I think your criticism is justified but the solution is not for me to stop creating bare lexeme entries. Instead, we should coordinate on improving the workflows in this space.
--Daniel Mietchen (talk) 11:50, 22 December 2022 (UTC)

Michael F. Chiang (Q115365471)

I had no further information and merged this duplicate just by its name. Correct? Seditious Joe (talk) 17:39, 20 December 2022 (UTC)

In general, merging duplicates just by the name is not advisable for people, and before any such merge, it is important to check both items as well as their "what links here" pages. In the case of Special:WhatLinksHere/Q115365471, this gave 106 publications, but since they all seemed to fall into the realm of ophthalmology and thus just the field that Michael F. Chiang (Q60651503) is active in, I have moved them over from Q115365471 to Q60651503 too. A good tool for that — and generally for author disambiguation — is the WD:Author Disambiguator, and a companion tool to check out the individual merge candidates (or indeed anyone known to Wikidata as an author) is WD:Scholia. Both tools are linked in various ways, e.g. via Scholia's curation pages (example), which complement the profile pages (for the same example) for most of the ca. 30 profile types that Scholia offers. --Daniel Mietchen (talk) 20:48, 20 December 2022 (UTC)
Es ist übrigens auch sehr mutig, Items wie Q115365471 ohne irgendeine Aussage über die Person zu erstellen. Lass dich nicht ärgern, --Seditious Joe (talk) 21:01, 20 December 2022 (UTC)
Es geht ja hier um verlinkte Daten, da muss also nicht immer alles auf einem Blatt stehen bzw. Werkzeuge wie die obengenannten oder WD:Reasonator können sich die Informationen aus verschiedenen Seiten zusammenbasteln. --Daniel Mietchen (talk) 21:29, 20 December 2022 (UTC)
Ich empfinde es schon als unhöflich bis frech, Datenobjekte anzulegen und andere dann die Arbeit machen zu lassen. Speziell wenige Tage nach einer Teilsperre des eigenen Accounts. --Emu (talk) 21:37, 21 December 2022 (UTC)
Es ist nicht meine Absicht, mit der Anlage solcher Objekte anderen Mehrarbeit zu verursachen, und ich beteilige mich umfänglich an der weiteren Ausgestaltung diverser Klassen von Datenobjekten, unabhängig davon, wer die einzelnen Seiten jeweils angelegt hat. --Daniel Mietchen (talk) 11:42, 22 December 2022 (UTC)

Wikidata weekly summary #552

Many thanks to everyone who has contributed to and read the newsletter this year. If you have a moment, please let us know what you would like to see changed in the newsletter in 2023. Thank you again for your support and have a happy new year!

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming
      • The next Wikidata+Wikibase office hours will take place on Wednesday, November 9th 2022 at 17:00 UTC (18:00 Berlin time) in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
    • Ongoing
  • Development
    • Due to the winter holidays, the development team is taking a break and no deployment is happening for Wikidata at the moment.

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

Retrieved from "https://www.wikidata.org/w/index.php?title=User_talk:Daniel_Mietchen/Archive/2022&oldid=1862966405"