Jump to content


From Meta, a Wikimedia project coordination wiki
(Redirected from WD4WMP/AddIssue)
Wikidata Integrations Team

What is the Wikidata Integrations Team?[edit]

We are trying to understand why community members from any Wikimedia project connect to Wikidata.

  • What issues do they encounter?
  • Are there ways the projects could be linked differently?

We aim to enhance these integrations in areas where they are needed and wanted by the community.

This space is to report those issues and collect community concerns anywhere that Wikidata is currently, or could be, integrated to other Wikimedia projects and to collaboratively discuss their potential for further development.

Submit an issue

Write in any language you prefer, we will use a machine translation to convert to English if we do not have native speakers available.

Example Submission[edit]

Description of issue[edit]

In this section, I describe the problem, such as how it interrupts or hinders my workflow(s).
I may have ideas on how Wikidata could help. If I know, I can enter details on what functionality or technical details are required to make the idea a reality.
If the issue or idea has previously been discussed within the community, I would mention that here with any relevant links to the discussion / talk / project pages.
If I have multiple issues, or this issue is one of a chain of related issues, I remember to submit them separately and link them with Wikitext.

Affected Wikimedia Project(s)[edit]

This example affects projects: Wikipedia, Wikidata, Wikisource.

Phabricator Ticket[edit]

I can put here the link to Phabricator ticket(s) that involve this topic:
T123456 - (Title / Summary of the ticket)

Submitted By[edit]

--Danny Benjafield (WMDE) (talk) 08:51, 20 November 2023 (UTC)[reply]

Integrate Lexemes to Wiktionary[edit]

Description of issue[edit]

Hello! We need to integrate lexemes into Wiktionary. For example, there is a lexeme in Wikidata that cannot be found using a search engine on the Internet. (d:Lexeme:L600000)

Affected Wikimedia Project(s)[edit]

Phabricator Ticket[edit]

Submitted By[edit]

-- Сергій Липко (talk) 18:52, 26 November 2023 (UTC)[reply]

Hello @Сергій Липко, New year's Greetings to you! Lexemes is indeed a very big topic and I'm excited to see what happens with it in the coming year(s). In regards to your comment, I was able to find a link from Page 1 of Google SERPs to the Lexeme in question (d:Lexeme:L600000) when searching by it's L# or its Lemma (заклепковий), but maybe that's because my search term is so specific? I'd be happy to discuss this further with you, oh and apologies this reply is so late in coming to you! Thank you, -- Danny Benjafield (WMDE) (talk) 12:22, 8 January 2024 (UTC)[reply]
@Danny Benjafield (WMDE) thank you, I also saw it on Google. I believe that lexemes should help Wiktionary, and not just transfer words from Wiktionary to Wikidata lexemes. Wiktionary looks better visually for reading.--Сергій Липко (talk) 01:03, 9 January 2024 (UTC)[reply]
Hi @Сергій Липко, thanks for elaborating further! Do you think the Lexemes functions should be moved / hosted on Wiktionary? And do let us know if you have any ideas or feedback on how Wikidata could be used to enhance or help Wiktionary and your workflows! Thanks again, -- Danny Benjafield (WMDE) (talk) 09:24, 9 January 2024 (UTC)[reply]
@Danny Benjafield (WMDE) I think lexemes should be integrated into Wiktionary as a template, like d:Q6249834 in Wikipedia, or use a Wikifunction to create a sentence.--Сергій Липко (talk) 00:38, 11 January 2024 (UTC)[reply]
Dear @Сергій Липко, I spoke with some of the Wikidata team here and they forwarded me the following information, I hope it is useful to you and your Wiktionary project.

...one missing feature was the ability to access and use the data from Wikidata’s Lexicographical Data on the other Wikimedia projects via Lua modules. This feature has been requested for a long time by editors, and after a test phase on a few Wiktionaries, we are happy to announce that Lua access to Wikidata Lexeme will be enabled on June 21st (2022) on all Wikimedia projects.
Practically, Lua access means that we created some new Lua functions that will allow you to integrate Lexemes, Forms and Senses from Wikidata on any of the pages of any Wikimedia wiki.

Among many possibilities that this feature offers, you will be able to create for example: conjugation or declination tables, stubs of Wiktionary entries, tools displaying the meaning of a word on Wikisource, and many other things, depending on what your project needs.

Until someone on your project writes a Lua module that makes use of these new functions and then uses this module on a page, nothing changes for your project.

In order to use it, people with experience with Lua modules and templates can look at *the documentation [Lexeme Documentation]> listing the available functions*.

You can also have a look at simple example showing the singular and plural forms of an English noun: [Template], [Module] , [Result].

— Léa Lacroix, Wikimedia HyperKitty Mail Archiver 20.06.2022

Further information and discussion can be found at the Wikidata:Wiktionary project page. Kind regards, --Danny Benjafield (WMDE) (talk) 10:55, 22 January 2024 (UTC)[reply]

@Danny Benjafield (WMDE) thank you very much for the information!--Сергій Липко (talk) 23:04, 23 January 2024 (UTC)[reply]
My pleasure. Please let me know if this helps, or if there is no-one available to write Lua module for your Wiki.--Danny Benjafield (WMDE) (talk) 10:15, 24 January 2024 (UTC)[reply]

