Wikidata:Project chat

Wikidata project chat
A place to discuss any and all aspects of Wikidata: the project itself, policy and proposals, individual data items, technical issues, etc.

Please use {{Q}} or {{P}} the first time you mention an item or property, respectively.
Other places to find help

For realtime chat rooms about Wikidata, see Wikidata:IRC.
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 2023/09.

Is there a way to get all STEM pages on wikipedia? Edit

I've been going through the categorylinks table a fair amount, and walking the tree/graph you end up pulling in almost all of wikipedia when you start from science as your root category and recursively pull in subcats/pages. Someone pointed me to wikidata as a way perhaps to solve this problem, but I'm unconvinced as building a proper categorization of something like STEM pages I think would require a very specific effort. Wikiqrdl (talk) 19:04, 10 September 2023 (UTC)Reply[reply]

One idea I proposed was 'category views'. Sort of like portals, where an individual or a group takes ownership of a category view and they control what gets included in it. It could use only existing tags / categories, but the connections between them and to pages would be controlled by the view. My thoughts are that it would lie generally outside the main flow of things, similar to wikidata. Importantly, the category views would be 'purpose built' by domain experts who understand how something might be useful to similar practitioners. Some sort of category view rating system might be useful, perhaps along different dimensions. Wikiqrdl (talk) 19:50, 10 September 2023 (UTC)Reply[reply]
As an example for the above, let's say a professor of education wanted to create a high quality list of all the pages for STEM on wikipedia. First they'd categorize it and then then they'd include the pages they felt met their bar in the categories. Something like this -> but more complete and with a very well thought out hierarchical arrangement that would serve someone going into STEM field of study might be find credible and useful. Importantly, it wouldn't get sidetracked by things like botany->plants->coats of arms with plants (as an example) Wikiqrdl (talk) 19:54, 10 September 2023 (UTC)Reply[reply]
Wikidata itself is not organized into categories or tags. ChristianKl❫ 23:09, 11 September 2023 (UTC)Reply[reply]
@Wikiqrdl: If you only care about the English Wikipedia, use See w:WP:PROJDIR/S for a full list of science WikiProjects. Dexxor (talk) 10:32, 12 September 2023 (UTC)Reply[reply]
Very cool, the wikiprojects/portals are exactly what I was looking for. Is there a database dump of the projects I can import? I'm trying to create a compilation of all the stem pages. I have all the other dumps imported. Can I traverse the wikiprojects and their subcats/subpages via the categorylinks table? Wikiqrdl (talk) 07:14, 18 September 2023 (UTC)Reply[reply]
Thanks, that's what I thought. Wikiqrdl (talk) 07:12, 18 September 2023 (UTC)Reply[reply]
fwiw, I tried to create a sparql to solve the problem, but it looks like the tagging just isn't complete. eg: instance of science, part of education. 8 results? Wikiproject / portal folks could help here. Wikiqrdl (talk) 02:29, 25 September 2023 (UTC)Reply[reply]
@ChristianKl @Dexxor One idea that came to me is that things like wikiprojects and portals could be organized around sparql queries. This would help get domain expertise to help inform the wikidata project. Eg, say a portal around botany was created, they would topline the query they used to capture the articles of interest. They would work with the wikidata project to make sure their wikidata was expressive enough and that their query was not overly broad / in appropriate. Wikiqrdl (talk) I proposed this here - 1:54, 25 September 2023 (UTC)

we need to fix the problem with Edit

I think I brought this up once before. See Margaretha of Louvain (Q2610800) where we get an error message for "statement with Gregorian date earlier than 1584" because instance_of is reserved for main values. Would it be better if we changed all of the statements to be: nature_of_statement="statement with Gregorian date earlier than 1584"? Or should we change the parameters of instance_of? I am for nature_of_statement. What do you think? We would need an automated way to change off of them, and modify the bot that adds the statement. RAN (talk) 00:15, 15 September 2023 (UTC)Reply[reply]

I'm not sure whether sourcing circumstances (P1480) or nature of statement (P5102) is the right one, but instance of (P31) certainly isn't. ChristianKl❫ 01:06, 15 September 2023 (UTC)Reply[reply]
nature of statement (P5102) sounds most appropriate to me. Vojtěch Dostál (talk) 04:52, 15 September 2023 (UTC)Reply[reply]
Yes, let them be visible. We do need to do something about the clean up. I see quite a few easy cases, take for example Q23563#P585. If the value has precision of a year, isn't it a matter of fixing the calendar and removing the qualifier? That would be a good bot job. Multichill (talk) 19:11, 19 September 2023 (UTC)Reply[reply]
@Multichill Yes, I think it would be a good start to remove the calendar from these altogether. Vojtěch Dostál (talk) 06:47, 20 September 2023 (UTC)Reply[reply]

