Wikidata:Project chat/Archive/2025/03

This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

location vs located in administrative https://m.wikidata.https://m.wikidata.org/wiki/Wikidata:Project_chat/Archive/2025/03#/editor/all/wiki/Wikidata:Project_chat/Archive/2025/03#Vector_2022_will_be_the_default_skin entity, a muddle

location (P276) guidance is: location of the object, structure or event. In the case of an administrative entity as containing item use P131

located in the administrative territorial entity (P131) guidance is: the item is located on the territory of the following administrative entity. Use P276 for specifying locations that are non-administrative places and for items about events.

If this wording means you need to choose the property depending on the type of location, why is the guidance to use location (P276) exclusively for events, after all the location properties are the same for everything.

A different interpretation is that you should use located in the administrative territorial entity (P131) for chains of administrative items, and location (P276) if the item is not administrative itself, like an event, landform or building. This makes more sense to me, but its certainly not how its been used across WD, where we mix the two properties with gay abandon.

It can be hard to know if either source or target items are administrative or not, and can trip you up for historical events, where you might say some battle was in Kent, when its actually in the modern construct of the Medway unitary authority. And who administers the oceans when defining shipwrecks. location (P276) might be used for a wreck, but {{P|131} for a museum ship in a port, so in practice you need paired queries for the information.

I'd like guidance on whether the constraints should be place on the object or subject to try and keep the 2 properties distinct. Vicarage (talk) 14:32, 21 February 2025 (UTC)

There is also located in the present-day administrative territorial entity (P3842), which would probably be more useful than P131 for many historical events. For the example of Kent and Medway, there are separate items where necessary for counties in England, where one includes unitary authorities and the other does not. Most things that have P131 could also have P276, but usually it is not added. I think P131 should be administrative only, and there were constraints last time I looked, but city, town, village and hamlet are all subclasses of administrative territorial entity (Q56061) so do not show as violations: city and town via city or town (Q7930989) (although not correct for all towns or cities), and village and hamlet via statements that apply only to Canada and Spain. Some instances also have P31 statements that would be valid for use as P131, but with end time (P582) qualifiers. I'm not sure about the guidance for events - it also says "Use P1382 if the item falls only partially into the administrative entity" but that is probably only correct for linking two administrative units that overlap (such as a ward and a parish). Peter James (talk) 18:09, 21 February 2025 (UTC)

located in the present-day administrative territorial entity (P3842) would be good for events, except it has a dissolved, abolished or demolished date (P576) constraint, not a end time (P582) one, and its name suggests its a variant of located in the administrative territorial entity (P131) which should not be used for events. I still think the choice of property should be with the object, as present, or the subject. River Thames (Q19686) uses located in the administrative territorial entity (P131) when it should use partially coincident with (P1382). I did add historic county (P7959) for some historic buildings, but found the task too big.

I'd certainly prefer the decision to made on the subject (who's features the editor can see), not the object (which may or not be administrative, now or at some point in the past), so queries for events and buildings could all use location (P276), and for places located in the administrative territorial entity (P131) Vicarage (talk) 11:34, 23 February 2025 (UTC)

I don't think it's useful to have partially coincident with (P1382) on a county or a country linking to every road, river, hill and building crossing its boundary. I've always used multiple P131 (and P7959), and that's what I've seen others use. P7959 is also added by CountyBot for most types of place or structure. For buildings P131 has always been used (it's a constraint on National Heritage List for England number (P1216), Cadw Building ID (P1459), NRHP reference number (P649) and Wiki Loves Monuments ID (P2186)), but most can also have P276. There also has to be something for suburbs (to say that places are suburbs of Huddersfield or Southport, not of areas that are only administrative such as Kirklees or Sefton, or Scottish council areas), I've used location (P276) in the past but now use part of (P361) (or both P276 and P361 for housing estates). Changes to P131 and P3842 could be proposed to allow use for events. Peter James (talk) 18:27, 23 February 2025 (UTC)

As there seems too few people interested in the subject, no consensus, and any change would be disruptive, I don't plan to proceed. Vicarage (talk) 17:46, 1 March 2025 (UTC)

I've literally just noticed that the ceremonial counties in England use located in the administrative territorial entity (P131) incorrectly, for example Devon is claimed, with preferred rank, to be located in the admin territorial entity South West of England, which is a purely statistical region (albeit a notable one).

While I can't speak for other countries, at all, I think it's very useful for local items, ie a listed building, to have a P131 for the the civil parish or borough in which it is in, as many times they will be responsible for approving for example planning applications or will be the location by which heritage items are grouped, or are otherwise linked to a wider area (eg by the area having another P131, like the london boroughs are P131 in Greater London).

An example of an item with both P131 and P276 is the Church of St Bartholomew. It has P131 for it's Civil Parish & a P276 for it's village, which doesn't have it's own administrative body or a defined extent. Tæppa (talk) 21:23, 23 February 2025 (UTC)

Identifier changed, old identifier was redirected

Hi. Spanish Biographical Dictionary ID (P4459) was the identifier for a person in the online version of the Spanish Biographical Dictionary (Q41705771) (currently 26 644 uses as main statement). Months ago, the page heavily changed and was renamed to "Historia Hispánica". All identifiers changed, but redirections were kept from the old ones (for example Mariano Álvarez de Castro (Q2698525) changed dbe.rah.es/biografias/6943/mariano-alvarez-de-castro to historia-hispanica.rah.es/biografias/1981-mariano-alvarez-de-castro (it works as historia-hispanica.rah.es/biografias/1981 too). There's apparently no easy way to reach the old ID's. I guess a new property should be proposed for Historia Hispánica ID. And the old property should be tagged as deprecated or so. But... is there a way to mass-add, somehow, via bot, the new identifiers for all the items we already have with the old ID? I mean, a bot that follows external redirects? strakhov (talk) 10:59, 1 March 2025 (UTC)

Given the large number of claims, it is probably safest to propose a new property. Currently it's at least used in the Authority Control template on spanish wikipedia, could be used in more places, I haven't checked that thoroughly. I have a tool to harvest redirects, which can be used to batch-add new claims (or update existing claims). I don't have anything that updates references however and there are over 16 000. Infrastruktur (talk) 13:36, 1 March 2025 (UTC)

Thanks. I proposed a new property (Wikidata:Property proposal/Historia Hispánica ID). Let's see what happens... strakhov (talk) 19:27, 1 March 2025 (UTC)

What qualifier could I use to designate a "senior" version of a role?

I have producer (P162)Heather Challands (Q132737177), she's a producer on an audio drama, But, I also want to add a senior producer. There's no property for senior producer, but rather than suggest one, I thought perhaps designating a senior could be done with qualifiers instead, is there an ideal qualifier/value combo for this or is lodging a property proposal the best way forward? ElDubs (talk) 01:30, 28 February 2025 (UTC)

Producer (P162) = Heather Challands (Q132737177), with the qualifier 'object of statement has role' (P3831) = senior producer (Q7450743). At least, I would do like this. --Wolverène (talk) 05:15, 28 February 2025 (UTC)

Thank you for that, that works perfectly. ElDubs (talk) 22:11, 2 March 2025 (UTC)

What is the status of English "en" labels and aliases?

I've always understood that "en" was the main fallback language used in Wikidata, but now I see that "mul" is being used instead and "en" labels and aliases are being deleted, eg on Douglas Adams (Q42). Is this now official policy? There are probably hundreds of SPARQL queries and tutorials that assume the existence of "en" labels, for example https://www.wikidata.org/wiki/Wikidata:SPARQL_tutorial#Expressions,_FILTER_and_BIND refers to the string literal "Douglas Adams"@en and a random YouTube tutorial https://www.youtube.com/watch?v=1jHoUkj_mKw which assumes "en" labels using the WDQS Label Service Piecesofuk (talk) 10:17, 2 March 2025 (UTC)

'Official policy' is lacking in this area, as while the mul team implemented the change technically, they've not instigated a successful hearts and minds campaign to define its usage, nor addressed the loose ends that abound.. You might want to ask at Help_talk:Default_values_for_labels_and_aliases, but no-one there is speaking for WD as whole. For the moment, people seem to be adding mul widely, but with few exceptions, leaving existing labels alone, apart from a few that think the bold action of removing labels will trigger activity downstream when others are annoyed by holes in their data. Vicarage (talk) 11:33, 2 March 2025 (UTC)

Thanks, I've reposted the question in https://www.wikidata.org/wiki/Help_talk:Default_values_for_labels_and_aliases Piecesofuk (talk) 11:49, 2 March 2025 (UTC)

"Duplicates" that aren't actually duplicates

It seems to me that going by the Polish Wikipedia Q115269162 and witch (Q1616828) are not actually identical concepts, the prior seems to refer to half-demons in Polish folklore (that women who were accused of witchcraft may have been accused of being) while the later is about the idea of a witch more broadly. StarTrekker (talk) 13:21, 3 March 2025 (UTC)

Wikidata and Sister Projects: a new online community event

Hello, a new Wikidata online event approaches: Wikidata and Sister Projects.

We're bringing together editors from across the Wikimedia Projects who are using Wikidata to enhance their articles, content, workflows and more, so please head on over and register!

The event is taking place online from May 29 to June 1, 2025. You will be able to join live or watch the videos later. Proposals are welcome from editors of all Wikimedia projects where Wikidata is used, in Wikipedia, Commons, Wikisource and more!

You can propose sessions on the talk page until March 31st, here’s some ideas for inspiration:

• demos of tools, gadgets or templates using Wikidata's data in another Wikimedia project
• discussions between Wikidata editors and editors from other projects on collaboration and knowledge sharing
• success stories, creative uses and experiments.

If you have any questions or suggestions, feel free to write below, on the event talk page or to reach out to me directly. - Danny Benjafield (WMDE) (talk) 13:55, 3 March 2025 (UTC)

Wikidata weekly summary #669

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

Discussions

• Other: Email Chain "Elephant in the room" - discussing the large number of Wikidata Items lacking Statements, Sitelinks or Labels/Descriptions.

Events

• Upcoming events:
  • All the information you need to start working on your Wikimania 2025 program submissions is now available on the Wiki. Deadline: March 31 st, Anywhere on Earth.
  • New Wikidata Event! The upcoming "Wikidata and Sister Projects" event (May 29–June 1) is looking for speakers to share how Wikidata connects with other Wikimedia projects - if you are interested, request more info or submit your session idea here.
  • New Linked Data for Libraries LD4 Wikidata Affinity Group project series! We have our next LD4 Wikidata Affinity Group project series session on Tuesday, March 4, 2025 at 9am PT / 12pm ET / 17:00 UTC / 6pm CET Time Zone Converter Eric Willey will be facilitating a series of four sessions focused on starting a Wikidata project from the foundation up at your institution. The third session will focus on making the most of your time and work. Event page.
  • Wikidata and Wikibase - Curriculum Transformation in the Digital Humanities - Join for 4 free talks showcasing how linked open data can support teaching, research and collections. March 5, 1500 - 1700 GMT (UTC-0).
  • Wiki Workshop 2025 CfP - Call for Papers (Submission deadline: March 9)
  • Open Data Day Taiwan 2025 March 9 Time: 09:30-17:30 UTC+8 at Taipei Humanities Building (Q122750631)
  • Wiki Mentor Africa (WMA) Hackathon 2025 - Registration & Scholarship Now Open. Date: 28th - 30th March 2025. Who Can Participate? African developers, Wikimedia contributors, and anyone interested in Wikimedia projects.
• Ongoing:
  • Wiki Loves Ramadan 2025 - annual global contest aimed at documenting and sharing the diverse customs and traditions observed during the month of Ramadan. Date: 25 February 2025 – 16 April 2025. Register here!
  • Items with P31 (instance of) = human settlement without a country has dropped from 7600 to below 4600 Items. You can help to get it even lower.
  • Wikidata & OpenStreetMap Datathon & Mapathon as part of International Open Data Day 2025 from 1st - 15th March 2025 by WikiProject India (Q11037573).
• Past events: Data Reuse Days 2025: you can watch the sessions that you missed at your own pace.

Press, articles, blog posts, videos

• Blogs
  • UK universities educate the most national leaders globally, analysis (based on Wikidata) shows. By The Guardian
  • Two Wikimedians-in-Residence appointed to increase Maltese literature representation on Wikipedia and Wikidata Times of Malta
• Videos
  • (French) PasseGares: Bug fixes and data imports from Wikidata YouTube
  • Adding Wikidata label and descriptions, from the Wali Language Art+Feminism Editathon (Ghana 2025) YouTube
  • Workshop showcasing QuickStatements 3.0! Learn how this updated tool streamlines your workflow and discover new features. YouTube
  • Contributing to Wikidata 101, a series of demonstrations organised by WM Community UG Uganda Part 1, Part 2, Part 3
  • Optimize SPARQL queries to avoid timeouts: Efficiently count entities sharing values YouTube
  • Data Reuse Days playlist and live-editing session with User:Ainali and User:Abbe98 YouTube
  • LUDAP: Shared authority file for Luxembourg's Scientific and Cultural Heritage, with Wikibase YouTube

Tool of the week

• QuickStatements 3.0 - new version of the original QuickStatements with enhanced functionality, performance, and user experience.

Other Noteworthy Stuff

• On March 17, Vector 2022 will become the default skin on Wikidata
• Jobs
  • Senior UX Designer for Wikidata - Apply online
  • Product Manager for Wikibase Suite - Apply online

Newest properties and property proposals to review

• Newest General datatypes:
  • thesis submitted for degree (the academic degree for which a thesis or dissertation is submitted)
• Newest External identifiers: Korean National Species list ID, NES Directory game ID, Miraheze wiki ID, Global Energy Monitor Wiki ID, FU-Lexikon ID, MACM artwork ID, Hiking Note chalet identifier, domain name, ‎TechRaptor game ID, ‎TechRaptor company ID, ‎TechRaptor genre ID, Sanzhi Dargwa dictionary ID
• New General datatypes property proposals to review:
  • copy present in institution (copy present in institution)
  • single extrait de l'album (indicates the album from which the item is taken)
• New External identifier property proposals to review: HelloAsso organization ID, europlayers.com club ID, eLIBRARY Document Number, LIBRIS Library ID, parlament.fyi person ID, Embryo Project Encyclopedia ID, factordb id, Yukon Register of Historic Places ID, Our Campaigns container ID, Encyclopaedia of Islam (glossary and index of terms) ID, badmintoncn.com star ID, Game Input Database ID, Historia Hispánica ID, Coasterpedia ID, Captain Coaster coaster ID, Captain Coaster park ID, Dark Ride Database IDs

You can comment on all open property proposals!

Did you know?

• Query examples:
  • Map of Birthplace of Polish Nationals, born after 1900 who have an article on Polish Wikipedia
  • Items with no Statement or Sitelinks - You can help by expanding these Items!
  • Showcase lexemes and their language/lexical category (source)
• Newest WikiProjects: Climate Change Policies - aims to model policies related to Climate change on Wikidata.
• Newest database reports: Most linked category Items
• Showcase Items: Basshunter (Q383541) - Swedish singer, record producer, and DJ
• Showcase Lexemes: baguette (L7347) - French noun that can mean "elongated type of bread loaf", "elongated type of bread loaf", "conductor's baton", "chopsticks", "drum sticks" or "magic wand".

Development

• Wikibase REST API: We are continuing the work on the simple Item search (phab:T383126)
• Dumps: We fixed an issue that prevented the dumps from being generated (phab:T386401)
• Search: We are continuing to work on the search UI that will let you search not just Items but also other entity types (phab:T321543)

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: Australia
• 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!

· Read the full report · Previous issue · Unsubscribe · Mohammed Abdulai (WMDE) talk · MediaWiki message delivery (talk) 15:26, 3 March 2025 (UTC)

Duplicated salt warehouses

Hello, those items are potentially about the same subject but I am not 100% sure: salt warehouse (Q3116478) salt warehouse (Q2216217) and salt warehouse (Q101085451). In your opinion can I merge them? Una tantum (talk) 16:13, 4 March 2025 (UTC)

Edit summaries

Hi, Apologies in advance if this is a really stupid question but I only edit here like twice a year so don't really know,

Is there a way I can use an edit summary when removing things ?, For instance when I remove a logo I'd like to state why I'm removing it,

I'm having to undo my edit and then re-undo it so I can explain what I'm doing, Surely there's an easier way right ?.... Thanks, Warm Regards, Davey2010 (talk) 18:53, 1 March 2025 (UTC)

Wikidata:Tools/Enhance user interface#EditSum sounds like it can do what you want, but I don't have experience with it. William Graham (talk) 20:44, 1 March 2025 (UTC)

Just tested it out and it worked for me. I'll also mention I'm using the Vector 2022 skin. William Graham (talk) 20:56, 1 March 2025 (UTC)

For statements that change over time, an alternative to deleting old statements is to mark the current statement to preferred, see Help:Ranking, and use start time (P580) and end time (P582) qualifiers. For examples, see the logos of IHOP (Q1185675) and Pepsi (Q47719). Difool (talk) 02:11, 2 March 2025 (UTC)

@Difool, does that include: Image P18? Thanks, -- Ooligan (talk) 10:22, 2 March 2025 (UTC)

@Ooligan - For using the most recent image: I think you can use it as a guideline but not as strict rule; you could argue that the preferred image (for people) is the one that best represents how they are commonly known. For an actor who passed away some time ago, an image from their active years might be more appropriate than a more recent one. I would only use multiple images if the images are clearly distinct/unconnected, not for a person that grows older. Difool (talk) 10:53, 2 March 2025 (UTC)

That is good advice, @Difool. What do you think about all persons- always having only one photo? To the contrary, does not the fact that P18 has the "designed-in" ability for volunteer editors to choose, Preferred, Normal and Deprecated ranks indicate that P18 was designed for more than one photo? -- Ooligan (talk) 05:30, 5 March 2025 (UTC)

@William Graham You sir are amazing thank you! :),

