Wikidata:Project chat

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

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

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:

1. whether the subject meets Wikidata’s notability criteria
2. whether “BlackSheep Fund” is the most appropriate and unambiguous label for the entity

Thank you in advance for your guidance. Marcicello (talk) 14:49, 19 March 2026 (UTC)Reply

Hello, just a quick follow-up. As there were no objections, I have created a minimal item for BlackSheep Fund based on the sources mentioned above.

Happy to adjust or improve it based on any feedback. Thanks! Marcicello (talk) 17:05, 26 March 2026 (UTC)Reply

You should have included this link: BlackSheep Fund (Q138795484) Bovlb (talk) 21:51, 31 March 2026 (UTC)Reply

Thanks for sharing the link, much appreciated.

Happy to adjust or improve the item based on any feedback. Marcicello (talk) 22:01, 31 March 2026 (UTC)Reply

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):

• Some items refer to the method (e.g. literature review (Q2412849))
• Some items refer to academic publications using the method (e.g. review article (Q7318358))
• Some items refer to the method as a research topic (e.g. scoping review (Q101116078))

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.

So the question is: does it make sense to merge items such as twin study publication (Q131366935) and twin study method (Q244775) even though they have different MeSH descriptor ID (P486) ? (As a researcher I would merge those items but maybe librarians have a different opinion on this?)

Jeanne Noiraud (talk) 18:06, 24 March 2026 (UTC)Reply

This is no different from painting (Q11629) and painting (Q3305213): the method and the result are different items. Not all twin study method (Q244775) necessarily result in a publication. While sometimes a weird distinction seems to exist in a database that is not justified in Wikidata, here this is not the case. Circeus (talk) 13:44, 30 March 2026 (UTC)Reply

Okay, that makes sense. I will try to make the labels clearer to reflect the distinction then because it can be confusing sometimes.

Jeanne Noiraud (talk) 13:29, 3 April 2026 (UTC)Reply

I began working on Raul Panther III (Q138792280) and Sir Dr. Robert Bakker (Q138791926) but I wasn't certain how to proceed, particularly when it comes to questions of whether they are instances of humans. Panther and Bakker are the stage personas of anonymous performers who cannot have their own Q item because they intentionally hide their real identities. Everyone in their band is "in universe" for their rock opera's narrative and many of those characters are robots, rather than humans. However it's easily apparent to anyone that these folks are human, and the robot thing is part of the performance. This was also causing me some confusion because Panther plays another character in universe: Joe (Q138792105). It was causing an error on Joe's item if I didn't list Panther as some kind of human. The man who plays Panther is human but fictionally it's not clear whether Panther the character is human. And the character Panther in universe performs as other characters like Joe.

Are there other Q items that have pinned down how this kind of performance stuff should be reflected on Wikidata? Thanks. Pingnova (talk) 21:45, 27 March 2026 (UTC)Reply

"anonymous performers who cannot have their own Q item because they intentionally hide their real identities"—Yes they can. Simply label them as "anonymous".

But are the two personas always related to the same two anonymous individuals? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:13, 27 March 2026 (UTC)Reply

So I make a new Q item called "anonymous" and fill out the real person's known information there, such as "human"? And then say that anonymous plays Panther? And then Panther plays Joe?

Yes, Panther and Bakker are always played by the same anonymous stage performers. Pingnova (talk) 01:27, 28 March 2026 (UTC)Reply

Yes, to each of your questions. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:40, 28 March 2026 (UTC)Reply

Got it, thanks for your help! Pingnova (talk) 06:52, 30 March 2026 (UTC)Reply

I must say it both looks and feels much better now! Trade (talk) 01:24, 28 March 2026 (UTC)Reply

It doesn't work for me, all I get is a red error box containing "Request failed: Failed to fetch dynamically imported module: https://mix-n-match.toolforge.org/vue-components/index.js" Piecesofuk (talk) 11:02, 28 March 2026 (UTC)Reply