Hello, I wonder if countries values are allowed into location (P276) ? My understanding is that only countries should be into country (P17) and any other (more precise or very vague localisations) and no countries per se inside P276, as it is not the case in these samples : Are there any rules about P276 ? Bouzinac💬✒️💛 16:21, 16 September 2023 (UTC)Reply[reply]

I've seen states used in located in the administrative territorial entity (P131) for the same purpose - that is, for things that don't fit in any administrative division smaller than the state. It seems better than location (P276) but I don't know if any of them is recommended.--Pere prlpz (talk) 17:09, 17 September 2023 (UTC)Reply[reply]
By states, did you mean for instance US or canadian states ? Them being in P131 does not shock me, just saying.
But a country being in P131 instead of P17 is shocking, such as this item

Compañía Lucamoros(Q117351131).

I think it'd be a good idea to show constraints values into P131 and P276, should one trying to put a country inside Bouzinac💬✒️💛 19:56, 17 September 2023 (UTC)Reply[reply]
For works of art we want to have the location (P276), see Wikidata:WikiProject_Visual_arts/Item_structure#Describing_individual_objects for full overview. Both located in the administrative territorial entity (P131) and country (P17) are not appropriate or ambiguous for movable works of art.
For some works of art we only know what country these works are currently in so that's listed as the location. I just did to find some cases. Some valid, a lot of junk. We could possibly adopt a different convention to avoid using countries. Multichill (talk) 19:22, 18 September 2023 (UTC)Reply[reply]
I see the distinguo. Something that has been inside the country (but without precision on the location because it is movable or is hidden), then one might state P131=(country). I can get the distinguo and perhaps a qualifyer
like this but I am not satisfied (does the qualifyer applies to the qualifyer of date or to the country ?)
Do you nevertheless agree it is totally nonsense to input located in the administrative territorial entity (P131)=country ? Bouzinac💬✒️💛 19:41, 21 September 2023 (UTC)Reply[reply]

there is no subtopic for data flaws / wrong data in the large Edit

In the heading {{Discussion navigation}} there is a lot of subtopics, but astonishingly no subtopic for systematic data flaws or wrong data in the large. Is there a place where kind of work packages can be dropped (for those interested in the correctness of the data) or is it intended to have the triage: love the data, correct the data, or leave wrong data as they are? best --Herzi Pinki (talk) 08:16, 17 September 2023 (UTC)Reply[reply]

Kannst du das bitte nochmal auf Deutsch schreiben? Ich (Englisch C1) verstehe nur Bahnhof. Welches heading? Was meinst du mit subtopics? Was ist "love the data"? Jonathan Groß (talk) 08:21, 17 September 2023 (UTC)Reply[reply]

Sure, I can, but this is the English project chat. Sorry for my English. Ich suche einen Platz, wo ich Arbeitspakete abladen kann und wo jemand sich ev. auch drum kümmert. Triage ist ein doppeltes Wortspiel / Anspielung, hier auf die Daten in Wikidata angewandt. Triage im militärischen Sinn heißt, die die eh sterben, sterben zu lassen. Triage hier auf Wikidata hieße, die sinnlosen Daten, die falschen Daten, die inkonsistenten Daten einfach liegen zu lassen. Auch beim Militär sterben ja nicht alle, die dafür aussortiert werden. Der zweite Teil der Anspielung bezieht sich auf Love it, change it or leave it (Liebe es, ändere es oder geh). Was dann heißen soll: Wunderbare Daten, alles ok - ich liebe die Daten; fehlerhafte Daten, widersprüchliche Daten, unvollständige Daten - dann krempel ich die Ärmel hoch und ändere sie halt; oder ich geh (es gibt unfeinere Formulierungen dafür) bzw. lasse sie wie sie sind, schau nicht hin, .... lg --Herzi Pinki (talk) 08:38, 17 September 2023 (UTC)Reply[reply]

Alright, then I would like to know what sort of data (subject matter, format) you are referring to and how you imagine it could be integrated with Wikidata. In principle the community can help with curating data donations of this sort, but we need to know what we would be dealing with more specifically. Jonathan Groß (talk) 09:10, 17 September 2023 (UTC)Reply[reply]

Or maybe I again misunderstood, and by "Arbeitspakete" you mean tasks that need to be done on existing data in Wikidata? We have Wikidata:Bot requests, but that is mostly inactive. Why don't you just use this venue and list your jobs here? Jonathan Groß (talk) 09:21, 17 September 2023 (UTC)Reply[reply]

see below --Herzi Pinki (talk) 09:26, 17 September 2023 (UTC)Reply[reply]

