Jump to content

Wikidata:Project chat

Shortcuts: WD:PC, WD:CHAT, WD:?
From Wikidata

Edit

Vector 2022 will be the default skin

[edit]
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)[reply]

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)[reply]
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)[reply]
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. [1] (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)[reply]
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)[reply]
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)[reply]
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)[reply]
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)[reply]
(Sorry, see the image to the right) Myrealnamm-alt (talk) 16:06, 25 March 2025 (UTC)[reply]
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)[reply]
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).[reply]
@Oursana: You may change the skin back to the old Vector in your preferences if you want. Samoasambia ✎ 12:40, 20 March 2025 (UTC)[reply]
yes thank you, I did so. Oursana (talk) 13:21, 20 March 2025 (UTC)[reply]

Bad merges

[edit]

I noticed that a year ago Christian Yakubu has done thousands of author mergers with Wikidata Games many of which were incorrect. I already went through the edits between 14 and 20 February 2024, and found and reverted dozens of bad merges. If you wanna help, please pick a date, comment it below, go through the merges and revert the bad ones. Thanks to ArthurPSmith for already reverting many of them during the last year. Samoasambia ✎ 20:38, 16 March 2025 (UTC)[reply]

@Samoasambia: Thank you for your work. I am not familiar with this specific editor but I've come across many similar cases. People just merging items left and right.StarTrekker (talk) 20:51, 16 March 2025 (UTC)[reply]
According to https://outreachdashboard.wmflabs.org/users/Christian_Yakubu, this user is an instructor for multiple outreach programs that target Wikidata among other projects. Bovlb (talk) 02:06, 17 March 2025 (UTC)[reply]
@Bovlb: has undone several merges, but this is not enough - KrBot resolved the redirects, so the papers now linked to wrong author items. This should also be reverted. GZWDer (talk) 11:02, 17 March 2025 (UTC)[reply]
Thank you very much for the corrections.Please am very sorry for the wrong merges.ArthurPSmith showed me a different way to contribute without merging which I learnt.But I would be happy to be guided on how I can help undo some of these.
Thank You. Christian Yakubu (talk) 14:34, 17 March 2025 (UTC)[reply]
To fix the problem, you need to:
1. Review your merges to find bad merges that have not been fixed. This link might be a good starting point.
2. Undo your changes, or revert both items to a pre-merge state.
3. Review every page on the "What links here" for the merge target, to see if they need to be moved back.
In addition, it would be useful to know how this problem arose, as you are not the only editor to have made bad merges. Is there something missing or wrong in the instructions, the tool's interface, or some training course that leads to this problem? What could be improved? Bovlb (talk) 15:49, 17 March 2025 (UTC)[reply]
It's been a week since he offered to help clean up, but he has not contributed to this project since. He has been active on other projects, primarily to change his username to User:Ato Quamina Ceo. We expect better from editors, especially those placed in charge of outreach programs or training for the project. Bovlb (talk) 16:08, 24 March 2025 (UTC)[reply]
https://outreachdashboard.wmflabs.org/users/Ato%20Quamina%20Ceo
Here's an updated link to their outreach dashboard. Bovlb (talk) 16:12, 24 March 2025 (UTC)[reply]
Please, I offered to help revert the mistakes I made, but please, I have a serious problem at home that I am currently taking care of. And my changing username has nothing to do with the bad merges I have made. Also, the projects I have contributed to were done before I saw a message informing me of my bad merges. @Bovlb, please check my last contribution to other projects ever since I received the message of my bad merges. I sincerely apologise for any inconvenience caused to anyone helping to undo my bad merges. I am really sorry, especially to you @Bovlb if i've given you a bad impression about me.I didn't mean to do that intentionally Ato Quamina Ceo (talk) 22:59, 26 March 2025 (UTC)[reply]
Also, @Bovlb,i want to plead with you to direct me on how to find the bad merges I have made since I have no idea which of the merges I did was bad.Please help me Ato Quamina Ceo (talk) 23:13, 26 March 2025 (UTC)[reply]
There's no easy way to find the bad merges. We have to go back though them (say using the link I posted above) and examine each one, following the procedure I outlined above. It's time consuming work. We invite you to participate in this clean up. Bovlb (talk) 23:38, 27 March 2025 (UTC)[reply]
Kindly resend the link please Ato Quamina Ceo (talk) 08:36, 28 March 2025 (UTC)[reply]
https://www.wikidata.org/w/index.php?title=Special:Contributions&end=&namespace=0&start=&tagfilter=OAuth+CID%3A+1831&target=Ato%20Quamina%20Ceo&offset=&limit=500 Bovlb (talk) 19:53, 28 March 2025 (UTC)[reply]
For the items where I reverted the merges I also reverted any changes done by KrBot. However, some new articles may have been added during this year, and they will now have a wrong author. Samoasambia ✎ 15:01, 24 March 2025 (UTC)[reply]

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

[edit]

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

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

KFC fried chicken

[edit]

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)[reply]

@RoyZuo What would the purpose be? Ainali (talk) 14:03, 21 March 2025 (UTC)[reply]
Big Mac (Q506796)
Beyond Fried Chicken (Q85746816)
Big King (Q8247846)
Popcorn Chicken (Q17064676)
...? RoyZuo (talk) 14:15, 21 March 2025 (UTC)[reply]
@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)[reply]

Tools without active maintainers

[edit]

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)[reply]

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)[reply]
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)[reply]

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)

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

[edit]

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)[reply]

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)[reply]
[edit]

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)[reply]

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)[reply]
@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)[reply]
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)[reply]
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)[reply]
@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)[reply]
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)[reply]

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