That's weird, it didn't like my ad blocker Piecesofuk (talk) 08:44, 30 March 2026 (UTC)Reply

Same here. Nice to see it's using vue though. This error shows when opening [1] and I have none of the two things blocked in NoScript. Hopefully that will get fixed soon along with other things requested / discussed at m:Talk:Mix'n'match. Prototyperspective (talk) 11:02, 3 April 2026 (UTC)Reply

Does Wikidata have a spam block list? If so, can you please add this specific Youtube URI to it? It has been added to this page six times already... :-( - Erik Baas (talk) 17:14, 28 March 2026 (UTC)Reply

If we add the YouTube URLs to the spam list, the YouTube properties will no longer work. So I don't think this is the solution. RVA2869 (talk) 18:32, 28 March 2026 (UTC)Reply

I don't think this is about blocking all YouTube links. Peter James (talk) 19:19, 28 March 2026 (UTC)Reply

Right. @RVA2869 : Please read my question again, especially the words (now) in bold text. - Erik Baas (talk) 19:31, 28 March 2026 (UTC)Reply

We have MediaWiki:Spam-blacklist. I have just populated it with a few more links.

However, do you think this will be effective? When we have them know the link is blocked, they will find another one to insert.

In fact, there is already a different solution in place.

--Matěj Suchánek (talk) 08:45, 29 March 2026 (UTC)Reply

Thank you. There is no way to predict if this will be effective, but I think any form of protection may help a bit. - Erik Baas (talk) 09:10, 29 March 2026 (UTC)Reply

Hello everyone, I’ve noticed that DigiPortA is offline, and I’m unable to find the IDs in the web archive. So changing the URLs to a web archive location won’t work. The prints (and the persons) are available via Archivportal-D (Q24045714). Example: Q6353#P973 -> https://www.archivportal-d.de/person/gnd/118580973.

My question is: is it okay to delete all 12,000 dead links? (QLever Query) RVA2869 (talk) 18:15, 28 March 2026 (UTC)Reply

no. Such properties are usually maintained with the statements on the property adjusted. I'm fairly sure there is an item for dead identifiers, but I don't what it is since I don't dabble in that space. You can always put the properties up at Wikidata:properties for deletion though. That's the proper way to do it! Circeus (talk) 13:34, 30 March 2026 (UTC)Reply

@Circeus That's exactly the point: it's not a property—they're all URLs described at URL (P973) RVA2869 (talk) 13:37, 30 March 2026 (UTC)Reply

OH, then I have no idea what the Wikidata policy is about that. Maybe the admin discussion board is a better place to ask. Circeus (talk) 13:48, 30 March 2026 (UTC)Reply

No, this is nothing the administrators are needed for. Here it is fine. --Matěj Suchánek (talk) 16:03, 30 March 2026 (UTC)Reply

Since I didn't get a “useful” answer, I think I can go ahead and delete them.  Doing… #26359

Can someone create a Mix-n-match catalog for the property ‎RITVA company ID (P14230)? Or where can I request catalogs to be created? Sabelöga (talk) 20:24, 28 March 2026 (UTC)Reply

You can also create it yourself: https://mix-n-match.toolforge.org/#/scraper/new. Say if you need guidance. --Matěj Suchánek (talk) 08:49, 29 March 2026 (UTC)Reply

I know, I just haven't really figured out how that works. Anyway, I got help from User:Trade. Thanks, I'll keep that in mind. Sabelöga (talk) 08:12, 1 April 2026 (UTC)Reply

Hello, I'm trying to understand how to add a spouse to Marie Salmon (Q138507599). His name was Jean-Louis Savary (not Jean Louis Savary (Q59258498)). Don't I need to create a new wikidata entity for him, if I'm going to add him as a spouse? But he's only really notable for having married Marie Salmon, so I'm not sure he would meet notability guidelines on his own. What should I do? (For now, to avoid inaccurately pointing to the wrong Jean Louis Savary, I've changed the spouse entry to "no value".)