Most people on Wikidata have certain data they are interested on and work on that data. There are few people on Wikidata who want to do large packages of work that someone else believes should be done. One place where you can discuss data problems is in the relevant Wikiprojects. ChristianKl❫ 14:47, 21 September 2023 (UTC)Reply[reply]

@ChristianKl: thanks for the hint, got your point. My problem is the other way round. What if people are not really interested in the data they have imported from somewhere else? What if they do not care and curate and complete the data? Am I one of those few people on Wikidata who want to do large packages of work that someone else caused and nobody is eager to fix? Is quality a common goal of the community here on Wikidata? Or is it just number of items? As an example see the mountains in the state of Washington assigned to country Canada (Q16) (just below). The assignment of Canada (Q16) has been done by User:&beer&love, not active any more. I just stumbled across. Sure, I can try to fix it and not bother someone else. And this is only Canada in the US. What about Kenia in Tansania, or Chile in Argentina? I also stumbled across data imported from peakware (discontinued for more than 2 years now) with a lot of duplicates. I asked the importing user to fix this or to help me to fix it. He gave me the advice that I will waste my time. I'm working on Austrian geographical objects imported via geonames / Ljsbot / WP:ceb / EmausBot for years now: Existence is not always clear, spelling often is incorrect, location is cut to minutes mostly, elevation is derived from this inaccurate location info and there are a lot of duplicates (and I did not dare to have a look across the Austrian borders). I'm also working on the protected monuments of Austria for just a while, those have been imported by some bot in 2017 using wrong heuristics. There was no will (=no reaction to my complaints) from the bot operator to care for the necessary fixes. These are only some examples. Thanks for listening. --Herzi Pinki (talk) 11:18, 22 September 2023 (UTC)Reply[reply]
Different people have different goals. Generally, finding some place where data quality can be improved on Wikidata isn't that hard. The bottleneck is not in having people point to problems.
People who do care about data usually care about a certain subset of the data. When it comes to data quality of mountains, that should probably be talked about in some Wikiproject about geography. ChristianKl❫ 00:24, 23 September 2023 (UTC)Reply[reply]
ok. I did not find a suitable wikiproject here on wikidata (only items linking to various projects in various languages in various wikipedias), can you give me an example here in wikidata? The other point is how do we get a feeling about the overall quality of wikidata in the large, if we not even do collect flaws? Is quality a goal of Wikidata? (different people have different goals)? How is quality organized and created? best --Herzi Pinki (talk) 11:12, 24 September 2023 (UTC)Reply[reply]
Also see
M2k~dewiki (talk) 12:31, 24 September 2023 (UTC)Reply[reply]

Google Maps Place ID Edit

We have Google Maps Customer ID (P3749) with the customer ID for an business on Google Maps, but we don't seem to have an equivalent property for their place id, which occurs both for businesses and for places, and is the better identifier for use in the Google Maps API (See Property talk:P3749 for how I managed to use it). As Google has collected lots of information in their Maps system, does it seem sensible to add the place property? It would be a big job to populate it. Vicarage (talk) 20:38, 17 September 2023 (UTC)Reply[reply]

Google Maps Customer ID (P3749) was also a big job to populate Trade (talk) 10:21, 18 September 2023 (UTC)Reply[reply]
What is the difference between Google Maps Customer ID (P3749) and Google Maps Place ID?
+ Google recommends refreshing place IDs if they are more than 12 months old. I don't know what the effect is from a refresh. RVA2869 (talk) 17:50, 18 September 2023 (UTC)Reply[reply] says
"Notice: On March 30, 2022, all Google Maps Platform APIs will stop accepting certain obsolete place IDs. Beginning on March 30, 2022, any requests made using obsolete place IDs will be rejected, and return error code INVALID_REQUEST. To prevent user experience degradation, please refresh all place IDs that are older than 12 months before March 30, 2022." Vicarage (talk) 08:27, 19 September 2023 (UTC)Reply[reply]

linking interlanguage articles Edit

I'm trying to link en:Kephala, Kea with de:Kephala and 3 other related articles. This used to be an easy procedure but now I'm not sure how to do it. Y-barton (talk) 22:47, 18 September 2023 (UTC)Reply[reply]

I've merged the items into one. --Wolverène (talk) 23:05, 18 September 2023 (UTC)Reply[reply]
Thank you very much. I would like to know, please, if there's some sort of a manual somewhere for how to do this in the future. Y-barton (talk) 01:11, 20 September 2023 (UTC)Reply[reply]
Help:Sitelinks explains interlanguage linking. Generally speaking in any item you can scroll to the bottom and link an article at a site. For merging items Help:Merge explains the several ways to do so. I personally prefer to use the Merge.js Gadget that is described on that page. -- William Graham (talk) 01:26, 20 September 2023 (UTC)Reply[reply]