Wikidata Across Projects[edit]

Description of issue[edit]

I've noticed that Wikidata, as it is currently used, doesn't work well for connecting all the projects. It seems to work pretty well for Wikipedia, where there is often one page per language for each article. However, it is much more complicated to use on Wikibooks, where there may be multiple books that touch on a given subject. Since Wikidata doesn't allow multiple pages on a given project to be linked to the same Wikidata item, or for one page to be linked to multiple Wikidata items, this creates issues. For example, should Wikibooks:Cookbook:Milk be linked to Wikidata:Q8495? Should it link to a separate Wikidata item called "Cookbook:Milk" to create book-level specificity in Wikidata? What if someone wanted to create a book on the dairy industry that also discussed milk—how should that be handled? What if one wikibook connected across multiple languages diverges so much between languages that they are no longer equivalent—how would this be handled in Wikidata?

I don't necessarily have good proposed solutions, especially since I wasn't around when Wikidata was being developed, and I don't necessarily know all the complicated background. But, I think it's important to consider the issues I've raised in the context of Wikidata's core functionality across Wiki projects.

Happy to talk more about this/answer questions!

Affected Wikimedia Project(s)[edit]

Wikibooks, Wikiversity

Submitted By[edit]

Kittycataclysm (talk) 00:47, 29 November 2023 (UTC)[reply]

Dear @Kittycataclysm, thank you for your submission and New year's greetings to you! If I understand the crux of your issue correctly, the problem is on how to link a Wikidata Item that represents a concept, to multiple pages (or in this case, books) that share that concept? Perhaps a Category or other form of collective label? Also, sorry if this reply is so late in coming! Feel free to reply underneath if you have any further thoughts! Thank you again -- Danny Benjafield (WMDE) (talk) 12:15, 8 January 2024 (UTC)[reply]
@Danny Benjafield (WMDE) Thank you for your response! Yes, that is one of the big issues. Linking to categories is a potential solution, but categories at Wikibooks are a little unusual in practice (we have books, subjects, and shelves)—you can check it out here. Additionally, there is the Wikibooks cookbook, which has different conventions from the other books. I'll also refer you to a relevant conversation on the subject currently taking place at wikibooks. Cheers! —Kittycataclysm (talk) 13:08, 31 January 2024 (UTC)[reply]

Comment from en.wikiquote[edit]

Description of issue[edit]

"I personally use WD to search for less-known information which can be used in pages that are currently included in the English Wikiquote. For example I used WD to locate a page on the Hebrew Wikiquote about the 2023 Israel-Hamas war.

I also use this information to start new pages that currently do not have a complementary English Wikipedia article, a practice that some here would like to eliminate, but which is crucial for those of us involved with the #shesaid campaign, since it is well-known that for one reason or another some very deserving women do not have an article on the English Wikipedia. Some women may have an article on say, the German wikipedia, when one is not available on the ENWP. It is possible for determined contributors to extract useful information for building an article from a foreign language wiki, even when they do not speak the language. I use google translate a lot for these purposes.

Unfortunately I am not able to use any of the advanced features available to those with sql access to this database, but I can still use WD in a purely manual fashion as I tried to convey above."

Affected Wikimedia Project(s)[edit]

Phabricator Ticket[edit]

Submitted By[edit]

Original comments found here 02:16, 14 January 2024 (UTC)[reply]

Automated links to Wikipedia[edit]

Description of issue[edit]

On Dutch Wiktionary I made a template that automatically links books/movies/writers/publishers/etc om Wikipedia. For example, {{Wikipedia artikel link|schrijver|Max Jacob}} results in Max Jacob. This part relies only on data imported from petscan.

Wikidata is however used to identify publishers/websites by domain. For example, {{Wikipedia artikel|websitedomein|gutenberg.org}} returns w:nl:Project Gutenberg. In this case, that information is stored in wikt:nl:Sjabloon:Wikipedia artikel/nlwiki-websitedomein-all.*

There's no real issue here, though the scraping process is kinda slow. I need sitelinks+P856 for (depending on the wiki) hundreds or thousands of Q-numbers that Petscan gave me. Example API request. Doing this for 50 Q-numbers at once doesn't work, the JSON get truncated sometimes and is extremely slow to process on the client side. So I'm only getting 10 Q-numbers at a time.

All I need are the sitelinks and P856, but I'm getting a ton of other claims too that I simply discard. https://www.wikidata.org/w/api.php?action=help&modules=wbgetentities has no filter options for claims. Luckily I don't have to run this very often.

* I'm aware of the data: namespace. It doesn't perform any better, can't be kept locally and counts the parsed size as the page size further limiting its usefulness.

Affected Wikimedia Project(s)[edit]

Dutch Wiktionary

Phabricator Ticket[edit]

phab:T243138 from 2020 and phab:T93519 from 2015 seem to cover it.

Submitted By[edit]

Alexis Jazz (talk or ping me) 01:39, 4 April 2024 (UTC)[reply]