Thanks for your time and assistance. Chao Garden 🪴 (hi) 05:09, 30 March 2026 (UTC)Reply

"no value" means that there was no spouse. Use "unknown value" instead with an object named as (P1932) qualifier, see for example https://www.wikidata.org/wiki/Q335855#P26 However, since she has a Wikipedia article I would probably add the spouse as an item as I believe it would pass WDN3: "It fulfills a structural need, for example: it is needed to make statements made in other items more useful." Piecesofuk (talk) 06:17, 30 March 2026 (UTC)Reply

Here's your quick overview of what has been happening around Wikidata in the
week leading up to 2026-03-30. Missed the previous one? See issue #724.

Discussions

• New requests for permissions/Bot:
  • Thetalentone - Tasks: Adding and updating references, qualifiers, publication dates, and provenance on my own personal and company items (Q138324775 and Q138324581) to improve entity confidence for Google Knowledge Graph. Small batches only, no edits to unrelated items.
  • Dušan Kreheľ - Task: Sitelinks existing and newly created municipality pages on hrwiki and Wikidata.
• New request for comments: Wikidata:Requests for comment/Mass-editing policy has a new proposal incorporating feedback and is awaiting votes.

Events

• Upcoming events:
  • 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.
  • Wiki Mentor Africa - Women Tech Summit takes place until 20:00 CET, 30 May 2026.
  • "Wikidata in der Sammlungserschließung" (free online event in German on how GLAM institutions can use Wikidata, 20 April 2026, 10-11:30 CET, organized by Research and Competence Centre Digitalisation Berlin (Q51845259). More info and registration here.
  • Wikidata Ontology Course: The second offering of the Wikidata ontology course will be given in May and June 2026, with sessions 1-3 pm EDT (UTC-4) on Thursdays. The Wikidata ontology provides structure and organization for the rest of Wikidata and is thus fundamental to Wikidata. The course starts with the basic notions underlying the Wikidata ontology and goes on to cover querying using SPARQL, inference, constraints, advanced ontology notions, problems with the ontology, and other ontology-related aspects of Wikidata. Participants in the course are expected to complete weekly exercise sets and a project. More information on the course can be found at WikiProject Ontology/Ontology Course. To register for this offering fill in and submit the Google form.

Press, articles, blog posts, videos

• Blogs:
  • Wikidata contains many gaps in its political data. We’ve built a tool to change that (PoliLoom)
  • From a summer school idea to an ESWC paper: Teaching AI to “repair” Wikidata
• Papers:
  • Did AI Crawlers Kill SPARQL Federation?, including Wikidata examples
  • Gender and intersectional bias in featured biographies on the front page of the Italian edition of Wikipedia, 2014–2024 Open Access - Wikidata featured heavily in the design and methodology. By Rovira et al., (2026).
• Videos:
  • Adding architectural data to a Wikidata item for a Historic Building from OpenStreetMap for History Buffs.
  • Live Wikidata Editing #119 - Ainali and Abbe98 are back to edit Wikidata and explain their thinking along the way.
  • (Spanish) Wikidata and the public domain - Tools for bulk editing in Wikidata: Mix n Match and QuickStatements, last class of a 9-part series provided by Jorge Gemetto.
  • (German) Art History Loves Wiki im Museum Schnütgen, day 2, digital/local collection loves wiki.
  • (German) Von OpenStreetMap zu semantisch vernetzten Wissensgraphen FOSSGIS 2026 Conference.
  • Using Wikibase as an Integration Platform with Matthew Ong. Originally given at the Digital Classicist Seminar Berlin, 19 November 2024.

Tool of the week

• WikiVisage - Train a machine learning model to detect depicted subjects in Wikimedia Commons images and assist with adding the P180 (depicts) property.
• Yesterdays - A web platform for cataloging and georeferencing historical images of Richmond, Virginia. It uses Wikidata items to help organize the georeferenced images.

Other Noteworthy Stuff

• Mobile editing user testing: join the participant panel: 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.

Newest properties and property proposals to review

• Newest General datatypes:
  • Digital Public Good ID (identifier of a digital public good in the Digital Public Goods Registry)
  • apportionment diagram (image that displays the representation of seats won by party in an election to an assembly)
  • peer-review process for scholarly journals or publications (''(without English description)'')
• Newest External identifiers: ‎X Games athlete ID (new), AIK soccer player ID, ‎Uitleenwoordenbank ID, abadis.ir word ID, ‎AmericanAristocracy house ID, ‎AmericanAristocracy person ID, British Newspaper Archive publication ID, ‎Buitenlandse aardrijkskundige namen in het Nederlands ID, Landskrona BoIS player ID, Library of the University of Santiago de Compostela authority ID, ‎DBNL place ID, Faulhaber edition ID, Foto Atlas taxonomy ID, ‎Integbio Database Catalog ID, ‎KCUE academy ID, ‎LibriVox reader ID, ‎Manga-DB person ID, ‎Manga-DB magazine ID, ‎Manga-DB publisher ID, Digital Public Goods Registry, NSK ID, Tribuna.com football players ID, Sport Express person ID, ‎Open Food Facts brand ID, ‎RITVA company ID, OldRacingCars.com drivers ID, ‎Spellingwijzer Onze Taal ID, ‎EpiMedDat ID, ‎Pinkhof ID, ‎Scheikunde ID, ‎Movist person ID, ‎ISSN-H, Names, Persons, and Groups of People of the Middle Ages ID, ‎Parlement.com object ID, wikiru.jp wiki ID, BGAFD actress ID, IFK Norrköping player, ‎LINE official account ID, Norwegian war prisoner histories ID, ‎indexxx.com performer ID, SetesdalWiki ID, ‎Shellers From the Past ID, ‎SocioMap ID, Publication ID in e-Marefa database
• New General datatypes property proposals to review:
  • civil service position level (classification level of a civilian public service position within a government administrative hierarchy)
  • Usenet newsgroup (Usenet newsgroup associated with the item)
  • predicted winning party (the party predicted to win an election, according to some source)
• New External identifier property proposals to review: Numen ID, member of the Azorean assembly ID, identifiant Rappels d'une personne, Identifiant dans la base de noms France Archives, Anarâš aavis topic ID, Perfumery Glossary ingredient ID, MangaBaka manga ID, JVID performer ID, PlayStation Trophies achievement ID, BERON lexeme ID

You can comment on all open property proposals!

Did you know?

• Newest WikiProjects: WikiProject Hogback - Hogbacks are a type of gravestone marker used in 10th - 12th Century Northern England.
• WikiProject Highlights:
  • University of Otago/Books of Mana
  • Schnütgen Museum Collection/Sum of all paintings
  • Govdirectory/United Nations
  • Nonprofit Organisations
• Newest database reports: Humans with the same date of birth year (P569) and date of death year (P570).
• Showcase Items: Australia (Q275180) - 2008 film by Baz Luhrmann
• Showcase Lexemes: viɛla - Dagbanli adjective (of quality that is pleasing to human senses).

Development

• Wikibase GraphQL: We added support for a number of additional datatypes and started working on the functionality for querying Items by the external ID statement values or site links.
• Mobile editing of statements: We spent time testing the current state and fixing remaining issues we found.

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

Weekly Tasks

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

· Previous issue . Full report · Unsubscribe . JosefAnthony talk ·MediaWiki message delivery (talk) 15:30, 30 March 2026 (UTC)Reply

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?

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.

This direction is aligned with the Movement Strategy recommendations to:

• explore earned income through enterprise-grade APIs, and
• improve the Wikimedia API suite for all users.

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.

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.

More details on all free access options, including how to apply for free access as a community member, are available here: https://meta.wikimedia.org/wiki/Wikimedia_Enterprise#Access

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.

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).

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.