I got a smile Edit

There are, of course, a number of entries whose Q-numbers are significant. I got a big smile yesterday out of noticing who Q12345 is, and I'm sure any other fans of Sesame Street (Q155629) will agree. (On the theory that smiles should be spread, I'm posting about it here — not for any other reason.) —scs (talk) 03:10, 19 September 2023 (UTC)Reply[reply]

Well, that makes two, two of us with big smiles   Ah ha ha! –FlyingAce✈hello 05:30, 19 September 2023 (UTC)Reply[reply]
Make that 3 😁😁😁 QuickQuokka [⁠talkcontribs] 08:34, 19 September 2023 (UTC)Reply[reply]
@scs, FlyingAce: See WD:Humor for more such easter eggs. QuickQuokka [⁠talkcontribs] 08:37, 19 September 2023 (UTC)Reply[reply]
Same but less funny with bead(Q12345678) Bouzinac💬✒️💛 08:48, 19 September 2023 (UTC)Reply[reply]
@scs:: Thank you so much, this really made my day! Jonathan Groß (talk) 09:41, 19 September 2023 (UTC)Reply[reply]
Hmmmmm, technically speaking, I guess we would have to consider bead (Q12345678) hijacked ... --Dorades (talk) 19:38, 20 September 2023 (UTC)Reply[reply]
Indeed, I do not understand the redirect stated by @MisterSynergy on Q12345678 Bouzinac💬✒️💛 07:54, 22 September 2023 (UTC)Reply[reply]
There is a misunderstanding; I meant that the item was hijacked/repurposed in this state, because it was originally about beads and was merged with bead (Q1053956), before it was remodeled as Space Creator Day. As you certainly know, we don't repurpose/reuse redirected items. --Dorades (talk) 15:45, 22 September 2023 (UTC)Reply[reply]

How to mark dialect region for IPA? Edit

If an IPA is a description of a pronunciation in a regional dialect, how should the region for the dialect be marked? I tried adding location (P276) to an IPA but this triggers an exclamation mark. See Lexeme:L1149927#F1. I have also asked this question at Property_talk:P898#How_to_mark_dialect_region. Robert (talk) 07:41, 19 September 2023 (UTC)Reply[reply]

I found two Lexemes with each having two IPAs with different language of work or name (P407): German Eigen L344376 (German and Austrian German) and English Talk (L379) American and British English). The query I used. So presumably I should create wikidata objects for dialects and use those? Robert (talk) 08:30, 19 September 2023 (UTC)Reply[reply]

How to mark dialect region for IPA? Edit

The International Phonetic Alphabet (IPA) is an alphabetic system of phonetic notation based primarily on the Latin script. It was devised by the International Phonetic Association in the late 19th century as a standardized representation of speech sounds in written form. IPA is also not universal among dictionaries in languages other than English. Monolingual dictionaries of languages with phonemic orthographies generally do not bother with indicating the pronunciation of most words, and tend to use respelling systems for words with unexpected pronunciations. Traditionally the IPA is used for articulating sounds and pronouncing words accurately, most commonly when looking them up in a dictionary. Jubaidul Alam Khan (talk) 13:14, 19 September 2023 (UTC)Reply[reply]

Google's Cloud Text-to-Speech (and presumably other text-to-speech solutions) supports IPA and X-SAMPA phoneme coding for multiple languages including English, German, Spanish, French, Chinese, Korean, Hindi, Russian, and more. So IPA does not seem to be limited to English in the future. Robert (talk) 07:40, 20 September 2023 (UTC)Reply[reply]
While they support it as input many of these system internally don't use IPA to represent sounds. One reason is that just because two languages use the same IPA sign for a phoneme does not mean that they are pronounced exactly the same. ChristianKl❫ 18:01, 21 September 2023 (UTC)Reply[reply]

enwiki watchlist Edit

So here's a cross-wiki conundrum. I have my watchlist on enwiki set up to display Wikidata changes for all my watched pages. In the past week, it's been showing me Wikidata changes for certain pages, but when I click through to see diffs, it's a different Wikidata item.

D  m   21:46 Communion and Liberation‎ (Q652) (diff | hist) . . Illchy (talk | contribs) (‎Changed label, description and/or aliases in id)
D  m   21:46 Catholic Church‎ (Q652) (diff | hist) . . Illchy (talk | contribs) (‎Changed label, description and/or aliases in id)

