This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Merging
Latest comment: 6 months ago4 comments3 people in discussion
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. RVA2869 (talk) 07:18, 5 April 2026 (UTC)
Property for formal names in non-native and non-fluent languages
Latest comment: 6 months ago1 comment1 person in discussion
Latest comment: 6 months ago1 comment1 person in discussion
TL;DR: Mobile editing now supports all datatypes (not just Strings and External IDs). Enable the beta feature in Preferences and test on any Item. Share feedback on the project talk page.
Hi everyone,
Following our earlier beta release for String and Entity ID datatypes, we're happy to announce that mobile statement editing now supports all datatypes. You can edit any statement directly from your mobile device, just like on desktop.
To try it out, make sure the beta feature is still enabled in your Preferences (Beta features --> "Edit Wikidata Items on mobile devices"). Then visit any Item on your mobile.
If you run into issues or have feedback, please share it on the project talk page: Mobile editing of statements.
Join our user testing panel and help improve mobile editing for everyone
We are planning new testing sessions from late April to early May. We're looking for volunteers of all experience levels, especially less experienced editors and users of RTL scripts (eg. Arabic, Hebrew, Persian, Urdu). Sessions are typically held via video call where you’ll try editing different datatypes and share your impressions with the team. Sign up (Great Question) to join the mobile testing panel, and we'll share details closer to the sessions.
Your feedback and participation are greatly appreciated.
Wikidata’s data will be available through Wikimedia Enterprise
Latest comment: 6 months ago6 comments4 people in discussion
Since October 2021, Wikimedia Enterprise has offered services for high-volume commercial reusers of Wikimedia content. Over the past two years, Wikimedia Deutschland and Wikimedia Enterprise have collaborated during regular exchanges to explore how Wikidata’s data could be included in this service in a way that reflects our shared movement mission, values and responsibilities.
Wikimedia Enterprise is now announcing the beta release of its Wikidata APIs: read the announcement blog for more details on its technical features.
We want to share why we believe this decision is necessary in today’s context, what principles guide it, and which safeguards WMDE has put in place together with Wikimedia Enterprise to ensure we continue to work together toward our vision to freely share in the sum of all human knowledge for everyone?
Why we support Wikimedia Enterprise
Our main goal is to distribute knowledge as widely as possible.
Large, high-volume reusers play a major role in bringing Wikimedia content to people. Many of the tools, apps, and services that millions of people use every day depend on Wikimedia content. This has been true for years, long before an API designed specifically for the needs of commercial users existed.
Until now, these organizations have placed a significant technical burden on Wikimedia’s infrastructure — including server capacity, hardware, bandwidth, and the personnel required to run these services — all funded by donors who want to support Wikipedia and the Wikimedia projects. At the same time, they have been able to use this data at scale without offsetting the costs they generate. On top of that our infrastructure nowadays is under pressure in ways never seen before due to a significant rise in automated requests and scraping.
We believe it is reasonable and fair that companies that rely on Wikidata’s data and availability at a very large scale, and that profit from it, contribute to the cost of maintaining and improving this infrastructure. This is what has driven Enterprise’s principles https://meta.wikimedia.org/wiki/Wikimedia_Enterprise/Principles.
We are taking these steps to ensure that organizations that profit commercially in substantial ways are not doing so at the expense of the volunteers, donors, and infrastructure that make the Wikimedia projects possible.
The ideals of free and open knowledge arose in an earlier, more distributed internet, where power and access were shared among many actors, a landscape that has since changed significantly. Today, a small number of very large companies draw immense value from community-generated content and shape how knowledge flows online. If we want to protect the principles that have guided us since the beginning, we need updated models of stewarding the digital commons to match today’s realities. Asking heavy commercial beneficiaries to contribute financially is one way of upholding those values, not abandoning them.
Moreover, investments by enterprise customers benefit all reusers and will enable improvements such as improved documentation, higher reliability and new public-availability access methods and community-requested features that benefit Wikidata editors and reusers more broadly.
explore earned income through enterprise-grade APIs, and
improve the Wikimedia API suite for all users.
What concerns we have heard and how we are addressing them
We acknowledge that providing a commercially-focused service has raised concerns within our open-source and free knowledge communities. Below, we outline the major issues raised and how we are working with Wikimedia Enterprise to address them responsibly.
Concern: Mission-aligned organizations should benefit for free
There are multiple ways to access Wikimedia Enterprise datasets for free, including through free accounts or Wikimedia Cloud Services (WMCS) and via third-party platforms. Free accounts are available to anyone, for any purpose, in line with Wikimedia’s licensing policies.
If you have a Wikimedia mission-aligned use case and your requirements exceed what is offered at no cost, you may request free access to a higher tier of the Enterprise APIs.
For cases that involve substantive use of Wikidata content, Wikimedia Deutschland is embedded in the review process for “exceptional access” requests. Wikimedia Deutschland's input is given significant weight, and any disagreement on the interpretation of the exemption criteria triggers a good-faith joint review within Wikimedia Enterprise’s existing governance and review mechanisms.
Concern: Improvements made for enterprise users will not benefit the rest of the community
We believe that Wikimedia Enterprise should improve access for everyone, not just paying customers. To support this, WMDE is working in close collaboration with Wikimedia Enterprise to emphasize work on:
Better, centralized documentation for developers about all available APIs for Wikidata
Documentation explaining how community developers can use Enterprise resources including clear information about authentication and available access paths through Wikimedia Cloud Services
Jointly aligning on community-requested tools and services that benefit Wikidata editors and reusers more broadly (e.g. data integrity tooling such as the RevertRisk machine learning model).
Concern: What will the money be used for? Will Wikidata benefit?
Wikidata needs ongoing investment. As data and traffic grow, so do the costs of hosting, development and maintenance. All revenue generated through Wikimedia Enterprise is treated like any other unrestricted revenue received by the Wikimedia Foundation, which funds and hosts Wikidata and other Wikimedia projects. It flows into the Wikimedia Foundation’s general budget and is governed through the Foundation’s annual planning and budgeting process, with final oversight by the Board of Trustees. This is the same process used to allocate funds raised through donation campaigns and other fundraising efforts.
Revenue from large-scale enterprise use will support the infrastructure on which Wikidata depends, helping maintain stability and technical capacity for all users.
We support including Wikidata’s data in Wikimedia Enterprise's APIs because we believe the future of free knowledge depends on equitable, sustainable infrastructure to enable broad, responsible reuse. By combining Wikidata’s community-curated, openly licensed knowledge graph with Wikimedia Enterprise’s focus on reliable distribution at scale, this collaboration helps ensure that the value created by volunteers reaches more people and systems worldwide.
Asking high-volume data reusers to contribute financially or through other means is a practical step to protect the work of volunteers, reduce strain on shared resources, and reinvest in the movement. Raja Amelung (WMDE) (talk) 15:00, 31 March 2026 (UTC)
Yes - the most elaborate answer is on our FAQ page on Meta: "Who are the customers?". There's lots of links, context, history there.
But here's some info here too:
We have many individual customers named in ‘long form’ case-studies. At that link - which goes to our project blog, filtered for the tag 'partners') you can see stories about Firecrawl, Mistral, Reef Media, Nomic AI, ProRata, Pleias, Ecosia...
Also, ‘short form’ lists of customers in the annual financial report. The relevant paragraph of the most recent report - the 4th such annual report, stated:
Wikimedia Enterprise had 13 commercial customers utilising the paid tier of the service at the end of this financial reporting period. This includes single and multi-year contracts for either monetary or in-kind support, as well as organisations currently trialing the service. Also, there are many more individuals and organisations using the free tier.[...] Also, there are many more individuals and organisations using the free tier. New commercial contracts signed since June 30 and the publication of this report will be represented in the 2025-26 FY report.
It notes that the total commercial revenue at the end of the last fiscal year represented 4% of the WMF total, and that the project had now fully paid-back its startup investment costs and was profitable.
Google was announced as the "launch customer" several years ago, but in the context of the 25th birthday this year, we also were able to announceAmazon, Meta (facebook), Microsoft and Perplexity.
Relatedly, the relevant policy governing this is the WMF "Wikimedia Foundation Commercial Sales and Contracts Policy". This formalises that there is exactly the same degree of governance and financial oversight for commercial customers as there is major philanthropic grants or donations (subsection: "Commercial Sales and Contracts Requiring Board Notice") - This includes a Human Rights assessment [see also the WMF "Gifts" policy]. Furthermore, that Commercial Sales and Contracts Policy states that we always always prefer to transparently report customers (Subsection "naming") but anonymity remains a right of all donors, grantors, and customers (just as this is also the case for readers, downloaders, and editors). Nevertheless, we will comprehensively report on the revenue received and expenses incurred, both within the normal WMF financial reports as well as separately (subsection: "Reporting"). You can see all those reports and other legal documents on the governance wiki.
I hope that thorougly answers the question. If you've got followups, I invite you to ask over on the Enterprise talkpage on Meta - to consolidate information there for the benefit of other future people with similar questions. LWyatt (WMF) (talk) 16:18, 1 April 2026 (UTC)
Latest comment: 6 months ago6 comments3 people in discussion
On the English Wikipedia, "Organometallic compound" (organometallic compound (Q2642710) on Wikidata) redirects to "Organometallic chemistry" (organometallic chemistry (Q237200) on Wikidata), and Wikidata doesn't allow more than one item to be linked with a given Wikipedia article. When trying to merge Q2642710 to Q237200, I got an error indicating a conflict with links to non-English Wikipedia articles. Further complicating matters, Q2642710 was linked with the English Wikipedia article "Metal-organic compound", which, as defined there, is a distinct concept from "Organometallic compound"; but see the talk pages for Q2642710 and for the English Wikipedia article about metal-organic compounds. However, Q2642710 is primarily about organometallic compounds, not metal-organic compounds. ZFT (talk) 22:03, 1 April 2026 (UTC)
You should leave them be. They are indeed distinct concepts, as @Secretlondon has said. If the editors on enwiki chose to conflate topics, that's on them and should not be reflected here since we know better than to do something so daft. - Yupik (talk) 16:53, 2 April 2026 (UTC)
I repeat: "However, Q2642710 is primarily about [i.e., mostly links to articles or websites about] organometallic compounds, not metal-organic compounds", which makes it redundant with Q237200. It therefore seems to me that it should not be left as is. ZFT (talk) 17:02, 2 April 2026 (UTC)
Latest comment: 6 months ago4 comments3 people in discussion
Здравствуйте! У меня проблема с объединением двух элементов Викиданных, посвящённых одному событию — военному перевороту в Судане 1969 года.
- Элемент с русской статьёй: https://www.wikidata.org/wiki/Q29542127 (Военный переворот в Судане (1969))
- Элемент с английской статьёй: Q21515053
При попытке добавить ссылку на английскую статью выдаёт ошибку, что она уже привязана к Q21515053. Самостоятельно объединить не получается. Помогите, пожалуйста, объединить эти два элемента.
Заранее спасибо! Selass74 (talk) 05:39, 2 April 2026 (UTC)
But that was a temporary location, within a shopping mall, vacated by the museum in 2025. The museum currently has no site open to the public but plans to have a new building, elsewhere in London, by 2028. See its website at https://www.migrationmuseum.org/about-our-project/ for more info.
So what do we do with the Wikidata location fields, which now refer to a site previously occupied by the museum, to which it will not return, and which is now presumably used for some other retail or display purposes? We need to get the map removed from the infobox, and I don't know how to do this apart from just removing the location data from the Wikidata record: is that the way to go? Advice please! PamD (talk) 10:07, 2 April 2026 (UTC)
See my edits: I set the old coordinates as deprecated with a start and end date, with a new preferred "no value" to indicate the current status. Dogfennydd (talk) 17:14, 2 April 2026 (UTC)
Any way to set images based on infobox / first image in linked Wikipedia article?
Latest comment: 6 months ago1 comment1 person in discussion
For example, for Wikidata items about skin diseases an illustration / photo of the skin disease would be quite useful to have. For most cases where a useful image is available on Commons, an image is used in the English Wikipedia article, often even as the image in its infobox (which makes it easy to decide which is the image most fitting for the Wikidata item if multiple images are used in the article).
However, for many of these items, no image has been set even when the EN Wikipedia has had a good-quality image for a long time. The SPARQL-generated dynamic list Wikidata:List of skin diseases with a Commons category but no image set is very long and doing this manually is exhausting and sth to automate more.
Is there a way to add the images to these items in one go? If not, I think it would be nice if somebody could code a tool for such tasks. It could also list the items in a table with a column for the added images so one can go over them. Prototyperspective (talk) 00:00, 3 April 2026 (UTC)
Research methods
Latest comment: 6 months ago3 comments2 people in discussion
I am working on research methods and it seem there are several items refering to the same methods but using diffrent logics of categorisation (some double items notably coming from distinctions existing in the MeSH descriptor ID):
I assume these dinstinctions exist because they are useful in a tree-structured database. But in wikidata we just need the first type of item because we can include in the academic publication item the property study type (P8363) to say the publication use the method and the property main subject (P921) to say that the paper is about the method.
@TTWIDEE: There should be two separate statements with the same value and different qualifiers; you don't need to deprecate anything or mark anything, just make the edit to split off Czech and Hungarian into a distinct statement. No reference is cited here, so the change is quite simple. - Jmabel (talk) 01:17, 4 April 2026 (UTC)
Action Required: Update templates/modules for electoral maps (Migrating from P1846 to P14226)
Latest comment: 6 months ago1 comment1 person in discussion
Hello everyone,
This is a notice regarding an ongoing data migration on Wikidata that may affect your election-related templates and Lua modules (such as Module:Itemgroup/list).
The Change:
Currently, many templates pull electoral maps from Wikidata using the property P1846, combined with the qualifier P180: Q19571328.
We are migrating this data (across roughly 4,000 items) to a newly created, dedicated property: P14226.
What You Need To Do:
To ensure your templates and infoboxes do not break or lose their maps, please update your local code to fetch data from P14226 instead of the old P1846 + P180 structure. A list of pages was generated using Wikimedia Global Search.
Deadline:
We are temporarily retaining the old data on P1846 to allow for a smooth transition. However, to complete the data cleanup on Wikidata, the old P1846 statements will be removed after May 1, 2026. Please update your modules and templates before this date to prevent any disruption to your wiki's election articles.
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Matěj Suchánek (talk) 15:59, 9 April 2026 (UTC)
Help
Latest comment: 5 months ago4 comments3 people in discussion
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Matěj Suchánek (talk) 16:01, 9 April 2026 (UTC)
Merge pages
Latest comment: 6 months ago3 comments2 people in discussion
I was trying to add translations for a page, but discovered that the pages have a "different ID".
From what I have read, a "merge" of the pages is needed, but I don't know exactly how to do it.
The pages are:
Latest comment: 6 months ago3 comments2 people in discussion
There's probably something simple I'm missing, but I'm at my wit's end. The map on Q7571284 displays correctly. But where it's pulled by the infobox on en:Southern Regional Technical College, it is not centered showing the lat/lon point. It's centered on a point significantly northeast. But the marker is on the correct point when you expand the map. On Commons, the map on commons:Category:Southern Regional Technical College is doing the exact same thing and is centered on the exact same point, even though if you move the map, the pointer is in the correct place. I tried moving the lat/lon point here, and it moved the "wrong point" on the map on Commons (and presumably on en.wiki) by the exact same amount - it's like there's some kind of "offset" programmed in that the infoboxes are applying. I tried completely removing the "coordinate location" parameter on Q7571284 and re-adding it from scratch, and nothing changed. Note that it's not happening with other pages' infoboxes (see commons:Category:Southern Regional Technical College Bainbridge Campus). Help please. - The Bushranger (talk) 04:42, 5 April 2026 (UTC)
I've seen similar things before, but I don't know the reason or it has been explained somewhere. The infobox shows a location between Thomasville and Moultrie, so these are possible reasons: it could be some of the locations in Q7571284#P355 but not the last two (unlikely, as the maps of multinational organisations would look more obviously wrong); there is also Q17041613, which is linked to a redirect; but what I think is more likely is that it's the average of the coordinates in Wikipedia or Wikidata and those in OpenStreetMap - only the site in Moultrie (https://www.openstreetmap.org/relation/7943244) has links to Wikidata and Wikipedia, which are currently Q7571284 and the article, not Q17041613 and the redirect. If it is from OpenStreetMap, there could be a delay in updating after it's changed there. Peter James (talk) 10:28, 5 April 2026 (UTC)
Autodescription bug
Latest comment: 6 months ago2 comments2 people in discussion
The "All claims about..." query found at the top of the talk page of every item does not recognise mul labels when (in my case) no English label exists.
Proposal: Add "combat sports nutrition" as a new item
Latest comment: 5 months ago2 comments2 people in discussion
I would like to propose creating a new item for "combat sports nutrition".
This is a specific sub-field of sports nutrition focused on weight cutting, hydration strategies, and performance nutrition for combat sports such as MMA, boxing, and Muay Thai.
It is distinct from general sports nutrition due to the unique requirements of rapid weight management and regulated hydration systems used in promotions like ONE Championship and UFC.
There are practitioners and published work in this area, but currently no clear item exists to represent this field.
Would it be appropriate to create a new item for this concept? Thehwrproject (talk) 23:49, 5 April 2026 (UTC)
Request to add/update Turkish description for Q49844
Latest comment: 5 months ago3 comments2 people in discussion
Hello,
I am a Turkish Wikipedian and I've noticed that the Turkish description for Q49844 (Posta kutusu) is missing or needs a more precise definition. Since the item is currently protected, I am unable to edit it myself.
Could an administrator or an editor with the necessary rights please add the following description for the Turkish (tr) language:
Turkish Description (tr): Mektup ve Posta gönderilerinin toplandığı veya dağıtıldığı fiziksel kutular.
Thank you for your assistance!
--AlarYakp (talk) 15:45, 2 April 2026 (UTC)
"Hi Andy, thank you for the correction. You are right about the capitalization. I will adjust the description to: 'Mektup ve posta gönderilerinin toplandığı veya dağıtıldığı fiziksel kutular.' with proper Turkish grammar rules. Thanks!" AlarYakp (talk) 18:09, 7 April 2026 (UTC)
Wikidata weekly summary #726
Latest comment: 5 months ago1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata in the week leading up to 2026-04-07. Missed the previous one? See issue #725.
Discussions
Wikidata:Requests for permissions/Oversight: EPIC (2) (RfP scheduled to end at 9 April 2026 12:35 UTC)
New requests for permissions/Bot:
ChooseLocal - Task/s: Read-only harvest of Wikidata entities (businesses, banks, etc.) by country, for use in a Canadia-centric local business directory.
JigildikBot - Task/s: Sitelink Management: Connecting newly created articles on kaa.wiki to their corresponding Wikidata items using Pywikibot. Label and Description Updates: Adding or updating Karakalpak (kaa) labels and descriptions for various items (especially geographical and biographical items) using OpenRefine.
JJPMaster (bot) - Task/s: Automatically add sitelinks for Abstract Wikipedia articles
TracklisterBot - Task/s: Adding missing external identifiers to Wikidata items for music artists, sourced from Tracklister (Q138905706), a music database that aggregates data from 20+ platforms. Properties: Discogs artist ID (P1953), Spotify artist ID (P1902), SoundCloud ID (P3040), Bandcamp ID (P3283), Beatport artist ID (P5765), Deezer artist ID (P2722), Last.fm ID (P3192), AllMusic artist ID (P1728), Apple Music artist ID (P2850), Tidal artist ID (P11853). Each claim includes a reference with stated in: Tracklister + reference URL pointing to the artist's page on tracklist.live.
The next Wikidata+Wikibase office hours will take place on Wednesday, 18:00 CEST, 08th April 2026 in the Wikidata Telegram group. The Wikidata and Wikibase office hours are online events where the development team presents what they have been working on over the past quarter, and the community is welcome to ask questions and discuss important issues related to the development of Wikidata and Wikibase.
digiS Workshop: Wikidata für die Sammlungserschließung - 20 April 2026, 10.00 CEST (08:00 UTC), this online workshop (held in German) will practice Wikidata skills across SPARQL, OpenRefine and QuickStatements with a focus on using Wikidata for GLAM Institutions. To register, visit the link.
Mobile editing user testing: Wikimedia Deutschland is planning new user tests for the mobile editing experience (including more data types as a beta feature) in late April–early May. Participants of all experience levels are welcome, and users of right‑to‑left scripts are especially encouraged to sign up. Register here. Participants will be compensated for their time.
Research workshop on content verifiability in Wikidata: Researchers from King's College London (in partnership with the Wikimedia Foundation) invite Wikidata contributors of all experience levels to a 2‑hour online workshop. Participants receive £90 compensation. Research details and registration.
Salon de Paris - a list of annual temporary exhibitions usually held in the Salon Carré of the Louvre Palace.
Mesocosms - about modelling research infrastructure, processes and outcomes involving use of mesocosm (Q138857216)(experimental system to examine the natural environment under controlled conditions).
Wikidata integration in the other Wikimedia projects: We are continuing to investigate how to reduce the number of irrelevant changes showing up in Recent changes and Watchlist by seeing if we can compare the articles before and after the Wikidata change and detect a change in the article (phab:T419823)
GraphQL: You can now do lookups using itemByExternalId and itemBySitelink
Request for feedback: notability and labeling of “BlackSheep Fund”
Latest comment: 5 months ago6 comments3 people in discussion
Hello, I would like to request feedback before creating a new Wikidata item for BlackSheep Fund, an Italian venture capital fund.
The fund appears to have received independent coverage over multiple years. Relevant sources include:
Il Sole 24 Ore
Financecommunity
EconomyUp
Engage.it
Startupbusiness.it
StartupItalia
BeBeez
I have a connection to the subject, so I would like to disclose a potential conflict of interest and seek community input before proceeding.
My intention is to create a minimal, neutral, and well-sourced item, including only basic statements such as:
instance of (venture capital fund)
country (Italy)
official website
LinkedIn organization ID
At this stage, I would avoid adding promotional or non-essential information and focus only on verifiable data supported by independent sources.
As an additional note, the name “BlackSheep Ventures” is currently used in external communication as a broader brand reference. However, based on the available independent sources, “BlackSheep Fund” appears to be the most consistently attested name for the investment vehicle itself. For this reason, I am considering using “BlackSheep Fund” as the main label and potentially including “BlackSheep Ventures” as an alias, subject to community feedback.
I would appreciate feedback on:
whether the subject meets Wikidata’s notability criteria
whether “BlackSheep Fund” is the most appropriate and unambiguous label for the entity
Latest comment: 5 months ago3 comments2 people in discussion
There are a ton of instances listed in the german Also known as field of
film format (Q759853):
Negativformat
6 × 6
6 × 9
Plattenformat
6x6
6x6 cm
6x9 cm
4,5 × 6
6 × 7
Mittelformatfotografie
4,5x6 cm
6x7 cm
60x70 mm
60x90 mm
60x60 mm
45x60 mm
Negativformate
60 × 60 mm
45 × 60 mm
60 × 70 mm
6 x 6
60 × 90 mm
4,5 x 6
6 x 7
6 x 9
6 x 8
Filmformat
Bildformat
Konfektionierung
Latest comment: 5 months ago5 comments2 people in discussion
SPARQL queries don't follow Wikidata redirects, and therefore whenever two elements are merged some queries and automated list stop working.
Part of this problem could be solved if a bot replaced redirects with their destination - or maybe just added the destination without deleting the redirect.
Has this issue been discussed previously? Is there a downside to adding redirect destinations to statements? Would it be OK to open a bot request for that task? Pere prlpz (talk) 09:10, 5 April 2026 (UTC)
Both KrBot and MatSuBot should do this periodically. Are you aware of a redirect item for which the links have not been replaced? --Matěj Suchánek (talk) 15:00, 6 April 2026 (UTC)
No, I'm not aware of remaining redirects - but since I neither was aware of them being replaced, I asked to understand how they were dealt with.
However, I'm aware of redirects that haven't been replaced in Commons structured data - just mentioning as I'm aware that this particular problem should be addressed in Commons and not here. Pere prlpz (talk) 10:04, 7 April 2026 (UTC)
Latest comment: 5 months ago7 comments4 people in discussion
Can we all agree that text-to-speech synthesizers does not belong on this property (or anywhere else on Wikidata outside very specific circumstances) Trade (talk) 10:03, 6 April 2026 (UTC)
Example. Professional audiobook-narrator audio quality, not a 10 years-old amateur recording.No. The particular files are of good quality, useful, and more up-to-date than most manually read audios. Things like image captions are not read in them (and abbreviations spelled out etc etc) to enable a smooth podcast-like listening and I often listen to these files (apparently thousands of other people do as well). Once some dynamic audio is possible of the same quality is not just possible but built in in a way that makes it accessible to most relevant people from the Wikidata item and the Wikipedia article, then this could be brought up again. These are also somewhat a taste or demo for what could eventually be implemented that way. Prototyperspective (talk) 11:40, 6 April 2026 (UTC)
It would be good to rename it to audio version of Wikipedia article. That's also because currently that property is very ambiguously containing both audio versions of Wikipedia articles as well as audiobooks, spoken poems, etc. This is most problematic for items which are about a book or poem but also have a Wikipedia article. You didn't provide any explanation for why you think the audio production method should be that way so it seems to be about the naming/scope of the property which again is ambiguous. Prototyperspective (talk) 21:07, 7 April 2026 (UTC)
This is used for wikipedia articles? That seems a bad idea given they constantly change. I thought this was to be applied to fixed works like poems, books, or lexemes for instance where it's something that does not change over time. Perhaps this should be split into separate properties? ArthurPSmith (talk) 12:43, 8 April 2026 (UTC)
This is used for wikipedia articles? That seems a bad idea given they constantly change. This property is used for about/at least 90% audio versions of Wikipedia articles, the remainder being audio versions of books/poems7.. themselves. I recently added qualifiers for language and recording date (P10135). The latter is I thought important to see how outdated the audio version is (the read Wikipedia article is).
For human-read audios (often hard to listen to since they're read by amateurs), the average age after I categorized all the files on Commons via the cat I created c:Category:Spoken Wikipedia by year is about 14 years (the average age of versions used in Wikipedia maybe 11 years). The average age of the audio versions that I added is 2 years. Now Trade is complaining that my audio versions are outdated. I can't make much sense of that. Perhaps this should be split into separate properties? That's exactly what the property proposal I created Wikidata:Property proposal/audio version of text is about. If it gets implemented the property could be renamed and things can be disambiguated. Prototyperspective (talk) 12:54, 8 April 2026 (UTC)
Anybody know about QuickStatements authentication?
Latest comment: 5 months ago2 comments2 people in discussion
Several of us are having trouble with the message "Problem generating OAuth signature; user needs to have submitted a batch manually at least once before", as described here. Can anyone help? —scs (talk) 00:50, 9 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 10:31, 14 April 2026 (UTC)
How to handle Company name change for items
Latest comment: 5 months ago4 comments3 people in discussion
I need help/advice as to what the correct procedure is when a company has changed it's name, and how that is handled in Wikidata.
The company in question is a public library service called Connected Libraries, where editors have updated it's associated Wikipedia page with the changes, but the linked Wikidata page still has the old name.
i have done a little bit of editing on Wikidata before, but still find it all very confusing. I would guess the process would be to create a new item with the new/current company name and link that to the Wikipedia article, and then have a some kind of statement on both the old and new name item pages that point back to each other? Dave247 (talk) 12:02, 13 April 2026 (UTC)
Thanks, much appropriated. I did try searching and perhaps just didn't look hard enough as to what (if any) the procedure was for name changes, and didn't want to take the risk in case there was something.
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 10:30, 14 April 2026 (UTC)
P625 for countries
Latest comment: 5 months ago9 comments3 people in discussion
After introducing hundreds or thousands of coordinates myself, I'm not aware of any page or approved policy about where to place them for non zero area items like countries (or counties, or cities, or buildings, or battles), despite some loosely followed usual practices for some classes of items.
I've been having fun creating SPARQL queries to calculate distances between countries. When I did this for Canada, I tried to understand how the specific coordinate was chosen. I gathered that it corresponds to a 'geographic mean,' but it isn't immediately obvious to the eye. I would just like to know a bit more about the methodology used to determine these points. Simon Villeneuve (talk) 11:01, 8 April 2026 (UTC)
If you want to use coordinates to calculate distances, you should expect error bars as large as the size of the involved countries. You might find some consistency between countries but I wouldn't put much hope on it, and much less for smaller objects than countries. Maybe coordinates of geographic center (P5140) could be useful to compute distances in a more reliable way. Pere prlpz (talk) 11:13, 8 April 2026 (UTC)
Yes, I have made other requests to that effect. However, the focus here is not my requests, but rather the reliability of the P625 coordinates for countries. These are currently unsourced, and I cannot determine their origin. Sooner or later, we will need to improve their verifiability. Simon Villeneuve (talk) 22:04, 8 April 2026 (UTC)
We could standardize how we choose the coordinates to specify better their meaning, but it doesn't seem that specifying which map was used to take the coordinates of Canada among the thousands of reliable maps depicting Canada in the same place doesn't seem to be a noticeable improvement. The help page in Wikipedia about verifiability used to say that it's not necessary to add a citation to claim that Paris is the capital of France. A citation about where is Canada seems an equivalent situation to me. Pere prlpz (talk) 22:15, 8 April 2026 (UTC)
Hi there, I have to disagree with you. First of all, the method for determining a single set of coordinates for Canada, or any other big geographical zone, is not as trivial as stating that Paris is the capital of France. Furthermore, the idea that it’s unnecessary to source the fact that Paris is the capital of France is a habit imported from Wikipedia. There, the goal is to maintain a certain balance and prevent encyclopedic text from being overwhelmed by citations when the added value seems minimal. On Wikidata, this is a non-issue. If we look at similar properties for the NSEW extreme points (P1332 to P1335)—which are much closer to your "Paris=capital of France" example—these are detailed with statement is subject of (P805) and, for the most part, start time (P580). I believe it is legitimate to expect that P625, which is arguably the most used geographical property in our open knowledge base, should be better supported when it comes to big geographical objects like countries. Simon Villeneuve (talk) 22:40, 10 April 2026 (UTC)
I don't remember where I've seen it documented, but here are the guidelines I remember (and use) when choosing coordinates for non-point objects:
The chosen point should be within a distance X of the ideal point, where X is 10% of the "size" (diameter) of the object. Now, of course, most objects aren't circular, so they don't have a single diameter. Also I haven't said what the "ideal point" is. It's probably the geographic mean, suitably defined, but in conjunction with the 10% threshold, and point #2, it doesn't end up mattering a whole lot. Others might disagree, but in my opinion it's fine to just pick a point that looks good, in terms of being "in the middle".
It's important not to specify the chosen point with too much precision. In fact, you want to use the least precision you can, without violating the 10% threshold. Basically, the bigger the object, the coarser the precision you want to use.
Some years ago I went through the exercise of picking coordinates for all the countries in the world, and all the states in the United States, based on the above two guidelines. I then compared the points I'd chosen to the coordinates given in Wikipedia. I think I remember finding that in almost all cases the two points (mine and Wikipedia's, for each object) coincided exactly.
Here's another way of thinking abut it. You want to pick a point "in the middle", which is more or less the same spot you'd pick to put the object's name if you were drawing a map. In both cases you want it to look good, because cartography — mapmaking — is, famously, rather subjective — artistic, even. Good maps are drawn with, unapologetically, a fair amount of human judgement of what looks good, i.e. not necessarily basing everything on purely objective algorithms. So I don't see anything wrong with picking coordinates the same way. —scs (talk) 02:04, 9 April 2026 (UTC)
I appreciate this detailed explanation of the guidelines you follow. To be clear, I have no issue with the criteria for choosing a point being based on aesthetics or cartographic judgment. My main concern is that we currently have no information regarding these criteria within the items themselves. Consequently, these coordinates are not "reliable" in the sense that they are not linked to a verifiable source or a documented methodology. Even if the choice is subjective or artistic, that choice should still be supported. Without a source or a qualifier (like P805 or a reference URL) explaining why this specific point was chosen—whether it’s based on a specific algorithm or a manual cartographic selection—the data remains "silent" about its own origin. On a collaborative platform like Wikidata, being able to trace back the "how" and the "who" is essential for the long-term reliability of the database. Simon Villeneuve (talk) 22:47, 10 April 2026 (UTC)
Multiple castings of a sculpture
Latest comment: 5 months ago3 comments2 people in discussion
Is there an explanation somewhere of how to do this right? I assume it should be somewhat analogous to what we do with multiple editions of a book, but everything I've thought to look up as an example seems to do it wrong, e.g.:
Indeed. This is how they have been displayed on Wikimedia sites for ages (except here until now?). As you noticed it Wednesday evening, it was likely part of the regular site update, but I couldn't quickly find it in the changelog.
That seems to be it and I've found the reason. Since it doesn't bother me personally that much, I'll leave it at that. But if anyone's interested, I can explain. --Gymnicus (talk) 16:37, 9 April 2026 (UTC)
Correct. All links that are equipped with the class "external" in the source code are displayed this way for data objects with geographic coordinates. --Gymnicus (talk) 08:56, 11 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. RVA2869 (talk) 07:08, 17 April 2026 (UTC)
move party memberships to precise property
Latest comment: 5 months ago3 comments2 people in discussion
Latest comment: 5 months ago2 comments2 people in discussion
Hi. I lack experience with regard to link spamming in Wikidata. Although this would certainly raise the alarms in Wikipedia, does it qualify as spam here? They are adding to described at URL (P973) a shitty website that generates a "Your connection is not private" browser warning. It apparently does not include original content, but some data, probably interpolated or so (machine generated). Is this useful for Wikidata? strakhov (talk) 09:44, 12 April 2026 (UTC)
Latest comment: 5 months ago2 comments2 people in discussion
How are the transliterations on Wikidata made? They seem to be faulty. E.g. they use m for ং which is plain incorrect. Maybe Chittagonian does it idk, but Kolkata and Dhaka Bangla pronounce it like ng/ŋ. ChaoticVermillion (talk) 12:00, 12 April 2026 (UTC)
@ChaoticVermillion: You may wish to be more specific about which transliterations you are referring to (on item aliases? on lexeme forms?) and to read about the various schemes--such as ITRANS and ISO 15919--that are used for transliterating Indic scripts, of which Bengali is but one. Mahir256 (talk) 13:04, 12 April 2026 (UTC)
notices for multiple
Latest comment: 5 months ago10 comments3 people in discussion
I receive notices that multiple Wikidata infobox have been created (from the text saying saying Wikidata item has been created for xxx and nnn other categories) (for Commons categories that I created), but when I open the notice, I only find information for the xxx Commons category, not the nnn others. How can I see info on all multiple categories supposedly involved? Hmains (talk) 20:23, 4 April 2026 (UTC)
Just making sure: You get notifications like "Category:Foo and 10 other pages were connected to Wikidata items, where data relevant to the topics can be collected." and you would like to see the individual notifications like "The page Category:Foo was connected to the Wikidata item Q12345, where data relevant to the topic can be collected."
I don't use email and your description and analysis are completely correct. Other than using the link you provided here, how can I navigate to this special notifications pages. I have looked around and cannot find it. Hmains (talk) 03:24, 10 April 2026 (UTC)
The simplest way to access to commons:Special:Notifications is to click the notifications button in Commons. If you click the notification button in Wikidata (or any other project different than Commons) you go to d:Special:Notifications (or the local equivalent on other projects) which show all the notifications for Wikidata but only a digest of the notifications from Commons and other projects. Pere prlpz (talk) 23:12, 10 April 2026 (UTC)
Good, but where is this 'notifications button' in commons? I sure do not see such a button. Is there an option I have to turn on? Thanks Hmains (talk) 04:03, 12 April 2026 (UTC)
In the same way of the notifications button in Wikidata, at the top right of the screen.
Latest comment: 5 months ago2 comments2 people in discussion
Is there anyway to show all references for an item, like a gadget or a JS addition, instead of manually opening each one? Trivialist (talk) 16:21, 11 April 2026 (UTC)
Latest comment: 5 months ago4 comments3 people in discussion
Just recently I started shifting my focus to Wikidata. I want to create and edit items concerning musical works by Guided by Voices (Q1472033). Starting with singles, I almost immediatly stumbled upon an interesting issue. A song isn't just a song. It can be described as a song (Teenage FBI (Q72696472)), as a vocal track (Teenage FBI (Q117815892)), as a single (Q139166320, where side A is the actual song). The single can have different (re)issues, on different formats. I can imagine following the logic of the likes of MusicBrainz or Discogs, where there is a release group or master with different releases. But that approach is very labor intensive and prone to error. On top of that, MB's database also contains recordings of songs as separate entities. How far do we want to take this? Hiro (talk) 13:31, 11 April 2026 (UTC)
If we went as far as books, each recording of each song should have its own entry, as they are different interpretations of the work. And you could imagine how many versions of a band's most popular songs they might have released over a career, or recordings of Beethoven's Fifth done by orchestras. Pragmatically we want entries for every (notable, ie published) musical ensemble, the albums and singles they created from scratch. Every song they wrote would be nice, but once you get to classical recordings, covers and variants of each song we'd probably be overwhelmed, unless they were regarded as special by the community. Vicarage (talk) 14:09, 11 April 2026 (UTC)
Probably also worth discussing this with other interested folks involved with WikiProject Music. It looks like there was a discussion on the talk page a few months ago about a similar issue, and problems with how various language editions of Wikipedia deal with the difference between songs and singles. M2Ys4U (talk) 17:36, 11 April 2026 (UTC)
Question about best practices for adding source citations?
Latest comment: 5 months ago2 comments2 people in discussion
Hello Wikidata community! I'm relatively new to editing and wanted to ask about best practices for adding source citations to statements.
Specifically, I'd like to know:
1. What are the preferred reference properties for different types of sources (books, websites, academic papers)?
2. How detailed should citations be? Should I always include page numbers for books?
3. Are there any tools or gadgets that make adding references easier?
4. What are common mistakes beginners make with citations that I should avoid?
Best practices for adding references to statements?
Latest comment: 5 months ago2 comments2 people in discussion
Hello Wikidata community!
I'm relatively new to editing Wikidata and I've been working on adding statements to various items. I've noticed that some statements have references while others don't.
Could someone please share best practices for:
When should I add references to statements?
What makes a good reference source?
Are there preferred properties for different types of references (URLs, books, academic papers)?
Any common mistakes to avoid when adding references?
Latest comment: 5 months ago2 comments2 people in discussion
Hello everyone! I'm new to Wikidata and would love to start contributing. Could someone point me in the right direction? What's the best way for a beginner to get started with editing? Are there any simple tasks or tutorials you'd recommend? Thanks in advance! ~2026-22513-08 (talk) 10:17, 13 April 2026 (UTC)
Adding type classification for Serbian cultural heritage monuments (P4245)
Latest comment: 5 months ago15 comments6 people in discussion
I hope I'm in the right place... Hello everyone, I would like to ask for help and guidance regarding Serbian cultural heritage monuments on Wikidata. There are currently around ~2,658 items using the property P4245 cultural heritage monument in Serbia ID. Each ID includes a prefix that clearly defines the type of monument:
СК – monuments of culture (cultural heritage)
ПКИЦ – spatial cultural-historical unit (historic district)
АН – archaeological site
ЗМ – landmarks (notable place)
This means that the classification already exists implicitly in the identifier (as defined by the regex), but in most cases it is not explicitly modeled in the data. There is also an additional division and categorization, but this is the most important.
Proposal: We would like to classify all these items into the four categories above using structured statements (for example, via instance of or another appropriate property).
Why this matters:
better querying and filtering
improved reuse in tools and applications
clearer structure of cultural heritage data
One concrete use case is Wiki Loves Monuments, where this classification would be very helpful for data processing and analysis.
We already have lists of monuments on Wikipedia grouped by these categories, which could potentially be used as a source. And here is an official list.
We need help with:
deciding the best modeling approach (e.g. instance of vs. another property)
confirming that this approach is appropriate
possibly running a bot or semi-automated process to add this classification
We currently do not have the technical capacity to perform mass edits ourselves, and your help is greatly appreciated. Any advice, examples, or collaboration would be greatly appreciated. Thanks a lot :) --MikyM (talk) 04:45, 9 April 2026 (UTC)
Faced with similar problems, in other countries we use heritage designation (P1435) to specify the kind of protected monument.
Using instance of (P31) for the same purpose is not a good idea because instances may be related to different characteristics of the item. For example, a castle and a wayside cross (with different P31) could be both protected as ЗМ. Pere prlpz (talk) 23:04, 10 April 2026 (UTC)
That sounds fair. Now we just need to find technical support (a bot) for mass editing. thanks everyone for the suggestions MikyM (talk) 22:03, 11 April 2026 (UTC)
@MikyM Does this work for you? Dry run reports (I only have data from the Ministry of Culture via opendata gov, which is about 1,300 monuments). Report: link Proposed changes: link - Mmns21 (talk) 19:42, 12 April 2026 (UTC)
I have noticed that new "item-requires-statement" constraints have been added to cultural heritage monument in Serbia ID (P4245), which now specify distinct Q-codes for different protection levels of Historic Landmarks and Spatial Units (Great vs. Exceptional Importance).
Since my initial plan treated these as general categories, do we have access to specific data regarding the protection levels for "Historic Landmarks" (ZM) and "Spatial Cultural-Historical Units" (PKIC)?
To satisfy the new Wikidata validation rules and avoid warnings, I would need to split them into their respective specific importance items. I would appreciate your input on whether our source data supports this granularity.
@Multichill Regarding Property:P31, I mistakenly thought that the "Cultural Heritage of Serbia" status should also be listed there as an instance, as I had seen it implemented that way on some other items. I understand now that it is redundant/incorrect and I won't be doing it anymore. I will go back and check my recent edits to remove those entries from P31 where I added them.
I have a quick follow-up question regarding Property:P1435 (heritage designation). Since we established that Q3370018 (Cultural Heritage of Serbia) doesn't belong in P31, should I add it as a value in P1435 alongside the specific protection level (like "Exceptional Importance"), or is the specific level alone sufficient?
About the redirect for Q4785451, I noticed it right after the first edit. I have already updated my script to check for redirects to prevent this from happening again; luckily, that was the only one.
Also, I have copy of the official databases from the Ministry of Culture via the Open Data portal, so I can automatically update or cross-reference all items that are in their registry.
Latest comment: 5 months ago1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata in the week leading up to 2026-04-13. Missed the previous one? See issue #726.
Discussions
Open request for adminship: ZI Jony (2) - RfP scheduled to end after 17 April 2026 13:09 (UTC)
New requests for permissions/Bot:
Nirmos Bot 3 - Task(s): Turn one or more consecutive hard (non-breaking) spaces into one regular space in Swedish descriptions.
Alex NB OT - Task(s): Correction of incorrectly specified links to population data sources containing wikitext artifacts with categories, which leads to incorrect categorization of articles.
ReNeuralAgent - Task(s): (1) add descriptions, (2) Latvian labels/descriptions, (3) 'retrieved from' and 'source URL' to unreferenced Statements, (4) missing aliases from external Identifier sources, (5) Geo coordinates, (6) external identifiers, (7) Population numbers, (8) remove 'dead sitelinks', (9) constraint violations.
Open request for comment: Mass-editing policy is still open and requires your input.
Events
Past: Missed the second quarter Wikidata+Wikibase office hour? You can catch up by reading the session transcript here: 2026-04-08 (Q2 2026)
Current: (Spanish) Public Domain in Latin America 2026 - 1st edition of the campaign to improve public domain data for Latin America is running until 15 June.
Next Linked Data for Libraries LD4 Wikidata Affinity Group session 14 April, 2026: We have our next LD4 Wikidata Affinity Group Session on Tuesday, April 14, 2026 9am PT / 12pm ET / 16:00 UTC / 6pm CEST (Time zone converter). QuickStatements is one of the most widely used tools in Wikidata, enabling users to upload and edit large volumes of structured data efficiently. Originally developed by Magnus Manske, the tool has become essential for institutions, researchers, and volunteers working with open data. The new QuickStatements 3.0, developed by Wikimedia Brasil with support from Wikimedia Deutschland, introduces a modernized interface, improved performance, and new features shaped by community input, making it easier than ever to contribute high-quality data to the Wikimedia ecosystem. Event page: https://www.wikidata.org/wiki/Wikidata:WikiProject_LD4_Wikidata_Affinity_Group/Project_Series/QuickStatements3
Open Scholarly Profiles with Wikidata - Wednesday, April 22, 2026 1300 - 1430 EDT (1700 - 1830 UTC). This is an onsite event at University of Central Florida.
Visibility of Communities in Nigeria 2.0: 17.04 - 25.04, (please register on the link). Help enrich Wikidata with cultural preservation, tourism and inclusive development data for items on South Nigerian communities.
HumansMap - a connection-visualiser and explorer app for 3 million notable humans, all data sourced from Wikidata.
Other Noteworthy Stuff
Call for tool builders: EntitySchemas listening tour: The Wikidata team wants your feedback on EntitySchemas to improve data quality and discoverability. Share your experiences, pain points, and needs via the project talk page or this short Google form (including option for a 30-min video call).
hardware is incompatible with (significant elements with which a computer hardware or electronic device is incompatible and which indicates a significant property of this hardware.)
Peh-oe-ji (writing system for Taiwanese Hokkien (Q36778) or other Southern Min (Q36495) language varieties in Fujian and South East Asia.)
heir apparent (person designated to take on royal position after death of subject)
Newest database reports: Short Pages - A list of pages (mostly Items) that are very small, often appear completely blank. A review to judge whether they are suitable for deletion, victims of vandalism or require merging or expanding may be appropriate.
Wikidata integration in the other Wikimedia projects: is working on introducing metrics that help observe the impact of Recent Change related work. Work continues on improving the Diff (T419244, T419823)
Royal Horticultural Society plant IDs need updating
Latest comment: 5 months ago2 comments2 people in discussion
Lately I've noticed some items on species of plants don't have a Royal Horticultural Society plant ID (P8765) even though the Royal Horticultural Society (Q1032739) has a listing for that species. I suspect this is because the RHS updated their website, and Wikidata has not caught up. This would be on the order of 100 or so "new" species. I've been adding them manually, but could anybody get the data from the RHS website and add those IDs? Abductive (talk) 09:42, 14 April 2026 (UTC)
Latest comment: 5 months ago1 comment1 person in discussion
Exposure has historically been listed as a cause of death / medical condition at least in the United States. Most often the actual cause of death / medical condition is hypothermia or hyperthermia, but at least in the 19th century it was common to write "exposure" on death certificates and medical examinations. I have a number of examples, but Q132794167 is the one I am working on. I don't have hard dates, but this practice fell out of fashion sometime in the 20th century.
I posted a discussion topic on Impact of the Environment (Q26897695) a year ago, but I did not get any feedback. I am trying to determine if "exposure" should be its own item as an instance of cause of death (Q1931388), or if Impact of Environment should be an instance or subclass of cause of death.
I lean towards creating "exposure" as its own item as impact of environment could apply to any number of non-medical examples. However, I am happy to list impact of environment as a cause of death. I need to be able to list one or the other as a cause of death (P509), which cannot happen currently.
Option 1. Create new item Exposure as an instance of Cause of Death (Q1931388) and/or Disease (Q12136). I am also happy to list this as an instance of an obsolete medical term (Q61915880), although I do not know if the term is still in use outside the United States.
Option 2. Edit Impact of the Environment (Q26897695) to be an instance or subclass of cause of death or disease.
Latest comment: 5 months ago3 comments3 people in discussion
I'm a new user trying to create an item for my company, but I'm getting blocked by the abuse filter. Can someone help me with this issue? Solomining (talk) 18:14, 14 April 2026 (UTC)
Latest comment: 5 months ago3 comments3 people in discussion
Q31102633 (Dun Creich, hillfort in Highland, Scotland, UK) and Q24645733 (Dùn Creich, hill in Highland, Scotland, UK) both seem to be referring to the same locale, but I'd like a second opinion on this, especially as neither has an English-language Wikipedia page. Edfan32 (talk) 01:49, 13 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 14:33, 20 April 2026 (UTC)
Request for item: Ryan Finnie
Latest comment: 5 months ago4 comments3 people in discussion
Hi, a quick background: I am the author of Finnix, which is notable due to popularity and history, has a Wikipedia page and Wikidata item (Q1153304), etc. All good. However, I myself am arguably not notable. That's okay, but a complication is there is someone with the same name as me, a Scottish footballer (Q7384054).
This has caused organizational confusion, to the extent that there is a disambig at the top of his page to "Ryan Finnie (software developer)" which redirects to Finnix. At one point Q1153304 even listed Q7384054 as the author, which was obviously incorrect. Someone corrected that at some point, but it Finnix currently lists no author.
Reading Wikidata:Self-promotion, it seems like I should not be the one to create my own item, but I do believe it should exist for taxonomy and to help with confusion. Would someone be willing to own this? Thank you. Fo0bar (talk) 20:47, 14 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 14:33, 20 April 2026 (UTC)
Polymarket (Q123502863) is under active attack
Latest comment: 5 months ago3 comments3 people in discussion
Malicious URLs are being repeatedly injected into the official website property for Polymarket, which is propagating to Wikipedia's official URL on its article. The WikiData entry for it at Q123502863 should be protected. ~2026-23806-52 (talk) 21:08, 17 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 11:51, 20 April 2026 (UTC)
Latest comment: 5 months ago6 comments3 people in discussion
Hi, on the wikidata infobox on Commons, the value writer (Q36180) is rendered as "penman"?? Should that not just be the neutral "writer"? (see Category:Edward_Henry_Vizetelly for example. Deadstar (talk) 12:19, 18 April 2026 (UTC)
@Deadstar: the wikidata infobox on Commons is picking up "penman" as the English language "male form of label" for Category:Edward Henry Vizetelly. The English language "female form of label" is "penwoman" and non-binary individuals get "writer". I agree that the output on the commons infobox is unhelpful, I don't know whether penman and penwoman should be removed or deprecated as male and female forms of label. TSventon (talk) 14:43, 18 April 2026 (UTC)
@TSventon: Thanks for your reply. I would agree that these are not in current use, is there somewhere else that I need to raise this to get the labels deprecated? Deadstar (talk) 07:45, 19 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 14:31, 20 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 14:31, 20 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 13:14, 20 April 2026 (UTC)
Make Lexeme titles like Wikidata items
Latest comment: 5 months ago1 comment1 person in discussion
I like to copy title+ID for later use, e.g. `universe (Q1)`. with Lexemes I cannot do that easily (sometimes there are multiple possible titles for the same lexeme, and in that case I am fine with `en`): any ideas? AddyLockPool (talk) 06:36, 15 April 2026 (UTC)
Weird stuff coming from the new Open Wikipedia Ranking
Latest comment: 5 months ago5 comments4 people in discussion
https://www.wikidata.org/wiki/Q9184 is "graphic novel" (nonsense, and makes the Book of Genesis the top of the list of books; you fixed something a couple of years ago when all books of the Bible were "books")
"play" now includes all sketches. There must some new "instance of" weird transitive closure. Wasn't true in 2025. Will investigate.
That was indeed an edit by InventaireBot (talk • contribs • logs) on behalf of an Inventaire user without a Wikidata account. Thanks for investigating, I'm happy to see that it was probably done in good faith. I'm considering restricting edits on behalf of Inventaire users for protected pages, which would have prevented this specific case. Maxlath (talk) 21:21, 15 April 2026 (UTC)
Latest comment: 5 months ago2 comments2 people in discussion
I have got a valid request from someone who is using OAuth. They need to be given an IP exemption request. I know the name of the tool and the name of the IP range, but I am not sure how I give the IP exemption just for this tool and for OAuth. Could someone help me please? Thanks. Ymblanter (talk) 10:11, 15 April 2026 (UTC)
Hi @Ymblanter, please send me an email with the tool information and details about your exemption request. Members of my team (Wikidata Platform) or WMF site reliability engineers should be able to help. BTracy-WMF (talk) 18:48, 16 April 2026 (UTC)
Italics in part of a title of a scientific paper?
Latest comment: 5 months ago3 comments2 people in discussion
Regarding the scientific article about ornithology at Q134876458. It is used as a Wikipedia {{Cite Q |}} reference. Is it possible to italicize the species scientific name in the statement title? It appears that Help:Label#Fonts and characters says it's not possible. I'd be more inclined to use Wikidata references for scientific papers if italics were available. Thank you. SchreiberBike (talk) 14:59, 16 April 2026 (UTC)
In summary, it is (in my opinion rightfully) argued that there is a should be a distinction between name pages and general disambiguation, A name page focuses on the name meaning of a word and should ideally in addition to list notable people with the name, also give information about the name (origin/statistics). See w:Watt (disambiguation) and w:Watt (surname).
However, except for English Wikipedia, no other language version are as ambitious with the name pages. They are mostly the same as disambiguation page. This leads to constant interwiki conflicts.
Property proposal: MeetStadium ID (external identifier for stadiums)
Latest comment: 5 months ago2 comments2 people in discussion
I've proposed a new external identifier property for MeetStadium, a stadium visitor guide database covering 135 venues (expanding to 700+) across the USA, Mexico, Canada, England, Spain, France, and Brazil, including all 16 FIFA World Cup 2026 host stadiums.
Each stadium has a stable slug identifier (e.g., metlife-stadium, estadio-azteca, camp-nou) and the formatter URL is https://meetstadium.com/stadiums/$1/.
Latest comment: 5 months ago3 comments2 people in discussion
On SIG Sauer (Q2280505), I tried to properly denote all the legal forms of the company, and the fact that it is in fact several separate ones, but if my understanding of this is correct, there should be seperete items for all the companies (branches?). Michael21107 (talk) 18:39, 14 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 14:50, 23 April 2026 (UTC)
HI
Latest comment: 5 months ago4 comments3 people in discussion
Maybe that place could be linked more visibly or be shown when people register here or come here (registered first on another Wikimedia project). --Prototyperspective (talk) 12:55, 23 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Prototyperspective (talk) 12:55, 23 April 2026 (UTC)
Now I can not edit modules
Latest comment: 5 months ago9 comments3 people in discussion
I can not edit MediaWiki:Gadget-markAdmins.js, it tells me that me central login expired and invites me to login. When I try, it sends me back (central login expired) after I add my code from TFA. Otherwise, I am logged in and can edit and delete items. I have never seen anything like this. Does anyone else have the same problem? Ymblanter (talk) 19:35, 17 April 2026 (UTC)
First idea is that there is something wrong with your browser, e.g. security settings too strict or some adblocker blocking servers that are necessary for authentication. Do you have anything like this, and can you verify with another, clean browser or browser profile? —MisterSynergy (talk) 11:28, 18 April 2026 (UTC)
After experimenting a bit on two devices, if I type the password manually from the keyboard it asks for my TFA but then sends me back. If I copy it by the mouse or let the automatic password manager to fill it in, I still get asked about TFA but then I can edit. Ymblanter (talk) 12:06, 18 April 2026 (UTC)
Latest comment: 5 months ago6 comments3 people in discussion
I can't help but notice this gadget seems to produce an extremely high amount of constraint errors and poor data from Russian Wikipedia that others users are expected to clean up after. I feel like it's getting to a point where the existence of the gadget is actively harmful to Wikidata
The technology behind it, the Graph extension, got disabled years ago. The successor doesn't offer Wikidata support and will probably get it in 25 years, so till then they will be broken. Sjoerd de Bruin(talk)19:38, 17 April 2026 (UTC)
According to the Japanese wiki article the manga came first. The Italian wiki article and the English wiki article for the main series make no mention of the sequel manga series for whatever reason. The other issue is that Tiger Mask (Q1211572) is a big conflated mess that I haven't got round to fixing yet. —Xezbeth (talk) 05:16, 20 April 2026 (UTC)
However, I think the German translation is incorrect because it refers to a different concept (related to cooking, not advertising) : https://de.wikipedia.org/wiki/Annonceur
This has been fixed - I created a new item for the German term (I couldn't find anything like this kitchen position in other languages, but it may be a duplicate of something else), and merged the French and Spanish ones. See announcer (Q2851757). ArthurPSmith (talk) 16:12, 20 April 2026 (UTC)
modelling graves
Latest comment: 5 months ago2 comments2 people in discussion
What is the primary modelling scheme for graves? Do we, when we are nor sure how to model, model all the alternatives? Is there a process (provided former questions being answered properly) to get rid of parallel modelling alternatives (including streamlining personal tastes to a single alternative)? best --Herzi Pinki (talk) 21:11, 20 April 2026 (UTC)
Hi, it's probably specific to Père-Lachaise cemetery for historical reason. Some wikimedians asked me to stop what I was doing on Commons and created Wikidata items for graves. That's why the info is now duplicated. Pyb (talk) 21:36, 20 April 2026 (UTC)
Wikidata weekly summary #728
Latest comment: 5 months ago1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata in the week leading up to 2026-04-20. Missed the previous one? See issue #727.
Discussions
Open request for adminship: Yamato Shiya - RfP scheduled to end after 26 April 2026 11:10 (UTC)
Closed request for adminship: ZI Jony 2 - Closed as successful
Open Scholarly Profiles with Wikidata - April 22, 2026 1300 - 1430 EDT (1700 - 1830 UTC). This is an onsite event at University of Central Florida and requires registration (see link).
University of Central Illinois - How does data power Wikipedia and Wikidata? Discover how your data skills can make an impact. Join the two onsite sessions (April 21, follow the link for registration details). Module 1 - GLAM Wiki and the Wikimedia Ecosystem: Commons and Structured Data: 0930 - 1130 CDT - An overview of GLAM-Wiki (Galleries, Libraries, Archives and Museums). Module 2 - Wikidata: Editing, Querying, Citations and GIS Applications, 1300 - 1500 CDT
Press, articles, blog posts, videos
Blogs:
Women in Photography – Wikidata Workshop with LightBox Photo Library - to address the underrepresentation of women photographers in the Wikimedia Projects, this workshop brought tech reporters, librarians, researchers and photography enthusiasts to understand how Wikidata can unlock data silos and connect different projects (in the Wikiverse and external) to make data on women photographers more searchable.
Depictor by Hay Kranen is a tool that add structured data statements to Wikimedia Commons using a game-like interface
Other Noteworthy Stuff
What is Wikidata? - Library Carpentry is part of The Carpentries, a registered non-profit teaching foundational coding and data science skills. They recently updated their introductory course to Wikidata and knowledge graph concepts.
New General datatypes property proposals to review:
especially (qualifier for statements to refine a value that applies more generally, but applies especially to a more specific value; a more specific qualifier than "including" (P1012))
independent of theory (theory that proves neither this proposition nor its negation)
EPBC conservation status (the conservation status from the Australian Environment Protection and Biodiversity Conservation Act 1999 assigned by the Australian Department of Climate Change, Energy, the Environment and Water)
Newest database reports: Children of unborn parents, this list shows the child entity's birth date predates the parent entity's birth date: good candidates to check if the birth and relationship statements need correcting.
Showcase Lexemes: slide (L9704) - English noun (slaɪd) meaning "a photographic transparency", "a playground or gym apparatus", or "a mass movement of earth or snow"
The Wikidata team worked on explored how to reduce load for low data users T400325, fixed some bugs on the new mobile editing on Items T418110, T414454 and improved some error messages T417797, T412145
Latest comment: 5 months ago2 comments1 person in discussion
I noticed this morning while cleaning up items that have the same Library of Congress Authorities ID (P244) that constraint violation flags no longer seem to appear on items that violate the unique value constraint. This is an example pair: George Leslie Rapp (Q94413386) and George Leslie Rapp (Q84562141). I took a look in Phabricator and couldn't find an issue for this, but I'm not very techy so it's very possible I've missed it. I first noticed this happening at least a couple weeks ago, and figured someone was working on it. Since it hasn't been resolved yet, I figured I should check in. Is this happening to anyone else? If so, are there plans to fix this?
each item here has mul-label "en" and seems to have part of BLOD: Biomedical Linked Open Datasets, at least each links there.
The creator of the items is User:Sanalatif0806 who also created "BLOD: Biomedical Linked Open Datasets (Q137008561)", the latter has "author name string" = "Sana Latif, Maria Angela Pellegrino", publication date 2025 and several claims "has part", but no evidence for that has been provided.
And several items, including those that existed before 2025, received part of BLOD, e.g. Basic Formal Ontology (Q4866972), that is where I found BLOD and then the related items.
A bot (User:MsynABot) protected the BLOD-item https://www.wikidata.org/w/index.php?title=Special:Log&page=Q137008561 22:02, 27 February 2026 MsynABot talk contribs protected BLOD: Biomedical Linked Open Datasets (Q137008561) [Edit=Allow only autoconfirmed users] (indefinite) (Highly used item: to be indefinitely semi-protected per Wikidata:Protection policy#Highly used items; please use Template:Edit request on the item talk page if you cannot edit this item
Latest comment: 5 months ago1 comment1 person in discussion
Hello Project chat/Archive/2026/04,
We are excited to announce that Wiki Loves Bangla 2026 has started! This year’s theme focuses on Bengal festivals, inviting participants to capture and share images and videos of the diverse cultural celebrations across Bengal.
Wiki Loves Bangla is an international photography contest on Wikimedia Commons aimed at documenting Bengali culture and heritage worldwide. It is organised annually as part of the Bangla Culture and Heritage Collation Program, with a dedicated theme each year.
How You Can Participate, it's easy and simple, and every upload contributes to the world's largest free knowledge repository:
Q376 once was labeled "clock" in English - that was changed last July in this edit. Q376 is listed as a subclass of Q42622779, but I'm not entirely convinced the distinction is there clearly in the many language wikilinks on Q376. Not sure what's best here, but a merge might make sense (after removing the subclass relation). ArthurPSmith (talk) 16:16, 20 April 2026 (UTC)
No, in Dutch the difference is clear:
clock (Q376) is a clock, a (mechanical or electronic) device that tells the time
timepiece (Q42622779) is "clockwork", ie. the mechanics inside a clock or any other timing device
I think a clock is an example of a of timepiece. If the Dutch term for clockwork is linked to timepiece then that's a mistake. Secretlondon (talk) 07:17, 22 April 2026 (UTC)
Pre-announcement: Expanding occupation labels from GSCO database
Latest comment: 5 months ago1 comment1 person in discussion
Hello everyone,
I am writing to inform the community about a planned expansion of my bot's activities (User:Maris Dreshmanis).
What
I plan to add missing labels, descriptions, and aliases for occupation items (instances/subclasses of profession (Q28640)) in underrepresented languages.
Data source
GSCO (Global Standard Classification of Occupations) — a multilingual occupation database I have compiled from 50+ national occupation registries. All data comes from legally authoritative government sources (national statistical offices, ministries of labor), not machine translation. My sources include:
ESCO (European Skills, Competences, Qualifications and Occupations) — 28 EU languages
National registries: Turkey (ISCO-TR), Brazil (CBO), India (NCO), Indonesia (KBJI), Bangladesh (BSCO), Canada (NOC), Mexico (SINCO), Russia (OKZ), Kenya (KeSCO), and 40+ others
ISCO-08 codes as the universal linking key
Scope
Phase 1 (current): Labels for occupations in languages with low coverage (Maltese, Irish, Icelandic, etc.)
Phase 2: Descriptions for occupation items
Phase 3: Aliases from alternative occupation names in national registries
Quality assurance
I run pre-validation via a local SQLite cache — every edit is checked against current Wikidata state before submission
I only fill empty fields — existing labels/descriptions are never overwritten
I use a confidence tier system: only 100% confidence edits are automated
I have automatic revert monitoring every 10 minutes with emergency stop
I use dynamic throttle: speed increases only if 0 reverts over 7 days
My current track record: ~4,000 edits across 27 languages, 0 reverts, 0 errors
Latest comment: 5 months ago2 comments1 person in discussion
I read Recuyell of the Historyes of TroyeRecuyell of the Historyes of Troye or Recueil des Histoires de Troye (1464) is a translation by William Caxton of a French courtly romance written by Raoul Lefèvre, chaplain to Philip III, Duke of Burgundy. It was the first book printed in the English language. so I made this list/query for data we got in Wikidata: Wikidata:List of earliest books available in English. Looks like there are items with years down to 155, these probably need fixing. Additionally, maybe the book should be linked with just 1 row per book instead of the editions? The list can also be used for further data improvements and adding missing items. Prototyperspective (talk) 14:57, 23 April 2026 (UTC)
Looking for co-maintainers for Pasleim’s Javascript tools
Latest comment: 5 months ago8 comments6 people in discussion
Hey Wikidata community
Around 3.5 years ago, User:Pasleim retired from editing Wikidata, and shortly before he left he handed over his tool and bot accounts to me (User:DeltaBot, User:PLbot, and some tools such as harvesttemplates and reCh that are running under https://pltools.toolforge.org/).
While I can and do operate the Python bots which are meanwhile fully consolidated under the User:DeltaBot account, I do not have sufficient Javascript skills to maintain Pasleim’s Toolforge tools. Thus, I am looking for an experienced co-maintainer for the pltools and plnode tools. I would expect the co-maintainer to be a seasoned Wikidata editor and tool operator with proven experience in Javascript.
The source code is pretty much unchanged since Pasleim has left, and due to API changes the tools are meanwhile not operational any longer. There is certainly some clean-up required on Toolforge, and some changes are necessary to fix the tools.
Nice to hear, and fine with me of course. If you happen to know someone who would fit, feel free to invite them to this discussion. —MisterSynergy (talk) 22:36, 20 April 2026 (UTC)
I can help co-maintaining the tools. I'm using them often, and familiar with JS. I think the recent issues with the tools are mostly due to DB changes, requires some revisit of the DB queries. Eran (talk) 09:49, 24 April 2026 (UTC)
I suspect the only reason Pascal chose React for harvesttemplates was to learn it, which is a reason I can get fully behind. It otherwise makes little sense to use an SPA framework for something that isn't highly interactive. So the tool might benefit from a rewrite if a developer who is into the KISS principle is so inclined. Infrastruktur (talk) 11:06, 24 April 2026 (UTC)
Would you also be interested here? As of now, User:Sjoerddebruin and User:ערן (Eran) have raised their hands that they are at least interested and rather soon I would like to talk to them regarding the future setup.
We have full access to the current tool, and from a simple fix to a full rewrite everything is possible. I am not sure how the current production code relates to the code referenced at his Github account, as the inventory of the tool account is a bit messy and apparently not cloned from Github. Anyways, most of his code is CC0 "licensed".
I can’t tell what Pasleim’s intention was in the past, I just managed to offer co-maintainership to him when he was about to leave (it kinda was a one-year-long foreseeable event) and I think he gladly accepted in order to keep the tools around, without him being around at the same time. —MisterSynergy (talk) 14:53, 24 April 2026 (UTC)
I offer some help, but not as the chief maintainer.
I made some contributions to harvesttemplates long time ago, before the rewrite.
reCh has not changed much since its first version. I have regularly used it for a few years, and I think after the security incident some elements stopped working. Let's if we can fix that, otherwise if we were to rewrite, I'd recommend it as a user script integrated to the Wikidata interface. --Matěj Suchánek (talk) 09:11, 25 April 2026 (UTC)
Any batch QuickStatements users here?
Latest comment: 5 months ago4 comments2 people in discussion
If you (a) use QuickStatements, and (b) use it by submitting batches programmatically to the API (as opposed to copy/pasting them into the UI), are you able to offer help to someone who's having trouble getting this to work? Or, if this isn't the right place to ask, can you suggest a better place for asking about QuickStatements? Thanks! —scs (talk) 14:32, 19 April 2026 (UTC)
Hello, discussions regarding Version 1.0 and 2.0 can be found at
Okay, QuickStatements 3 is working for me. It's too bad about QuickStatements 2 — it's got one feature I really wanted to use, but that's the one that's broken, seemingly irretrievably. —scs (talk) 13:48, 25 April 2026 (UTC)
Wikidata:Requests for comment/External identifier sorting
Latest comment: 5 months ago2 comments2 people in discussion
Removing labels redundant with mul causing problems to automatic lists
Latest comment: 5 months ago17 comments6 people in discussion
The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section. A summary of the conclusions reached follows.
That is causing problems with automatic lists because sometimes ListeriaBot is not handling properly mul labels, as I've checked in cawiki and in enwiki. With default settings, for items with only mul label and without labels in any other language:
If the item doesn't have an article in the wiki, the Wikidata item is linked with the mul label, which is right.
However, if the item has an article in the wiki, the article is linked (which is right) but the Q id is used as text (which is wrong) instead of the mul label (which would be right).
If there are labels in other languages, those are used (according to the undocumented language fallback rules) yielding nice human readable text as expected - and as we were used to until redundant labels started to be removed.
I plan to report the issue to be fixed in ListeriaBot, but since maintenance of ListeriaBot is usually slower than ideal because @Magnus Manske is busy, I propose to pause removing redundant labels in Wikidata until Listeria can handle mul labels properly. Pere prlpz (talk) 09:14, 22 April 2026 (UTC)
Yes, the problem should be solved from ListeriaBot.
But no, we can't just let Wikidata be unusable to other projects just because we can put the blame somewhere else.
Some projects -notabley enwiki- don't trust Wikidata and store all their data locally, while others (like cawiki an others) rely on hundreds of automated lists and work with them on Wikidata. Wikidata suddenly withdrawing support for automated lists because somebody else should fix it is a gross betrayal to everybody who has trusted it. In fact, that's the best way to encourage projects to do as enwiki does and not to use Wikidata.
And maybe the fix is easy. If that is the case, the pause doesn't need to be long, just enough for somebody to build a replacement for ListeriaBot with more than 1 maintainer - something you said you could do easily with AI. Then, it's just doing it and having a replacement before making the existing lists by deleting language labels. Pere prlpz (talk) 13:39, 23 April 2026 (UTC)
In the examples I linked (from cawiki and from enwiki) ListeriaBot fails to fall back to the mul label when building the text for the link to an article, and shows the Qid instead of the label. I only checked enwiki and cawiki but I assume it is happening across all wikis.
That error is already happening in some rows in ca:Viquiprojecte:Wikidata/Defuncions recents -the rows about the people where all labels except for mul have been removed-, and is expected to happen more pages as more labels are being removed. I'm not sure if it just affects the default setting for links or what are the effect in other settings.
Fortunately, as far as I can see, items with coordinates are excluded from label removal and that limits the effect on cawiki because a lot of our automatic lists are about geography.
And just as removal of labels in items with coordinates is paused because a function needs to be fixed first to keep working without language labels -which seems a sensible plan- it should be paused for other items until ListeriaBot can properly handle fallback to mul labels in all cases where other languages have been removed. Pere prlpz (talk) 14:33, 23 April 2026 (UTC)
English Wikipedia does not allow listeria tables. In indirect uses the user can and is expected to fix bug-caused content like missing or false language labels. Didn't know cawiki uses listeria tables directly, thanks for your investigations. Don't know if pausing listeria updates is the right approach, maybe it is. Prototyperspective (talk) 14:42, 23 April 2026 (UTC)
It isn't. The whole point of using Wikidata and Listeria is to allow for continuous updating of lists - and in fact Wikidata and its tools streamlines a lot the workflow of updating lists. The previous few times than due to Listeria malfunctions it has stopped updating lists for some time, it has been an important disturbance.
And please notice that cawiki is not the only wiki using Listeria in its main namespace. I agree that issues in Wikipedias that don't allow use of Wikidata in main namespace aren't a big deal, but I understand that our goal must be to persuade all projects to trust Wikidata and use it in lists and infoboxes, not to punish those that already trust it by withdrawing support. Pere prlpz (talk) 14:58, 23 April 2026 (UTC)
Of course, pausing sine die the removal of redundant labels might not be the only solution, but before continuing with removal it should be assessed which projects use ListeriaBot in main namespace and if sensible workarounds exist - which could exist or not depending on how different configurations of link parameter are affected and on whether lists with different parameters still serve its intended purpose.--Pere prlpz (talk) 15:23, 23 April 2026 (UTC)
According to Help:Default values for labels and aliases#Am I free to remove redundant labels and aliases?, labels for each language are being removed and replaced with a single mul label when possible. (I am the main author of the section.) It seems most problems can be avoided by keeping the English label, which used to be the fallback (which is written on that page after all). Unfortunately, this chicken-egg problem will hunt us forever: we will never know where removing 'mul' causes problems until we try it. --Matěj Suchánek (talk) 07:38, 24 April 2026 (UTC)
Removing the English label is fine if it's the same as the mul label. If there is something one could do is allowing to specify explicitly langs that the default label and/or which don't have it; the input field for these could then be disabled and by default it could be all langs with Latin alphabet (if the mul label is of that type?) or one could have a multi-select to select eg 'Latin alphabet langs'. Prototyperspective (talk) 09:38, 24 April 2026 (UTC)
Fortunately, Magnus Manske has updated ListeriaBot to include mul in the fallback list for label language[1] so that mul takes precedence over Qid. Therefore this particular problem should be solved by now and, as far as I can see, redundant labels removal can proceed. (Disclaimer: I haven't tested that it actually works).
However, I'd like to stress that, as a general principle, any new development in Wikidata should take in account the tools and projects that rely on Wikidata, do some reasonable testing before deploying, and be ready to pause deployment if problems arise downstream.--Pere prlpz (talk) 12:32, 24 April 2026 (UTC)
Kudos to Magnus the Great. The issue was about his precious availability. Now Listeria works properly with mul labels. Vriullop (talk) 15:52, 24 April 2026 (UTC)
The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made in a new section.
Why JSON and not RDF?
Latest comment: 5 months ago1 comment1 person in discussion
Just wondering why JSON has been recommended here and not RDF: what are the advantages?
My use case would involve queries (mostly akin to https://www.wikidata.org/w/index.php?search=, and editing my local copy. I would like to incrementally update my dump, rather than have to download the entire thing every time.
It's not gonna be easy, but I'm looking into / would like to experiment with contributing changes to Wikidata local-first (like `git`).
Creating Wikidata items for every chapter of a book
Latest comment: 5 months ago9 comments5 people in discussion
We have separate Wikidata items for most, but not all, chapters of Anne Bradstreet and her time, e.g. Anne Bradstreet and her time/Chapter IV (Q138301957). This seems excessive to me, but according to Wikidata's notability requirements, "The status of subpages of [Wikisource] mainspace pages (for example, individual chapters) is undetermined." Can we please make this status determined one way or the other? One major downside to having these as separate Wikidata items is that we then need to maintain the proofreading status of every chapter separately, which is just extra work. I don't really see any practical purpose to having these chapter items (as interwiki links are better handled at the book level). My suggestion would be that we say Subpages of mainspace pages (for example, individual chapters) are not considered valid unless they are written by separate authors or could be considered stand-alone works.Nosferattus (talk) 21:31, 17 April 2026 (UTC)
Re: "unless they are written by separate authors or could be considered stand-alone works" would apply to poems, plays, short stories, letters, speeches, forewords and introductions, and a lot of other things. But there are additional items that probably should have data items that aren't covered in that. The cantos of Dante's Divine Comedy, should probably have listings; the individual stories in Ovid's Metamorphoses; the books of Homer's Iliad. Each of these has been translated in part by various authors and there would be no other way to interconnect the various translations. So where do we draw the line? --EncycloPetey (talk) 22:12, 17 April 2026 (UTC)
@EncycloPetey: So how about ... unless they are written by separate authors, could be considered stand-alone works, or have been translated separately.? Does that work? Nosferattus (talk) 22:39, 17 April 2026 (UTC)
I'm more or less fine with that wording, but of course I think we should be generous with allowing for edge cases. I'd be fine with allowing separate wikidata items for each canto of Inferno, or each book of Euclid's Elements, or even each Act of a Shakespeare play. I think the qualifiers you use in this is both broad enough to offer flexibility and specific enough to avoid a new item for every chapter of every book ever. -- Mathmitch7 (talk) 19:59, 25 April 2026 (UTC)
It's fine if they show up in that report. It isn't expected that all cases in that report are solvable. It's just a list to review for cases that probably need either a redirect resolved to the target or a new Wikidata item added, but some cases are neither. Thus why the instructions say "For most cases, one of these two solutions exist". Another option is to create separate Wikisource pages just for those poems. If the poems are notable enough to need a redirect, they are presumably also notable enough to stand as separate Wikisource texts. Nosferattus (talk) 16:04, 18 April 2026 (UTC)
But that often won't be the case. On English Wikisource we have many instances of linking Shakespeare quotes to particular places in plays that contain the quotes. Since this is a related issue, ought we to have Wikidata items for those quotations, independent from any specific page or text on Wikisource? I'm looking for ideas on how best to handle such situations, because it's a related issue and fairly common for certain authors, and might be relevant to Wikiquote as well. --EncycloPetey (talk) 18:08, 19 April 2026 (UTC)
wikisource has 660k pages, wikiquote 1/10 of that, so we could have items for every quote, but I doubt we'd want items for sub-pages in other wikis, like the wikisource chapters are. Vicarage (talk) 18:38, 19 April 2026 (UTC)
@EncycloPetey: That's totally fine. Just don't create Wikidata items for the chapter that the quote is in simply because it contains a famous quote. Just create a Wikidata item for the quote and sitelink it to the chapter (or a redirect to the chapter). There's no policy or guideline saying that sitelinks have to be notable in and of themselves or have their own Wikidata items. And if a chapter has multiple notable quotes or poems we wouldn't be able to interwiki link them all anyway, so I don't think that should be an expectation. Although interwiki links sometimes work for subpage content, it's not what they are intended for. Nosferattus (talk) 00:48, 21 April 2026 (UTC)
Anatomical mess
Latest comment: 5 months ago7 comments2 people in discussion
Have anyone else noticed our anatomical items being a complete mess? In most items there aren't even any attempt at differentiating between human anatomical parts and animal anatomical parts. Everything is just treated interchangeably Trade (talk) 07:58, 24 April 2026 (UTC)
Good to raise this here, thanks. This is also an issue on Commons and on Wikipedia; "human" is left out of the title or the article / category is mostly about human-specific anatomy while scoping it differently in the lead and having contradictory categorization etc. A table I think would help improve things on Wikidata but ultimately it needs some users/wikiproject to do extensive work on that and this probably also involves editing Wikipedia & Commons, e.g. to suggest page moves or page splitting etc or maybe things are good as they are and there should just be splitting+item creation on Wikidata which get redirects in the Wikipedia section. Prototyperspective (talk) 22:04, 25 April 2026 (UTC)
There's also the issue with identifiers since the vast majority are about humans rather than mammals Trade (talk) 02:38, 26 April 2026 (UTC)
New user adding thousands of entries
Latest comment: 5 months ago6 comments4 people in discussion
I have noticed a very new user with the name 'Hermeticasuperoods' has been adding entries on the pages of thousands of botanical taxa, in the 'described at URL' field P973. The field is, I believe, supposed to contain a link to a journal or book where the particular plant was described, but this user is adding links to what appears to be their own website hermeticasuperfoods.com, with details of the nutritional content. It looks like spam to me, but I don't know what to do about it. Could someone help please? Junglenut (talk) 07:37, 25 April 2026 (UTC)
I think we need to either mass nuke all the edits as spam, or, if that website is actually good (I can't really tell), ask them to propose a new external identifier. Ainali (talk) 08:57, 25 April 2026 (UTC)
Thanks for that @Držav23, but I was thinking more along the lines @Ainali has mentioned. I'm sure there are bots that could revert the edits, I just don't know who to report this to. Junglenut (talk) 10:09, 25 April 2026 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. —Justin (koavf)❤T☮C☺M☯01:50, 27 April 2026 (UTC)
Nutrients data
Latest comment: 5 months ago18 comments5 people in discussion
Waistline is an open source calorie tracker app with which one can scan products and easily see their ingredients (eg to avoid certain ones) as well as for tracking calorie intake, micronutrient intake (eg to limit salt intake), and macronutrient intake (eg to increase protein intake). Its probably biggest disadvantage to closed-source proprietary apps is that one can't easily enter generic foods like 'Apple' where the precise numbers don't matter and it's more or less the same for products of the same kind. code issue here
This is one of the so far rather rare opportunities where Wikidata could be very useful in the real world outside of Wikimedia projects as people could enter nutrients data on Wikidata for generic foods and Waistline could load it. This data is very useful in general and could also be used for other purposes so it's not limited to this kind of application or that particular already-popular example app.
If we want more data about food, having a good data model is important. If we take an apple, it has on the order of 40,000 to 50,000 different proteins that we certainly don't want to all include in apple (Q89).
If you want to make progress here, the path would be to start reading the FDA and EFSA definitions of what various terms mean, probably read through the definitions of projects like OpenFoodFacts and then argue for a data model for Wikidata that plays well with the existing definitions. This is some work, asking a chatbot to give find the relevant definitions can be useful if you don't want to look them up yourself. ChristianKl ❪✉❫ 13:06, 7 April 2026 (UTC)
Thanks. Those two properties are useful but they don't seem to be set on many items. Maybe somebody could import more of that data?
As for the links at the end of my postm I thought nutrients was contained in there; https://wiki.openfoodfacts.org/Translations_-_Names_of_nutrients seems to be the right OFF place and USDA also seems to have a list but I couldn't find it and the API site seems down currently.
In the property proposal there already is a list of proposed nutrients to include. The question now is if that list is fine or how it should be changed and I hope people here will participate. Prototyperspective (talk) 14:42, 7 April 2026 (UTC)
Allow me to veer off on a tangent. I loathe the new USDA database for several reasons. First it doesn't list information for cooked ingredients, which for white rice has three times less food energy per unit when it is cooked. You can find them in the legacy section, but this isn't being updated. It also doesn't list provitamins like beta-carotene in the new database. If that wasn't bad enough they also stopped listing any foods that aren't "foundational". This all makes it very hard to use it for real-life purposes.
For Vitamin E, only alpha-tocopherol is listed and not alpha-tocopherol equivalents which means you get numbers that apparently might be way off. For boiled eggs the numbers are off by a factor of 5. I was told by the local oversight authority that these numbers can be influenced by factors such as enriched poultry feed, which AFAIK is done locally, but the feed cooperative doesn't publicly list this data. I only know the numbers match values measured in a laboratory. Any fresh animal produce is unlikely to be imported so this might be highly regional.
What I use for database is https://www.matvaretabellen.no/en/ . It's available in machine readable form (JSON), in an English language version, under a license for public open data. Personally I'm interested in all aspects of my nutrition, not just the calories, so I just use a spreadsheet, probably gives me a better overview than some simple calorie tracker apps. Infrastruktur (talk) 17:13, 7 April 2026 (UTC)
Examples of USDA FoodCentral being dysfunctional and misleading: Carrots apparently don't have any beta-carotene or retinol-equivalents. [2] On this page it lists all the individual vitamin Es, but doesn't give us a value for alpha-tocopherol equivalents. [3] And boiled eggs list alpha-tocopherol in the legacy section, which is just one of the E vitamins. [4]. If we look at raw eggs in the new database, where did vitamin E go? [5]. Egg yolks apparently have a bunch of different vitamin Es, but last time I checked eggs contain egg yolks. [6]Infrastruktur (talk) 14:50, 8 April 2026 (UTC)
Well if we get things onto Wikidata, that would finally able the open source world to adopt our data instead of USDA (which also requires users to get an API key first) for generic foods data.
I named the USDA database only in the context of how to find a reasonable comprehensive list of nutrients. This all makes it very hard to use it for real-life purposes. exactly an additional reason for why things should be available on Wikidata.
matvaretabellen.no/en/ . It's available in machine readable form (JSON), in an English language version, under a license for public open data sounds like a potential source for data to import, would be great news. Prototyperspective (talk) 18:01, 7 April 2026 (UTC)
Interesting. That's an issue with that database as source for filling the proposed property. However,
it's not reasoning to not create the new property
it's an extra reason to create that property and get its data into Wikidata since USDA which is used by open source apps for generic foods currently is so bad
Amazing, thanks a lot – this one looks promising. Would probably be best to try to get the best out of the ~3 resources available with such data other than OFF. Prototyperspective (talk) 12:32, 15 April 2026 (UTC)
I have tried on several occasions to build an app around the USDA FoodData Central. It works but is not the best. I think what youre doing would be a huge help to Wikidata so we can import the USDA and other sources so we do have the best data available and for free.
has listed ingredient seems like a good place to store these, we can edit that property if theres nutrients you want to add to be valid. Youll just have to think of a model. A McDonald's Cheeseburger (sorry, im American) is really 1 bun, 1 beef patty, and 1 slice of cheese, which each have their own nutrient makeup. So a WD item of "McDonald's Cheeseburger" wouldnt have the nutrients direct. Youd use `has part(s)` bun, patty, cheese which each has their respective nutrients.
At least that's how i'd model it. Of course its your project so just nake sure what you decide is documented somewhere! GA Kevin (talk) 17:28, 7 April 2026 (UTC)
Agree. And yes that's a good point: maybe many items would get ingredients specified and only those ingredients would have nutrients specified. However, I don't know if this impedes practical use eg making queries far far more complex and long to load since one also has to consider weight and quantity of ingredients. However, the subject here is not yet so broad I think: for now it's just for things like nutrients in 1 carrot or 1 apple (maybe average sour and average sweet type but one could also just specify a default specific product for the types). Regarding the Cheeseburger example, I don't know if the nutrients of the separate parts are known but the official site about the product has nutrients information for the product overall. However, this kind of product is not where this would be most valuable and useful – it's generic foods, not specific ones that are missing in OpenFoodFacts-based open source apps. It's not my project by the way; I didn't even make the property proposal but I see how it's super valuable and could be one of the first ways Wikidata gets widely used outside of WM. And the model for that property proposal is quite clear as far as I understood it: a property that can be added to items with a list of nutrient being possible values that each require a certain qualifier for the amount as in the examples. Prototyperspective (talk) 13:04, 8 April 2026 (UTC)
Well modeling with the ingredients would avoid duplication across items. For instance, if McDonald's uses the same beef patty for it's hamburger and cheeseburger, you'd be able to update one item (the patty) if it ever changes, instead of changing every instance where it is used. I understand your goal is generic foods at first, just an example! Querying should be fairly straight forward now that we can query for specific values on specific items (in this case only nutrients, I wouldn't query the statement of `start date` for example for a cheeseburger, though another researcher / project may find that useful on the QID page.
I'm glad you point out OpenFoodFacts, I think that + USDA + some web scrapers could be of massive benefit to Wikidata. OpenFoodFacts would require some serious parsing as every variant is it's own thing, but there's a lot of useful information there, in a compatible license, with an API. It's truly a goldmine for an import.
Let me know when you start this, I'd be interested in contributing to the import. I'm currently working on uploading every NBA and MLB game but that should be in maintenence mode by the time this kicks off. Im on the Wikidata Telegram or on Signal (Kevin.6614). GA Kevin (talk) 14:06, 8 April 2026 (UTC)
I replied on the issue of a controlled vocabulary. And the issue of a definition of what is a nutrient is not a show-stopper since that's covered by said vocabulary. If @Shisma: and the rest of the nutrition dilettantes (a group I count myself in) can get behind not using an intentionally enshittified database like USDA for data import (you can thank lobbyists for this) I'll be more than happy to give my supporting vote. Literally any other database will do. If they insist on importing data from USDA I can't support the proposal as spreading incomplete nutritional data is tantamount to misinformation! Infrastruktur (talk) 10:37, 20 April 2026 (UTC)
Yes, thanks for participating! (You already commented there earlier.) I have no issues with excluding various databases if their data quality is deemed too low. However, I think that's somewhat separate to the property itself and I wonder how one would populate the prop otherwise. I think there are two links here to other databases that could be used but I wonder how much data they have. I don't think there is insistence on importing data from USDA or any similar call – just so far there was no other known database with generic foods nutrients data other than it, you help in locating additional ones has been great. I do wonder though if one could import from USDA in some selective / smart way where data for some types of items are imported from there (ideas on how to identify good-quality items would be nice).
No objection to avoiding USDA unless some consensus – or rather a solution to the data quality issues (assuming they do exist and I haven't done sufficient verification efforts to say for sure but it seems to be a genuine concern) – is developed for some selective import from their database. Prototyperspective (talk) 13:22, 20 April 2026 (UTC)
That's great! Thanks, I could not find this last time I checked and it looks like in all this time none of the databases named here have been named in the repo of the open source nutrient/calorie/intake/ingredients scanner app (the large open source one for these purposes) I named above where nutrients data on generic foods is probably the biggest problem and so far the only way in it around it is for the user to add a USDA API key. Maybe these need individual checking and if the resource is fine one could build a script that turns the data into QuickStatements to add the data. Prototyperspective (talk) 12:50, 27 April 2026 (UTC)
Wikidata weekly summary #729
Latest comment: 5 months ago1 comment1 person in discussion
Here's your quick overview of what has been happening around Wikidata in the week leading up to 2026-04-27. Missed the previous one? See issue #728.
Discussions
Closed request for adminship: Yamato Shiya - Congratulations to our newest Admin!
New requests for permissions/Bot: Chamiln17@FineWiki - Task/s: Read-only Wikidata entity cache build for an academic temporal language model dataset.
Events
Upcoming events: Next LD4 Wikidata Affinity Group session — 28 April 2026 at 9am PT / 12pm ET / 16:00 UTC / 6pm CEST. This session covers QuickStatements 3.0, the updated batch-editing tool for Wikidata, redeveloped by Wikimedia Brasil with support from Wikimedia Deutschland, featuring a modern interface and improved performance. Watch the previous session recording: on youtube. More details: QuickStatements3
The Human History Atlas (WikiTime), a browser-based atlas that uses Wikidata and Wikipedia-sourced data to construct timelines and allows exploration of significant historical events.
Wikilympians, a real-time list of all 153,412 known Olympic competitors with Wikidata and Wikipedia coverage statistics
Other Noteworthy Stuff
Wikibase Suite 7.0 and Wikibase Suite Deploy 7.0.0 have been launched! It brings Wikibase closer to feature parity with Wikidata. Here's what's in the latest release:
Temporary Accounts: The support for temporary accounts without IP address exposure has been added. It will, however, remain disabled by default, in line with Wikibase Cloud.
SELL rating (classification in the Syndicat des éditeurs de logiciels de loisirs rating system)
time expansion (factor by which a recording's duration has been extended or compressed relative to the original real-time event, without pitch correction; values greater than 1 indicate time expansion (e.g. 10 = ten times longer than real life, pitch lowered tenfold); values less than 1 indicate time compression (e.g. 0.1 = ten times shorter, pitch raised tenfold); 1 = real-time)
Newest database reports: Without Claims by Site - this report will list how many Wikidata Items have 0 Statements, with a linked Wiki Article/page. Click reports/all items for a per wiki list, and consider expanding.
Showcase Lexemes: transfer (L29733) - English noun/verb (ˈtræns.fɜːr) meaning "to move from one place to another", "a sports team member moving to another team", or "a ticket allowing continuation of a journey"
Development
Query Service: It is now possible to download query results in Wikidata Query Service that include coordinates as KML & GPX (GeoJSON has been available since last year). Text from the first column in the results is used as the value for naming POIs. Thanks again to Atom.oil.2 for the patch. (phab:T414376)
The Wikidata team continued working on a prototype to make WikiProjects more visible (phab:T420907) and made the new Wikidata mobile UI use auto-resizing text areas instead of single-line text inputs, in order to make longer values easier to edit (phab:T414420)
The Wikidata Integrations team now has a working prototype of LilDiffCheck, injecting wikidata changes into recent changes only if there was a change on the wikipedia html (phab:T421390)
Language fallback will be available this week on the labels of linked entities functionality in GraphQL (phab:T413655)
Request: create new item for GALADO (Malaysian phone accessories brand)
Latest comment: 5 months ago2 comments2 people in discussion
Hi all,
I'm a new (not-yet-autoconfirmed) editor and would like to request creation of a new item for GALADO, a Malaysian phone case and accessories brand. I'm the founder of the business and would like the structured data to exist on Wikidata so that knowledge-graph consumers (Google, Bing, Perplexity, Claude, etc.) ingest correct facts — currently several AI summaries describe GALADO as "Melaka-based" when the headquarters is in Bayan Lepas, Penang.
I am declaring a conflict of interest up front: I am the company's founder. I have prepared the statements below using only public, verifiable sources, no promotional language, and only structured facts (location, founding date, products, legal form, social handles).
Notability rationale: GALADO has been independently covered by:
Vulcan Post (2023 brand profile)
Malay Mail (Raya 2025 feature)
SAYS.com (Malaysian phone-charm listicle)
Marketing Interactive (industry coverage)
EasyParcel (logistics case study)
Pos Malaysia (institutional product collaboration, 2024)
I'm happy to add additional independent reference URLs to specific statements if a reviewer would like.
Statements (Quickstatements V1 format):
CREATE
LAST Len "GALADO"
LAST Lms "GALADO"
LAST Lzh "GALADO"
LAST Den "Malaysian phone case and accessories brand based in Bayan Lepas, Penang"
LAST Dms "Jenama bekas dan aksesori telefon dari Malaysia, beribu pejabat di Bayan Lepas, Pulau Pinang"
LAST Dzh "马来西亚手机壳与配件品牌,总部位于槟城峇六拜"
LAST Aen "GALADO NETWORK"
LAST Aen "galado.com.my"
LAST P31 Q4830453 S854 "https://galado.com.my/about-us/" S813 +2026-04-28T00:00:00Z/11
LAST P31 Q431289 S854 "https://galado.com.my/about-us/" S813 +2026-04-28T00:00:00Z/11
LAST P17 Q833 S854 "https://galado.com.my/contact-us/" S813 +2026-04-28T00:00:00Z/11
LAST P159 Q4874282 S854 "https://galado.com.my/contact-us/" S813 +2026-04-28T00:00:00Z/11
LAST P571 +2015-01-01T00:00:00Z/9 S854 "https://galado.com.my/about-us/" S813 +2026-04-28T00:00:00Z/11
LAST P856 "https://galado.com.my" S854 "https://galado.com.my" S813 +2026-04-28T00:00:00Z/11
LAST P452 Q581105
LAST P452 Q484847
LAST P1056 Q10587165
LAST P1056 Q6887188
LAST P1056 Q1065579
LAST P1454 Q64816476
LAST P1448 en:"GALADO NETWORK"
LAST P1813 en:"GALADO"
LAST P2002 "galadomy"
LAST P2003 "galadomy"
LAST P2013 "galadomy"
LAST P7085 "galado_my"
LAST P11245 "galadomy"
As far as I understand theres no such list available by default system. Since users declare both languages they know and language the learn and also language they do not understand using Babel, and so there are no actual accurate data. Some user who speaks certain language also does not add Babel in their userpages. Yamato~kun (Talk • Contribs) 10:39, 28 April 2026 (UTC)
New property “industry served” / “client industry”?
Latest comment: 5 months ago2 comments2 people in discussion
Hi there, I would like to see if the following idea makes any sense for Wikidata: Companies belong to P452:Industry, and they offer P1056:Product or material produced. So a consulting company might be classified as P452 Q11032, meaning its industry is information technology. And it might offer P1056 Q182478 SAP as a product.
But what I am missing is a way to describe the industries a company serves as clients. For any B2B business, this is a highly relevant structural information.
So would it make sense to have a new property such as “Industry served”, which means the industry or sector in which an organization's clients or customers primarily operate.
So in my example from above, the new property would allow us to label the company Q11032 works for clients from the Q190117 (automotive) and Q43015 (finance) indutry.
What do you think?
I've checked P2360 (intended public) and P2541 (operating area) but neither fits – P2360 is designed for audiences of creative works, and P2541 is geographic. Happy to file a formal proposal if there's interest. Newbie28042025 (talk) 12:56, 28 April 2026 (UTC)
A property proposal is the best place to discuss this further; it sounds like a good idea to me, although the right label for this may need to be settled. ArthurPSmith (talk) 19:43, 28 April 2026 (UTC)
Change of Signitaure Iosif Vulcan
Latest comment: 5 months ago2 comments2 people in discussion
Hello! I am the curator of Iosif Vulcan Memorial House in Holod, Bihor County, Romania. I want to add this writer's signature in ROmanian. The previous one was in Hungarian. It was not wrong - as he signed in both Hungarian and Romanian, but he was a Romanian author. [7]CMIVHolod (talk) 06:52, 26 April 2026 (UTC)
@CMIVHolod: Then probably both should be present, with the Romanian one marked as preferred, but neither one deprecated. Is the Romanian signature already on Commons? If not, then the first step would be to upload it there. - Jmabel (talk) 17:44, 29 April 2026 (UTC)
"instance of" property in "inception" value of Spain
Latest comment: 5 months ago2 comments2 people in discussion
Some of the inception (P571) values of Spain (Q29) have the property instance of (P31), and they seem to be used in a wrong way. The "inception" values are dates, but the "instance of" values for them are items for constitutions. Neither the dates themselves nor the inceptions of the Spanish political entities by the constitutions can be said to be instances of the constitutions. How should this situation be handled? Intolerable situation (talk) 10:01, 28 April 2026 (UTC)
Latest comment: 5 months ago4 comments3 people in discussion
Dear Team, I got the page that say any institution or organization can donate their data - so I have organization (Non Profit) they has data nut dont know how to donate - and also what kind of data can be donated - if there is any guide then would be better Riddhiborisagar (talk) 09:37, 15 April 2026 (UTC)
Could you summarize what the data contain, what institution you worked for and the format of the data you have? What field your organization work for? Yamato Shiya大和 士也 (Talk • Contribs)04:46, 22 April 2026 (UTC)
my Non profit organization is working for community upliftment - data can be anything - just let us know which kind of data can be donated so accordingly we can prepare the same Riddhiborisagar (talk) 05:09, 27 April 2026 (UTC)
You should probably start by trying to understand how Wikidata works. We care about linked data. So the best data is that which makes existing items more valuable. ChristianKl ❪✉❫ 08:24, 30 April 2026 (UTC)
New property for buildings - "projektant"
Latest comment: 5 months ago10 comments6 people in discussion
Dear all, the Czech community wants to propose a new property for a person who is responsible for the technical documentation of a building. This person is distinct from architect (P84) - an architect focuses on the overall design, aesthetics, and spatial concept of a building, while a building's "projektant" is responsible for the technical design, detailed plans, and ensuring the structure works safely and efficiently. "Projektant" is often listed alongside architects for each building in the Czech environment. The item building designer (Q106425528) seems very similar to the concept of building "projektant", but I would like to ask English, German, or other native speakers to help me find best translations for this concept, if possible - to prevent further confusion - even if it's not just one word. Vojtěch Dostál (talk) 11:59, 22 April 2026 (UTC)
Note, that projektant is used also for people making documentation for roads, bridges, pipelines or powerlines and sometimes also machines, so ideally find name that covers all these professions. JAn Dudík (talk) 13:25, 22 April 2026 (UTC)
Having a different property for every professional that participates in the creation of things is possible but it doesn't seem what we are doing.
Additionally, not only the name changes between countries. Also professions and roles change, too. For example, the statement "an architect focuses on the overall design, aesthetics, and spatial concept of a building, while a building's "projektant" is responsible for the technical design, detailed plans, and ensuring the structure works safely and efficiently" isn't true in Spain, where architects are also responsible for the technical documentation of buildings. It might be difficult to find a property that could be applied across enough countries to be useful. Pere prlpz (talk) 18:39, 22 April 2026 (UTC)
Please don't get me wrong: having a dedicated property for every specific role would be nice, but we would need a lot of properties. One property for projectant would only work for the Czech Republic and countries that have an equivalent role. In Spain, for example, that role doesn't exist, but we would need properties for Q6089080, Construction manager (Q16557264) and Q5808120 (or more specific items) and several roles more.
Therefore, I don't think having a property for projectant is a bad idea in itself. It's just that it's not practical to have a dedicated property for each specific role in the creation of buildings and other kinds of works. And since we don't even have a dedicated property for roles as clearly identifiable and widespread as sculptor or painter, not having properties for very specific creator roles seems the rule in Wikidata. Pere prlpz (talk) 12:54, 24 April 2026 (UTC)
@Pere prlpz Hello, (I am the one who proposed the property to be created)
1. Yes, there is a problem that the term or its meaning are not the same for all countries. However, the same problem exists in many cases already on the Q level, so I don't think it should block us from creating the P equivalent. there are zillions of properties that are country-specific and still meaningful (e.g. NRHP reference number (P649)).
2. The alternative solution to use creator (P170) with qualifier object of statement has role (P3831) would somehow fit the purpose and I'm not experienced in the system aspects to assess whether it is better. It might be easier on the system (no new property needed), but more complicated for each entry that would use it (as the information would be 'hidden' on a secondary level). I incline towards the first solution, as it seems 'straighter'. And I don't really see why having one more property would mean a problem.
3. In my understanding, for sculptures and paintings it is fine to use just creator (P170), because it is obvious that creator of a sculpture is a sculptor and creator of a painting is a painter, so there is no need to add another level of information.
I still can't see why projektant is different from any other creator role, because there are lots of items where the role of the creator is not evident. For example, a lot of monuments involve an architect and an sculptor, and sometimes other artists.
However, I must admit that consistence is not the rule in Wikidata -as the existence of a property for architect shows-, and I can't predict the outcome of a proposal. Pere prlpz (talk) 19:33, 29 April 2026 (UTC)
I'm not saying it is different from other creators, just that I find it useful as a property for structures, and I think it's better for each such item to provide the information using two inputs (property + value) than four (P170 + P3831 + Q14623005 + value). JiriMatejicek (talk) 14:21, 30 April 2026 (UTC)
International websites
Latest comment: 5 months ago8 comments4 people in discussion
Hey, there seems to be a bit of ongoing drama with multilingual websites being removed from entries. I would really like to see Wikidata hold these, it solves a problem for OpenStreetMap, hopefully I'm not misunderstanding
Wikidata here.
Can you give an example? Is this just about Jeep? The talk page doesn't have anything about this, but has lots about unhelpful merging. Secretlondon (talk) 10:38, 23 April 2026 (UTC)
Including all the links for every language variant of the website serves no purpose, except to "clutter" Wikidata with external links. There's the international one (www.jeep.com), which when opened lets you choose whether to stay there or redirect to the local one. Paranoid25 (talk) 18:43, 23 April 2026 (UTC)
Having all the domains associated with an Wikidata entry has a very real purpose for OpenStreetMap and other projects which want to link websites to brands. CjMalone (talk) 08:12, 28 April 2026 (UTC)
I'm not very familiar with OSM, but how would having all the links help the project? I'll reiterate, however, that www.jeep.com still redirects to local sites when you open it. Paranoid25 (talk) 09:08, 28 April 2026 (UTC)
The use case is the inverse of the possible .com redirects you describe. If we are on .de, that can't be linked to the Wikidata entry without that data being in Wikidata, or elsewhere.
If a POI has a website of jeep.tld/whatever, we would know that it is associated with that Wikidata entry, then Wikidata can be used for various metadata such as social media links, or QA such as link jacking. (If a POI is associated with Q38076, but if its website is mcdonaids.com/whatever, it's a massive red flag)
The general principle of Wikidata is that you don't delete data that's valuable to other people just because you don't find it valuable yourself when the data fulfills the criteria of Wikidata. There are many usecases of Wikidata that don't involve looking at a Wikidata page and clicking the link on Wikidata.
Having the information about the actual websites does help with showing a user the Wikidata item if anyone wants to have a browser plugin that does so. It seems OpenStreetMap also has some use of knowing all the official domains. ChristianKl ❪✉❫ 08:34, 30 April 2026 (UTC)
Latest comment: 5 months ago9 comments4 people in discussion
Can we get some restrictions on this property? Some Wikidata properties are extremely sensitive and using unverified data has a high risk of spreading misinformation or cause harm to the subject of the article. Yet seemingly there is no limits to the statements we are allowed to use Wikipedia as the sole source despite even Wikipedia itself telling people not to cite it as a source
It just feels foolish of me to go out of my way to find news sources to statements when i could just attribute everything to Wikipedia which only takes a 1/10 of the time and effort it would have been to find an actual source
Hell, you don't even need an URL. You can just add imported from Wikimedia project (P143) to any and this is apparently considered just as good by Wikidata considering it doesn't trigger any errors or warnings or even doing the bare minimum to discourage it
I think Q130558618 and Q108371443 are both good example of the property being used reasonably. But then you see stuff like sexuality, medical conditions, calling people sex criminals, mass shooting casualties and etc. Trade (talk) 10:19, 29 April 2026 (UTC)
It still serves as a statement of where someone got the information. In many cases, it serves more as a warning than a validation. - Jmabel (talk) 17:41, 29 April 2026 (UTC)
Then it shouldn't remove the citation needed constraint. That is the complete opposite of a warning. It's a signal that the statement already have a source Trade (talk) 02:02, 30 April 2026 (UTC)
As far as I understand it, the constraint violation is just a gimmick for Wikidata front end. It has no effect on the data we provide. It would definitely be nice if we could improve this constraint like you suggest, but constraints are only provided in the Wikidata interface. Vojtěch Dostál (talk) 14:51, 30 April 2026 (UTC)
Merged. Samoasambia ✎ 08:57, 2 April 2026 (UTC)
Done 
Category:Edward_Henry_Vizetelly for example. Deadstar (talk) 12:19, 18 April 2026 (UTC)