See the Wikimedia Enterprise FAQ and financial reports for details: https://meta.wikimedia.org/wiki/Wikimedia_Enterprise/FAQ#How_will_the_money_be_spent

https://diff.wikimedia.org/2025/11/24/wikimedia-enterprise-financial-report-fiscal-year-2024-2025/

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)Reply

And if anyone has any questions/comments about the Enterprise API in general or this announcement specifically, you are also welcome to comment over on the project talkpage on meta wiki. LWyatt (WMF) (talk) 17:44, 31 March 2026 (UTC)Reply

Will a list of some of the customers become publically available for the sake of transparency? Trade (talk) 18:25, 31 March 2026 (UTC)Reply

Hello @Trade.

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 announce Amazon, 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)Reply

google is a customer? could you ask them to please reciprocate a favour by not obstructing wikimedia users from importing youtube videos to commons? see https://phabricator.wikimedia.org/T236446 . RoyZuo (talk) 18:52, 1 April 2026 (UTC)Reply

Yes - since 2022.

and yes, I’ve asked them about this specifically, and will continue to do so. LWyatt (WMF) (talk) 13:42, 2 April 2026 (UTC)Reply

Hello, I would like to create a Wikidata entry for myself, Linda Saul, a UK-based visual artist with both traditional and digital practices. Below are the key details and sources: Identity:

• Name: Linda Saul
• Instance of: human
• Country of citizenship: United Kingdom
• Professional Details:
• Occupations: visual artist, digital/algorithmic artist
• Fields of work: painting, digital/algorithmic art
• Memberships / Affiliations: Royal Watercolour Society (RWS) – [RWS Member Page /https://www.royalwatercoloursociety.co.uk/artists/400-linda-saul/biography/]
• Notable works / exhibitions: Royal Academy Summer Exhibition participation – [2]
• Websites:
  • https://lindasaul.co.uk (fine art practice)
  • https://lsaulcode.art (digital art practice)
• Community & Media Contributions:
  • Significant event: 2019 “Save Reading Gaol” campaign (“Gaol Hug”) – covered by [
    • https://www.readingchronicle.co.uk/news/17966761.reading-gaol-hug-great-success-hundreds-hold-hands-around-prison/
    • https://wokingham.today/the-battle-of-reading-gaol-residents-brave-heavy-rain-to-give-a-hug-in-support-of-plans-for-new-arts-centre/
    • https://www.irishtimes.com/culture/heritage/the-ballad-of-reading-gaol-wilde-enthusiasts-lead-campaign-to-save-site-1.4068000]
• Publications: co-author of Reading’s Influential Women – ISBN 978-1909747623
  • Other Sources:
• Article in ‘the artist’ magazine April 2021[3]
• https://www.banksidegallery.com/exhibitions/148-rws-spring-2026-wherever-you-go-there-you/works/
• https://www.banksidegallery.com/exhibitions/141-rws-autumn-2025-the-shapes-of-water/works/
• https://www.banksidegallery.com/exhibitions/129-rws-spring-2025/works/
• https://www.banksidegallery.com/exhibitions/134-tim-marlow-selects-bankside-gallery-45th-anniversary-exhibition/works/
• https://www.messums.org/product/linda-saul-the-farm-i/
• https://www.messums.org/product/linda-saul-the-road-ahead/
• https://www.messums.org/product/linda-saul-the-foot-of-spakonufell/
• https://makingamark.blogspot.com/2019/09/10-best-paintings-in-sunday-times-watercolour-2019.html
• https://www.royalwatercoloursociety.co.uk/exhibitions/75-common-ground-frances-hatch-caroline-mcadam-clark-robin-richmond/overview/

I am happy to provide any additional references or clarifications. Please advise on the next steps to create this Wikidata entry. Lindasaul (talk) 22:07, 31 March 2026 (UTC)Reply

A work of Linda Saul was indeed exhibited here which, as far as I am concerned, ensures notability by our standards. The user clearly has a COI and must be commended for coming here instead of just creating an item or paying an external company. Unless I hear objections reasonably soon, I will create an item (which might be tricky since I will leave for holidays in a few hours without my laptop, but I will find some way). Ymblanter (talk) 18:18, 1 April 2026 (UTC)Reply

Already done by: @Trade Linda Saul (Q138845990) RVA2869 (talk) 18:35, 1 April 2026 (UTC)Reply

some people have "real" (aka official/formal) names in languages which are not their native languages, or they may not even be fluent in those languages. for example, many descendants of chinese may have a "chinese name", but they dont actually speak chinese, or this list of chinese names of sinologists https://home.uni-leipzig.de/clartp/ChineseNamesWesternScholars.html . what property do i use for this? none of Template:Name properties other than name (P2561) seems suitable. official name (P1448) and native label (P1705) cannot be used on humans. Kamala Harris (Q10853588) lists it as pseudonym. it's not a pseudonym (i.e. false name) but a real name for specific cultural contexts. RoyZuo (talk) 13:21, 1 April 2026 (UTC)Reply

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.

Thanks. -Mohammed Abdulai (WMDE) (talk) 14:39, 1 April 2026 (UTC)Reply

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)Reply

At first glance they are different things and shouldn't be merged. Secretlondon (talk) 06:27, 2 April 2026 (UTC)Reply

Then what should be done? ZFT (talk) 06:35, 2 April 2026 (UTC)Reply

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)Reply

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)Reply