As you can hopefully see, @Illchy made only one change to Italian (Q652), yet this one change showed up twice in my watchlist, for articles which are tangentially related. How did Wikidata get tangled up in this way? "Italian" is the first link on the Communion & Liberation article, but believe it or not, "Italian" is linked nowhere from "Catholic Church" at all, not even from navigation templates. "Italian" is not on my enwiki watchlist, so I wouldn't expect to receive updates for it. My Wikidata watchlist (which should not matter) contains Catholic Church (Q9592) but not Communion and Liberation (Q868651) nor Q652. Q652 does not appear to reference "Catholic Church" or "Communion and Liberation" in any way.

Here's another example, from yesterday:

User talk:Dcheney‎‎ 7 changes history  0‎  [RogueScholar‎ (7×)]
16:39 Q57451712 (diff | hist) . . RogueScholar (talk | contribs) (‎Created claim: Property:P580: 8 April 2014)
16:38 Q57451712 (diff | hist) . . RogueScholar (talk | contribs) (‎Created claim: Property:P371: Q106864469)
16:38 Q57451712 (diff | hist) . . RogueScholar (talk | contribs) (‎Created claim: Property:P437: Q24633474)
16:38 Q57451712 (diff | hist) . . RogueScholar (talk | contribs) (‎Created claim: Property:P407: Q7976)
16:37 Q57451712 (diff | hist) . . RogueScholar (talk | contribs) (‎Created claim: Property:P1019:
16:35 Q57451712 (diff | hist) . . RogueScholar (talk | contribs) (‎Created claim: Property:P136: Q74303978)
16:34 Q57451712 (diff | hist) . . RogueScholar (talk | contribs) (‎Created claim: Property:P31: Q24634210)

How is this editor's talk page related to a radio broadcaster? Elizium23 (talk) 05:11, 21 September 2023 (UTC)Reply[reply]

If you click on Edit on those pages, below the edit window there is a list of Wikidata entities used on that page; you will find the item you saw in your watchlist there. In the case of the talk page, one of the posts there linked to a WD item; for articles, the callouts to WD items most likely come from templates. –FlyingAce✈hello 05:37, 21 September 2023 (UTC)Reply[reply]
@FlyingAce, the editing process has no such list, but I did find it in the "Page Information" tool, and all entities are accounted for, as you described. Thanks for the accurate info! Elizium23 (talk) 08:52, 21 September 2023 (UTC)Reply[reply]

WikidataCon 2023: registration open Edit

Hello all,

On behalf of the WikidataCon 2023 organizing team, I’m happy to share some exciting news about the WikidataCon 2023. The conference dedicated to the Wikidata community and co-organized by Wikimedia Deutschland and Wikimedia Taiwan will take place on October 28-29 with a hybrid format. In this email, you will find more information about the format and registration for the conference.


While most of the world will attend the sessions and discussions online, people living in Taiwan and the neighbouring countries can decide to join the onsite part of the event taking place in Taipei. Online participants will be able to join the conference, follow the sessions and interact with other participants on the platform GatherTown. Onsite participants will be hosted at the National Taipei University. You will find more information about the onsite and online aspects of the conference onwiki.

The first version of the program will be released on October 2nd - stay tuned!


You can now sign up to the event by registering here on the Pretix platform. The registration form includes both online participation and onsite participation in Taiwan. Registration will be open until the start of the event. Some useful information will be sent in the upcoming weeks to people who registered, including the link to the event platform for online participants. Please note that registration is free of charge, but no scholarship to attend the online or onsite event will be provided.

Questions ? Feel free to contact the organizing team by writing on this talk page or at

We are looking forward to seeing you at the WikidataCon 2023!


我代表WikidataCon 2023組織團隊,很高興與大家一起分享,關於WikidataCon 2023的令人興奮的消息。 這項由Wikimedia Deutschland和Wikimedia Taiwan共同舉辦的,意旨Wikidata社群的會議,將於10月28日至29日,以混合形式舉行。 在這封電子郵件裡你將找到,有關會議的格式以及更多關於註冊報名的資訊。


即便世界上大多數地區的人在線上參加會議和討論,但居住在台灣及週邊國家的人,可以選擇參與在台北舉行的實體活動。 線上參與者將能夠參加線上會議,在Gather Town平台上加入會議,並與其他世界各定的參與者互動。 實體參與者將入住國立台北大學。 你將會在維基上找到關於會議現場及線上部分的更多資訊。

行程表的第一個版本將於10月2日發布 - 敬請關注!


你現在可以透過在Pretix平台上註冊並報名活動參加。 註冊表格裡包括:線上參與和在台灣的現場實體參與。 註冊將一直開放至活動開始。 在接下來的數周,我們將對已註冊的人傳送有用的一些資訊,包括:線上參與者的活動平台連結。 請注意,註冊是免費的,但我們不提供參加線上或實體活動的獎學金。

有問題嗎? 請隨時透過在此討論頁面上留言,或發送電子郵件至contact@wikidatacon.org與組織團隊聯繫。

我們期待在WikidataCon 2023見到你! Lea Lacroix (WMDE) (talk) 06:44, 21 September 2023 (UTC)Reply[reply]

Split entries or keep together as is now? Edit

Case in point: Q4131491 is now about the person (instance of human).
The ru-wiki article is about the event led by this person, and normally should have its own wikidata entry separate from the person.
However, the linked az-wiki and lez-wiki articles, which look like biographical articles, are primarily about the event, not the person.
What's the proper course of action - change the instance of of existing wikidata record, or split it, or let it stay as is? Retired electrician (talk) 07:20, 21 September 2023 (UTC)Reply[reply]

I would split them up and if possible add intentional sitelinks to redirects. I.e. in Q4131491 the sitelink for ruwiki be ru:Гаджи Магомед Эфенди Штульский, an article redirect that is the person's name. -- William Graham (talk) 14:51, 21 September 2023 (UTC)Reply[reply]
Generally, having a Wikidata item for the person and one for the event is good. explains how to still have interwiki links. ChristianKl❫ 14:52, 21 September 2023 (UTC)Reply[reply]

merge "data carrier" and "recording medium" ? Edit

Q193395 and Q104450446 seem to denote the same thing. The first is a lot more detailed. Graefestrasse (talk) 15:32, 21 September 2023 (UTC)Reply[reply]

If one is more detailed than the other, they aren't the same thing and should not be merged. ChristianKl❫ 17:02, 21 September 2023 (UTC)Reply[reply]
The one that has less properties can be merged into the one that has a lot, I think. Graefestrasse (talk) 10:24, 22 September 2023 (UTC)Reply[reply]
Both items link to different articles in ruwiki, so we would not be able to merge them. –FlyingAce✈hello 13:20, 22 September 2023 (UTC)Reply[reply]
OK, thanks! Graefestrasse (talk) 13:22, 22 September 2023 (UTC)Reply[reply]

fallback language behavior? Edit

Hi, is there a definition somewhere how language fallback will work on wikidata and adjacent wikipedias? Consider language pairs (en & en-ca, en-br; de & de-at; pt & pt-br etc.) I often find copies of labels / descriptions / aliases here in wikidata, which are just copies (redundant copies) from the main language to the variant language. In worse cases those labels / descriptions are meant as copies, but have been modified on one side only and give different values, not because of the underlying language, but due to edits not done on all ends. My assumption is that if there is no label for en-ca, the label for en will be taken automatically (eventually depending on some user config). This is the fallback from en-ca to en. Does my assumption hold true for

  • page title of items
  • page titles and descriptions shown in auto-completion when typing ahead
  • page titles and descriptions shown in search results
  • page titles and descriptions in Sparql results
  • labels and descriptions shown on wikipedias?

Concluding: Is there any need to have labels, descriptions & aliases for en-ca, if they are all identical to en? best --Herzi Pinki (talk) 11:31, 22 September 2023 (UTC)Reply[reply]

We've had discussions of duplicated labels before, see Help_talk:Mul_language_code for how a 'mull' language code might help. Most people believe there is no need to duplicate a value if a more general language class has it, or if the label in the home country language of an item would apply in equally well in other languages. [[ describes how a query can return values in a preference list of languages. Vicarage (talk) 12:49, 22 September 2023 (UTC)Reply[reply]
my question was not about discussions and not about beliefs, but about specification and implementation. best --Herzi Pinki (talk) 11:03, 24 September 2023 (UTC)Reply[reply]
M2k~dewiki (talk) 11:06, 24 September 2023 (UTC)Reply[reply]
if I understand it correctly, this will not be of any use for users without language specific settings here, for flyby users not logged in, for anonymous users, for users in other Wikipedias. It is editor-centered, not reader-centered? --Herzi Pinki (talk) 15:55, 25 September 2023 (UTC)Reply[reply]
If you are not logged in, you get some mix of browser language settings for content pages and english as standard language, e.g. for user interface elements. For SPARQL-Queries you have to specify the language for the labels in the query. M2k~dewiki (talk) 16:06, 25 September 2023 (UTC)Reply[reply]

Interested in a little image-cropping project? Edit

Normally I would contact the user about this, but the account is appears to be stale. This pertains to a user who have added P18 statements which I consider to be unsuitable, partly because they are PDFs but mostly because they they do not serve as illustrations or photos of the subject in question, as exemplified on Edvard Grieg (Q80621) and Giuseppe Verdi (Q7317). Now it should be possible to crop an image from some of the PDFs if you are interested in a little project. If there is no interest I plan to mass-deprecate all the statements, that is every P18 statement made by the user that links to a PDF. Infrastruktur (talk) 18:06, 22 September 2023 (UTC)Reply[reply]

Careful, though - some of them do serve as illustrations of photos of the subject in question, even if they are PDFs.
As for stale - the user appears to have been Wikipedian in Residence in Belgrade, so if you really want, you could contact Wikimedia Serbia. DS (talk) 19:38, 22 September 2023 (UTC)Reply[reply]
IMO if the illustration is on the first page, it might be better than nothing, if it's on page two it's useless in it's uncropped state. Infrastruktur (talk) 21:01, 23 September 2023 (UTC)Reply[reply]
I think it would be useful to start with a page using Wikidata:Listeria query to track the usage. -- William Graham (talk) 15:37, 23 September 2023 (UTC)Reply[reply]
You can install the Crop Tool ( at c: and easily crop out PNGs from PDFs. If someone needs help with that, let me know. —Justin (koavf)TCM 23:26, 23 September 2023 (UTC)Reply[reply]
I tested it on Lazar Jovanović (Q31186075) just now. It looks much better. Infrastruktur (talk) 00:11, 24 September 2023 (UTC)Reply[reply]
Nice. Teamwork makes the dream work. <3 —Justin (koavf)TCM 00:13, 24 September 2023 (UTC)Reply[reply]

Help needed entering P1435 Edit

I've created Waterloo Round Tower (Q122801355) and am having difficulty correctly entering a heritage designation (P1435). The tower has an Irish Record of Monuments and Places (Q30688227) catalogue number (CO062-200002), and is adjacent to St Mary's Church (Q55055108). (See w:Waterloo Round Tower) -- Cl3phact0 (talk) 12:51, 24 September 2023 (UTC)Reply[reply]

@Cl3phact0: Please use Irish Sites and Monuments Record ID (P4057) for entering SMR numbers. Please do not forget the terminal hyphen, i.e. “CO062-200002-” is correct. I've also added {{c:Template:Archaeological Survey of Ireland}} to your photo. Regards, AFBorchert (talk) 16:07, 24 September 2023 (UTC)Reply[reply]
BTW, CO062-200001- appears more correct for the church, the other SMR is just for the belfry tower. --AFBorchert (talk) 16:12, 24 September 2023 (UTC)Reply[reply]
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. -- Cl3phact0 (talk) 07:12, 25 September 2023 (UTC)Reply[reply]

Limit of 400 readings from Wikidata per page Edit

On Slovene Wikipedia we have List of populated places in Slovenia (S) that consists of 694 entries. We are trying to add Wikidata image (Property:P18) to every entry, but there is a limit of 400 readings from Wikidata. Is there any possibility to set this limit at 700? Janezdrilc (talk) 13:57, 24 September 2023 (UTC)Reply[reply]

@Janezdrilc: Changing that limit alone won’t be enough, I’m afraid – as the change that introduced it points out, above 500 accesses you also start to run into the general expensive parser function limit, which is 500 for all wikis. You can file a Phabricator task (that might be a better place to discuss this than project chat), but to me it doesn’t feel likely that this limit will be lifted significantly :/ Lucas Werkmeister (WMDE) (talk) 10:59, 25 September 2023 (UTC)Reply[reply]

Ok, no problem. Thanks for answer. --Janezdrilc (talk) 11:57, 25 September 2023 (UTC)Reply[reply]

Unable to add interior category for an item Edit

I am trying to add category for the interior of the item (P7561) for St Columba's Church (Q55027653) pointing to c:Category:Interior of St. Columba's Church, Tullow which constantly fails with “No match was found”. I was entering the category name without the “Category:” prefix, i.e. as “Interior of St. Columba's Church, Tullow”. Unfortunately, “publish” remains greyed out. Hence I am unable to add this property. Any ideas? Thanks, AFBorchert (talk) 16:00, 24 September 2023 (UTC)Reply[reply]

Hello AFBorchert, the category c:Category:Interior of St. Columba's Church, Tullow needs to be connected to a wikidata object, for example similar to d:Q75111002. This object can be used in the wikidata object for the church building, similar to d:Q55049807 M2k~dewiki (talk) 16:41, 24 September 2023 (UTC)Reply[reply]
@M2k~dewiki: Thanks for replying. Well then I am wondering how to connect that category to the Wikidata object. I thought I would do this through category for the interior of the item (P7561). --AFBorchert (talk) 16:49, 24 September 2023 (UTC)Reply[reply]
If there is not yet an existing wikidata object, then a new one has to be created, where the commons category can be connected to. M2k~dewiki (talk) 16:52, 24 September 2023 (UTC)Reply[reply]
Thanks, that's it. I thought a simple connection would do, having to create Category:Interior of St. Columba's Church, Tullow (Q122802380) just for this purpose didn't appear straightforward. I initially thought this would be handled like Commons category (P373). Regards, AFBorchert (talk) 16:58, 24 September 2023 (UTC)Reply[reply]
To have the commonscat (instead of the commons gallery) connected as a sitelink is kind of a "shortcut". Theoretically, articles could be connected to galleries as a sitelink, and categories could be connected to commonscats. Since galleries often do not exist, there is no extra object necessary for the direct sitelink to the commonscat (instead of the commons gallery). Also see
M2k~dewiki (talk) 17:12, 24 September 2023 (UTC)Reply[reply]
I know of this theory. But this is not the viewpoint of Commons which sees the categories as main subjects. Galleries do not play a significant role and are, if interwiki-linked, just another stumbling block on the path to the proper category at Commons. --AFBorchert (talk) 17:19, 24 September 2023 (UTC)Reply[reply]
Also see Wikidata:Properties for deletion/P373 M2k~dewiki (talk) 17:33, 24 September 2023 (UTC)Reply[reply]
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. AFBorchert (talk) 12:46, 25 September 2023 (UTC)Reply[reply]

Page deletion Edit

This page should be deleted, I accidentally created it when the page already exists

Q122804948 21:40, 24 September 2023 (UTC)Reply[reply]

Which is the correct page? Michgrig (talk) 21:50, 24 September 2023 (UTC)Reply[reply]
Q117634166 is the correct page 21:59, 24 September 2023 (UTC)Reply[reply]

One item about two lakes is a mess. Edit

Lake Akdoğan (Q30681483) states that it is instance of (P31) lake (Q23397). But the linked Wikipedia articles are about two neighboring lakes with the same name (distinguished as the "bigger" and the "smaller"). The numbers in the item for height, depth and area are for the bigger lake, but the image pictures the smaller lake. This is confusing and misleading. How to fix it? Dipsacus fullonum (talk) 00:13, 25 September 2023 (UTC)Reply[reply]

It seems that the only reason that there is currently one item is because the Wikipedias each represent two lakes in a single article. There should be nothing preventing us from dividing this up into two items, Akdoğan Gölü and Küçük Akdoğan Gölü, because if I am to believe the English-language article, they are distinct, neighboring lakes, and they are separated by a strip of land, and as you describe, they each have separate characteristics. Elizium23 (talk) 02:16, 25 September 2023 (UTC)Reply[reply]
This is known as the "Bonnie and Clyde" problem (see intro paragraphs at Wikidata:Sitelinks to redirects). There are two options: 1) Keep it a an item about the pair of lakes, and create new items (unless they already exist?) about each lake or 2) Make it about one lake, and create a new item about the other, and another item about the pair. In either case, move the relevant values and interwiki links to the correct items. Since the item was originally created to match the en.Wikipedia article, option 1 would eb best in this case. Link the tree items with "has part"/ "part of" statements. Finally, check all inbound links and update if needed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:25, 25 September 2023 (UTC)Reply[reply]
Bonnie and Clyde (Q219937) is instance of (P31) duo (Q10648343). What should an item for two lakes be an instance of? Dipsacus fullonum (talk) 13:03, 25 September 2023 (UTC)Reply[reply]
group of lakes (Q5926864), possibly also dyad (Q29431432) but it isn't used much. Peter James (talk) 16:28, 25 September 2023 (UTC)Reply[reply]

Merge two items Edit

These two items should be merged. I tried, but the following error appeared: "Failed to merge Items, please resolve any conflicts first. Error: Conflicting descriptions for language en." Gor1995 (talk) 09:13, 25 September 2023 (UTC)Reply[reply]

I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Someone did that. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:18, 25 September 2023 (UTC)Reply[reply]

Suggestion list ordering Edit

How can we fix the ordering in the suggestion list for sex or gender (P21), so that the most frequently used values appear first? Discussion on its talk page has proved fruitless. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:16, 25 September 2023 (UTC)Reply[reply]

Wikidata weekly summary #595 Edit

Basic question. How do I mark that a drug has a en:boxed warning? Edit

Basic question. How do I mark that a drug has a en:boxed warning? I notice that Boxed warning (Q879952)exists, but I just can't figure out what statements I should add. I don't see that binary values are supported (0/1 or No/Yes...). I'm not sure if how to do the source property stuff. Looks like I have to look up the Q#s for each thing? Or no? Use the UNII? Even once I figure out what to do, I need help. Can't use - I'm not autoconfirmed. See . RudolfoMD (talk) 21:31, 25 September 2023 (UTC)Reply[reply]