@Difool, I'll be honest I didn't understand a word of that but thank you for replying anyway :),

Thanks again Willian and Difool your help is greatly appreciated, Thanks, Warm Regards, Davey2010 (talk) 16:47, 3 March 2025 (UTC)

Population by nationality

Is there an accepted way to enter the population of a place (country, city, region, etc.) by nationality? Say, the city of Copenhagen has X many Danish nationals living there, Z many Swedes, Y many Poles, etc. Such statistics are often available but I don't see an obvious way to include it on Wikidata. Bjarki S (talk) 21:41, 3 March 2025 (UTC)

What would be needed would be some kind of independent body compiling those statistics. It's not wikidata's role to compile such stats and many countries measure such statistics differently, particularly with respect to dual-citizenship holders, minors, etc. Stuartyeates (talk) 09:22, 4 March 2025 (UTC)

I have the official data which can be cited. Just wondering about the proper properties to use here to save it here. Bjarki S (talk) 06:32, 5 March 2025 (UTC)

Wrong sitelinks

The item That Vegan Teacher (Q105699114) have a sitelink that is not about That Vegan Teacher

Permalink: https://www.wikidata.org/w/index.php?title=Q105699114&oldid=2290483879

Sitelink: https://war.wikipedia.org/wiki/Karen DinhHuy2010 (talk) 13:41, 4 March 2025 (UTC)

 Done the wrong site link removed. RVA2869 (talk) 14:15, 4 March 2025 (UTC)

war:Karen seems to be a hoax. The date of death is the same as Charles M. Schulz (Q298920), the names are based on de:wikt:Karenz, there are no references, and Google search doesn't find anything relevant. Peter James (talk) 16:08, 5 March 2025 (UTC)

Location names that have changed

Cor van Gogh, the youngest brother of the famous painter Vincent van Gogh, died in Brandfort. Brandfort is a town name that has been changed to Winnie Mandela in 2021. The Q number for Brandfort (now Winnie Mandela) is Q2805770. When I search for Cor van Gogh, the result I get shows that he died in Winnie Mandela. Is this a Wikidata problem. If so, how can this be rectified? Derek J Moore (talk) 09:57, 4 March 2025 (UTC)

I'm not seeing this - maybe you should post a screenshot if it's still an issue? Brandfort (Q2805770) is labeled "Brandfort" in English, and has been for years. ArthurPSmith (talk) 21:58, 5 March 2025 (UTC)

Hello Arthur. Thanks for the reply. Have done a few Google search queries in the past few days using the phrase "Cornelis van Gogh" and I always get the same result. Here's screenshot https://weblearning.co.za/blog/wp-content/uploads/2025/03/Brandfort-1024x375.png I'm also writing a blog post (as yet unpublished) about this odd situation. I was going to wish you a happy friday. But on second thoughts stay safe might be a more appropriate greeting Derek J Moore (talk) 06:34, 7 March 2025 (UTC)

References

Universal Code of Conduct annual review: proposed changes are available for comment

Please help translate to your language.

I am writing to you to let you know that proposed changes to the Universal Code of Conduct (UCoC) Enforcement Guidelines and Universal Code of Conduct Coordinating Committee (U4C) Charter are open for review. You can provide feedback on suggested changes through the end of day on Tuesday, 18 March 2025. This is the second step in the annual review process, the final step will be community voting on the proposed changes. Read more information and find relevant links about the process on the UCoC annual review page on Meta.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review was planned and implemented by the U4C. For more information and the responsibilities of the U4C, you may review the U4C Charter.

Please share this information with other members in your community wherever else might be appropriate.

-- In cooperation with the U4C, Keegan (WMF) 18:50, 7 March 2025 (UTC)

Merge for a song?

Hi, can someone help me figure out of if these results are all the same? If so, how do I merge them? Myrealnamm-alt (talk) 14:29, 7 March 2025 (UTC)

Also, there is now w:en:Ça sent si bon la France, which can be connected with one of those items. Myrealnamm-alt (talk) 14:30, 7 March 2025 (UTC)

A musical work (the song) can have many recordings -- which can be included in musical releases (singles, albums, etc) as tracks.

These should remain distinct items as they each have their own distinct identifiers (ISWC, ISRC, etc) and properties.

You can learn more about the music ontology in the Wikidata:WikiProject Music project. Iamcarbon (talk) 19:06, 7 March 2025 (UTC)

@Iamcarbon Thanks for the reply. So which should w:en:Ça sent si bon la France go into? The article covers both the song as a single and both tracks. Should it go with Ça sent si bon la France (Q46541479) because that's where I translated the article from?

Also, I strongly believe these two following are the exact same/duplicate:

• Ça sent si bon la France / La Chanson du maçon (Q105395507)
• Ça sent si bon la France / La Chanson du maçon (Q105395562)

Could you help me double check these two only? Thanks. Myrealnamm-alt (talk) 19:13, 7 March 2025 (UTC)

I would recommend associating the Wikipedia page with the song / musical composition, as it's the item shared in common with everything it describes.

Although the last two items appear nearly identical, there is a subtle distinction: the "Single" refers to the release itself, whereas the second item represents the 78 RPM, 10-inch shellac edition of that release. Iamcarbon (talk) 19:58, 7 March 2025 (UTC)

Thank you for helping me distinguish those items, really appreciated! Myrealnamm (talk) 21:32, 8 March 2025 (UTC)

Delete or mark as deleted?

The following hotel chain does not exist any more: Q16325118: It has been taking over by another hotel chain, FourPoints Flex by Sheraton (Q1439966). The same goes for the invidual hotel Q111409494. What should be done about obsolete Q16325118? Should it be deleted? Or should it somehow (how?) be marked as obsolete?

Troels Arvin (talk) 21:02, 7 March 2025 (UTC)

We want to record the evolution of companies, so for the chain record the mergers as we do for Vickers (Q13220673), deciding whether the brand still exists within the new organisation. Treat the hotel as a single object with a series of operator (P137) Vicarage (talk) 22:47, 8 March 2025 (UTC)

Problems to merge with mergeitems tool

I've been trying with Special:MergeItems to merge from Q98968175 to Q117422231, but it always shows me the same message: Failed to merge Items, please resolve any conflicts first. / Error: Conflicting descriptions for language en ... Please could someone assist me to solve this?. Fma12 (talk) 22:25, 7 March 2025 (UTC)