I changed my mind. ZFT (talk) 02:37, 3 April 2026 (UTC)Reply

I think it would be better if this article from the French Wikipedia were connected to element LGBTQ history in China (Q6457851), as it deals with LGBTQ history in China, while this article would be better suited to element LGBT rights in the People's Republic of China (Q19514494), as it deals with LGBTQ rights. Questionadora ávida (talk) 00:28, 2 April 2026 (UTC)Reply

Hi guys,

Could you please merge the wikidata items linked to this page and this one as they cover the same topic? Thanks! PalleyCov2030 (talk) 03:37, 2 April 2026 (UTC)Reply

First is Template:Presidents of Franche-Comté (Q22775951) and second is Template:Presidents of Franche-Comté (Q22720513). Secretlondon (talk) 06:23, 2 April 2026 (UTC)Reply

 Merged. Samoasambia ✎ 08:57, 2 April 2026 (UTC)Reply

Здравствуйте! У меня проблема с объединением двух элементов Викиданных, посвящённых одному событию — военному перевороту в Судане 1969 года. - Элемент с русской статьёй: https://www.wikidata.org/wiki/Q29542127 (Военный переворот в Судане (1969)) - Элемент с английской статьёй: Q21515053 При попытке добавить ссылку на английскую статью выдаёт ошибку, что она уже привязана к Q21515053. Самостоятельно объединить не получается. Помогите, пожалуйста, объединить эти два элемента. Заранее спасибо! Selass74 (talk) 05:39, 2 April 2026 (UTC)Reply

Via translation they want to merge Q29542127 and 1969 Sudanese coup d'état (Q21515053). One is a disambiguation page. Secretlondon (talk) 06:32, 2 April 2026 (UTC)Reply

The disambiguation page is about ?mountains in Iran named Kūh-e Qūchān though? (Which should be merged with Kuh-e Quchan (Q29543905) though but can't be thanks to cebwiki...) - Yupik (talk) 17:01, 2 April 2026 (UTC)Reply

Ah, from the section below, I think the original issue has now been resolved. - Yupik (talk) 17:02, 2 April 2026 (UTC)Reply

Здравствуйте!

Помогите, пожалуйста, объединить два элемента Викиданных об одном событии — военном перевороте в Судане 1969 года:

- 1969 Sudanese coup d'état (Q21515053) (есть английская статья 1969 Sudanese coup d'état) - 1969 Sudanese coup d'état (Q138852093) (есть русская статья Военный переворот в Судане (1969))