[edit]

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

OpenRefine is a powerful tool for reconsiling identifiers with Wikidata items and for uploadong them. Samoasambia ✎ 15:06, 24 March 2025 (UTC)[reply]
Do you mind helping me with OpenOffice? Think that will work better for me Trade (talk) 02:06, 26 March 2025 (UTC)[reply]

"Described at URL" spam?

[edit]

Edits like this one seem to use described at URL (P973) to promote specific websites. Do we have no limitations on what information should be cited from websites? The "quotation" used as part of the citation contains no reference to the subject, so I'm baffled. --EncycloPetey (talk) 15:21, 24 March 2025 (UTC)[reply]

Big Think (Q4906529) is a notable source but if it's not related then it's redundant. In case of On the Origin of Species (Q20124) it is mentioned at this link so? Eurohunter (talk) 21:27, 24 March 2025 (UTC)[reply]
Just because a website is notable enough for its own item doesn't necessarily mean that its content is in any way useful. The property should only be used for high-quality content, not just to link to random web pages simply because a specific topic is mentioned. The page in question seem more like the kind of cheap listicles that are a dime a dozen on the net. That's not in any way useful for topics like On the Origin of Species (Q20124) where tons of highest-quality sources exist. Links like that should simply be removed om sight, IMO. And if more pages like it are added by users, treat it as spam. --2A02:810B:581:C300:81F0:421E:56:CD82 16:03, 26 March 2025 (UTC)[reply]

Missing icons (logo property)

[edit]

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)[reply]

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)[reply]
Please first see the examples. They overlap. Prototyperspective (talk) 12:38, 25 March 2025 (UTC)[reply]
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)[reply]
No. Prototyperspective (talk) 13:24, 25 March 2025 (UTC)[reply]

Wikidata weekly summary #672 (correct version!)

[edit]
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

Events

Press, articles, blog posts, videos

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

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

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

Anything to add? Please share! :)

Wikipedia as a source

[edit]

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)[reply]

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)[reply]
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)[reply]
Ok, thanks Masai giraffe (talk) 19:59, 25 March 2025 (UTC)[reply]

Merge or delete?

[edit]

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)[reply]

→ ← Merged RVA2869 (talk) 13:04, 26 March 2025 (UTC)[reply]
Thank you. I just noticed that we also have this one too: Felicity Scott (Q133003758). -- Cl3phact0 (talk) 13:14, 26 March 2025 (UTC)[reply]
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)[reply]

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

Could you please help me merge Q133539143 & Q131830184?

[edit]

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)[reply]

→ ← 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)[reply]

Separating cookbooks on WikiBooks from other wikibooks links?

[edit]

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)[reply]

Impossible to merge Q8444008 and Q133571542

[edit]

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)[reply]

✓ Done Ayack (talk) 13:24, 28 March 2025 (UTC)[reply]

tap yard - no item?

[edit]

Is there no item for a brewery tap yard? As I write this I'm cautioning myself against giving a bad summary as to how it's defined, and I'm unfamiliar with the wd rules for notable "concepts" and the various sources (ie encyclopaedias) used to evidence the existence of concepts. There's barroom (Q115760943) but that doesn't meet the usage of the word in the UK. Can't find anything on wiktionary either. Does anyone have any thoughts on how to add this, lest I create it and leave an item orphaned without identifiers? Tæppa (talk) 21:25, 27 March 2025 (UTC)[reply]

@Tæppa: could beer garden (Q857909) be a closer match? –FlyingAce✈hello 21:30, 27 March 2025 (UTC)[reply]
I would need to study the usage of the term in more detail but they can fall between "bar room" (aka "tap room" on the item) and "beer garden" (which is actually 2 distinct concepts when comparing UK "Beer Garden" and German "Biergarten" usage).
This article uses "tap yard" "tapyard" and "taproom" to describe a specific type of location only found at the site of a brewery.
https://www.siba.co.uk/2021/05/12/independent-brewery-tap-yards-new-beer-garden-breweries-busier-usual-pubs-unable-open-indoors-next-week/
The key feature of this concept is it's relation (management & supply of beer) to the brewery, and likely proximity (even if it's possible it doesn't share the exact premises) whereas barroom (Q115760943) and beer garden (Q857909) don't relate to a brewery at all and explicitly require a place to be indoors or outdoors. Which is awkward as the words we're working with in english are "room" and "yard" which themselves define whether something is indoor/outdoor. Tæppa (talk) 21:47, 27 March 2025 (UTC)[reply]

Are non-Wikipedia notable individuals acceptable?

[edit]
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)[reply]

@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)[reply]
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)[reply]
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)[reply]
If you mean people like William Waite Waters (Q133698526) (which you created today): no, this item is in its current state not notable. --Dorades (talk) 21:54, 29 March 2025 (UTC)[reply]
Ah, what makes it count as notable specifically? The criteria seem a bit vague to me. User01938 (talk) 22:01, 29 March 2025 (UTC)[reply]
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)[reply]

API for Wikimedia Commons Query Service (Q107997224)?

[edit]

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)[reply]

@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)[reply]
So does that mean there is a sparql API for Wikidata but not for Commons? Prototyperspective (talk) 12:37, 28 March 2025 (UTC)[reply]
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)[reply]
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)[reply]
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)[reply]

"mul" language code

[edit]

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)[reply]

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

IAU member ID (P9467)

[edit]

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)[reply]

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)[reply]
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat&oldid=2332261098"