I would recommend to use Merge.js (see Help:Merge#Gadget), which should be easier. D3rT!m (talk) 10:25, 8 March 2025 (UTC)

In this specific case, just choose the English description you prefer, and simply delete the other one prior to using the tool. --Matěj Suchánek (talk) 14:58, 8 March 2025 (UTC)

Hide

Is there a way to hide the languaje label "default for all languages"? Thank you --Fantastoria (talk) 13:31, 1 March 2025 (UTC)

.wikibase-entitytermsforlanguageview-mul { display: none; } GZWDer (talk) 11:32, 3 March 2025 (UTC)

Sorry @GZWDer:, but I don't understand what you mean. --Fantastoria (talk) 12:34, 9 March 2025 (UTC)

Add it to Special:MyPage/common.css. GZWDer (talk) 12:57, 9 March 2025 (UTC)

Ok, Thanks. --Fantastoria (talk) 13:09, 9 March 2025 (UTC)

Duplicate entry

Q18580797 is a duplicate of Q6412786. Ostensibly one had a typo in the header, and instead of just fixing that (or without knowing it existed), someone created an entirely new entry. Thoughts on what is usually done with entries like this? 04:45, 9 March 2025 (UTC) TheTechnician27 (talk) 04:45, 9 March 2025 (UTC)

 Done I eliminated the typo in Q6412786 and simply merged Q18580797 into it. --Matěj Suchánek (talk) 08:30, 9 March 2025 (UTC)

zelph: A tool for finding logical contradictions and making inferences in Wikidata

Hello Wikidata community,

I'd like to introduce you to zelph, a semantic network system I've developed that can help identify logical contradictions and make deductions within Wikidata's knowledge graph. The project is available at:

• GitHub: https://github.com/acrion/zelph

• Website: https://zelph.org (with a tree of 4,580 pages showing deductions and contradictions)

Key features relevant to Wikidata:

• Contradiction detection: zelph can identify logical inconsistencies in Wikidata's knowledge structure, which could help improve data quality.

• Inference capabilities: Using a rule-based system, zelph can derive new facts from existing ones (e.g., through transitive relationships).

• Innovative representation: zelph represents relations as first-class nodes rather than edge labels, perfectly matching Wikidata's approach to properties. Moreover, not only facts but also the inference rules themselves are represented within the semantic network (theoretically allowing rules to generate new rules).

• Memory efficiency: zelph processes the entire 1.4TB Wikidata JSON into just 9.2GB of memory, requiring only ~80 bytes per Wikidata item.

• Customizable inference rules: The inference mechanisms aren't hardcoded but defined through a scripting language. The current tree was generated using a script designed to follow Wikidata's usage guidelines.

The system has already successfully processed the complete Wikidata knowledge base multiple times and published results that highlight both potential issues and new connections.

I'm very interested in exploring potential collaboration with the Wikidata community. Any feedback, suggestions, or questions would be greatly appreciated, e.g. regarding the inference rules and their alignment with Wikidata best practices.

Best regards, Stefan Acrion-dev (talk) 14:46, 9 March 2025 (UTC)

"Also known as"

Hello, how do I access the data stored in "Also known as" in a Qid with Module:Wikidata ?

{{# i n v o k e: Wikidata| getLabel |entity= Qid |lang= mul }}

will get the name - default for all languages

{{# i n v o k e: Wikidata| getDescription |entity= Qid |lang= fr }}

will get the desc in French

What

{{# i n v o k e: Wikidata| ?function? |entity= Qid }}

will return "Also known as" list ?

It doesn't seem to be a property, as neither label nor description seem to be properties.

-- 65.92.246.77 22:30, 6 March 2025 (UTC)

You will be much better off using the Wikidata template or the corresponding Wd module. Plenty of examples on its page, and several wikis have a copy of it, if not ask your local administrator to import it. Infrastruktur (talk) 11:24, 10 March 2025 (UTC)

Wikidata 101 MOOC for Beginners (in English) - Starting March 17, 2025!

Hi everyone,

We’re excited to announce a rerun of the Wikidata Open Online Course for beginners, starting on March 17, 2025.

About the Course

The Wikidata Open Online Course is designed to simplify learning how to edit Wikidata through a structured online program in English. Originally developed in French by Wikimedia France, the course content has been updated and translated into English.

Whether you're:

• A beginner taking your first steps,
• In need of a refresher on Wikidata concepts, or
• A seasoned trainer looking to level up your skills,

this course is perfect for you. Participants will gain insights into how Wikidata works, its rules, its vibrant community, and how to contribute effectively.

What to Expect

• Chapter 1: The Wikimedia Movement and the Creation of Wikidata
• Chapter 2: Understanding Knowledge Graphs and Queries
• Chapter 3: Discovering Wikidata, Open Data, and the Semantic Web
• Chapter 4: Contributing to Wikidata, the Community, and Data Quality
• Chapter 5: Bonus Resources on Scientific Bibliography from Wikidata

How to participate:

• Head over to Wikidata 101: An Introduction to enroll using your Wikimedia credentials.
• Don’t hesitate to share this opportunity with your friends and colleagues.

If you have any questions, feel free to leave a note here or write to me directly.

Cheers!

Zita Zage (WMDE) (talk) 10:02, 10 March 2025 (UTC)

Wikidata weekly summary #670

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

Events

• Upcoming events: Tuscan Women & Wikidata - data entry lab for shared memory, 5 March.

Press, articles, blog posts, videos

• Blogs
  • WMDE Blog - Highlights of Data Reuse Days: The post showcases 3 excellent apps: WikiFlix (public domain full-length films), KDE Itinerary (travel assistant app) and Scribe Keyboard (easier writing in secondary languages). These are just some of the applications built using Wikidata; check out more at the Data Reuse Days pages.
  • (German) Digital Stumbling Blocks – How the Wiki Community Drives Remembrance Culture: User:Cookroach highlights the efforts of Wikimedians across projects (Wikidata, Wikipedia, Commons) to digitally document the Stolpersteine, brass-plaques laid to commemorate victims of the National Socialism.
  • (German) Digital History Berlin: Field research with LOD - a write-up of the methods, experiences data-model and SPARQl queries of the field research conducted as part of the WikiProject: Field Survey Digital Humanities.
  • (Italian) Wikipedia & Wikidata project for Cesare Alfieri - an introduction to the project to expand articles and data of the archives of Cesare Alfieri University of Florence.
  • Communicating Ontology: Technical approaches for facilitating use of our Wikibase data (Semantic Lab at Pratt Institute)

Tool of the week

• zelph: A new tool for detecting logical contradictions and making inferences in Wikidata, using a rule-based system to improve data quality and derive new facts. Check it out on GitHub or explore results on the project website.
• New Tool for Women’s Day: Scheherazade identifies women without articles in your Wikipedia but present in many others, helping editors prioritize creating missing biographies.

Other Noteworthy Stuff

• Wikimedia Research Fund had launched. You're encourage to submit proposals around Wikidata. The deadline to submit your proposal is April 16, 2025.
• The 4th iteration of the Wikidata:Open Online Course will begin from March 17 until April 30. Whether you're a beginner taking your first steps, an individual in need of a refresher on Wikidata concepts, or a seasoned trainer looking to level up your skills - this course is right for you.

Newest properties and property proposals to review

• Newest General datatypes:
  • model number (identifier for a product model)
  • provides data for property (dataset associated with this external ID usually contains data applicable to this other Wikidata property)
  • items classified (class of items that this classification system classifies)
  • presented works (works of art or creative works performed, displayed or presented at a given event)
  • number of goals scored in penalty shootouts (total number of goals scored by a team in a penalty shootout)
• Newest External identifiers: ‎Thinky Games game ID, Lenape Talking Dictionary ID, Biographical Dictionary of Republican China (X-Boorman) ID, LEMAC ID, Bane NOR station ID, Sutian entry ID, Platform for Taiwan Religion and Folk Culture ID, Meine Abgeordneten ID, Hiking Note plant ID, VGC game ID, VGC company ID, VGC people ID, Archives in Bavaria ID, VGC theme ID, ‎Steam group ID, AllGame game ID (archived)
• New General datatypes property proposals to review:
  • kigo of (the season the sense denotes in haiku in Japanese)
  • Hare Psychopathy Checklist-Revised score (score that the subject have received on the Hare Psychopathy Checklist-Revised psychological assessment tool as administered by a suitably qualified and experienced clinician under scientifically controlled and licensed conditions, standardized conditions)
• New External identifier property proposals to review: Archaeological site (Japan) ID, Hmong Studies Citations ID, GitLab topic, Christchurch City Council Park ID, Clio-online researcher ID, Clio-online web resource ID, Clio-online organization ID, Congress.gov committee ID, AGORHA ID, Crunchyroll artist ID, ZOOM Platform product ID, GCMD keyword ID, KnowWhereGraph entity ID, VejinBooks author ID, SteamDB tech ID, Identifiant Cartofaf d'une organisation, Saarland Biografien ID, Murderpedia ID, Big Fish Games game ID, Danskefilmstemmer.dk work ID

You can comment on all open property proposals!

Did you know?

• Query examples:
  • Obscure units of measurement and where to find them
  • Female scientists with most number of sitelinks (but not English Wikipedia)
• Newest WikiProjects: AncientCoinsAndModernMedals
• WikiProject Highlights:
  • WikiProject Biology: List of Mushrooms - revived by User:Prototyperspective, help catalogue all known fungal friends, and join the subreddit (for all Wikidata topics): r/WData
  • India/Police Stations
• Newest database reports: List of free software without an image set - This is a table of Wikidata items about a free software missing an image.
• Showcase Items: Doctor Strange (Q18406872) - 2016 film directed by Scott Derrickson
• Showcase Lexemes: felle (L476372) - Bokmål verb that can mean "to make something fall", "to kill", "to force a resignation", "to prove guilt", "to let lose", "to announce" or "to join."

Development

• Search: The search team at the WMF has added a new search keyword for Lexemes. You can use the keyword "inlanguage:en" or "inlanguage:Q1860" to limit your search to Lexemes with Lexeme language English and so on. Here is an example search for "bank" within English Lexemes: https://www.wikidata.org/w/index.php?search=L%3Abank+inlanguage%3Aen (phab:T271776)

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.
• 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!

· Read the full report · Previous issue · Unsubscribe · Mohammed Abdulai (WMDE) talk · MediaWiki message delivery (talk) 15:01, 10 March 2025 (UTC)

Citing a calculated birth date

The birth date citation on George James Cottom Broom (Q133200542) is throwing a constraint error.

What's the preferred way to cite a birth date calculated from a cited age at death? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:35, 9 March 2025 (UTC)

I would go for date of death (P570) qualified with age of subject at event (P3629) and inferred from (P3452) -> age at death (Q50379085) as source for date of birth (P569). See for example Edward "Jock" Stewart (Q124981459). based on heuristic (P887) might also be an option. Multichill (talk) 16:47, 10 March 2025 (UTC)

Director / governor of the bank of england

We have both director of the Bank of England (Q93338235) and Governor of the Bank of England (Q2579905). Are they really something different ? Don't know anything about that position and its history, so … A query of who held that position : https://w.wiki/DNTT one of the item is used more than the other, it seems. author  TomT0m / talk page 15:06, 10 March 2025 (UTC)

https://www.bankofengland.co.uk/about/people shows there is one governor (and several deputies), and many directors Vicarage (talk) 15:28, 10 March 2025 (UTC)

OK so it is left to decide whether or not just the governor is organization directed by the office or position (P2389) or not. It raises a constraint error because it does not currently have an inverse. If there is several I guess there is a college of presidents (the court of directors) that is actually the head of the organism ? author  TomT0m / talk page 19:54, 10 March 2025 (UTC)

Francine M. Benes

How should the Emeritus status of Francine M. Benes (Q119495999) be added to the item? Ideally, this would also then be reflected in the corresponding infobox/Wikidata of the w:Francine M. Benes article. -- Cl3phact0 (talk) 18:50, 7 March 2025 (UTC)

@Cl3phact0: professors are a bit of a mess at the moment. This is because the concept looks the same in most countries, but turns out to be slightly different.

Take for example Andrew S. Tanenbaum (Q92621): American-Dutch computer scientist (no so random example, I had him as a professor). He was nl:Hoogleraar (full professor under Dutch law) and is now a nl:Emeritus hoogleraar (retired full professor under Dutch law). Maybe we need to create per country subclasses to sort it out? Automated imports made the data quite the puzzle to work with. Multichill (talk) 17:01, 10 March 2025 (UTC)

Thank you for this interesting (and non-random) example. Being neither a data scientist nor particularly expert about this corner of the wikiverse, I don't know that I have too much to add beyond an opinion, and the sense that it may add unwanted complexity to try and capture both administrative legal employment status together with what seems largely a honorific title indicating the retired status of an esteemed academic (notwithstanding differences from country to country). My focus in this case is trying to eke out the best possible results using w:Template:Infobox person/Wikidata (which I find fascinating and woefully underexploited). -- Cl3phact0 (talk) 15:41, 11 March 2025 (UTC)

Wikidata item for Wikimedia project category for item with its own Wikidata item

Q24044101 is for "Category:Paraselenis", and has the Wikimedia Commons category linked to it, thus forbidding it from being linked to Q2443412, which is "Paraselenis". Doesn't this defeat the purpose of Wikidata? Is it standard for Wikimedia Commons categories to be linked to meta-entries like this rather than to the entry that corresponds to the actual subject matter? Zanahary (talk) 05:51, 11 March 2025 (UTC)

@Zanahary: Yes, this is perfectly normal and is the intended behaviour. Paraselenis (Q2443412) is linked through Category:Paraselenis (Q24044101) to the Commons category. That's why the data from Paraselenis (Q2443412) shows up correctly while looking at the Commons category. — Huntster (t @ c) 14:43, 11 March 2025 (UTC)

Is there a way to see that the Commons category exists from the Paraselenis Wikidata item? Zanahary (talk) 16:14, 11 March 2025 (UTC)

@Zanahary: The normal practice is to add Commons category (P373) to both the subject item and the category item, but the interwiki link (under "Multilingual sites") only goes to the category item. That said, it's only necessary to add Commons category (P373) to the category item when such an item exists. — Huntster (t @ c) 20:59, 11 March 2025 (UTC)

Yes: Q2443412#P373. Jonathan Groß (talk) 16:16, 11 March 2025 (UTC)

FYI: Wikisource and Wikidata together: lessons from the Wikisource Conference

https://diff.wikimedia.org/2025/03/12/wikisource-and-wikidata-together-lessons-from-the-wikisource-conference/ —Justin (koavf)❤T☮C☺M☯ 07:49, 12 March 2025 (UTC)

Mass import of bad data - title page value

Saiphani02 (talk • contribs • logs) is mass importing bad data. I have explained the problem on their talk page, but they shrugged this off and continue mass importing the bad data. They are importing values of "page displayed" from Wikisource Index pages, which may be a title page, or a frontispiece, or a bound cover, or something else. Looking at the values imported, nearly 99% of them are incorrect so far because they are the first page of the scan, not the title page, which is typically 7 or 9 pages into a scan of a Wikisource copy.

This will require a mass revert to remove all the bad data. --EncycloPetey (talk) 15:28, 13 March 2025 (UTC)

Examples of the problem:

• edit adding qualifier: title page number (P4714): 1, but the title page is actually page 9.
• edit adding qualifier: title page number (P4714): 1, but the title page is actually page 9.
• edit adding qualifier: title page number (P4714): 1, but the title page is actually page 7.
• edit adding qualifier: title page number (P4714): 1, but the title page is actually page 5.

Thus far, after checking lots of these edits, I have found only a single instance where the claim of title page location was correct. --EncycloPetey (talk) 15:46, 13 March 2025 (UTC)

Update: Where I have pointed out and removed an error [1]; the user simply adds the incorrect info back onto the data item.

Since the user is refusing to acknowledge the data is bad; is refusing to consider the data is bad; has claimed to have stopped, but in fact has not; and is continuing to not only add bad data, but is restoring bad data that was removed, this user may need to be blocked to protect the project. --EncycloPetey (talk) 16:41, 13 March 2025 (UTC)

I understand that the value of "Image" might not be as accurate in the Wikisource index page template and have stopped the temporary batch - #temporary_batch_1741877013384 and the batch #244414 immediately as soon as @EncycloPetey brought it to my notice. the batch #244414 added couple more qualifiers after 50 minutes for reasons I'm unaware of. Saiphani02 (talk) 18:04, 13 March 2025 (UTC)

It took two sets of requests and posting twice here to get the process stopped. But now, knowing that the data was bad, you should voluntarily remove the bad data. --EncycloPetey (talk) 18:39, 13 March 2025 (UTC)

done. Saiphani02 (talk) 19:09, 13 March 2025 (UTC)

QLever wikidata index updates / QLever service/instance with current index

Tracked in Phabricator
Task T386401

Hello, for some SPARQL-Queries I have been using

• https://qlever.cs.uni-freiburg.de/wikidata

when

• https://query-main.wikidata.org/

returns a timeout. In the past, according to the button "Index information" on QLever the wikidata index has been updated almost every weekend (Saturday or Sunday). At the moment, "index information" shows, that the index has been updated on 29th of January 2025. Is there another service which is using the QLever software, but with a more current wikidata index?

• https://github.com/ad-freiburg/qlever/discussions/1833

Thanks a lot! M2k~dewiki (talk) 22:23, 14 March 2025 (UTC)

@M2k~dewiki - The file latest-all.ttl.bz2, located under /wikidatawiki/entities/ and referenced when you click the "Index information" button on the QLever website, is still dated January 29, 2025. Attempting to download it results in a 404 error, and its size is just 43 bytes, so i think that might be the issue. Difool (talk) 01:38, 15 March 2025 (UTC)

Tracked in Phabricator
Task T388954

Thanks a lot! I have opened https://phabricator.wikimedia.org/T388954 now. M2k~dewiki (talk) 01:51, 15 March 2025 (UTC)

Documenting repeated deletions: Sakurako Miki and Sakiko Miki

At commons:Special:Diff/1007617797, Nakonana told me that the Wikidata items for Sakurako Miki (currently Sakurako Miki (Q125694445): Japanese girl) and Sakiko Miki (currently Sakiko Miki (Q125693481): Japanese girl) have been deleted and recreated multiple times.

The current items cited in the previous paragraph were created on 30 April 2024 and have no logs. Searching Wikidata (excluding the File namespace) or the Requests for deletion archive does not give any other results. This situation would not arise on any other project. It arises on Wikidata because every item is identified by a meaningless string of digits prefixed by ‘Q’, that apparently cannot be assigned meaning again once the item has been deleted.

There is plenty of discussion about Sakurako and Sakiko on Commons, which is easy to find. Surely there is discussion about Sakurako and Sakiko on Wikidata too, but I have no idea how to find it. Surely there is also discussion about making the Requests for deletion archive more usable, but I cannot find that either. Brianjd (talk) 02:50, 12 March 2025 (UTC)

As another example, I found Wikidata:Requests for deletions/Archive/2025/03/11#Q72384834, where one user said the item was non-notable, another user said it was notable, and the item was simply deleted without further discussion. We may never know whether it really was notable.

I don’t intend to look further. Brianjd (talk) 04:13, 12 March 2025 (UTC)

I don't know whether it will be of any help for you, but the way I noticed that there have been Wikidata items on the two girls in the past was by spotting Pi bot's edits in the history of "Category:Sakurako Miki" and her sister. Pi bot was adding the then current qIDs and listing them in the edit summary. What you'll find this way for Sakurako is at first Q113989811: no description, which was then removed[2]. Then there was some back and forth[3][4] which ended with the statement that the Wikidata item has been deleted[5]. Some time later you see Pi bot adding a new Wikidata item to the category: Q120549006: no description. That one was later deleted: [6]. I don't know where the deletion discussions happened, though, or whether there were any discussions at all. Nakonana (talk) 21:40, 12 March 2025 (UTC)

It looks like identifying the qIDs is the key to find the discussions:

• https://wikidata.org/wiki/Wikidata:Requests_for_deletions/Archive/2022/11/10#Q113989811
• https://wikidata.org/wiki/User_talk:2404:0:8516:9F92:5C42:2DFA:3926:ABC0 (the section about recreating deleted items)
• https://wikidata.org/wiki/Wikidata:Requests_for_deletions/Archive/2023/07/17#c-DeltaBot-20230717220000-Eien20-20230714224700

That's what I could find when searching for the first qID listed for Sakurako. Nakonana (talk) 21:50, 12 March 2025 (UTC)

I created a tool to help with this problem. Currently it is only accessible by admins and rollbackers.

Sakurako Miki Q113989811 (Eien20), Q120549006 (2404:0:8516:9F92:5C42:2DFA:3926:ABC0). CC deleting admins @Fralambert, Ymblanter

Sakiko Miki: Q113989871 (Eien20), Q120549314 (2404:0:8516:9F92:5C42:2DFA:3926:ABC0). CC deleting admins @Fralambert, Ymblanter

Bovlb (talk) 01:20, 14 March 2025 (UTC)

This is helpful. I don’t have time to look at details now. What I see so far is Wikidata ignoring some important facts:

1. The Commons help desk is not a deletion forum.
2. The categories’ actual deletion requests on Commons were all closed as ‘kept’.
3. Data on Wikidata is displayed in a category infobox as if it was part of the category, so deleting it from Wikidata directly harms Commons. Wikidata should have an equivalent of c:COM:INUSE to mitigate that harm.

Brianjd (talk) 02:58, 14 March 2025 (UTC)

The wd-deleted results match the Commons Pi bot edits, giving a total of three Wikidata items (two deleted) for each subject.

On 10 November 2022, the first Wikidata item for Sakurako was deleted as not notable per Wikidata:Requests for deletions/Archive/2022/11/10#Q113989811. At the same time, the first Wikidata item for Sakiko was deleted as not notable without discussion. The discussion incorrectly claimed that the category was out of scope per c:Commons:Help desk/Archive/2022/10#Category:Sakurako_Miki; that is not a deletion forum. The first actual deletion request (c:Commons:Deletion requests/Files in Category:Sakurako Miki) was closed as ‘kept’ withdrawn after less than 9 hours (and there were no substantial comments between then and the request being closed as ‘kept’).

On 18 July 2023, the second Wikidata item for each of Sakurako and Sakiko was deleted as a recreation of a deleted item per discussion (the second and third last discussions at Wikidata:Requests for deletions/Archive/2023/07/17). Q120549314 had another deletion rationale: a reference to WD:LP. Both discussions had this comment: The uploader added all her picture since her birth on Commons. Probably have to warn them a deleted them all. This comment did not say what the problem was and ignored the earlier deletion request; it also falsely claimed that all the images were uploaded by the same user (as far as I can remember, they were uploaded by many different users). In a strange coincidence(?), a few hours later, both Commons categories had deletion requests created. Both of those requests were eventually closed as ‘kept’, yet the Wikidata items remained deleted. Brianjd (talk) 11:39, 15 March 2025 (UTC)

At least four different uploaders. And that’s just for the small subset of images I documented so far. Brianjd (talk) 11:52, 15 March 2025 (UTC)

Since the subject was minor, We have a WD:Living people policy. Having a category alone on Commons is not part of our WD:N policy alone (It could be if it have notable identifier or fullfil a structural need). Also, that item was recreated many time instead of simply ask the first deleter to undeleted a previous deleted item. Fralambert (talk) 12:21, 15 March 2025 (UTC)

I may also add that neither of these items have references so they are violating WD:LP. Fralambert (talk) 12:32, 15 March 2025 (UTC)

Having a category alone on Commons is not part of our WD:N policy alone Correct.

It could be if it have notable identifier It doesn’t.

fullfil a structural need Does it? It contains important information such as the birth date and the relationship between Sakurako and Sakiko, which is displayed in the category infobox and used to help sort the images on Commons. Is that enough?

Also, that item was recreated many time instead of simply ask the first deleter to undeleted a previous deleted item. How could a user even know that that there was a previous deleted item? That’s one of the main points of this discussion.

I may also add that neither of these items have references so they are violating WD:LP. @Nakonana: Can you comment? Brianjd (talk) 13:31, 15 March 2025 (UTC)

I'd say that the repeated recreation of the items by different people is an indicator that there's no consensus for deleting them.

I also agree that the Wikidata item helps with properly categorizing the images on Commons (e.g. in categories such "Girls by age"). As for the references, the birthdays of the girls are provided by the primary uploader on Flickr (i.e. the father of the girls) who documents the events in the photos and the age of the girls at the time the photos were taken. If I remember correctly, it was either the photos of the girls as babies, shortly after they were born, that contained the information regarding their birth dates, or there were some birthday celebration photos that contained the date of birth. It's possible that I had added the relevant reference files in hidden notes in the main category for each girl before I finally recreated the Wikidata item. So, looking through my edits in the category history might help finding the references. (I can't do that myself right now because I'm on mobile and going places.) As for creating new Wikidata items instead of asking for undeletion of the old ones, I didn't (and still don't) know where to go and how to make an undeletion request on Wikidata, that's why I chose the process that I know how it works. Nakonana (talk) 13:51, 15 March 2025 (UTC)

Then source the date of the birth with flickr files, because they have actually no source. Some people still aim these pictures for RfD, you know. Fralambert (talk) 14:04, 15 March 2025 (UTC)

Here are the relevant files with the birth dates:

• Commons:File:SAKURAKO (2931486610).jpg
• Commons:File:SAKIKO - Glad to see you!. (23789987453).jpg

Nakonana (talk) 14:16, 15 March 2025 (UTC)

I didn't (and still don't) know where to go and how to make an undeletion request on Wikidata: You might find Wikidata:Guide to requests for undeletion useful on this point. Bovlb (talk) 16:32, 15 March 2025 (UTC)

Thanks! Merging the deleted items with the new ones is probably not an option, is it? Can admins see whether the deleted items had any information that the current items don't have and that might be worth merging? Nakonana (talk) 17:11, 15 March 2025 (UTC)

I still want to highlight the original issue here: it is impossible to make sense of deleted items on Wikidata. I just happened to find Yoshihito Miki (Q120548822): Japanese photographer (Yoshihito Miki, Sakurako and Sakiko’s father), which was delinked from Q120549006 and Q120549314 after they were deleted. There is no ‘delinker log’ like there is on Commons. For what it is worth, Yoshihito is also unsourced and possibly non-notable. Brianjd (talk) 14:22, 15 March 2025 (UTC)

Yes, it's generally impossibly to fully reverse the deletion of an item when the item had incoming links. The links are automatically removed and I'm not aware of any log. In many cases, the existence of incoming links is evidence of notability, so we are cautious in deleting such items. In addition, those incoming links ought to be considered as part of any deletion review.

It would be nice if we could snapshot incoming links when items are deleted. Bovlb (talk) 16:38, 15 March 2025 (UTC)

Yoshihito Miki has primary sources such as his Facebook account as references. I'd also say it's worth keeping his Wikidata item because there are thousands of professional quality photos by him on Commons, documenting things such as Japanese festivals and customs which is clearly educationally valuable. If I remember correctly, some of his photos are also used on Wikipedia. Nakonana (talk) 17:23, 15 March 2025 (UTC)

Some properties do have references; I missed that earlier. Regarding notability, unfortunately, we have to work with Wikidata’s notability policy; as I pointed out at c:Template talk:Wikidata Infobox#Infoboxes for categories that are below Wikidata’s threshold of notability, Wikidata’s policy is generally stricter than Commons’ policy. I was hoping that someone more familiar with Wikidata would explain how that policy applies here.

Merge request

Hi all

I just created a Wikipedia article and then created a Wikidata item to go along with it, unfortunately a bot also created an item at the same time, could I ask someone merge them? Also the bot added names to multiple languages which looks like its wrong.

• Q133283498
• Q133283476

Thanks

John Cummings (talk) 13:11, 15 March 2025 (UTC)

Hello, the two items have been merged. Also see Help:Merge. M2k~dewiki (talk) 13:26, 15 March 2025 (UTC)

email address (P968)

Which statement to use for email address (P968) at Gmail (Q9334)? maintained by (P126) doesn't fit. Eurohunter (talk) 20:42, 13 March 2025 (UTC)

Why do we need to add a qualifier to say that when it's obvious from the email address itself? Midleading (talk) 15:28, 16 March 2025 (UTC)

Valid Google Play author ID not matching regex

The Google Play author ID (P12871) 11fnxrlx72 is marked with a regex error on Thane K. Pratt (Q70784628), even though the identifier resolves correctly. Any way to fix the regex so it doesn't come up with this false flag? BhamBoi (talk) 05:49, 16 March 2025 (UTC)

 Done The value has 10 characters, whereas the constraint allowed only 8. There were even more violations like this, hence I updated the regex. --Matěj Suchánek (talk) 08:28, 16 March 2025 (UTC)

Adding tempers to alloy data sets

I noticed something that needs to be brought up sooner rather than later if you want your datasets to be complete and well organized by engineering and material science standards.

Each alloy needs a subcategory of tempers. Tempers can have a significant influence on yield strength and tensile strength of a material, and NEEDS to be a subcategory before you start to enter those kinds of properties into the data set. (Or maybe something more general, like temper/manufacturing process, as some alloys are cold worked during the manufacturing process and that's technically different from temper.)

For instance, aluminum 6061 O temper has a yield strength of 55-65 MPa. Whereas aluminum 6061 T6 has a yield strength in the region of 276 MPa. This needs to be a habit for people adding alloys to your database.

I actually created a table of properties and tried uploading it to wikipedia some years ago. It seems there was a purge a few years ago taking down tables with "too many" data points. I understand that an encyclopedia should be general information, but rather than deleting it, they could have transferred it to your wikidata sets. Given I'm largely unfamiliar with your processes and practices here, I'm not sure how to convert my tables (that I had copies of because of their utility to myself). I would like to contribute that data, but citing my sources other than in a general sense will be problematic. Would the wikidata community like me to attempt it anyway? This is a smart idea to better organize bigger data sets rather than tables like I was doing on wikipedia, and there is potential for me to add many of the engineering properties tables from my textbooks if I can get some help navigating your system and making sure I add the data to the correct locations. Given I'm an engineer and more used to dealing with tables than databases, I would need some guidance on how you have things organized and where those tables ought to end up if I'm going to be adding useful data in the right place to contribute in any meaningful way (given the fairly strict standards of the wiki community).

This is a wikipedia table I was planning on adding to your database: User:Jlefevre76/isotropicmaterialproperties - Wikipedia Guidance from the wikidata community on how to go about that would be welcome. Jlefevre76 (talk) 16:49, 16 March 2025 (UTC)

I sort of put together a couple of examples of how we might go about it. Using 6061 as an alloy, for instance, and then use 6061 T-6 and 6061 O-temper as subcategories of the aluminum (or aluminium if you're from the UK) 6061 alloy. I think this might be a good template for how we should organize the different tempers/manufacturing processes as subcategories of each alloy.

FYI, it got a little messy, as spelling and data type makes it difficult to find properties pages like coefficient of thermal expansion and fracture toughness. I recreated both pages which incidentally were not in existence as property with quantity data types. I wish there were a better way of converting the existing pages into property of quantity data types. I made the requests and maybe they will use the existing page's data to create the appropriate, usable property page? Jlefevre76 (talk) 21:14, 16 March 2025 (UTC)

Confirmation Google Knowledge Graph ID

At the moment, confirmation (Q214802) has three Google Knowledge Graph ID (P2671) statements. When I click on the links, the latter two (https://www.google.com/search?kgmid=/g/11dykjs_n and https://www.google.com/search?kgmid=/g/120s1v6n) show me exactly the same Google results page, and for the first link (https://www.google.com/search?kgmid=/g/120x6cwp), the results seem to be the same, too. So I do not know which of these statements actually refers to which item (an item should only have one Google Knowledge Graph ID (P2671) statement, according to the constraint violation).

Could someone who is familiar with Google Knowledge Graph please move at least two of the three statements to other items? In particular, confirmation (Q133292863) (for confirmation in Protestant churches, confirmation (Q214802) is apparently supposed to be the specialization to Lutheran ones) is lacking any Google Knowledge Graph ID at the moment. --2A02:8108:5091:E900:41F3:3057:9966:B41F 17:53, 16 March 2025 (UTC)

(Only) a random subset of items about TV series has their episodes set in 'part of'

As far as I can see only some television series have their episodes set via has part(s) (P527) (example) but not many others (example). There doesn't seem to be any criteria or rule for when it's set vs when it's not and also I think it should either be reliably consistently always be set or never (in the latter case one could retrieve the episodes via What Links Here or sparql-querying part of the series (P179)).

Also I wonder whether it would be better to have a separate property that complements part of the series for series episodes in particular since has part(s) is used for all kinds of things.

There are also several complications like these:

• Many series have separate items for only a few episodes but not all
• Some series (and also podcasts (example)) have very many episodes so this would make the WD item very large/bloated and long to scroll through
  • this is made more a severe issue by that there still doesn't seem to be a keyboard shortcut for adding a statement where the button for it as at an always varying location near the bottom
  • long sections like that also can't be collapsed (by default)
  • nevertheless, as long as the item loads and there are no other technical issues, Wikidata items aren't really meant to be read by humans but just queried and/or used via other UIs such as infoboxes or listeria tables

Now, if episodes are to be set (are they?) and so via has part(s) (P527), then this is inferrable due to part of the series (P179) if that's set on the episodes so I think setting the episodes on the series item is much better done by a bot than time-intensively by editors. The publication date qualifier would also be set via the publication date set on the episode. (And most of that could be imported en masse from IMDb anyway but that's outside the scope of this discussion.)

I think it could be useful to have the episodes linked. It could make various queries easier and more performant (or enable them to be below constraints), enable users to find the Wikidata item they were looking for or related ones, and enables people to better spot which items are still missing.

What do you think about setting episodes on series that way?

This goes to a broader issue but is there a list of briefly summarized regular bot tasks where one can see (here via ctrl+f "series") whether the maintenance/data-populating task one has in mind is already (and still) being implemented?
Prototyperspective (talk) 17:48, 10 March 2025 (UTC)

part of the series (P179) is much preferable to has part(s) (P527). As to whether an episode of a series is notable, that's up to the superfans involved. Vicarage (talk) 17:59, 10 March 2025 (UTC)

As to whether an episode of a series is notable I didn't ask that and the part Many series have separate items for only a few episodes but not all is only about it in regards to the subject of linking them all in the has parts i.e. people seeing/querying these may think/draw from that these episodes are all the episodes of the series when they're not and they're not even consistently all episodes that have Wikidata items.

part of the series (P179) is much preferable to has part(s) (P527) Okay so are you saying it should only be set via part of the series? If so I think it should be applied widely and not sometimes that way, sometimes this way, sometimes both ways and that there should be a constraint violation if an TV series episode is set as value into has parts since most users don't know this. Prototyperspective (talk) 23:46, 10 March 2025 (UTC)

It's not really necessary to record single episodes on the TV series' item, the relevant information is already stored in the episode items. Listing the episodes on season or series items (or season items on the show's item) is usually done more as a helpful way to show users who maintain these kind of items that the episode items exist. Personally, I would maybe use has part(s) (P527) to list episodes on items of miniseries (even though miniseries should also get season items), or for special episodes that aired outside of a normal season structure. But never for episodes of a normal show. Querying the statements on the episode items is the intended way of getting that kind of information. --2A02:810B:581:C300:A8BD:9AFE:1E2F:8237 17:43, 17 March 2025 (UTC)

Assuming is usually done more as a helpful way to show users who maintain these kind of items is the case as you said, then isn't that useful so editors can for example see which episodes are missing? On the other hand, I think episodes like series should usually be imported from some series database instead of being created manually and therefore this wouldn't be that useful.

Maybe series items should get some button 'View episodes' that runs the query and shows the episodes in an embedded frame within the item with a click? Prototyperspective (talk) 18:40, 17 March 2025 (UTC)

Any way to query Wikipedia infobox templates to sync data with Wikidata?

Example: de:Hatu-Hou (Ort))

Example: de:Nächste Ausfahrt Glück – Katharinas Entscheidung)

So for example, I set the video for the full episode on Mr. Bean Rides Again (Q6928419) and there also is a Wikipedia article about this series episode, en:Mr. Bean Rides Again, with an infobox (this) at its top but it's not having the video in it (as en:Goodnight Mr. Bean has). It may also have several other parameters not set where that data is in Wikidata and likewise there could be data in the infobox template not yet in Wikidata but one could just focus on media for now.

This makes me wonder: is it possible to query Wikipedia articles' infobox templates so that one can see which articles with an infobox have some of the infobox parameters that are mapped to Wikidata properties not set for which the Wikidata item has a value set (e.g. a photo)?

Infoboxes on Commons pull all their data in all infoboxes from Wikidata. It's not like that on Wikipedias.

For media, I think the easier way would be what I suggested at Suggest media set in Wikidata items for their Wikipedia articles. This is especially the case if the item doesn't just have an article in one language Wikipedia article but in many language versions. Updating just one item would take very loong and would be difficult and there's thousands of such cases where some good-quality media is set on the Wikidata item but none is in the article. Nevertheless, that's not possible now and even if it was this could still be useful especially since infoboxes have all sorts of data, not just media. (Note that it's not just about setting new data but also about e.g. spotting inconsistencies,errors,vandalism.) Since most data in specified parameters is set in infoboxes in Wikipedia in structured format and Wikidata is meant to be the place for such structured data I thought maybe sth like it is actually possible somehow since that would make a contribution to either more beneficial. Prototyperspective (talk) 00:12, 11 March 2025 (UTC)

@Prototyperspective You can try https://pltools.toolforge.org/harvesttemplates/ for Wikipedia-to-Wikidata sync but you should be very careful about transferring data this way and pay attention to correct modelling. Moreover such transferred data would not be referenced. For the other direction, you'll probably have to do some sort of monitoring via categories etc. Vojtěch Dostál (talk) 14:59, 11 March 2025 (UTC)

Great, that's interesting, thanks! So if this direction is already implemented, that could maybe be used for the other direction.

Something I should add regarding using this method to set media in Wikipedia articles, the method described here is probably not the best way to set these as they may sometimes be better placed somewhere in the article and it would only scan the infobox but not whether/which media is set in the article. On the other hand, it also makes sense to set some representative image in the infobox (for some cases that may rather mean moving a media file somewhere in the article into the infobox). It would also have to check whether the media file is used elsewhere in the article. However, if not there could still be a very similar one or the extra file be too much/redundant.

Then regarding other data, maybe it's relatively uncommon that Wikidata items contain some data that the Wikipedia articles don't contain but since there is such a large number there's probably lots of data that could be added to there and it would be a major use-case of Wikidata. Not many Wikipedians go on Wikidata to see whether it has some data or some new data since they last checked that they could add into the infobox. I think many Wikipedias have infoboxes that use data from Wikidata. Maybe somebody clarify all this a bit. For example, why not have the infobox display data from Wikidata (maybe imported by a bot from there) if nothing is entered for parameters? I think something is not unlikely already being done but I don't know what there is, maybe it's in some Wikipedia tools page. Prototyperspective (talk) 01:39, 12 March 2025 (UTC)

Hello, on the one hand there are PetScan/QuickStatements/HarvestTemplates etc. to enhance wikidata items, for example:

• User:M2k~dewiki/Tools/Enrich Objects

On the other hand, there ist the

• d:Help:Infobox export gadget
• de:Benutzer:M2k~dewiki/FAQ#Infobox-Export

(also see screenshots), where infos can be exported by double clicking on the red (=missing) information in the infobox / wikidata item. M2k~dewiki (talk) 20:40, 12 March 2025 (UTC)

Interesting, thanks!

However, that also seems to be only about Wikipedia->Wikidata export but not the other way around. Since you wrote on the other hand I thought the screenshots were showing how to import data from Wikidata into the Wikipedia infobox where one would click the red template parameter cell to add the suggested value until the edit is finished and then published by the user (I think better than that would be a way to view articles in quick succession where the data from Wikidata is suggested to be edited or that a bot does this automatically).

Is there a info page on Wikidata somewhere about everything relating to Wikipedia templates? It's how Wikipedia records structured data alongside article categories so I think both of these should be used to write Wikidata and be written using Wikidata data (both should be more or less in sync). Prototyperspective (talk) 19:38, 14 March 2025 (UTC)

For the German language wikipedia there is

• de:Benutzer:M2k~dewiki/FAQ#Wie_verwende_ich_in_Vorlagen_und_Infoboxen_Werte_aus_Wikidata?
• de:Hilfe:Wikidata/Daten aus Wikidata beziehen
• de:Wikipedia:Lua/Modul/Wikidata

M2k~dewiki (talk) 19:44, 14 March 2025 (UTC)

Okay thanks. So it looks like there is not yet an overview page in Wikidata. For other editors coming to this thread: what is still missing is info on how to sync Wikidata->Wikipedia (or a way to do so if it's not possible). For example to query a few hundred items and then for all the attached Wikipedia articles across languages that have a certain infobox, add certain data from Wikidata (such as the name of the film director or the infobox image is none is set). Prototyperspective (talk) 19:53, 14 March 2025 (UTC)

Also see for example:

• d:Q11985372 - en:Category:Templates using data from Wikidata
• d:Q19359694 - en:Template:Uses Wikidata
• d:Q20161412 - en:Category:Modules using data from Wikidata

M2k~dewiki (talk) 20:11, 14 March 2025 (UTC)

Thanks again, if nobody else does so, I'll likely compile some meta page about data in templates like infoboxes. Nevertheless, the pages you linked are if I understood correctly only about templates that load data from Wikidata but those are not about writing normal/any templates using data in Wikidata. This is what I'm most interested when it comes to templates.

Furthermore, I also could not find a page that lists specifications of what can be imported from templates like the IMDb link via the IMDb title template. Seems like people just guess what other users are or aren't importing and then run some import once or so but never again thereafter. If a user regularly runs imports from a hundred different templates and then stops editing, nobody would continue these imports. Prototyperspective (talk) 17:59, 17 March 2025 (UTC)

Wikidata:How to use data on Wikimedia projects and Wikidata:Infobox Tutorial could be of interest, too, and another entry into the rabbit hole. --Matěj Suchánek (talk) 18:46, 17 March 2025 (UTC)

For example, why not have the infobox display data from Wikidata (maybe imported by a bot from there) if nothing is entered for parameters? Some wikis do this, some do not. The reasons why not include lack of know-how, quality concerns or simply fear of having to learn to edit in another way. English Wikipedia has already held several RfC's on this, these should give you the idea. --Matěj Suchánek (talk) 17:10, 14 March 2025 (UTC)

There are Wikipedia languages that will extensively use Wikidata Infobox in templates to load, but they tend to be the sparser and less developed Wikipedias that rely more on automated article creation and machine translation.

The one exception being Wikimedia Commons that uses the commons:Template:Wikidata Infobox on a huge number of categories. That template does a huge number of things like add interwiki links. However it is also very complicated and a bunch of modules (programmed in Lua I think). So complicated and heavily used that editing of the template and modules are limited to a small number of users.

On English Wikipedia I think the most commonly used template box that uses Wikidata is en:Template:Authority control. William Graham (talk) 20:29, 14 March 2025 (UTC)

It's possible for Wikipedia templates to import data from Wikidata. The Commons template do that. For other Wiki's, each Wiki has their own policies. Given that the rules (and also module) in every Wiki are a bit different it's unclear to me what a Wikidata page about it would help. ChristianKl ❪✉❫ 18:46, 15 March 2025 (UTC)

Comment: Another good resource for anyone interested in the use of Wikidata in enwiki infoboxes can be found here: w:Category:Articles with infoboxes completely from Wikidata. Some of the articles result in better outcomes than others, and there are examples using many different types of Wikidata generated infoboxes. -- Cl3phact0 (talk) 10:55, 17 March 2025 (UTC)

Can anyone help me how to fix this constraint error?

Q115789820#P275 Trade (talk) 14:47, 15 March 2025 (UTC)

Licenses can only be granted for copyrighted works, so copyright license (P275) isn't applicable here. ineligible for copyright protection (Q61005058) is not a license, it's an explanation/justification why we/our source thinks the work isn't copyrighted. If the work is indeed public domain (which I'm not entirely sure of after reading the linked sources), ineligible for copyright protection (Q61005058) should be added to the copyright status (P6216) statement as a value of a determination method or standard (P459)qualifier. --2A02:810B:581:C300:A073:896:3280:2EE 23:42, 15 March 2025 (UTC)

So what value should i replace it with? Trade (talk) 03:31, 16 March 2025 (UTC)

IMHO, none. If a work wasn't explicitly released under a specific license, copyright license (P275) isn't needed. copyright status (P6216) is enough to record its public domain status. --2A02:810B:581:C300:A8BD:9AFE:1E2F:8237 17:27, 17 March 2025 (UTC)

polyL

I just simplified the English description on polyL (Q7226108), which was overly detailed. The Slovenian description also appears to be very verbose, but I don't speak Slovenian, so I don't know how to simplify it. Any Slovenian speakers here? TTWIDEE (talk) 21:08, 15 March 2025 (UTC)

Perhaps you can find Slovenian speakers at Wikidata:Project chat/sl. Also ping @TadejM. --Matěj Suchánek (talk) 10:30, 17 March 2025 (UTC)

Wikidata weekly summary #671

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

Discussions

• New request for comments: Time to deprecate P642 - of (P642) has spent 3 years marked asdeprecated. Is it time to finally mark it as an obsolete Wikidata property(Q18644427)?

Events

• Upcoming events:
  • Call for Wikimania 2025 Programme reviewers. Apply until Monday 17 March 12:00 UTC
  • Wikidata Affinity Group Update: The fourth session of Starting a Wikidata Project, originally set for March 18, will now be an asynchronous Slack discussion in the #wikidata channel of the LD4 Slack Space. Join us at 9am PT / 16:00 UTC to discuss Reporting Your Outcomes and Results. Join Slack here. Note: April programming will pause as we prepare the next series.

Press, articles, blog posts, videos

• Blogs
  • Training for the staff of the Museum of Photography in Krakow on Wikimedia Commons and Wikidata - "The training aimed to enable the MuFo staff to effectively navigate and develop skills in editing and managing the museum's digital resources within the Wikimedia projects."
  • (German) Wikipedia Unterwegs - this time in Neu-Ulm: This travelling community meetup for German Wikimedians discusses the growing ecosystem of Wikipedia, Wikidata and Commons.
  • REST in Rust by Magnus: "A new Rust crate has been developed to simplify access to the Wikibase REST API, featuring industry-level coding standards, 248 unit tests, >97% code coverage, and high maintainability. Check out the GitHub repo and contribute via the issue tracker or pull requests!"
• Videos
  • Useful videos that explain how to set up/make use of Wikibases. Put together by Valerie
  • Wikidata and Wikibase - Curriculum Transformation in the Digital Humanities
  • (Chinese) Open Data Day Taiwan 2025: more details and program agenda on the Wikimedia Taiwan Meta Event page
  • Wikidata as an Open Data Resource: Ian Watt at Open Source SG
  • Bridging GLAM and Wiki: The Khalili Perspective: Dr. Martin Poulter, WiR at Khalili Foundation.

Tool of the week

• Research Expeditions on Wikidata with itineraries - Visualization tool for research expeditions itineraries and natural history collections.

Other Noteworthy Stuff

• An update regarding the WDQS backend has been published, about the adoption of the new endpoints and the next steps that will take place.
• Call for Projects – Wiki Mentor Africa Hackathon 2025. Do you have a technical project that needs contributions? Or a testing initiative that could use more hands? Submit a project BY 21st March 2025.
• The Wikidata Vector Database prototype is almost ready! Developers interested in integrating semantic search into their applications and editors looking to explore Wikidata items using natural language search are invited to reach out for more details: philippe.saadewikimedia.de
• Join the Wikimedia Deutschland software development team: Product Manager Wikibase Suite (all genders)

Newest properties and property proposals to review

• Newest General datatypes:
  • OAI formatter (formatter to generate ID compatible with Open Archives Initiative Protocol for Metadata Harvesting services)
  • AI-generation prompt (exact prompt that was used to generate this AI-generated media or work)
  • data analysis method (methods used in the main item for inspecting, cleansing, transforming, and modeling data with the goal of discovering useful information)
• Newest External identifiers: Wikishire article ID, HelloAsso organization ID, Dictionnaire de la déportation gardoise person ID, Graceful17 entity ID, ‎Game Input Database ID, DRTV ID, Calindex person ID, Historia Hispánica ID, ‎TERMDAT ID, Kulturdatenbank ID, DDLC entry ID, Chinese Basketball Association player ID, ‎Captain Coaster coaster ID, Memoria Chilena ID, Jamendo track ID, MikuWiki article ID, ‎ZOOM Platform product ID, Clio-online researcher ID, Clio-online organization ID, ‎SteamDB tech ID, ‎Big Fish Games game ID, Clio-online web resource ID, Iowa State University Library Vocabularies ID, Newsweek topic ID, booru tag
• New General datatypes property proposals to review:
  • watercraft prefix (prefix applied to watercraft operated by different organisations)
  • accused (person or organization who has been accused of carrying out this harmful, illegal, or immoral act without having received a criminal conviction or where the accused have been acquitted in a court of law)
  • applies to volume (volume of the item (usually edition of a work) to which the claim applies)
  • oxygen endurance (The maximum time a submarine, spacecraft or enclosed vehicle can sustain life using its onboard oxygen supply.)
  • Coefficient of thermal expansion ()
  • fracture toughness ()
• New External identifier property proposals to review: Danskefilmstemmer.dk work ID, Danskefilmstemmer.dk character ID, Internet-Portal „Westfälische Geschichte“ person ID, Kosovo NGO registration number, Yale LUX ID, geraldika.ru symbol ID, Swimcloud swimmer ID, CACI company ID, VD 16 ID, World Higher Education Database ID, Qur'an Wiki article ID, JSIC code, Macrotransactions game ID, Landtag Tirol person ID, NexusMods mod ID, Thunderstore game ID, SideQuest app ID, IndExs Exsiccata ID, National Academy of Engineering member ID, DGO ID, The Rural Settlement of Roman Britain ID, Audiovisual Identity Database page, Encyclopaedia of Islam (Arabic edition) ID, Rodovid family ID, Cultural Heritage Azerbaijan ID, Zurich Kantonsrat and Regierungsrat member ID

You can comment on all open property proposals!

Did you know?

• Query examples:
  • Location of fire stations in Spain (source)
  • Oldest known individual per taxon (pre-20th century) (source)
• Newest WikiProjects: AncientMaths
• WikiProject Highlights: New country page for Poland in WikiProject Nonprofit Organizations, and on cividata.org. Help expanding it!
• Newest database reports: German lexemes without forms divided by lexical category (source)
• Showcase Items: Perm (Q915) - city in Russia
• Showcase Lexemes: Knoten (L298686) - German noun that can mean "knot", "fundamental unit of which graphs (in graph theory) are formed", "point where an orbit crosses a plane of reference to which it is inclined", or "hair wrapped in a circular coil around itself (bun)."

Development

• Wikibase REST API: We continued the work on adding search to the API (phab:T383126)
• Search: We are continuing the work on making it easier to search for entities other than Items in the search box (phab:T338483)
• Query Service: We set up the constraint checks to use the split graph instead of the full graph (phab:T374021)
• Integration in the other Wikimedia projects: We are looking into how changes from Wikidata are represented on the other Wikimedia projects and how that can be improved (phab:T386200)

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.
• 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!

· Read the full report · Previous issue · Unsubscribe · Mohammed Abdulai (WMDE) talk · MediaWiki message delivery (talk) 16:54, 17 March 2025 (UTC)

Vector-2022

Oh I see that the transition from Vector to Vector-2022 has just happened. I'd like to welcome dark mode when it will come also in items. -- ZandDev (talk) 20:46, 17 March 2025 (UTC)

@ZandDev: I'm sorry, could you clarify what you mean?StarTrekker (talk) 20:52, 17 March 2025 (UTC)

@StarTrekker: phab:T387154 got deployed. -- ZandDev (talk) 21:11, 17 March 2025 (UTC)

I have dark mode enabled, but items show up in the usual (white) mode. Ymblanter (talk) 21:00, 17 March 2025 (UTC)

@Ymblanter: Yes, it is temporarily disabled because it is actually buggy with Wikibase, see phab:T369385. But I hope that in short time dark mode will land also in items. -- ZandDev (talk) 21:16, 17 March 2025 (UTC)

Wikidata:Requests for permissions/Bot/Leaderbot

Hello, in order to move this request forward, I invite you to participate in the discussion there. Thank you! Kind regards, Wüstenspringmaus _talk 07:53, 18 March 2025 (UTC)

Q65285047

There is a sitelink, hi:मेरा घर, but the page is one line of text with no references or links and Google translation doesn't look like the subject can be identified, if there is a subject. There is a link to the page from hi:त्रिलोचन शास्त्री, which is Trilochan Shastri (Q2453338); is that relevant and hi:मेरा घर just lacks context, or is the link just a coincidence and the page should be deleted? Peter James (talk) 14:03, 18 March 2025 (UTC)

Please, update image

Please update image in Q121182 to https://commons.wikimedia.org/wiki/File:%D0%98%D0%BD%D1%84%D0%BE%D1%80%D0%BC%D0%B0%D1%86%D0%B8%D0%BE%D0%BD%D0%BD%D0%B0%D1%8F_%D1%81%D0%B8%D1%81%D1%82%D0%B5%D0%BC%D0%B0_(RU).png. Werwerton2525 (talk) 12:35, 20 March 2025 (UTC)

 Done — Martin (MSGJ · talk) 13:33, 20 March 2025 (UTC)

This section was archived on a request by: Samoasambia ✎ 14:54, 24 March 2025 (UTC)

Andrew Abbott enWP sitelinks swapped

I struggle with mutally wrongly assigned sitelinks for the items Andrew Abbott (Q4756169) (a sociologists) and Andrew Abbott (Q118697126) (a baseball player): At least in English (and potentially downsteam in other languages) the sociologist’s sitelink links the the baseball player’s en:WP page and the baseball player’s item to the sociologist’s page. Changing one will yield an error, since the other still points to it. I don’t know how to change this cleanly. The change already led to images of one appearing on the article of the other and the like. -- Simulo (talk) 17:22, 21 March 2025 (UTC)

 Done The trick is to (in this order) remove either link, put it in the other item and add the replaced link to the former one. --Matěj Suchánek (talk) 08:36, 22 March 2025 (UTC)

This section was archived on a request by: Samoasambia ✎ 15:14, 24 March 2025 (UTC)

Remove

I would like to remove this item.[7] It was already present but was left blank. Mhorg (talk) 14:12, 23 March 2025 (UTC)

 Done Merged with Slavoljub Slava Ković (Q31183976). Dogfennydd (talk) 20:31, 23 March 2025 (UTC)

This section was archived on a request by: Samoasambia ✎ 14:54, 24 March 2025 (UTC)

Defect presentation The Beach at Sainte-Adresse (Q3966658)

references etc are shown vertically ans are unreadable, useless and one cannot edit, this happens with all datasets. What has happened?? Oursana (talk) 14:48, 18 March 2025 (UTC)

I believe this is related to #Vector 2022 will be the default skin and Wikidata:Report a technical problem#new layout .... --Matěj Suchánek (talk) 07:21, 19 March 2025 (UTC)

Thank you, that is exactly my problem and I do see why they cannot solve it--Oursana (talk) 10:30, 19 March 2025 (UTC)

Repurposed items (Thai pop culture)

Matchabake (talk • contribs • logs) and 202.138.251.49 (talk • contribs • logs) have repurposed a lot of items. I might use some help with cleaning up the mess. --Matěj Suchánek (talk) 11:56, 19 March 2025 (UTC)

Can you give some examples? I suggest you contact this user and explain the problems with their edits — Martin (MSGJ · talk) 12:48, 19 March 2025 (UTC)

[8][9][10][11][12] to start with. --Matěj Suchánek (talk) 14:41, 19 March 2025 (UTC)

sameAs

I've just noticed that schema.org's official definition of sameAs says:

URL of a reference Web page that unambiguously indicates the item's identity. E.g. the URL of the item's Wikipedia page, Wikidata entry, or official website.

-- Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:12, 15 March 2025 (UTC)

Yes. And? Any issues on that definition or just joyful to see that? :-) For historical context, the Schema.org mailing list has the thread that gives credence to Wikidata from Schema.org's perspective https://lists.w3.org/Archives/Public/public-schemaorg/2017Apr/0008.html (note: we never did start separate enumeration lists in Schema.org as proposed in the thread by Denny and Guha, we just decided to point to Wikidata and asked others to do the same.) Dan's last paragraph summed it all up for us eventually https://lists.w3.org/Archives/Public/public-schemaorg/2017Apr/0012.html

"Wikidata is by far the most obvious default/mainstream option here so +1 from me, though we should make clear that e.g. highly technical scientific data might prefer to sameAs to more controlled repositories. But even there, Wikidata is winning over a lot of converts... - Dan"

Indeed we were right, and Wikidata has won over many.

-- Thadguidry (talk) 08:11, 20 March 2025 (UTC)

Not a good description

data type (Q190087) currently has the description "Wikidata metaclass of data, including classification type of data in computer science". When used on other wikis, the subheading shouldn't refer to Wikidata. TagUser (talk) 06:27, 20 March 2025 (UTC)

Looks like @Zhenqinli did that edit. What was the purpose? Ainali (talk) 09:13, 20 March 2025 (UTC)

Reverted. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:55, 20 March 2025 (UTC)

Open Civic Idenitifiers

I am looking to use the Open Civic Data Open Civic Data Identifiers (OCD-IDs) to uniquely identify political geographies, positions, and people. It's a standard that is used in Open Civic Data projects to organize information and compare civic information across different jurisdictions and over time. https://open-civic-data.readthedocs.io/en/latest/ocdids.html This is an example of a quickstatement I'd use for a person.

CREATE LAST|Len|"Sean Wiggins" LAST|P31|Q5 LAST|P39|Q13425721 LAST|P131|Q2207319 LAST|P580|+2025-01-06T00:00:00Z/11 LAST|P2888|"ocd-person/3df2cf28-ec3a-418d-8e9d-4e187aa45e36" Rkendel (talk) 15:04, 19 March 2025 (UTC)

@Rkendel: In that case, you need to make a Property proposal for that identifier. exact match (P2888) takes a full URL as the identifier, not the ID (or slug) itself. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:54, 20 March 2025 (UTC)

@Rkendel: For administrative and political divisions (Open Civic Data Division Identifier (Q99650527)), there is the property Open Civic Data Division ID (P8651). -- Dcflyer (talk) 21:33, 20 March 2025 (UTC)

How many properties do we aspire to have

We currently have about 13500 properties on WD. I've seen a lot of external ID property proposals recently that are pretty specific, like Wikidata:Property_proposal/Christchurch_City_Council_Park_ID, which had a few hundred items, many not notable in WD. If replicated for every local authority worldwide, we could have thousands of local council database properties, and so I persuaded they proposer that described by source (P1343) might work better for them, and they withdrew the proposal. Or Wikidata:Property_proposal/Congressional_Medal_of_Honor_Society_recipient_ID, which has 3500 entries, and I'd expect most to be notable, but again is narrow coverage of one medal from one country, and I'd expect there are many, many websites with similar specialist databases.

Do we want to increase the WD property count perhaps 10fold to cover all these databases, and are queries that cover multiple properties (say local council details of all parks in the UK, so perhaps eventually 200) easy to write and run. I have queries that select "properties related to the military", but they were clumsy to write, and "?item {property list} ?result" queries seem slow to run, and can break Blazegraph.

I don't like to rain on proposers parades, but can WD scale with their ambitions, and is cherry-picking individual sites OK rather than adding all sites in a class as a property suite. Vicarage (talk) 00:02, 19 March 2025 (UTC)

Perhaps there should be a lower limit for the number of expected uses of a property? — Martin (MSGJ · talk) 12:50, 19 March 2025 (UTC)

Yes, there should be at least 100 expected usages for a new external identifier. Midleading (talk) 06:09, 20 March 2025 (UTC)

It's good to have a figure as a guideline (if anything, 100 is too low), but we should also allow exceptions where it is useful to us. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:50, 20 March 2025 (UTC)

Honestly it'd be a lot easier if we could have a generalised "External ID" property, with "Christchurch City Council Park ID" as the value, and then the id itself as a qualifier. Thus we wouldn't need properties per site. ElDubs (talk) 01:56, 21 March 2025 (UTC)

I think described by source (P1343) does that well. Vicarage (talk) 17:58, 21 March 2025 (UTC)

To answer the question in the heading, we don't have a target, nor really a limit either. But I think it is realistic to think that we keep on adding properties in the same tempo as we do now for the foreseeable future. Ainali (talk) 18:26, 21 March 2025 (UTC)

Could you please help me merge Q133539143 & Q131830184?

I created Q133539143 and filled it out and then discovered that there already is a Wikidata for Lidl Lithuania (supermarket chain) with ID Q131830184.

The newly created one (Q133539143) has more data than the old one, so both are valuable, but there shouldn't be a duplicate. The newly created one also has correct links to parent organization, which the old one does not.

I have been searching for a way to merge (https://www.wikidata.org/wiki/Help:Merge) but can't figure it out. The user interface that I see does not look like the one on Help:Merge. Could you please help me merge? 2A00:801:704:1ADD:6DFF:83B7:76C0:121D 13:39, 26 March 2025 (UTC)

 Merged by Jklamo. We had a change in how the user interface looks a few days ago and pictures are from the old one. I think you need to have an user account to use the MergeWizard. Samoasambia ✎ 15:54, 26 March 2025 (UTC)

This section was archived on a request by: Samoasambia ✎ 15:27, 28 March 2025 (UTC)

Impossible to merge Q8444008 and Q133571542

Hello, I created the Categorie:Relations entre le Fatah et le Hamas in French, and I wanted to link it to the 11 interlanguages (Q8444008), but I didn't succeed. JMGuyon (talk) 20:06, 27 March 2025 (UTC)

 Done Ayack (talk) 13:24, 28 March 2025 (UTC)

This section was archived on a request by: Samoasambia ✎ 15:27, 28 March 2025 (UTC)

How to see which items are subclasses of a given item?

Am I right that the best, most-accessible way to quickly see which items are subclasses or instances of a given item is by:

1. Installing this non-default gadget Classification.js
2. On the item's page clicking on "Embedded tree of the classes of this instance" to see a graph about the item
3. At the bottom of that visualization clicking the toggle button "Outgoing" (Show outgoing links)
4. Clicking on the bubble for the item (the one that is named like the item) so it shows the blue bubbles about how other items link to it
5. Clicking on the blue "subclass of" and/or "instance of" bubble so it shows all the items that are subclasses of the item (which can then be opened in a new tab by double-clicking it)

If that is the best or most-used way to see the items I think that's a bit cumbersome so it may be good to do any of these things:

• making this easier so it only needs one click in the item to see a list of these items after installing this/a gadget
• having that gadget enabled by default (default gadget)
• enabling other fairly self-explanatory methods to easily see items that are instances/subclasses of an item
• adding the info on those 5 steps above to some page people looking for this can easily find or are made aware of

In Wikipedia and Commons one simply scrolls to the bottom of an article to see the categories, then clicks on the one(s) that one would like to see more instances and subclasses of. On the category page, the other articles (or files on Commons) are listed and subclasses (subcategories) can also be simply clicked to be navigated to (fairly self-explanatory). This is much easier and more accessible than on Wikidata and partly why I'm asking. Prototyperspective (talk) 20:18, 22 March 2025 (UTC)

There also is this method:

1. Copy the Wikidata item QID
2. Enter haswbstatement:P31=Q... (paste the QID)

It may be easier than the above method but it's not accessible from the item. Would be good to make it more accessible such as via having a button for that in the item (there could be a few common queries for the item, maybe even tailored to the type of item so an item about a TV series would have a button to see items that are episodes of the series). Prototyperspective (talk) 16:57, 23 March 2025 (UTC)

Is there any way to sort items by qid in Special:AllPages?

I've been wondering about this for a while. 46.10.16.130 16:34, 17 March 2025 (UTC)

Unfortunately there does not seem to be such feature. Samoasambia ✎ 14:56, 24 March 2025 (UTC)

Tools without active maintainers

Are there any popular tools on toolforge that are missing a maintainer? I don't do bots, but I could definitely adopt or usurp a tool that is in active use. Anything that does not write to Wikidata's main namespaces basically. And since I'm lazy nothing with a large source-code please. Infrastruktur (talk) 21:56, 21 March 2025 (UTC)

I think there is info on tool use like the WhatLinksHere feature for scripts to see how many have it installed. I don't know which tools you in/exclude here, is it just tools hosted on toolforge or also scripts/gadgets? I think WikiFlix and Listeria would be relatively high-priority ones. There certainly are many tools in need of continued development and many that would be good to develop (example). Prototyperspective (talk) 13:14, 24 March 2025 (UTC)

It was Toolforge tools I had in mind. I recently moved a tool to produce statistics over missing language labels to Toolforge to have it run regularly, but since I never heard anyone actually use it, I didn't bother to have it write reports to Wikidata or set up some properly cached and translated webpages. I figure more widely useful tools are probably already written, so it would make more sense to adopt an abandoned one than to write something niche that sees little use.

Thanks for tips and the link to Community wishlist. I'll definitely have a look for ideas there. Infrastruktur (talk) 19:35, 24 March 2025 (UTC)

I can't find any statistics on tool usage. Maybe I should instead ask if there have been tools that was in frequent use but has been deactivated because of lack of maintenance? Infrastruktur (talk)

Missing icons (logo property)

Many items that have an icon in logo image (P154) do not have an image set in icon (P2910).

That's an issue because sometimes logos are icons (like app icons on a phone) and sometimes they are wide banner-like logos as for example with Q19718090#P154 and Q50938515#P154. If one would then query icon, and if no icon set: logo that would result in mixed data of both these small more or less rectangular icons and other types of logos. When using that in a table column for example it would make the column much wider and having varying images in the column.

So I think it would be best if an icon was consistently in icon (P2910) without having to query logo image (P154). To understand what I mean, take a look at Wikidata:List of free software accounts on Bluesky which has a nice-looking icon for nearly all entries and compare it with Wikidata:List of free software accounts on Mastodon where the icon is missing for most items.

Is there a straightforward way to find all items missing an icon where an icon is set in logo? Would it be better to copy it to the icon property or to move it to it? Lastly there also is a prop small logo or icon (P8972) but if that's to be used, shouldn't SVG files in icon be copied to it in addition assuming again this property is useful and should be set since they can always be used as small icon or not? Prototyperspective (talk) 00:36, 25 March 2025 (UTC)

icon (P2910) has clearly a different scope: "pictogram suitable to represent the item. For logos of a subject, use "logo image" (P154)". Obviously, logos should be stated using logo image (P154). --Dorades (talk) 10:58, 25 March 2025 (UTC)

Please first see the examples. They overlap. Prototyperspective (talk) 12:38, 25 March 2025 (UTC)

Do you mean the examples given in Wikidata property example (P1855)? I don't see any overlapping there. --Dorades (talk) 13:04, 25 March 2025 (UTC)

No. Prototyperspective (talk) 13:24, 25 March 2025 (UTC)

Wikidata weekly summary #672 (correct version!)

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

Discussions

• New requests for permissions/Bot:Request for admin flag for MsynBot - From 2021 through 2024, this bot has implemented the 2019 RfC “semi-protection to prevent vandalism on most used Items” by maintaining page protections based on the outcome, d:Wikidata:Protection policy#Highly used items. The admin flag got lost due to bot inactivity but the bot operation could be resumed immediately if the admin flag is given back.

Events

• Upcoming events:
  • AAFRennes2025, 26-28 Mars 2025
  • 5-6 April & 12 April: Scholia Hackathon
  • Wikidata and Sister Projects to take place May 29 - June 1. Please send us your session ideas, we still have lots of space for proposals. This is a great chance to highlight the benefits of Wikidata use in other WM projects. See Talk page for proposals.

Press, articles, blog posts, videos

• Blogs
  • Enhance Your Wikibase With Extensions
  • Editing Lexemes with your little finger
  • Wikidata and the sum of all video games − 2024 edition by Jean-Fred
• Thread: Who wins in a Wikipedia race between GPT-4.5, o1, Claude 3.7 Sonnet, and @OpenAI's new Computer-Using Agent?

Tool of the week

• Lexica - a mobile-friendly tool that simplifies micro contributions to lexicographical data on Wikidata, making various editing tasks accessible and intuitive for contributors of all experience levels.

Other Noteworthy Stuff

• Mobile Editing of Statements - You have been asking for the ability to edit statements from mobile devices for years, this project will make editing statements on Wikidata Items more accessible and user-friendly for mobile users. Sign up to participate in prototype testing and interviews with our UX team
• Join the Wikimedia Deutschland software development team: Product Manager Wikibase Suite (all genders)

Newest properties and property proposals to review

• Newest properties:
  • General datatypes:
    • data analysis method (methods used in the main item for inspecting, cleansing, transforming, and modeling data with the goal of discovering useful information)
  • External identifiers: booru tag, Steam Group numeric ID, Kompass company ID, ‎Macrotransactions game ID, Thunderstore game ID, ‎JSR package ID, ‎GitLab topic ID, Amazon Music track ID, Crunchyroll artist ID, SideQuest app ID
• New property proposals to review:
  • General datatypes:
    • levels (levels, maps, episodes, chapters or stages of this video game)
    • Scilit scholar ID (author identifier on {{Q|77125337}})
    • وزن صرفي عربي (A feature to adjust the pattern of Arabic words in lexemes)
    • باب صرفي للأفعال العربية الثلاثية المجردة (Morphology of the Arabic triliteral verbs)
    • land degradation (The amount of land that is degraded by an object. Mainly for infrastructure projects)
    • Research projects that contributed to this data set (This property allows to identify research projects that they have contributed to or created an item)
    • Platform height (platform height above the top of the rail (or above the road for buses))
    • extended by (addons for this item) (Class of software this software is extended by)
  • External identifiers: Congressional Medal of Honor Society recipient ID, Delfi.ee theme ID, identifiant Dezède d'un individu, SeqCode Registry ID, Openalfa street ID, The Oxford Dictionary of Music entry ID, A Dictionary of Education entry ID, TDKIV wikibase ID

You can comment on all open property proposals!

Did you know?

• Query examples:
  • 2024 Population Census in Uganda (source)
• WikiProject Highlights:
  • Musée d'art contemporain de Montréal/Liste des artistes de la collection
• Showcase Items: Cinderella (Q15046091) - 2015 film directed by Kenneth Branagh
• Showcase Lexemes: страсть (L166968) - Russian noun that can mean "love", "passion", "desire", or "suffering."

Development

• Wikibase REST API: We finished work on the simple Item search (phab:T383126) and started on the one for Properties (phab:T386377)
• Vector 2022 skin: We fixed a number of the remaining issues with dark mode (phab:T385039) and sitelink positioning (phab:T316797)
• Search: We continued the work on making it easier to search in other entity types (Properties, Lexemes, EntitySchemas) besides Items (phab:T321543)

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:
• 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!

Anything to add? Please share! :)

· Previous issue · Danny Benjafield (WMDE) talk ·

Vector 2022 will be the default skin

A two-minute video about Vector 2022

Something like this, but for Wikidata :D

Hello. We are the Wikimedia Foundation Web team. We are here to announce that the Vector 2022 skin will become the default desktop skin here on 17 March. We will gladly answer your questions, concerns, or additional thoughts! We will also help you adjust things which Vector 2022 may not be compatible with. Check out our FAQ – you will find many useful answers there.

If you are using Vector legacy skin, you may find yourself receiving the Vector 2022 skin. You may select Vector legacy as your global preference to avoid seeing the change. Logged-in users can at any time switch to any other available skins, or stay with Vector 2022 and enjoy choosing between its light and dark mode. Users of other skins will not see any changes.

Why are we changing the skin now

For technical reasons (listed below), we need to deploy the skin soon. After deployment, we will continue discussing issues and questions about the interface, and we'll be ready to work with you on various issues like gadget compatibility.

More details on why we need to deploy the skin now

• Due to releases of new features only available in the Vector 2022 skin, our technical ability to support both skins as the default is coming to an end. Keeping more than one skin as the default across different wikis indefinitely is impossible. This is about the architecture of our skins. As the Foundation or the movement in general, we don't have the capability to develop and maintain software working with different skins as default. This means that the longer we keep multiple skins as the default, the higher the likelihood of bugs, regressions, and other things breaking that we do not have the resources to support or fix.  
• Vector 2022 has been the default on almost all wikis for more than a year. In this time, the skin was proven to provide improvements to readers while also evolving. After we built and deployed on most wikis, we added new features, such as the Appearance menu with the dark mode functionality. We will keep working on this skin, and deployment doesn't mean that existing issues will not be addressed. For example, as part of our work on the Accessibility for Reading project, we built out dark mode, changed the width of the main page back to full (T357706), and solved issues of wide tables overlapping the right-column menus (T330527).
• Vector legacy's code is not compatible with some of the existing, coming, or future software. Keeping this skin as the default would exclude most users from these improvements. Important examples of features not supported by Vector legacy are: the enriched table of contents on talk pages, dark mode, and also temporary account holder experience which, due to legal reasons, we will have to enable. In other words, the only skin supporting features for temporary account holders (like banners informing "hey, you're using a temp account") is Vector 2022.

How to request changes to the skin

We are guessing that some of you may want to see some changes to the skin. We are still improving Vector 2022 and the overall reading experience. If you have a feature request or a bug report, we encourage you to comment here or open a ticket in Phabricator. We will decide on the priority of these requests alongside our regular processes after deployment. Some fixes may be done via gadgets or user scripts, too.

About the skin

Global preferences

We encourage you to try out Vector 2022 by going to the Appearance tab in your preferences and selecting it from the list of skins. Getting used to it may take a few days, and that's the standard for interface changes.

Details about the skin

Vector 2022 is the modernized version of the currently default skin Vector legacy. It is the default on almost all Wikimedia wikis (there are about 10 left now). Most of the active editors use it and do not opt out of the skin at statistically noticeable rates despite easy access to the opt-out link. (Check the source here.)

[Our 2022 answer to why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were in 2010. Since then, new users have begun using the Internet and Wikimedia projects in different ways. Although there were changes to features the skin supported, the structure, navigation, visual layout, and overall readability of the skin did not change. The old Vector does not meet the current users' needs.

[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. We reduced PHP code in the other available skins by 75%. The project has also focused on making it easier to support gadgets and use APIs.

[Changes in a nutshell] The skin introduces changes to the navigation and layout of the site. It adds persistent elements such as a sticky header and table of contents to make frequently-used actions easier to access. It also makes some changes to the overall styling of the page. The analysis of the data collected concluded that these changes improve readability and usability, and save time currently spent in scrolling, searching, and navigating – all of which can be interpreted to create an easier reading experience. The new skin does not remove any functionality currently available on the old Vector skin. On wikis with this skin as the default, there are no negative effects to page views, account creation, or edit rates. On our project pages you will find findings and results in a nutshell.

A summary of findings and results

• On average, 87% of logged-in users on our early adopter wikis continue to use the new skin once they try it.
• The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
• The new table of contents makes it easier to navigate to different sections. Readers and editors jumped to different sections of the page 50% more than with the old table of contents.
• The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the wikis we tested on.
• The skin does not negatively affect page views, edit rates, or account creation. In fact, there is observational evidence of increases in page views and account creation across partner communities.

How can editors change and customize this skin?

• We make it possible to configure and personalize our changes. We are happy to work with volunteers with technical skills who would like to create new gadgets and user scripts. So far, many gadgets and user scripts have been built by volunteer developers. These aspects include making the background gray, turning off sticky elements, bringing back the old table of contents, and more. We encourage you to check out our repository for a list of currently available customizations and changes, or to add your own.
• In Vector 2022, logged-in and logged-out users can change the font size and color scheme based on their individual needs. Dark mode is now available for logged-in users of Vector 2022, and we would like to make it available to logged-out users as soon as most pages are dark-mode friendly.

How will we go through the change

• Wiki page: we would like to kindly suggest creating a page similar to English Wikipedia's w:WP:V22. It may explain the basics like how to opt-out or customize the skin.
• CentralNotice banner for logged-in users: before and shortly after deployment, we will display a banner announcing the change. It will be linking to Wikidata:Vector 2022 if you decide to create such a page. Otherwise, it will be linking to this announcement. This should limit the confusion and the number of repetitive questions about the change.

If you think there are any significant technical issues, let us know – perhaps we've missed something. We're looking forward to your comments before and reactions after deployment. Thank you! OVasileva (WMF) and SGrabarczuk (WMF) (talk) 22:14, 27 February 2025 (UTC) Unarchiving it to keep it a few days after deployment SGrabarczuk (WMF) (talk) 22:14, 20 March 2025 (UTC)

Tracked in Phabricator
Task T316797

About the page width and sitelinks going to the bottom in the Item, Property, and Lexeme namespaces - we've read comments about this issue, both here on Wikidata and on platforms like Discord, and it will be solved. There is an idea for a quick fix, and there may also be a different solution WMDE would work on. SGrabarczuk (WMF) (talk) 23:45, 27 February 2025 (UTC)

I have been using Vector 2022 for around a year now, and I haven't faced much issues other than the aforementioned page width issue, and the warning triangle icon of RequestDeletion gadget showing up in an awkward location on items which have an active RFD. Samoasambia ✎ 16:16, 11 March 2025 (UTC)

The new skin seems… completely unusable (like… literally, and I mean that literally!) on mobile? Sorry, maybe I’m doing something wrong or it’s some temporary glitch or something, because… I don’t believe I am the only one to try that, but I went in a private window (to remove all dependencies on my user settings and style) to e.g. [13] (and other random items) and… well, in all browsers I tried that (Firefox on desktop, Edge on desktop, Firefox on Android, Chrome on Android, Firefox Focus on Android), it was utterly broken, with all statements shown in a tiny vertical strip stuck between the termbox and the right sidebar with the rest of the page empty‽ (explained by Samoasambia below: the mobile skin will not be changed)

And… what I came to report originally was that the desktop view of the new skin is unusable for me on narrow screens, esp. on mobile when sidebar menus are shown (just a bit less terrible when only one is visible): the statement boxes split is bonkers: OK, the darker part for the property is OK-ish, but in the lighter value part, the edit section has a huge fixed width, with the (most important) value section receiving what’s left. Which, when on a narrow screen with both sidebars visible, is usually just a single-letter column; when only a single sidebar is shown, the value has something like five-letter lines, so not great as well. But bad luck for qualifier values and references either way, vertical writing you go.

--Mormegil (talk) 08:48, 14 March 2025 (UTC)

Also not a fan of the new design. And also even less of a fan of editing being impossible on mobile outside of labels and aliases.StarTrekker (talk) 11:35, 14 March 2025 (UTC)

The mobile website uses Minerva Neue skin, not Vector 2010 nor Vector 2022 which are meant for the desktop site. Forcing a different skin for mobile website with an URL parameter will obviously give a wrong result. Samoasambia ✎ 12:10, 14 March 2025 (UTC)

Thanks for the explanation, so the mobile skin won’t be changed, so that problem is moot. Anyway, the desktop view is quite unusable on narrow screens/mobile devices. The stylesheet tries to solve the problem, but apparently the thresholds for hiding the sidebars are too large. See a screenshot. --Mormegil (talk) 16:36, 14 March 2025 (UTC)

Vector skin causes Wikidata statements to display as one-character's.

This is another issue with the Vector skin. Myrealnamm-alt (talk) 16:06, 25 March 2025 (UTC)

(Sorry, see the image to the right) Myrealnamm-alt (talk) 16:06, 25 March 2025 (UTC)

The Web team could’ve spent some of their time fixing Wikidata-specific bugs with Vector 2022 before rolling it out, but apparently that’s entirely unnecessary. Even fixing the two-column view of Wikidata pages is apparently too much work. What a shame. stjn^[ru] 20:52, 17 March 2025 (UTC)

I have the same problem as Mormegil. So that is now for me the end of wikidata. I thought you were paid to support users.  – The preceding unsigned comment was added by Oursana (talk • contribs) at 10:05, 19 March 2025 (UTC).

@Oursana: You may change the skin back to the old Vector in your preferences if you want. Samoasambia ✎ 12:40, 20 March 2025 (UTC)

yes thank you, I did so. Oursana (talk) 13:21, 20 March 2025 (UTC)

What's the most effective way to add identifiers to a large amount of items (excluding Mix'n'Match)

Curious how everyone else here does it Trade (talk) 14:39, 24 March 2025 (UTC)

OpenRefine is a powerful tool for reconsiling identifiers with Wikidata items and for uploadong them. Samoasambia ✎ 15:06, 24 March 2025 (UTC)

Do you mind helping me with OpenOffice? Think that will work better for me Trade (talk) 02:06, 26 March 2025 (UTC)

Wikipedia as a source

Because Wikipedia is not considered a reliable source for citing info on Wikipedia. Should it not be cited here as a source, Masai giraffe (talk) 17:03, 25 March 2025 (UTC)

That is correct: pages on Wikipedia (and other Wikimedia sites) [...] are not appropriate as sources for Wikidata statements. Mahir256 (talk) 17:24, 25 March 2025 (UTC)

Please also note: "Tools that import data from Wikimedia projects generally add imported from Wikimedia project (P143) (and sometimes also Wikimedia import URL (P4656)) in the reference part of statements. Statements that are only supported by "imported from Wikimedia project (P143)" are not considered sourced statements. If you encounter one of these statements, please replace "imported from Wikimedia project" with an actual reference." (last sentence highlighted by me) -- This means that affected statements should not be simply deleted, but a better reference should be added. --Dorades (talk) 19:35, 25 March 2025 (UTC)

Ok, thanks Masai giraffe (talk) 19:59, 25 March 2025 (UTC)

Search

Is this possible to search items with specified occupation (P106) and by number of statements and or identifiers with Wikidata Query Service? Eurohunter (talk) 20:14, 23 March 2025 (UTC)

Yes.

SELECT * WHERE {
  ?item wdt:P106 wd:Q36834;
        wikibase:statements ?statements;
        wikibase:identifiers ?identifiers .
  # FILTER( ?statements > 100 ) .
  # FILTER( ?identifiers > 20 ) .
} LIMIT 100

Try it!

--Matěj Suchánek (talk) 21:45, 23 March 2025 (UTC)

@Matěj Suchánek: I just tried it but after few minutes I tried again and got fewer results. I don't know how is this possible. Some lag? Eurohunter (talk) 21:20, 24 March 2025 (UTC)

PS. I see now it shows different results each time - it even skips top results. I know results may change just because maybe someone just added something, but it's something more. Eurohunter (talk) 21:22, 24 March 2025 (UTC)

The above query is unordered and limited, so it may give you different results each run. You can simply remove the limit to get all results, but there can be a lot of them.

The arrows on the right indicate the lag on hover. --Matěj Suchánek (talk) 21:28, 24 March 2025 (UTC)

@Matěj Suchánek: So these 100 items are not taken from top 100? Why it just not show top 100 items out of 100 items? Eurohunter (talk) 22:02, 25 March 2025 (UTC)

You did not specify what "top" means. If the most identifiers, just sort it using ORDER BY DESC(?identifiers). Or analogously. --Matěj Suchánek (talk) 07:21, 26 March 2025 (UTC)

Merge or delete?

When we have two items for the same person where one contains no information that is not included in the other, is it preferable to merge them or delete the lesser of the two (see Felicity Scott (Q133294795) and Felicity Scott (Q84951092), the latter of which seems unnecessary, and possibly contains an inaccuracy)? -- Cl3phact0 (talk) 09:49, 26 March 2025 (UTC)

 Merged RVA2869 (talk) 13:04, 26 March 2025 (UTC)

Thank you. I just noticed that we also have this one too: Felicity Scott (Q133003758). -- Cl3phact0 (talk) 13:14, 26 March 2025 (UTC)

PS: The possible inaccuracy mentioned above is that "Associate Professor" in the description seems unlikely given her seniority, job title, and age. -- Cl3phact0 (talk) 13:20, 26 March 2025 (UTC)

 Done Thanks (also changed from "Associate Professor" to "Professor", per source). -- Cl3phact0 (talk) 15:09, 26 March 2025 (UTC)

Separating cookbooks on WikiBooks from other wikibooks links?

Would it be good or useful if particular kinds of Wikibooks and Wikiversity pages where separated from the ambiguous interwiki links? I think that's especially or at least needed when one can't query with sparql to filter which kind of subtypes of pages one is interested in.

So for example – and maybe there aren't more cases other than these – I think it would be good to separate cookbook/recipe pages from the many other types of Wikibook pages. This way one could easily using a query/queries get the free-license recipe pages for a certain food or dish which could be used for example by some recipe app or some table like Wikidata:List of dishes / List of fish dishes etc.

It could show the Wikibooks cookbook link(s) in one column dedicated to free editable recipes on Wikibooks or directly fetch its content using that link. Other free-license pages could also be used (maybe a property for Cookipedia (Q124960205) which is one of the free-licensed cooking websites would be good). The cookbook pages seem to all start with Cookbook: – for example b:Cookbook:Gimbap. I think without separating these one can't get these recipe pages in specific since for some items the wikibooks link would be other kinds of pages.

Likewise, Wikidebate (Q28043977) links on Wikiversity are not separated which can also be an issue if one intends to only fetch Wikidebates like in the wikidebate of this table. A difficulty here is that unlike Cookbooks on Wikibooks, these are not prefixed with Wikidebate:. However, that could and maybe should be changed. If one can filter by conditions on the page title (e.g. that it should only show links where the title starts with Cookbook:) in sparql, then separating these may not be needed (albeit it would make accessing this much easier since doing this kind of sparql is not accessible/easy to use).
Prototyperspective (talk) 17:50, 26 March 2025 (UTC)

API for Wikimedia Commons Query Service (Q107997224)?

Is there no API endpoint URL (P6269) for it like there is for Wikidata Query Service (Q20950365)? It's not just about it not showing on this list – I think having an API to e.g. fetch images from a certain category with certain criteria would be useful. Prototyperspective (talk) 00:51, 28 March 2025 (UTC)

@Prototyperspective: I am not sure what you mean. There is a SPARQL GUI at https://commons-query.wikimedia.org/ I am not sure you can get the category information from that endpoint though. You will probbably need to use https://commons.wikimedia.org/w/api.php to get category information. — Finn Årup Nielsen (fnielsen) (talk) 11:47, 28 March 2025 (UTC)

So does that mean there is a sparql API for Wikidata but not for Commons? Prototyperspective (talk) 12:37, 28 March 2025 (UTC)

You can query structured data at Commons with SPARQL similarly as the Wikidata graph, just from another endpoint. The main difference is that the Commons endpoint requires authentication, unlike the Wikidata endpoint. This can be automated using a script, but it is a bit tedious. ---MisterSynergy (talk) 12:45, 28 March 2025 (UTC)

I just found the help page describing the API endpoint: commons:Commons:SPARQL query service/API endpoint. —MisterSynergy (talk) 18:22, 28 March 2025 (UTC)

Thank you! It wasn't easy to find, I've added a category to the page; and now the WMC query service should also show up in that list of APIs with WD items. Prototyperspective (talk) 19:21, 28 March 2025 (UTC)

"mul" language code

I have not seen much discussion on the "mul" language code. At first it seem straightforward what should go into the label, but then you get into the issue on how to represent say a Japanese person. Katakana/Kanji version? Then only person with knowledge of katakana would be able to read it. When I see a Czech book, I add the Czech label to "mul", but then only people that read latin characters would be able to read it... — Finn Årup Nielsen (fnielsen) (talk) 11:56, 28 March 2025 (UTC)

You might like to read Wikidata:Requests_for_comment/Proper_names_in_multiple_languages Vicarage (talk) 13:33, 28 March 2025 (UTC)

KFC fried chicken

is there or can there be an item for c:Category:Fried chicken at KFC the specific kind of fried chicken sold by kfc? RoyZuo (talk) 14:01, 21 March 2025 (UTC)

@RoyZuo What would the purpose be? Ainali (talk) 14:03, 21 March 2025 (UTC)

Big Mac (Q506796)

Beyond Fried Chicken (Q85746816)

Big King (Q8247846)

Popcorn Chicken (Q17064676)

...? RoyZuo (talk) 14:15, 21 March 2025 (UTC)

@RoyZuo: I think it would be a better idea to use manufacturer (P176)KFC (Q524757) on such items than to create an item just for "fried chicken at KFC". I added one to Popcorn Chicken (Q17064676). Samoasambia ✎ 15:13, 24 March 2025 (UTC)

They literally named their franchise after this one product. It deserve it's own item Trade (talk) 01:46, 30 March 2025 (UTC)

KFC Original Recipe Chicken (Q133464422)  Done. RoyZuo (talk) 08:04, 30 March 2025 (UTC)

Are non-Wikipedia notable individuals acceptable?

Moved from Wikidata talk:Notability

Should deceased and well-documented everyday people be added? If so, is there a project to do this en masse? This would be similar to Wikipedia genealogy proposals. User01938 (talk) 06:03, 28 March 2025 (UTC)

@User01938: Hi, I moved this question here since it didn't really relate to changing the existing policy page, and here we have more people watching the page. Samoasambia ✎ 15:26, 28 March 2025 (UTC)

Wikidata:Notability: « An item is acceptable if [...] It refers to an instance of a clearly identifiable conceptual or material entity that can be described using serious and publicly available references ». So, yes. You can have a look at Wikidata:WikiProject Genealogy. Ayack (talk) 15:58, 28 March 2025 (UTC)

Hmm. Didn't we have one guy get in trouble for adding what I understood to be family members? The real question here is how far you can stretch those notability rules. Not sure those geneaology sites are good enough references by themselves, especially if they are of the crowdsourced kind. And obviously every single person who ever lived is linked to someone famous if you just go far enough back. If you take the rules to their logical extreme, it shows the absurdity. You can be sure however that listing people who are directly related so someone with a Wikipedia page is perfectly fine. It's also fine to list people directly related to anyone where notability is established per #2, but in the interest of preventing promotional items, the bar for modern day people is and should be high. Infrastruktur (talk) 23:14, 28 March 2025 (UTC)

If you mean people like William W. Waters (Q133698526) (which you created today): no, this item is in its current state not notable. --Dorades (talk) 21:54, 29 March 2025 (UTC)

Ah, what makes it count as notable specifically? The criteria seem a bit vague to me. User01938 (talk) 22:01, 29 March 2025 (UTC)

It can be tricky to determine if sources are considered "serious" according to our guidelines and there are lengthy discussions on WD:RFD about that. In general, sources that are not pusblished by the entity (or paid by the entity to be published) and that are not user-generated (like crowdsourced websites), are a good start. In this case, it's pretty clear because the two identifiers present on this items (FamilySearch person ID (P2889) and Find a Grave memorial ID (P535)) are both Wikidata property for an identifier that does not imply notability (Q62589320). --Dorades (talk) 22:13, 29 March 2025 (UTC)

There is also the possibility that primary sources might make an item within scope, by adding a sitelink — for example, if there were a bunch of letters to or from this serviceman scanned and uploaded to a Commons category, then an item would be justified. Sam Wilson 01:30, 30 March 2025 (UTC)

Thank you both! Would writing a Wikibook about people under a certain topic (e.g., in this case, World War II veterans from Minneapolis), would the subject then be considered notable? User01938 (talk) 02:53, 30 March 2025 (UTC)

Note, William W. Waters (Q133698526) appears to be a child of a notable person, Glen M. Waters (Q111321212), South Dakota State Senator and Minneapolis businessman. So all that would be needed to ensure Wikidata notability is a "serious" source like an obituary or news article that attests that William is the son of Glen who fought/died in World War II. -Animalparty (talk) 03:24, 30 March 2025 (UTC)

Is there a property for Strong's Numbers?

Most biblical words got their index number in the Strong's Concordance. If a word coexists in the Old and the New Testament, it will be assigned two index numbers, one for Hebrew, and one for Greek. (e.g. Christ as in Jesus Christ is assigned H4988 for Hebrew and G5547 for Greek.) Is there a property for Strong's Number that can be used on biblical word lexeme entries and data? 1F616EMO (talk) 08:51, 30 March 2025 (UTC)

@1F616EMO You can search for properties by using the P prefix, eg P:Strong. This returns Strong's number (P11416) and McClintock and Strong Biblical Cyclopedia ID (P8636) Piecesofuk (talk) 09:29, 30 March 2025 (UTC)

Request for deleting L1422137 or merging it into L66576

I accidentally created a duplicated entry for Messiah. I tried to merge using Special:MergeLexemes but failed. What should be done now? 1F616EMO (talk) 14:37, 30 March 2025 (UTC)

 Done Mahir256 merged it using merge.js. --Matěj Suchánek (talk) 20:20, 30 March 2025 (UTC)

IAU member ID (P9467)

It appears that the IAU has changed their IDs of all astronomers as well as the website where the ID leads to in Wikidata. Can someone look into this? Hobbema (talk) 22:28, 29 March 2025 (UTC)

For Harm Jan Habing (Q20336965) the id was 1859, and now the IAU has his information on this page with a number 31634. Hobbema (talk) 22:40, 29 March 2025 (UTC)

For completeness, currently the link in Wikidata leads here. Hobbema (talk) 15:08, 30 March 2025 (UTC)

@Hobbema: It's better to propose a new property for the new values at WD:PP. This property should be archived. While it might be tempting to re-use the property for the new IDs, in practice this is not a good idea. Often one can end up with a set of claims that is half right, half wrong for a long time. You also don't know who might depend on this data or re-use it. Infrastruktur (talk) 07:51, 31 March 2025 (UTC)

I tried something, but it did not work. I will leave this to you. The IAU has updated their website which changes everything. Hobbema (talk) 07:58, 31 March 2025 (UTC)

I can create a new property for you, but you will need to make a new property proposal (I can't do both). You can base it on the proposal for the existing property to make things simpler. Infrastruktur (talk) 08:05, 31 March 2025 (UTC)

I will try when I am at a computer (not telephone). Hobbema (talk) 08:27, 31 March 2025 (UTC)

I'm getting Lexemes in queries

I don't understand Lexemes, and have have never got them before in SPARQL queries, but now this query is returning https://www.wikidata.org/wiki/Lexeme:L1401164, because of its instance of (P31) weapon model (Q15142894). Is this statement an anomaly I can fix, a recent change to the SPARQL engine, or do I need to filter out lexemes now?

SELECT DISTINCT 
   ?item ?itemDescription ?modified WHERE {
  SERVICE wikibase:label {bd:serviceParam wikibase:language "en-gb,mul,en"}
      {?item wdt:P31/wdt:P279* wd:Q15142894}  # weapon model
UNION {?item wdt:P31/wdt:P279* wd:Q15142889}  # weapon family

MINUS {?item wdt:P31 wd:Q100710213} # combat vehicle model
MINUS {?item wdt:P31 wd:Q100709275} # combat vehicle family
?item schema:dateModified ?modified .
FILTER(BOUND(?modified) && DATATYPE(?modified) = xsd:dateTime).

}
GROUP BY ?item ?itemDescription ?label1 ?label2 ?modified
ORDER BY ASC(?label)

Try it!

Vicarage (talk) 07:15, 31 March 2025 (UTC)

Ssbuc (L1401164) had a wrong annotation. I have edited now, so it should not appear in the result of your query. — Finn Årup Nielsen (fnielsen) (talk) 13:07, 31 March 2025 (UTC)

Sanity check: AI-generated images

I've seen and reverted a couple of instances where users have added AI-generated images as the image (P18) of a person. Is there consensus (and/or policy) on this project that such edits should be reverted on sight? Omphalographer (talk) 19:43, 31 March 2025 (UTC)

I'm not sure if there has been any discussion about that here before but makes sense to me to remove them. Samoasambia ✎ 21:20, 31 March 2025 (UTC)