При попытке объединить через Special:MergeItems выдаёт ошибку "Conflicting descriptions for language en". Через гаджет Merge тоже не получается.

Сам разобраться не могу. Очень прошу кого-нибудь из опытных участников или администраторов выполнить объединение.

Спасибо! Selass74 (talk) 05:40, 2 April 2026 (UTC)Reply

I've done it for you. Secretlondon (talk) 06:36, 2 April 2026 (UTC)Reply

Thank you very much for your help with merging these items! I really appreciate it. Selass74 (talk) 07:14, 2 April 2026 (UTC)Reply

The Migration Museum in London Migration Museum (Q113370323) has a map in the infobox of its en.wiki article en:Migration Museum, London, derived from Wikidata.

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)Reply

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)Reply

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)Reply

Done, but is that captalisation correct? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:26, 5 April 2026 (UTC)Reply

On Earth (Q2), there's a named after (P138) statement with value land (Q11081619), with series ordinal (P1545) 1. However, the series ordinal (P1545) qualifier only correctly applies to Japanese and Korean, and not Czech or Hungarian, because only Japanese and Korean have a corresponding value with series ordinal (P1545) 2, so Czech and Hungarian should be split off into a separate statement. Is there an instance of Wikibase reason for deprecated rank (Q27949697) for improperly aggregated statements like this? TTWIDEE (talk) 21:06, 2 April 2026 (UTC)Reply

@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)Reply

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

What should be done about that? TimBorgNetzWerk (talk) 21:53, 2 April 2026 (UTC)Reply

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)Reply

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.

Let us know if you have any questions or need assistance with the query logic. Thank you for your help! ZI Jony using MediaWiki message delivery (talk) 17:09, 3 April 2026 (UTC)Reply

A potentially tricky merge (or maybe just said to be the same as (P460)): Feast of the Black Nazarene (Q105070555) and Feast of the Black Nazarene (Q138863488). On Commons, the category for the former is now just a redirect to the category for the latter. I don't think there is any meaningful distinction, just two names for the same thing. Anyway, both have a fair number of links, and I leave this to someone who is more active than I am on Wikidata. - Jmabel (talk) 19:01, 3 April 2026 (UTC)Reply

@Jmabel merged them Immanuelle (talk) 00:22, 4 April 2026 (UTC)Reply

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)Reply

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:

• Case 63 (Q116205398): scifi thriller podcast
• Case 63 (Q109423263): Chilean podcast

Can somebody do it? ~2026-20857-97 (talk) 22:30, 4 April 2026 (UTC)Reply

No, they should not be merged - the English one is a remake of the Chilean one, and has the correct based on (P144) relationship. ArthurPSmith (talk) 23:33, 4 April 2026 (UTC)Reply

Oh, I didn't noticed that. Thanks for pointing this out. ~2026-20857-97 (talk) 00:50, 5 April 2026 (UTC)Reply

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)Reply

(As a clarification, putting virtually the same coordinates into Q138899017 does not duplicate the problem on commons:Category:Southern Regional Technical College Thomasville Campus, so it's something specific with Q7571284 somehow. - The Bushranger (talk) 04:48, 5 April 2026 (UTC))Reply

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)Reply

Could this translation here be added to Q286702 ? Thanks ~2026-20934-24 (talk) 06:02, 5 April 2026 (UTC)Reply

 Done

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)Reply

I see in Help:Redirects that a bot is supposed to replace redirects. Is it still working? Its last contributions aren't conclusive.--Pere prlpz (talk) 12:20, 5 April 2026 (UTC)Reply

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.

I haven't checked other queries in that template, but perhaps the same is the case with them also? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:13, 5 April 2026 (UTC)Reply

This isn't a bug. I think mul should be added to Template:Item documentation. RVA2869 (talk) 15:02, 5 April 2026 (UTC)Reply