Wikidata:Project chat

On this page, old discussions are archived after 7 days. An overview of all archives can be found at this page's archive index. The current archive is located at 2025/08.

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose oldest comment is older than 7 days.

It seems like almost every Shinto shrine has an identical description: Shinto shrine in Japan. Imo this makes them useless and as many shrines share the same name, the prohibition on identical English label and short description really is restrictive. Is there a reason their descriptions are nearly identical? Immanuelle (talk) 21:00, 5 July 2025 (UTC)Reply

For buildings I'd use the location in the description to distinguish them. Use locations people will have heard of, mention a founding date if not unique Vicarage (talk) 05:37, 6 July 2025 (UTC)Reply

@Vicarage would municipality or prefecture be good? I feel something like this Q78321387 would be improved significantly by changing the description to "Shinto shrine in Nishi-ku, Nagoya" Immanuelle (talk) 07:24, 6 July 2025 (UTC)Reply

Descriptions are for people, write them so the casual user with some knowledge of the subject is informed, so neither be too specific or general. That user would know if Shinto is only in Japan (I don't), and how many there are, so whether the location can be general or specific, and whether Japan itself needs to be mentioned. And expect them to be used in combination with the label, so saying Winchester Cathedral is in Winchester is pointless, say its in Hampshire, UK Vicarage (talk) 07:58, 6 July 2025 (UTC)Reply

The main issue that I have with this is the fact that the shrines often have identical names. And with the en label and en short descriptioon combination needing to be unique. This heavily limits labelling ability Immanuelle (talk) 20:57, 6 July 2025 (UTC)Reply

The requirement of uniqueness exist to make you enter enough information so that among those shrines that have identical names a user knows which shrine is meant.

If you would talk with a person who understands something about those shrines about them, what would you say about the shrine besides it's name to help the person understand which of the shrines you mean? That information should be in the description. This might just be the location, but it might also be something more domain specific. ChristianKl ❪✉❫ 09:51, 10 July 2025 (UTC)Reply

I am working on changing a few of them. I think for many shrines they have very notable things such as being part of a certain group. But "Shinto shrine in Japan" is just too generic for being seemingly the default description of all shrines. Immanuelle (talk) 00:48, 16 July 2025 (UTC)Reply

Seems one person is responsible for almost all of this. Did a mass editing that overwrote the unique descriptions around April 2023 and applied descriptions to undescribed items

https://www.wikidata.org/w/index.php?title=Q59282646&oldid=1867070783 Immanuelle (talk) 01:08, 16 July 2025 (UTC)Reply

@Rachmat04 Is there a particular reason you mass applied this generic description? Is there a consensus I am not aware of? Immanuelle (talk) 01:23, 16 July 2025 (UTC)Reply

Hi Immanuelle! Thanks for bringing this up for discussion. At the time I did this, there was no consensus underlying the edits; I did them alone. The basis for making the edits was to complete the empty descriptions in both English and Indonesian. I put the description "Shinto shrine..." because I took the Q from the query involving Shinto shrine (Q845945). I failed to notice that there are some items that have more specific descriptions. I apologize if that makes you confused when exploring them. Let me know if there's anything I can do to fix the mess. Best, ··· 🌸 Rachmat04 · ☕ 04:10, 19 July 2025 (UTC)Reply

@Rachmat04 I wrote a script that replaced these descriptions with a similar one derived from the prefecture, see this one Taka Tenjinsha (Q11669115). It just checked every located in the administrative territorial entity (P131) property to see if it was an instance of (P31) prefecture of Japan (Q50337), and ran recursively until it found a prefecture and skipped it.

Would you want me to modify and run it for the Indonesian descriptions of "kuil Shinto di Jepang" to change them to something more descriptive too? I would need a basic template of how you would say "Shinto shrine in Shizuoka Prefecture, Japan" in Indonesian. Immanuelle (talk) 17:27, 19 July 2025 (UTC)Reply

That would be very helpful. For Indonesian, you can use "kuil Shinto di Prefektur Shizuoka, Jepang". ··· 🌸 Rachmat04 · ☕ 08:39, 20 July 2025 (UTC)Reply

@Rachmat04 okay so I ran it. It seems to be working. It might be good to look at this for other languages too. Although I am guessing those descriptions were done by other users. Immanuelle (talk) 06:08, 21 July 2025 (UTC)Reply

Kobimine Shrine (Q11447922) has a canned Ukrainian description "синтоїстське святилище в Японії" Immanuelle (talk) 06:09, 21 July 2025 (UTC)Reply

This one seems a lot harder, just looking at Ukrainian grammar. Since it would require editing the name of the prefecture to indicate location. @Renamerr Do you have any guidance? Immanuelle (talk) 06:42, 21 July 2025 (UTC)Reply

You were the one to add the Ukrainian descriptions, althoug I do not think they are nearly as common Immanuelle (talk) 21:07, 21 July 2025 (UTC)Reply

@Renamerr I just decided to attempt to rename some of them. I apologize if I got the cases wrong, but that kind of shrine description caused a lot of problems with the description uniqueness constraints. Immanuelle (talk) 05:01, 30 July 2025 (UTC)Reply

Remember if any one of them is wrong with Ukrainian you can easily just do a search for all the ones with that identical description and use quickstatements to fix it. I have a description for each prefecture that I replaced them with. Immanuelle (talk) 05:21, 30 July 2025 (UTC)Reply

As for the labels I think if we somehow figured things out, the conversion from Indonesian to Ukrainian would be the low hanging fruit of the conversion once we establish a proper protocol, since hard shrines are mostly absent from this

https://query.wikidata.org/#SELECT%20%3Fitem%20%3FidLabel%20%3FukDescription%20WHERE%20%7B%0A%20%20%3Fitem%20wdt%3AP31%20wd%3AQ845945.%20%20%23%20instance%20of%20Shinto%20shrine%0A%0A%20%20%3Fitem%20schema%3Adescription%20%3FukDescription.%0A%20%20FILTER%28LANG%28%3FukDescription%29%20%3D%20%22uk%22%29%20%20%23%20has%20Ukrainian%20description%0A%0A%20%20%3Fitem%20rdfs%3Alabel%20%3FidLabel.%0A%20%20FILTER%28LANG%28%3FidLabel%29%20%3D%20%22id%22%29%20%20%23%20has%20Indonesian%20label%0A%0A%20%20FILTER%28NOT%20EXISTS%20%7B%0A%20%20%20%20%3Fitem%20rdfs%3Alabel%20%3FukLabel.%0A%20%20%20%20FILTER%28LANG%28%3FukLabel%29%20%3D%20%22uk%22%29%20%20%23%20lacks%20Ukrainian%20label%0A%20%20%7D%29%0A%7D%0AORDER%20BY%20%3FidLabel%0A%0A Immanuelle (talk) 00:06, 2 August 2025 (UTC)Reply

@Renamerr do you have any insights on Ukrainian and Russian shrine names? This is gonna be the last time I will tag you. Immanuelle (talk) 01:48, 2 August 2025 (UTC)Reply

@Rachmat04 I wrote a similar script that converts English language Shrine names to Indonesian. Ran it on about 30 Shrines so you can see the results here https://query.wikidata.org/#SELECT%20%3Fitem%20%3Flabel_en%20%3Flabel_id%20WHERE%20%7B%0A%20%20%3Fitem%20wdt%3AP31%20wd%3AQ845945.%0A%20%20%3Fitem%20rdfs%3Alabel%20%3Flabel_id%20FILTER%20%28LANG%28%3Flabel_id%29%20%3D%20%22id%22%29.%0A%20%20OPTIONAL%20%7B%20%3Fitem%20rdfs%3Alabel%20%3Flabel_en%20FILTER%20%28LANG%28%3Flabel_en%29%20%3D%20%22en%22%29%20%7D%0A%7D%0AORDER%20BY%20%3Flabel_id%0A

Atsuta Shrine becomes Kuil Atsuta, etc

In your view would something like this be a positive thing to run? Immanuelle (talk) 23:35, 22 July 2025 (UTC)Reply

@Immanuelle: I can see that the translation is pretty good, but there might need to be some minor tweaks after you complete the mass edit. I can help with that afterwards. ··· 🌸 Rachmat04 · ☕ 05:22, 23 July 2025 (UTC)Reply

@Rachmat04 I applied it to an additional hundred or so. Considering this operation will add over 20,000 labels I think I want to be more sure of things. Immanuelle (talk) 10:50, 24 July 2025 (UTC)Reply

I made Jingu and Taisha into Kuil Agung like Atsuta Jingū (Q482065) Immanuelle (talk) 11:00, 24 July 2025 (UTC)Reply

The program just omits anything that is Daijinja or Daijingu or Tenmangu or Hachimangu. Immanuelle (talk) 11:00, 24 July 2025 (UTC)Reply

Hi @Immanuelle: Sure, let's get right to it. I'll help spot-check for minor corrections afterwards. ··· 🌸 Rachmat04 · ☕ 23:37, 24 July 2025 (UTC)Reply

@Rachmat04 I am running it now. There are currently around 4,000 labelled Shrines. I think you will probably have plenty of time to look over the shrine names.

btw have you heard of any project that could do something like just algorithmically display the Indonesian names without mass copying? Since across pretty much all languages, you just need to process the romaji in pretty regular ways to get a label in every language. It would help a lot with error correction, since only the english label (or maybe the Kana reading) would need to be edited to fix errors. Immanuelle (talk) 22:28, 25 July 2025 (UTC)Reply

I decided to put off more for a bit longer to try to check some of the Shrine names for English accuracy. Will hopefully continue soon. Do you know other people who would want to help with Shrine labels in their languages? Immanuelle (talk) 23:22, 25 July 2025 (UTC)Reply

I do not know yet who would be interested to these subjects. If you have a long-term plan to fill the local language labels in Indonesia, I can help to inform some users I know. ··· 🌸 Rachmat04 · ☕ 07:04, 26 July 2025 (UTC)Reply

@Rachmat04 For Indonesian my plan would be just to end with a full conversion of all the easy shrine names and maybe kami names. I have noticed a potential issue. Does Aichi Gokoku Shrine (Q4696584) work well. Keep in mind the idea is that a Gokoku Shrine is a type of Shinto shrine, so this is the one for Aichi Prefecture.

Doing non-automated label imports is definitely beyond my abilities or interest. I am not learning Indonesian, I just came across a situation where adding Indonesian labels like this was good. Immanuelle (talk) 07:58, 26 July 2025 (UTC)Reply

I would expect that pretty much every kami name can just be imported verbatim? I would think this would be a use case for the mul label, but apparently that is not the case. Immanuelle (talk) 08:58, 26 July 2025 (UTC)Reply

@Rachmat04 if I were to apply this to Japanese Buddhist temples would "Anpuku-ji Temple" be properly turned to "Wihara Anpuku-ji"? Immanuelle (talk) 20:23, 30 July 2025 (UTC)Reply

How would I do Ninety-Nine Ōji Shrines (Q3200280), I think this one is an issue Immanuelle (talk) 22:30, 30 July 2025 (UTC)Reply

I can make sure that Aichi Gokoku Shrine (Q4696584)'s Indonesian label is good. And, I added Indonesian label to Ninety-Nine Ōji Shrines (Q3200280). I'm not sure if there is a special name for this in Indonesia, but I added it based on the English and Japanese names.

For the name of the deity, I believe using a verbatim name is a wise choice to align their name with appropriate name terms, particularly in Indonesian. However, I haven't come across a similar or translation name in Indonesian dedicated to the name of a Japanese god.

For "Anpuku-ji Temple", does the suffix "-ji" indicate the translation of "temple"? If so, you can simply use "Anpuku temple". Other than that, I'm not sure if this can be translated as "kuil" or "wihara", depending on the context. ··· 🌸 Rachmat04 · ☕ 00:36, 31 July 2025 (UTC)Reply

What context would Kuil vs Wihara be better? My main concern is that I would not want Shinto shrines and Buddhist temples to be labelled as the same thing.

-ji indicates temple, but it is one of a few different suffixes that all indicate a temple. To my knowledge, unlike jinja for shrine, -ji is not independent and temples are called "Tera" when it is not a part of a temple name. Immanuelle (talk) 00:40, 31 July 2025 (UTC)Reply

@Rachmat04 so I think with that structure of temple names it would be good to keep -ji, other common suffixes are -an and -do. Immanuelle (talk) 01:09, 31 July 2025 (UTC)Reply

I'm gonna name them Wihara for now. Will do it with quickstatements when it starts working again Immanuelle (talk) 02:53, 31 July 2025 (UTC)Reply

All the shrines I had planned are done. Tmeples in progress. Immanuelle (talk) 20:00, 31 July 2025 (UTC)Reply

I understand that the "Ampuku-ji Temple" is primarily intended for Buddhists. Therefore, it would be more appropriate to use the term "wihara" instead of "kuil" in this context.

I also second to retain the suffix "-ji" and similar designations in the Indonesian labels for now. However, if an Indonesian Wikipedia article later adopts a local name or similar designation, we can adjust the labels in Wikidata accordingly in the future. Thanks, ··· 🌸 Rachmat04 · ☕ 03:21, 1 August 2025 (UTC)Reply

@Rachmat04 I imported kami names en masse. Here are the few ones I tried to do with words can you check them Eighty Gods (Q65249011), Nine War Gods (Q71133194), Three Goddesses of Munakata (Q10948069), Three Pioneer Kami (Q402052) Immanuelle (talk) 22:20, 1 August 2025 (UTC)Reply

All good! Thanks. ··· 🌸 Rachmat04 · ☕ 03:40, 2 August 2025 (UTC)Reply

btw have you heard of any project that could do something like just algorithmically display the Indonesian names without mass copying? Since across pretty much all languages, you just need to process the romaji in pretty regular ways to get a label in every language. It would help a lot with error correction, since only the english label (or maybe the Kana reading) would need to be edited to fix errors.

I have not found it outside or within the Wikimedia projects. However, if the use of the Kana alphabet in Wikidata is widespread, I believe it might help make this happen someday. ··· 🌸 Rachmat04 · ☕ 07:11, 26 July 2025 (UTC)Reply

Yeah that would be good especially with other scripts. I recently learned that cyrillization of Japanese (Q4400677) tends to be pretty different than the Hepburn system. Using the kana names could pretty straightforwardly represent shrine names, with a simple program that places "Shrine" or whatever variant is used in the language at the front or back depending on language word order.

A language could have a standard representation of Taisha, Jinja, Jingu, Daijinja, etc. And people could edit the protocol directly, if say the Russian community decides that Daijinja and Taisha should be represented the same. An opinion I disagree with, but do not have a good case for. Immanuelle (talk) 10:30, 26 July 2025 (UTC)Reply

Unfortunately while some people are working on this it does not appear to be anything people are working on on wikidata Immanuelle (talk) 04:40, 30 July 2025 (UTC)Reply

forensic autopsy (Q21402966) and inquest (Q6036832) should probably be merged. It doesn't work because of a Japanese conflict. Utfor (talk) 03:13, 25 July 2025 (UTC)Reply

These are not equivalent items and should not be merged. — Huntster (t @ c) 08:00, 25 July 2025 (UTC)Reply

Agreed here. Totally different things. English article en:Inquest explicitly says that an Inquest sometimes involves an autopsy but not always. Immanuelle (talk) 09:31, 25 July 2025 (UTC)Reply

more simply: just because the entity is included within another in most wikipedia project doesn't mean it should be merged. Circeus (talk) 00:34, 29 July 2025 (UTC)Reply

I recently saw a button pop up on this edit https://www.wikidata.org/w/index.php?title=Q670049&oldid=2384469581 saying I could mark it as patrolled. I clicked it. Is this a thing I am supposed to habe permission to do? Immanuelle (talk) 08:52, 26 July 2025 (UTC)Reply

We do grant patrolling permissions to autoconfirmed users: Special:ListGroupRights#autoconfirmed. --Matěj Suchánek (talk) 08:09, 27 July 2025 (UTC)Reply

Currently there is a property biography at the Bundestag of Germany - data type URL. I realized External identifier could be used instead, because these URLs contain a unique identifier and can be resolved similar to how X numeric user ID works (i.e. the website is called with a URL containing the ID, the website then redirects to the 'final' URL).

Example Angela Merkel:

• Current value: "https://www.bundestag.de/webarchiv/abgeordnete/biografien19/M/merkel_angela-521968 "
• Could be replaced with ID: "521968"
• Formatter URL: https://www.bundestag.de/abgeordnete/biografien/521968 -> resolves to the same URL (current value)

I don't know what's the correct procedure here, so I wanted to ask before doing anything.

• Should I propose a new property that will replace the other one?
• Should I propose a new property that will be used along the other one? (similar to how X (Twitter) username and X numeric user ID are both used)
• Should I propose the existing property to be changed? (How would I do that?)
• How is migration of existing data usually handled in such cases?

454c0d4b4788cc703c690fd56cfdfae8 (talk) 14:09, 26 July 2025 (UTC)Reply

New property proposal is best, to replace the old one if it really does cover everything the old one does. Changing the existing one is tough for several reasons. ArthurPSmith (talk) 20:30, 28 July 2025 (UTC)Reply

Thanks for your answer.

I realized that this website went through a few iterations. The latest iteration was active for quite some time now, so all newer URLs follow the same pattern, but there are also older pages that don't include such IDs and have different URL patterns.

So I guess one could introduce a separate ID property for the newer pages as I described and leave the rest as is, but that doesn't seem worth the trouble and added complexity. So I'll leave it like that. It shouldn't be too hard to parse 2-3 different URL formats when consuming this data.

But thanks for the feedback. That will probably be helpful in future cases I might encounter. 454c0d4b4788cc703c690fd56cfdfae8 (talk) 21:13, 28 July 2025 (UTC)Reply

Has anyone rate this item and sub, they have almost no independent sources, and why are their label capitalized? Anonymous (talk) 17:46, 26 July 2025 (UTC)Reply

@Henrydat the website presents it as capitalized that way https://groupenoesis.com/ Immanuelle (talk) 20:42, 26 July 2025 (UTC)Reply

Thanks. If you see closely they are only capitalized in heading, they are Groupe NOESIS in the body. I searched randomly on pappers.fr all names are capitalized. @EvanRDF What do you think? Anonymous (talk) 01:21, 27 July 2025 (UTC)Reply

groupenoesis.com actually wrote Johann SPONAR, maybe they have a purpose for the capitalization. I will use qualifier subject named as (P1810) for this case. Anonymous (talk) 09:55, 27 July 2025 (UTC)Reply

Hi, thank you for the feedback.

Yes, capitalization does matter in the case of Groupe NOESIS, this is how the group presents itself in its official branding. However, I fully understand if Wikidata conventions require standard capitalization in the main label.

The same applies to Johann SPONAR; the family name is capitalized on the official website. If needed, I’m happy to adjust the label and add a qualifier for that as well.

Let me know if any further changes are recommended. EvanRDF (talk) 20:22, 27 July 2025 (UTC)Reply

@EvanRDF: There are requests for deletions (WD:RFD) for several items that you created, including the one above, at Wikidata:Requests_for_deletions#Q135443693. — Dcflyer (talk) 01:32, 28 July 2025 (UTC)Reply

The lack of independent sources makes it difficult to identify the subject. You can add them with property described at URL (P973). I don't identify the identifiers you added that are relevant to notability but they would be helpful. Sorry for bringing up the item you created as an example here. Anonymous (talk) 14:37, 28 July 2025 (UTC)Reply

Hi! Yesterday, i created my first page about Fitia but, when i entered today and tried to search the page to add some topics that i forgot, the page wasn't on my contibutions. I want to know the reason why the page was deleted. Thank You! SebastianLT (talk) 18:31, 26 July 2025 (UTC)Reply

Relevant items: Q134884428 (Fitia.app), Q135469793 (SebastianLT), Q134884657 (Fitia.app), Q134959060 (SebastianLTI). CC deleting admins @Madamebiblio, WikiBayer

Notwithstanding your claim, this appears to be your fourth creation, and third account.

I have placed the standard warning on your user page, including the advice to read Wikidata:Guide to requests for undeletion. Bovlb (talk) 23:27, 26 July 2025 (UTC)Reply

Please read Wikidata:Notability WikiBayer (talk) 04:10, 27 July 2025 (UTC)Reply

Carol Burnett on screen and stage - Wikidata Carol Burnett - Wikidata This reflects the same person Half Goofy 2 (talk) 05:17, 27 July 2025 (UTC)Reply

It somewhat does, but not completely. Notice there are two pages on enwiki: w:Carol Burnett on screen and stage and w:Carol Burnett. --Matěj Suchánek (talk) 08:12, 27 July 2025 (UTC)Reply

Proposals to merge certain Wikipedia articles should be discussed on that Wikipedia version, on English Wikipedia in this case. Samoasambia ✎ 01:20, 31 July 2025 (UTC)Reply

Can I edit tag such as Reverted in some ranges? Anonymous (talk) 10:38, 27 July 2025 (UTC)Reply

Your question is unclear; please rephrase it.

And please fix your sig so that it doesn't mislead others. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:46, 27 July 2025 (UTC)Reply

No problem. They are not that important but there is always a reason for such things. Anonymous (talk) 12:59, 28 July 2025 (UTC)Reply

Please have henrydat visible in comments Vicarage (talk) 13:30, 28 July 2025 (UTC)Reply

It will be in new article. Anonymous (talk) 14:39, 28 July 2025 (UTC)Reply

The issue is your "sig" (your signature at the end of talk page posts; which names you as "Anonymous"), not article content. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:27, 28 July 2025 (UTC)Reply

Maybe we don't understand together. Anonymous (talk) 15:39, 28 July 2025 (UTC)Reply

I have brought this matter to the attention of the administrators. Wikidata:Administrators'_noticeboard#c-Henrydat-20250728180900-Report_concerning_User:Henrydat, as it smells fishy. Vicarage (talk) 18:33, 28 July 2025 (UTC)Reply

Hello everyone,

I've been researching recently regarding the distinction between "monolingual dictionary" and "explanatory dictionary", and I'd like to share what I found:

1. I found the term "explanatory dictionary" is a little more specific or niche, even instances like Oxford University Press rarely uses the term.

2. I found the terms "explanatory dictionary" and "monolingual dictionary" are often used interchangeably, however, it's never explicitly being said if they are equivalent to each other. Even Hartmann and James themselves who wrote the Dictionary of Lexicography never explicitly stated one of them is the definition of another. The quote itself basically stated.

"The monolingual general dictionary ... is therefore also often called [a] defining dictionary or explanatory dictionary"

Which, they used the wording of "is therefore also often called" rather than "is", thus, they are associations, not equivalences. I also found this statement from the [2] of the Enwiki version of the explanatory dictionary page stating.

"In a monolingual dictionary both the entry words and their definitions or meanings are given in the same language. They may also be called explanatory dictionaries, although the latter term has assumed a special signification. The term monolingual refers to the language only irrespective of the information given in it. Some dictionaries may just give word lists and their meanings and may be monolingual dictionary. The explanatory dictionary, on the contrary, gives more information about different aspects of the lexical unit-script, pronunciation, grammar, meaning, etymology and profuse illustrations. These dictionaries are meant for the native speakers and "the target set for creating Explanatory Dictionary aims at native speakers with a view to explain one or the other lexical items which might be half known or totally unknown to them" (Srivastava 1968. 124) Most of the bigger dictionaries in all the well known languages are explanatory in nature."

Which indicates a distinction between them. Because of that, I think monolingual dictionaries are commonly understood as the structure of the dictionary whereas only 1 language is present, while explanatory dictionaries are about the depth.

Proposal: I propose a creation of a new separate item regarding the monolingual dictionary and removing it as an alias of explanatory dictionary on Wikidata. Also an overhaul of Wikipedia pages that included monolingual dictionary as equivalence. Because, when users are looking and searching for the monolingual dictionary, they could get redirected into the explanatory dictionary page itself or they thought it will be the same thing, which, could be misleading and fatal, since they are not the same thing.

Thoughts?

Sincerely, thanks.

Nunoguevara (talk) 12:01, 27 July 2025 (UTC)Reply

"fatal" really? These seem close enough to me to not require disambiguation, especially if the associated wikipedia pages don't distinguish them. If you do create a new item you probably should link the two together with a property indicating they are different, or else they are liable to be recombined. ArthurPSmith (talk) 20:33, 28 July 2025 (UTC)Reply

You're right, perhaps "fatal" is a little bit too much.

However, from what I've observed, perhaps there is a potential contradiction or oversimplification on the related English Wikipedia page itself, because the cited source stated if monolingual dictionary and explanatory dictionary have assumed different significations (Srivastava 1968. 124). Also, in the same source it's stated if the explanatory dictionary is about the content depths, while monolingual dictionary refers to the use of single language.

In conclusion, I believe both may often overlap each other, but I also believe there is possible conceptual distinction between them.

I appreciate your feedback, thank you. Nunoguevara (talk) 06:50, 29 July 2025 (UTC)Reply

Hello Wikidata community,

I would like to request the addition of a sitelink to the following Wikidata item:

- Item: Q130396691 - Site: English Wikipedia (enwiki) - Page: Draft:Idris Abbasov

This is to link the existing Azerbaijani Wikipedia article “İdris Abbasov” with its English draft version on Wikipedia.

Thank you very much for your assistance!

Best regards, Ilyas Deli İlyas Deli (talk) 12:38, 27 July 2025 (UTC)Reply

 Not done, per Wikidata:Notability:

To be valid, a link must not be a talk page, page in MediaWiki namespace, special page, file, translations page, page in User or Draft namespace, page used by LiquidThreads (i.e. page in Thread and Summary namespace), page used by Structured Discussions (i.e., page in Topic namespace), subpage of Portal namespace, or any page that is intended for TemplateStyles (i.e. page names that end with ".css").^{[1][2][3][4][5]} Note that a single Wikimedia page cannot have more than one sitelink in Wikidata. It is permitted for a sitelink to point to a redirect (although the software intentionally makes this difficult),^[6][7] but such a link will not count towards establishing notability.

TLDR: You can't add drafts as sitelinks.

(Pinging @İlyas Deli) DinhHuy2010 (talk) 12:52, 27 July 2025 (UTC)Reply

Has any thought been given to enabling the Twinkle gadget on this project? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:53, 27 July 2025 (UTC)Reply

Bonjour comment lie-t-on un lien wikipédia à un article wikidata? Comment exploiter une photo Wikimédia commons dans un article wikidata EBENEZER ESDRAS (talk) 19:53, 27 July 2025 (UTC)Reply

I think a good feature on wikidata for avoiding redundancy would be to somehow automatically generate labels based on a formula. So if there are errors then they can be easily fixed and automatically propagate to all languages. I see some talk about it in this Wikidata:Requests_for_comment/Mass-editing_policy but I am a bit out of the loop about some of this database performance discussion. Immanuelle (talk) 01:33, 28 July 2025 (UTC)Reply

This is what Abstract Wikipedia will do. GZWDer (talk) 04:58, 28 July 2025 (UTC)Reply

@GZWDer when is this coming out? Is the intention to integrate this with wikidata somehow? Or is it an independent project? Immanuelle (talk) 06:48, 28 July 2025 (UTC)Reply

Have a look at https://en.wikipedia.org/wiki/Abstract_Wikipedia, Clearly some people don't like it, but work is being done, Vicarage (talk) 07:10, 28 July 2025 (UTC)Reply

That sounds like a cool idea. But more ambitious than what I was hoping for. Immanuelle (talk) 00:37, 29 July 2025 (UTC)Reply

Hello, this message is to notify that Chealer has been nominated for a global ban at m:Requests for comment/Global ban for Chealer. You are receiving this notification as required per the global ban policy as they have made at least 1 edit on this wiki. Thanks, --SHB2000 (talk) 11:20, 28 July 2025 (UTC)Reply

Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2025-07-28. Missed the previous one? See issue #689.

Discussions

• Open request for adminship: Aqurs1 (RfP scheduled to end after 31 July 2025 16:35 UTC)
• New requests for permissions/Bot: THEbotIT 3 - New functional aspect to automatic creation of items describing the articles of Paulys Realencyclopädie der classischen Altertumswissenschaft (RE). We want to model now the articles, which amends the main articles, as those information where suppressed so far.

Events

• Upcoming events:
  • Wikidata's 13th birthday decentralized events will take place in October and November 2025. Feel free to browse the documentation pages to learn how to organize an event in your area, get funding, and get in touch with other organizers. Help translate the documentation pages into your language.
  • COSCUP 2025 (Q134950534) OpenStreetMap x Wikidata Track will be held at National Taiwan University of Science and Technology (Q699543) on August 9-10.
  • Wikimania starts next week August 6 through August 9. Check out the Wikidata related session in the program and start marking your preferred Wikimania sessions (⭐/like) on your mobile apps or calendars. If you are joining online to watch live stream and use the interactive features, please register on eventyay through wikimania.org. Note also the Wikidata meetups organised outside the official conference hours.
• Past: WikiCon Brasil 2025 happened in person in Salvador (Q36947) including a technical session with two Wikidata-focused presentations (in Portuguese)

Press, articles, blog posts, videos

• Blogs:
  • Making Question-Answering Systems Smarter with Knowledge Graphs Using FrOG: A Wikidata Research Fund 2024 Highlight - How can large language models become more accurate using structured knowledge? A research team from Universitas Indonesia and WU Vienna explored this through FrOG, a framework that integrates Wikidata into question-answering language model. This research is supported by Wikimedia Indonesia through the Wikidata Research Fund 2024 program.
  • Wikidata’s next leap: the open database powering tomorrow’s AI and Wikipedia By Lydia Pintscher

• Presentations: O herbário da Universidade de Coimbra na Wikidata (Using Wikidata in Natural History Collection Management, in Portuguese)
• Papers: Wiki-Quantities and Wiki-Measurements: Datasets of quantities and their measurement context from Wikipedia - Researchers developed two large, validated datasets; Wiki-Quantities and Wiki-Measurements, from Wikipedia and Wikidata to improve automated extraction of quantitative data and its context using natural language processing techniques. By Göpfert et al., (2025)
• Videos: Wikidata:The shadow power behind Wikipedia and AI

Tool of the week

• Flashback Fiesta - is a trivia game that challenges players to guess the year of historical events using data from Wikidata.

Other Noteworthy Stuff

• The Wikidata:WikiProject Personal Pronouns drafted a new Wikidata Personal Pronouns Policy, using this recent RFC as a basis. It's the first time a policy on this topic has been proposed, and the Wikidata Living People Policy served as a reference. Feedback is encouraged and appreciated.
• The modeling of agrégation ("the most competitive and prestigious examination for civil service in the French public education system" according to w:en:Agrégation) has been reviewed in various aspects: a summary is available in d:Talk:Q397610#Modeling agrégation. Suggestions are welcome.
• Wikimedia Deutschland is inviting further feedback on the Mobile Editing Experience prototype (currently just a design file so not everything is clickable). Please follow the instructions below and share your thoughts at Wikidata talk:Usability and usefulness/Item editing experience/Mobile editing of statements:
  • Add "business woman" as an occupation
  • Add a start date to the relationship with A$AP Rocky and provide a reference
  • Find the place of birth (Saint Michael) and open that page
  • Add the coordinate location for Saint Michael

Newest properties and property proposals to review

• New General datatypes: ‎operating cost (estimated or average ongoing recurring cost for operating or using an object)
• New External identifiers: Ukrainian Memorial person ID, Portal of united hromadas of Ukraine ID, Portal Decentralization hromada ID, Facebook image ID, archieven.nl creator ID, ‎Elonet company ID, Embryo Project Encyclopedia ID, ‎Film Atlas ID, Klimadashboard.de region ID, ‎Knowledge Graph for Irish History person ID, myCast person or character ID, ‎nasljerseys.com player ID, ‎speedrun.com level ID, ‎FBref competition ID, ‎FBref match ID, ‎parlament.fyi person ID, Swimcloud swimmer ID
• New General datatypes property proposals to review:
  • organizational chart (image that displays the structure of this organization or government agency and the relationships and relative ranks of it's parts and positions/jobs)
  • Source Shrine (The shrine that the gods of this shinto shrine came from through Bunrei and Kanjo)
  • botanical photographs (a distinctive image of a flower, inflorescence, or a similar reproductive structure for this taxon)
• New External identifier property proposals to review: Deaf Movie Database language ID, Deaf Movie Database genre ID, Deaf Movie Database country ID, Swiss Films person ID, My Abandonware company, Encyclopedia of Indianapolis ID, Database dei fondi musicali toscani ID, NeoDB Movie ID, Serbian settlement ID, c64.cz game ID, NuGet package, Swiss Films company ID

You can comment on all open property proposals!

Did you know?

• Query examples:
  • Church buildings in Sweden on OpenStreetMap with links to Wikidata, but without the inverse link.
  • Tennis tournament titles won by specific player (source)
  • BarChart of chemical compound identifiers in Wikidata (source)
• WikiProject Highlights: WikiProject Sweden - A project to centralize, expand, and translate Sweden-related data on Wikidata while supporting the Swedish contributor community.
• Showcase Items: Harry Potter and the Philosopher's Stone (Q43361) - 1997 novel by J. K. Rowling
• Showcase Lexemes:ножницы (L9436) - Russian noun (nɐˈʐnʲitsɨ) meaning "cutting tool", "window hardware mechanism", or "ski position with split tips"

Development

• Mobile statement editing:
  • We finished a first version of formatting references (phab:T396098); qualifiers (phab:T396099); various data types (phab:T394888, phab:T394890, phab:T394904, phab:T394907); and multiple statements for one property (phab:T396637)
  • We enabled the new mobile editing experience on beta Wikidata so you can now try the very rough version there and follow along with development
• Wikibase REST API: We finished the simple Property prefix search endpoint and it will go live in the next days (phab:T397838)
• Additional APIs: We are working on a prototype for GraphQL to see if that is a going to be helpful for accessing Wikidata's data (phab:T399452)

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.

Weekly Tasks

• Add labels, in your own language(s), for the new properties listed above.
• Contribute to the showcase Item and Lexeme above.
• Govdirectory weekly focus country: Kenya
• Summarize your WikiProject's ongoing activities in one or two sentences.
• Help translate or proofread the interface and documentation pages, in your own language!
• Help merge identical items across Wikimedia projects.
• Help write the next summary!

· Previous issue · Full report · Unsubscribe · JosefAnthony talk · MediaWiki message delivery (talk) 14:54, 28 July 2025 (UTC)Reply

The Jackdaw Inn (Q26321342)

There is an issue at The Jackdaw Inn, Denton on Commons, where its location is showing as being in Texas, USA, not the UK. Can't work out where this info is coming from, but suspect it is down to Wikidata. ̴̴ Mjroots (talk) 15:27, 28 July 2025 (UTC)Reply

Fixed (location (P276) was set to Denton (Q128306): city in Denton County, Texas, United States not Denton (Q5259579): village in Denton with Wootton, Dover, Kent, England). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:32, 28 July 2025 (UTC)Reply

Thank you. ̴̴ Mjroots (talk) 05:29, 29 July 2025 (UTC)Reply

Hi I have been following and engaged in discourse surrounding the infrastructural issues around Wikidata. The core issue is: Wikibase was not designed from the beginning nor tested before launch to handle >10 bn statements.

The Wikidata team is not going to rewrite Wikibase nor is there an easy solution to the problems with Blazegraph.

So we in the community have to adapt to the current reality: We cannot have all the worlds knowledge or metadata about it in ONE wikibase nor in Wikidata. Thus we are forced to federate between multiple subgraphs each hosted in their own Wikibase.

Migration of all WikiCite scientific items even if we start today is going to take years because Wikibase is very slow when importing new items.

So the questions at hand given this reality is:

1. What to include in the split?
2. Is https://www.wikibase.cloud/ a good place to host it?

• If not: Who will fund and host the new WikiCite Wikibase?

1. Who wants to lead the work and is the Wikidata team willing to help?

My suggestion for split strategi is: all items not currently used in another project via CiteQ 2025-12-31 should be moved to a new Wikibase

To successfully move the millions of items we need:

1. a working group
2. a clear plan
3. centralized issue handling
4. new development efforts
   1. batch software to move a set of items from one Wikibase to another, maybe based on wikibase-sdk or WikibaseIntegrator?
5. go-ahead from the Wikibase Cloud team if the Wikibase is to be hosted there (it will need more resources than most Wikibase installations already there)

If we start today my guess is we could be done in 4 years. Migration will take at least 2 years if the software runs without pause.

The outcome of this work is going to affect about the same people and projects as the recent graph split did. So9q (talk) 11:00, 29 July 2025 (UTC)Reply

Properties now can have a value of type Item (e.g. stated in). How will you handle that this Item be found in more than one (particularly, not the current) Wikibase? --Egon Willighagen (talk) 11:29, 29 July 2025 (UTC)Reply

Federation done properly would be great. It's not there yet. That's what needs to happen first here. The essential missing element is being able to use an item from another Wikibase as a value (ideally also to be able to use properties from other Wikibase's - right now there seems to be only the choice of having your own properties or entirely depending on another Wikibase for your properties, which is not great either). That will require significant planning and discussion (should this be a separate datatype or we allow for two versions of the item datatype? How would caching and syncing be done?) and then development work in the guts of Wikibase. But to truly make a Wikibase ecosystem I think it's necessary. And there are a lot of other pieces of Wikidata that could be pushed off to a truly federated wikidataverse if this could be made to work. ArthurPSmith (talk) 14:13, 29 July 2025 (UTC)Reply

Lingua Libre appears to have something that gets part of the way there - see https://lingualibre.org/wiki/Q1136370 and the place of residence there. But in my opinion that is not a complete solution for incorporating external entities and that a complete solution is needed to support separating scientific literature into its own Wikibase. (What is missing? At least the ability to have both local and external entities as values for the same property and the ability to do completion on external entities.) Peter F. Patel-Schneider (talk) 14:27, 29 July 2025 (UTC)Reply

That's using an external-id datatype for the Wikidata item. Do you know what it's doing under the hood to pull in the label and description? ArthurPSmith (talk) 15:00, 29 July 2025 (UTC)Reply

There is custom JavaScript code for this pulled in by the standard JS page (common.js somewhere, I think). Peter F. Patel-Schneider (talk) 16:53, 29 July 2025 (UTC)Reply

@ArthurPSmith Check the JS code used in Lingua Libre here. —Ismael Olea (talk) 15:38, 30 July 2025 (UTC)Reply

I could be content with a linking property for authors that allows me to search Wikidata. I never got that to work in wikibase.cloud. Interesting that someone already did some nice integration work. 😀 So9q (talk) 17:21, 29 July 2025 (UTC)Reply

It does not address the problem that a Wikibase needs to have properties that are technically able to to link to external and internal Items. Neither is currently possible. --Egon Willighagen (talk) 05:42, 30 July 2025 (UTC)Reply

There was a prototype for this that was slightly trialled, but it never really went anywhere. And searching around on the internet, there isn't even a really nice place to go to to point and say that "this is federated properties".

TLDR is that it allowed you to have a wikibase, and directly use properties from wikidata.org. The next step was to allow wikidata.org and also local wikibase properties, but the trial never went that far.

I got part way through replying here, and decided to go and write it all up in a little blog post https://addshore.com/2025/08/what-was-wikibase-federated-properties/

·addshore· ^{talk to me!} 10:25, 1 August 2025 (UTC)Reply

Why do you say that the split will take 2 years of dedicated computation? Peter F. Patel-Schneider (talk) 16:51, 29 July 2025 (UTC)Reply

it's a back of the napkin calculation based on the numbers I heard others report. It takes about 1s to create a new item. 1s * 50 million=578 days so about 2 years for the batch to finish for all scientific articles. So9q (talk) 17:19, 29 July 2025 (UTC)Reply

Is this 1s compute time or elapsed time in some interface? If the latter then the time is likely a large overestimate of the amount of time that it would take to copy items over from Wikidata. Given that Wikidata supports hundreds of edits per minute I suspect that the actual compute time is much less than 1s. Peter F. Patel-Schneider (talk) 17:23, 29 July 2025 (UTC)Reply

Perhaps you are right. I have not done any testing. How would you do it? Download the dump? Download the mariadb xml dump? We don't have any dumps that make it dead simple to setup a copy of Wikidata fast. See https://www.wikidata.org/wiki/Wikidata:Project_chat#Why_you_should_probably_not_contribute_to_Wikidata_(before_the_infrastructure_has_been_fixed) So9q (talk) 17:29, 29 July 2025 (UTC)Reply

If any sort of migration would happen, it's certainly not going to be via making individual edits (or it shouldnt).

With a little effort, we could fairly easily just carve the whole of Wikidata content in half, based on some decided split, and then sew it back together again where needed, in terms of mapping across instances.

However i'd argue that beyond the "blazegraph is struggling" topic, most of the other issues are actual social ones, that liekly to need tehcnical intervention and features to improve on, but likely not an actually split of the data in wikibase in real terms. ·addshore· ^{talk to me!} 10:29, 1 August 2025 (UTC)Reply

So, there is actually a stupid amount of work involved in doing one single edit. I commented on some of the reasons why this is the case here. If you care about scalability, you should be interested. But like addshore says, this doesn't really apply in this particular setting. Infrastruktur (talk) 17:11, 2 August 2025 (UTC)Reply

There is a conversation and a potential solution for a faster massive Wikibase importer: T385018

Tracked in Phabricator
Task T385018

—Ismael Olea (talk) 15:44, 30 July 2025 (UTC)Reply

I volunteer Librarybase, which was purpose-built for hosting a very large amount of data. Harej (talk) 01:51, 31 July 2025 (UTC)Reply

@Harej what are your thoughts on the split? Should library base just be used for this large chunk of data? Are there blockers to making this all be "nice" such as cross wikibase integrations? ·addshore· ^{talk to me!} 10:54, 1 August 2025 (UTC)Reply

I have a written out scope document describing what I consider the scope of Librarybase to be. (I also have written out project principles.) At the moment, the goal is to not duplicate what's on Wikidata, but to add more. If an entity exists on Librarybase that is an exact match of Wikidata, it's to make it easier to incorporate into the Librarybase graph.

Where it gets interesting is, what happens if Wikidata chooses to evict data. (I think I "predict" that on the principles page.) If the Wikidata community elects to evict data, I would be more than happy to accept it on Librarybase's behalf. I even have an extension installed called BatchIngestion which allows you to rapidly create items through an API endpoint that accepts JSON documents. If this idea gets traction, please let me know before any significant migrations take place so I can make sure everything is working fine (particularly Blazegraph and ElasticSearch which I don't think I've had running for a while). I would recommend a staged migration, starting with the most obvious candidates for removal, and proceeding from there.

More detailed thoughts at User:Harej/Librarybase. Harej (talk) 07:39, 2 August 2025 (UTC)Reply

I absolutely love contributing to Wikidata and I have learned a ton of things and really enjoyed making tools and learned to program with help of others. The community is amazing 🤩.

But...

I just wrote a series of posts in the Wikicite telegram channel and thought you might want a summary here. The title might provoke some. Sorry! Few seem to realize the sad state of the project and it might be a good idea to read both sides of the coin before dedicating your spare time.

• Not Scalable: The system was never stress-tested for billions of triples or edits before launch.
• Outdated Servers: WDQS (Wikidata Query Service) servers are underpowered and nearing end-of-life.
• High Load: Simultaneous large query and edit volumes strain infrastructure severely.
• Lack of Transparency: No clear info on server specs (except recent WDQS reveal) or WMDE's server budget.
• MediaWiki Limitations: MediaWiki itself can't handle Wikidata’s needs well.
• Poor Dumps: Only a weekly dump exists, outdated and rarely used. No real-time replication like OSM offers.

• Follow OSM's Model: Let private actors host public query endpoints. Provide real-time replication data so anyone can mirror Wikidata including the mariadb tables and blob storage.
• Stop “Serving the World”: Scale back free services to reduce infrastructure pressure and foster commercial interest.
• Offer SLAs and APIs for Enterprises: As Wikimedia Enterprise attempts, but also fix the public infrastructure.
• Encourage Commercial Ecosystem: WMDE should stop discouraging third-party services and support an OSM-style model.

• Negligence Over Time: 13 years with little community involvement in dumps, no gap analysis, and poor planning.
• Low Adoption in Sweden: Despite great potential, virtually no agencies use Wikidata (unlike OSM, which has wide adoption).
• Lack of Schema or Validation Tools: No proper validation for imported data or structured editing.
• No Focus on Data Pipelines: Imports are not reproducible or trackable, leading to inconsistent coverage.
• Lexeme Gaps Unclear: Unlike OSM maps, it's hard to visualize what’s missing, especially for lexemes.

• Real-time dump and replication support like OSM.
• Clear gap indicators and validation tools for schemas.
• Better communication, transparency, and prioritization from WMDE.
• Make reproducible import pipelines
• Visualize gaps in data quality to everyone on the front page and make it dead simple to fix them

So9q (talk) 17:09, 29 July 2025 (UTC)Reply

The recent split has given us enough time to allow content to continue to be added, and while mass-editing needs to be monitored, we don't need to discourage casual use. Having multiple servers with variants of the database would be good. But I can see that while, say an "English only" copy with no other language content might be much fast, it would be hugely unfair to other languages relegated to the slow lane. Similarly a freemium model with commercial servers could pull the project apart. Blazegraph is my biggest frustration, given that QLever is so much faster, and I don't believe all the edge cases that are not currently being addressed by the latter's developers would slow it down to the same level as the former. There are huge gaps in data coverage, but back-filling is dull work, and probably best left for the AIs that are bearing down on us. Vicarage (talk) 17:54, 29 July 2025 (UTC)Reply

Oh well if no agencies in Sweden are using Wikidata that changes everything. Shut it down, folks, clearly we all need to just give up. </heavy-sarcasm> M2Ys4U (talk) 18:02, 29 July 2025 (UTC)Reply

Why do I have the sneaking suspicion that this post was in large part written by AI? And don't diss on Sweden bro. Sweden good! :-) Infrastruktur (talk) 19:00, 29 July 2025 (UTC)Reply

Oh I have nothing against Sweden, I just found it hilarious that Swedish agencies (and only Swedish agencies) are the benchmark being used to evaluate Wikidata's use. M2Ys4U (talk) 20:07, 29 July 2025 (UTC)Reply

So you think I should avoid contributing until when? If I have things that are valuable to contribute isn't it best to still contribute when I have the motivation to do so? Immanuelle (talk) 02:45, 30 July 2025 (UTC)Reply

The key question what is your goal and can you contribute to achieve that goal... my lesson learned is that many external organisations and researchers are not understanding the value of Wikidata so its a waste of time

• I have spent too much time on WIkidata but has done some cool things but the impact is low feels like wasted time
  • example help changing the Swedish Nobel Prize data now we get the Wikidata Qnumber of the winner in the API when the prize is announced --> much less linkroot and faster by having the qnumber and Nobel Laureate API ID (P8024)
    • in Swedish example how it works link
• I have added very good sources to all Swedish PM:s since 1885- 1970 - A research project got good persistent identifiers for all Swedish PM and could do Machine learning on a lot of Swedish PM documents and match people... - feels like they had problem understanding Persistent identifiers etc...
  • my feedback to the project

My lesson learned think twice what you would like to achieve and if you hope to change external organisations then think even more what is the best approach or its just a waste of time....

- Salgo60 (talk) 05:35, 30 July 2025 (UTC)Reply

On the first few points, you might like to take a look at, and join in at Wikidata:Requests_for_comment/Mass-editing_policy.

"Lack of Transparency: No clear info on server specs" I'm pretty sure all of this is as open as it could be? what are you missing? I have referenced the size and number of backend query service servers multiple times in blog posts, and overall WMF infra budgets are always published? This has all been published since the begining?

"Let private actors host public query endpoints", this already happens?

"Stop “Serving the World”: Scale back free services to reduce infrastructure pressure and foster commercial interest." & "Offer SLAs and APIs for Enterprises" already being done via meta:Wikimedia_Enterprise

Progressing through the rest of the points, I don't think there is anything that mind-blowing, and obviously lots of things can be done and improved in the space. Does WMDE always prioritize the things that the core Wikidata community might think are important, no. That in part is because the scope of what WMDE and WMF have jointly decided to try and push towards is far wider than just Wikidata. Whether it will work or not, who knows! ·addshore· ^{talk to me!} 09:07, 1 August 2025 (UTC)Reply

Certainly WMDE seem to be reluctant to engage with the community, Lydia excepted. The mul developers seemed to implement the feature without considering its downstream consequences, and weren't around to handle the detractors, so others had to justify their approach. The parameter enabled search box wanted Github comments rather than a RFC here, and you don't see them responding to project chat discussions about capacity like this one. I don't have a clear idea of their roadmap either. Vicarage (talk) 09:53, 1 August 2025 (UTC)Reply

I just wrote a blog post talking about the wikibase federated properties feature, where I included this little bit, which talks about some WMDE planning an activities "its hard to redirect a heavily planned organizational roadmap when the train has already left the station".

https://phabricator.wikimedia.org/T285156 was for example made in 2021, and thus the topic has been split across so many teams, people, and management folks that the origins and purpose at that point may be assumed, and may have mutated.

On the `mul` topic, the main user story seemingly is and was:

As a Wikidata editor, I want to avoid repeating identical labels in hundreds of languages, in order to reduce the amount of redundant content that needs to be maintained on Wikidata.

which of course can be implemented in different ways, and hindsight is 20/20, but perhaps the current situation isn't ideal, on wikidata, and also for the wider ecosystem. ·addshore· ^{talk to me!} 10:53, 1 August 2025 (UTC)Reply

Wikimedia has a roadmap on meta:Wikimedia_Foundation_Annual_Plan/2025-2026/Product_&_Technology_OKRs#Hypotheses. There are several tasks for Wikidata on it. Among them is doing more caching, so that Abstract Wikipedia can launch. Wikimedia Commons is also having issues, so all link tables are moving to a seperate server, see phab:T398709. Snævar (talk) 11:05, 2 August 2025 (UTC)Reply

On danskefilmstemmer.dk Adam Victor Bøje Meier (Q135511401) and Alexander Grandjean (Q135511752) have been credited as "Instruktør" (Instructor), "Tekniker" (Technician), "Oversættelse" (Translation), "Bearbejdelse" (Processing). What would be the correct Q items to use as occupation be? Trade (talk) 15:03, 30 July 2025 (UTC)Reply

I noticed that this item Gikousan Yanodou (Q102769019) has an english wikipedia article that is relatively different from the english label and alias. Is there a bot that would have normally added the english wikipedia title as an alias to this? Immanuelle (talk) 23:29, 30 July 2025 (UTC)Reply

We do have bots for adding labels from the titles of linked Wikipedia articles if the item doesn't yet have a label in that language. But I don't think we have such bots for adding aliases, at least in wide use. Samoasambia ✎ 01:37, 31 July 2025 (UTC)Reply

One thing to consider is that Wikipedia is not CCZero. --Egon Willighagen (talk) 05:26, 31 July 2025 (UTC)Reply

However labels or aliases shold not be copyrightable. GZWDer (talk) 10:11, 31 July 2025 (UTC)Reply

I think this would be useful, because someone might search wikidata for the current page title, or a previous title. Immanuelle (talk) 08:26, 1 August 2025 (UTC)Reply

Q3095107 is about an 11km tributary of the Dordogne in Corrèze, France, with w:Sandre river ID P1600560. It is titled "Gane" in several languages and associated with the page fr:Gane (affluent de la Dordogne) on French Wikipedia. In Sandre's database, the entry P1600560 is consistent with the properties, but has the name Ruisseau de Combejean. (There is a different entry P5440570 for a 5km long La Gane, also a tributary of the Dordogne.)

The French Wikipedia page carries an external link to archived 2011 version of Sandre DB where P1600560 is ruisseau de la gane. This seems to suggest that the official name has changed? Or perhaps there was a mistake in the records that was subsequently rectified? I'm not fully confident on this because I don't speak French, would appreciate if someone else could take a look. Thanks! 2406:3003:2007:1F3:70ED:AFA0:22AF:F1E2 08:31, 31 July 2025 (UTC)Reply

Children's Hospitals in East London (Q58753580) link shows the first page of the article that is fully available on the link at The East London Hospital for Children (Q58749397) : they refer to the same publication - should they be merged? And if so, can someone help as I always get stuck trying it. Deadstar (talk) 12:48, 31 July 2025 (UTC)Reply

No, I don't think they should be merged: they have distinct external IDs as they refer to two separate articles within the journal Piecesofuk (talk) 15:32, 31 July 2025 (UTC)Reply

Is there a way to just completely remove scholarly articles from every catalog except those that are actually about scholarly articles?

Constantly having things like this showing up while using the tool makes MnM really frustrating to work with when i have to remove items with 200+ long character label names before i even get the chance to assign the identifier to an item Trade (talk) 22:21, 1 August 2025 (UTC)Reply

If the entries of a catalog have a default type (e.g. human (Q5)), resetting automatches and relaunching them should work. Epìdosis 22:24, 1 August 2025 (UTC)Reply

First we would probably need to figure out just how many catalogs are affected by this issue in the first place. This thread were mostly made out of frustration tbh. Trade (talk) 23:27, 1 August 2025 (UTC)Reply

The existing

⟨ Winthrop National Fish Hatchery (Q49582245)    ⟩ subclass of (P279) ⟨ National Fish Hatchery System (Q2104552)    ⟩

seems wrong to me, and it also triggers a warning. However, I do not know what property would best express this relation. Can this be done with a different property (maybe maintained by (P126)), or do we need an entity in between for "National Fish Hatchery of the United States" analogous to National Park of the United States (Q34918903) for relating individual U.S. National Parks to the National Park Service? - Jmabel (talk) 02:25, 2 August 2025 (UTC)Reply

I moved it so it's part of (P361) National Fish Hatchery System (Q2104552). That is a reasonable way to model that. Your model would work as well, but might be excessive. But then again there are 71 hatcheries and that's a decent number. William Graham (talk) 03:14, 2 August 2025 (UTC)Reply

The more I think about it, creating an item for "National Fish Hatchery of the United States" is probably a good idea. Connect it to Category:National Fish Hatcheries of the United States (Q13275650) and go from there. William Graham (talk) 03:18, 2 August 2025 (UTC)Reply

Hej! significant environmental impact (P3643) has been slapped on all three of these items, but this is likely conflation because of the similarity in lake names and them all being in the same municipality. The person who added significant environmental impact (P3643) hasn't edited since 2017 and I can't access the source properly. The Swedish articles are also not of much help since they are bot-created articles, only one of which has been touched by a human being. What would be a good way of dealing with these? (Or would any of you have proper access to the cited source and could check which of these items it actually belongs on?) - Yupik (talk) 03:19, 2 August 2025 (UTC)Reply