Wikidata

Wikidata:Project chat/Archive/2024/06

< Wikidata:Project chat‎ | Archive‎ | 2024
This page is an archive. Please do not modify it. Use the current page, even to continue an old discussion.

Could someone please merge these?

https://www.wikidata.org/wiki/Q96000113 is a more recently-created duplicate of https://www.wikidata.org/wiki/Q28357688 .

I'm not a Wikidata geek, just someone who has created the en.wiki article on this Estonian-born singer (described in various sources as Russian or German).

I tried to merge them using Special:MergeItems: it said there was a conflict in the English descriptions, so I edited the newer one to remove all language descriptions. It then said there was a conflict in language "ast" description. At this point, I give up. Could someone who knows their way around Wikidata please combine the records? Thanks! PamD (talk) 07:39, 1 June 2024 (UTC)

On checking again, I removed the descriptors from the wrong version, so have reinstated them. PamD (talk) 07:42, 1 June 2024 (UTC)
Aaargh: a bot has created a third entry at https://www.wikidata.org/wiki/Q126227498 on the basis of my en.wiki article. PamD (talk) 07:45, 1 June 2024 (UTC)
I have removed the en.wiki link from Q126..., and added it to the oldest Wikidata record, Q283... . PamD (talk) 07:49, 1 June 2024 (UTC)
  Done (Please check that nothing has been lost. I am not familiar with the subject.) -- Cl3phact0 (talk) 07:56, 1 June 2024 (UTC)
@Cl3phact0 Looks good. Thanks. PamD (talk) 15:22, 1 June 2024 (UTC)

Invalid regex on P304

The regex for format constraint on page(s) (P304) is invalid. Could someone familiar with P304 fix it? Thanks DaxServer (talk) 11:17, 1 June 2024 (UTC)

If it's the error in regex101 "\x{10EAD} The character offset is too large" it's because the link to regex101 doesn't include the flags; the default is "/gm" but with "u" (for Unicode) added there are no errors. Adding "&flags=gmu" to the end of the regex101 URL also works. The bot that creates the constraint violations page can use the regex, although I don't know if that character (the Yezidi hyphenation mark) is recognised by the bot as I haven't found anywhere it is used. Peter James (talk) 15:45, 1 June 2024 (UTC)
Thanks @Peter James, I've made a comment to enable Unicode support in OpenRefine https://github.com/OpenRefine/OpenRefine/issues/1768 DaxServer (talk) 16:19, 1 June 2024 (UTC)

Swedish military history

There is a "Wieriska lantmilisregemente" mentioned in a biography, but I do not see it listed in Wikidata. At one time all the Swedish historical regiments had entries. Perhaps it is misspelled, and ideas? See: Hans Christoffer von Rohr II (1684-1754) biography (Q109269711) RAN (talk) 13:31, 31 May 2024 (UTC)

Seem to refer to a infantry regiment stationed in Wierland county present day Estonia. Infrastruktur (talk) 14:08, 31 May 2024 (UTC)

Proposals of transforming scripts into gadgets

Hi all! It has long been discussed, both here in Wikidata, on the Telegram group and in many events (lastly, as far as I remember, two months ago in the session "A few useful gadgets and scripts for Wikidata" in Wikidata:Events/Leveling Up Days 2024), that we have no standard procedure to promote CSS and Javascript scripts to gadgets. Sometimes proposals are made here in the Project chat, but it is difficult to follow them because in the Project chat many threads of every sort are opened frequently. As in the past I had created Wikidata:Tools/Proposals to collect proposals of new tools, I have just created also Wikidata:Tools/Potential gadgets in order to collect in a single place the proposals of transforming existing scripts into gadgets. Whilst I agree with the opinion expressed by many users that we don't need a formally structured process for a script to be approved as gadget (a certain number of users expressing their support, a minimum number of days for the discussion etc.), I think having a page to collect all these proposals would make it easier for interface administrators to follow these procedures and would probably encourage users in general to make such proposals. Of course feel free to propose improvements to the page (both the header and the title), here or in its talk page! --Epìdosis 17:05, 1 June 2024 (UTC)

It would be good to be also clear about how gadgets get updated/removed if we make the process more open. ChristianKl ❪✉❫ 09:41, 2 June 2024 (UTC)

How to represent filter size on a camera lens?

See Canon EF 70-300mm F4-5.6 IS USM (Q126286127) for an example. Interchangeable camera lenses have a lens mount on one end, and a threaded attachment for a lens filter on the other. The lens mount is described using connector (P2935), and I've also included a value of "some value", qualifiers applies to part (P518) pointing to photographic filter (Q876650) and diameter (P2386) pointing to actual number, to describe the filter size.

I think I'm working around something; when I tried to add photographic filter (Q876650) as a value for connector (P2935), I got a constraint error, because the value isn't a subclass or instance of electrical connector (Q2119531), optical fiber connector (Q2296938), or lens mount (Q205722).

Should the constraint be expanded, or am I expressing this incorrectly, or both? Grendelkhan (talk) 18:00, 2 June 2024 (UTC)

What to do when the maximum label length is too short?

Since there still(?) is not an automatic import of academic/scientific studies, I imported several studies for which I had uploaded images by hand with just the DOI. I noticed that for this item the maximum length of text for the label was too short: Q126369568 – what should be done when such occurs in general and for automatic imports?

It is missing this text at the end": a systematic analysis for the Global Burden of Disease Study 2021". I would suggest there is a separate field for something like "Full title" or "Trimmed title" where the remaining text or the full label can be entered but maybe such exists already. Prototyperspective (talk) 11:16, 8 June 2024 (UTC)

title (P1476) does exist to store the title. While the title can be often a good label for papers, labels exist for Wikidata internal purposes of giving people who look for an item easier access. They don't exist to provide people a reliable way to learn about the official title. For that purpose we have title (P1476). ChristianKl ❪✉❫ 22:02, 8 June 2024 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Thanks, all clarified now.--Prototyperspective (talk) 22:31, 8 June 2024 (UTC)

Items created using WikiShootMe

In a discussion on Discord, one user mentioned an item that he noticed, which seems to fail our notability guidelines: Q113319514 (it's just one of many power line pylons...). Looking at user:HighVoltage 5576 contributions, it seems that there are more such items. Is there any reason why these items exist in WD? Wostr (talk) 20:42, 30 May 2024 (UTC)

I thought wikishoot me was about images? but these items have no images? i'm confused. but yeah these items don't seem to be notable. BrokenSegue (talk) 23:49, 30 May 2024 (UTC)
I agree, no notability seen. Sjoerd de Bruin (talk) 09:26, 31 May 2024 (UTC)
@Magnus Manske: WikiShootMe seems to have a function to create a new Wikidata item for a Commons image (the blue circles). No mention at all about the notability policy. :-( Some sort of notification ought to be displayed the first time someone tries to use this functionality. Infrastruktur (talk) 09:44, 31 May 2024 (UTC)
Going to delete most of the power-line/pylon items. Not sure if the items for the electrical substations are worth keeping. Items for things like power stations should be notable. Infrastruktur (talk) 10:10, 31 May 2024 (UTC)
@Infrastruktur, Wostr, BrokenSegue, Sjoerddebruin, HighVoltage 5576: High-voltage pylons may be notable, dominant and distinctive, as well as other towers and masts. In areas that are thematically better covered, items are normally created and used for individual objects such as weirs, bridges, sculptures, bus or tram stops, railway crossings, houses, towers and masts, streets etc. A high-voltage pylon is certainly comparable in importance to them, especially when it has its own systematical identifier. This especially applies for pylons in a dominant position, but I don't think it's excessive to document main power lines pylon by pylon. The distance between such pylons is typically 300–500 meters – if it crosses a valley, it can be even a kilometer. As a rule, these are important orientation and landscape-forming structures. As a permanent registered structure of considerable size, such a pylon undoubtedly fulfills criterion 2 of Wikidata:Notability. In particular, if the pylon has it's photo here, it is advisable to identify it using its item to which the photograph is associated. However, a discussion can be held as to which types of power lines are so significant and which do not reach such significance to be elaborated in such detail. For my region, 400 kV and 220 kV (and some 110 kV) lines are the main long-distance lines. In some countries, also 750 kV lines are used. For local systems (35 kV, 22 kV, 15 kV, 10 kV, 6 kV), I would rather not consider individual masts to be significant - they are rather poles than pylons. But it can be open to debate whether it might make sense to import detailed street-furniture and infrastructure databases if they were available. --ŠJů (talk) 14:26, 2 June 2024 (UTC)
Reminds me about that time I asked if bus stops were considered notable, since they are after all semi-permanent infrastructure, although they don't form stable networks. Train networks don't have this problem. First things first, the items I deleted were technically not notable per WD:N since they lacked sitelinks, references or IDs, not even less "serious" ones. Nor were they interlinked. When I say that power stations are notable I mean there is significant precedence for those items, they are also of public interest.
I think section two of the notability policy is the only bad part of it. Often it is used as a poor excuse to keep items of dubious notability, it also does not lend itself to being easily assessed. What we should have accompanying that rule is granularity standards for what to include given no sitelinks. Example: Wikipedia sometimes have articles on a single house because it is interesting somehow, but I think you can agree it would be excessive to list houses in general. There are a lot of houses and very few of them are of public interest. You can also find official identifiers for houses, but none that implies notability.
Earlier I discovered that some dude had painstakingly documented the Australian power-grid. He did this down to the substation level. He did not document individual stretches of power-lines or pylons, he did however document the HV power-lines as a whole, which can be quite long. The granularity is reasonable here IMO. I would not consider intermediate voltage or consumer voltage lines notable. Infrastruktur (talk) 19:06, 2 June 2024 (UTC)
In Wikipedia, the question is often whether an item on it's own is of public interest. In Wikidata, we often have cases where a data set is of public interest even if the individual items on their own wouldn't be.
WD:N (2) says "It refers to an instance of a clearly identifiable conceptual or material entity that can be described using serious and publicly available references." It technically says "can" and not "are". That said, unfortunately we don't have infinite space on Wikidata and storing more data comes with a cost as shown in the proposed split of the citation graph. ChristianKl ❪✉❫ 08:39, 3 June 2024 (UTC)
I don't have any particular opinion on documenting HV lines pylon-to-pylon, but doesn't that sound more suitable for OpenStreetMaps? Infrastruktur (talk) 19:39, 2 June 2024 (UTC)
@Infrastruktur: It is a question of whether Wikidata can go to the same level of detail as map projects for some topics and some types of objects. Anyway, Wikidata goes into greater detail than Wikipedia's ambitions are. Individual benches, trash bins, post boxes or street light poles would seem excessive to me for Wikidata. However, items for high-voltage pylons, transformer towers, bus stops, level crossings, bridges or weirs sometimes make sense. In localities that have some cultural and historical value, it may make sense to register all address points (buildings). The purpose of Wikidata is relatively open - originally it was created primarily as a support for an encyclopedia, but at the same time it also serves as a support for a photography project and can potentially also serve as a database and metadata repository for map projects. --ŠJů (talk) 12:02, 3 June 2024 (UTC)

Angelina Mango (Q118390992) and Angelina Mango discography (Q124661336)

Some identifiers have been duplicated. i.e. AllMusic artist ID (P1728), Discogs artist ID (P1953), Genius artist ID (P2373), MusicBrainz artist ID (P434), and YouTube channel ID (P2397).-- Carnby (talk) 07:06, 2 June 2024 (UTC)

So delete them. Sjoerd de Bruin (talk) 14:06, 2 June 2024 (UTC)
In which item?-- Carnby (talk) 19:55, 2 June 2024 (UTC)
The discography one. Sjoerd de Bruin (talk) 20:03, 2 June 2024 (UTC)

Hyphenated surname

Should a hyphenated surname (for example, in the name of Ulrike Janssen-Bienhold (Q87885011)) be treated as a single surname (which would created a new surname Q for Janssen-Bienhold) or as two surnames, Janssen and Bienhold? I think that a single surname is the correct answer, but I would like to be certain. Eastmain (talk) 08:01, 2 June 2024 (UTC)

@Eastmain: IMHO a hyphenated surname can mean one surname containing a hyphen, as well as two various surnames (or even two people can be joined with a hyphen – incorrectly, instead of a dash). The customs of the language, country and period must be taken into account. As for the combination of birth surname and acquired surname, I would think of it as two surnames. When it comes to hereditary double surnames (for example, in the case of merged or divided noble families), it would be possible to treat them also as one surname. --ŠJů (talk) 09:40, 2 June 2024 (UTC)
@ŠJů@Eastmain: at several places this topic has been discussed. My clear opinion is that double family / double given names should be banned in Wikidata. Otherwise we end like auto-generated categories in other Wikiprojects, e.g. Commons:Category:Amalie Louise of Courland. Some discussion here: https://www.wikidata.org/wiki/Topic:Wwm2h3w8gw02roi1 Estopedist1 (talk) 07:33, 3 June 2024 (UTC)

Announcing the first Universal Code of Conduct Coordinating Committee

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Hello,

The scrutineers have finished reviewing the vote results. We are following up with the results of the first Universal Code of Conduct Coordinating Committee (U4C) election.

We are pleased to announce the following individuals as regional members of the U4C, who will fulfill a two-year term:

  • North America (USA and Canada)
    • –
  • Northern and Western Europe
  • Latin America and Caribbean
    • –
  • Central and East Europe (CEE)
    • —
  • Sub-Saharan Africa
    • –
  • Middle East and North Africa
  • East, South East Asia and Pacific (ESEAP)
  • South Asia
    • –

The following individuals are elected to be community-at-large members of the U4C, fulfilling a one-year term:

Thank you again to everyone who participated in this process and much appreciation to the candidates for your leadership and dedication to the Wikimedia movement and community.

Over the next few weeks, the U4C will begin meeting and planning the 2024-25 year in supporting the implementation and review of the UCoC and Enforcement Guidelines. Follow their work on Meta-wiki.

On behalf of the UCoC project team,

RamzyM (WMF) 08:14, 3 June 2024 (UTC)

Lexicodays, online event dedicated to Lexicographical Data, on June 28-30, 2024

- Indonesian version below -

Hello all,

Have you ever wondered how Wikidata stores and models words? How to create and improve Lexemes in your languages? Or even why it is useful and which projects could benefit from it?

The Lexicodays 2024 will answer these questions, and many more. During this online event, you will be able to learn more about Lexicographical Data on Wikidata, to discover how to model words in your languages, and to try out various tools that make it easier to work on Lexemes. It offers a space for editors involved in creating and maintaining Lexemes to discuss their ideas, challenges and best practices.

The online event will take place on June 28, 29 and 30, with sessions replicated in different languages and at different times across time zones. It is co-organized by Wikimedia Deutschland and the Software Collaboration Team in Indonesia, and we will focus on the languages of Indonesia and the Wikidata community in Indonesia. The event is open to everyone regardless of their knowledge of Lexemes. Most sessions will be recorded and published after the event.

On the main event page, you can discover the structure of the program, which will keep evolving in the upcoming weeks. We are also welcoming proposals for the program until June 20th - we are particularly interested in introductions to Lexicographical Data in different languages, and discussions run by community members on how to improve modelling and documentation in a specific language.

We will launch registration for the event in the upcoming days - if you’re interested, stay tuned by following the talk page or joining the Lexicographical Data Telegram group.

If you have any questions, feel free to write on the talk page of the event. See you soon, Léa (Lea Lacroix (WMDE)) and Raisha (Fexpr).

---

Halo, teman-teman!

Pernahkah Anda bertanya-tanya bagaimana Wikidata menyimpan dan memodelkan kata-kata? Bagaimana cara membuat dan meningkatkan Leksem dalam bahasa yang Anda tuturkan? Kenapa Leksem itu bermanfaat? Proyek-proyek apa yang akan terbantu dengan adanya Leksem ini?

Lexicodays 2024 akan menjawab pertanyaan-pertanyaan tersebut, dan masih banyak lagi. Selama acara daring ini, Anda akan dapat mempelajari lebih lanjut mengenai Data Leksikografis di Wikidata, menemukan cara memodelkan kata-kata dalam bahasa Anda, dan mencoba berbagai perkakas yang memudahkan Anda dalam menyunting Leksem. Acara ini membuka ruang bagi para penyunting yang terlibat dalam pembuatan dan pemeliharaan Leksem untuk saling berdiskusi mengenai ide, tantangan, maupun praktik-praktik terbaik.

Acara daring ini akan berlangsung pada tanggal 28, 29, dan 30 Juni, dengan waktu penyelenggaraan yang tersebar dalam beberapa zona waktu dan sesi-sesi serupa yang diantarkan dalam bahasa-bahasa yang berbeda. Acara ini diselenggarakan bersama oleh Wikimedia Deutschland dan Tim Kolaborasi Perangkat Lunak di Indonesia. Fokus dari acara ini adalah untuk bahasa-bahasa yang dituturkan di Indonesia dan komunitas Wikidata di Indonesia. Acara ini terbuka untuk siapa saja, terlepas dari seberapa akrab Anda dengan Leksem. Kami akan merekam sebagian besar sesi dan mempublikasikannya setelah acara selesai.

Anda dapat mengakses jadwal kegiatan pada halaman beranda acara, yang akan terus kami perbarui dalam beberapa pekan ke depan. Kami juga mengadakan panggilan terbuka untuk pengajuan proposal kegiatan hingga tanggal 20 Juni. Kami sangat tertarik dengan pengenalan Data Leksikografis dalam berbagai bahasa, dan diskusi yang dilakukan oleh anggota komunitas mengenai cara meningkatkan pemodelan dan dokumentasi dalam bahasa tertentu.

Kami akan membuka pendaftaran untuk acara ini dalam beberapa hari mendatang. Apabila Anda tertarik, silakan pantau terus laman pembicaraan ini atau bergabunglah dengan grup Telegram Data Leksikografis.

Jika Anda memiliki pertanyaan, jangan ragu untuk menulis di laman pembicaraan acara Lexicodays 2024. Sampai jumpa, Léa Lea Lacroix (WMDE) dan Raisha Fexpr. Lea Lacroix (WMDE) (talk) 08:58, 3 June 2024 (UTC)

Wikidata weekly summary #630

 
Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-06-03. Please help Translate.

Discussions

  • Open request for adminship: The Squirrel Conspiracy - RfP scheduled to end after 9 June 2024 06:47 (UTC).
  • New requests for permissions/Bot: TongcyBot - Task: Linking the Chinese and English Wiktionary, specifically in categories using Template:auto cat, and pages in the Template, Module, Appendix, Reconstruction, and Rhymes namespaces.
  • Open request for permissions/Bot: IliasChoumaniBot - Task: Automatic updating of data from JSON files on German scientists.
  • Closed request for comments: IP Masking Engagement - The RfC was closed due to inactivity. Discussions are still welcomed on Meta.

Events

Press, articles, blog posts, videos

Tool of the week

  • WikiTwister - RoloWiki: Replace the interwiki links of a Wikipedia article with a pop-up card full of useful Wikidata, & Wikidata Quick Dip: Browse the Wikidata properties used by the pages in a category.

Other Noteworthy Stuff

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

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

Merge req ✓ Done

Hello, can someone merge these two items? Q110413151 Q65248886. They're about the same thing. Idk if I can merge as an IP user and I don't wanna make an account. Thanks. 104.232.119.107 02:02, 6 June 2024 (UTC)

I have merged the items. For more information on merging see Help:Merge. William Graham (talk) 02:27, 6 June 2024 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. DannyS712 (talk) 07:13, 9 June 2024 (UTC)

Are these the same person or siblings?

Orif Toshmatov (Q126327618) and Orif Toshmatov (Q20534101) RAN (talk) 18:18, 8 June 2024 (UTC)

The articles seem to say they are the same; the "garmon" version is mentioned in both articles and is a nickname. Peter James (talk) 20:20, 8 June 2024 (UTC)
I redirected one Uzbecki article to the other and merged the Wikidata items. --RAN (talk) 21:27, 8 June 2024 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. Matěj Suchánek (talk) 13:09, 9 June 2024 (UTC)

Wikidata:Main_Page

Hi, The daily rotation of "current highlights" is broken. RVA2869 (talk) 11:35, 9 June 2024 (UTC)

@MisterSynergy: can you take a look? Sjoerd de Bruin (talk) 11:44, 9 June 2024 (UTC)
Seems the database schema of the pagelinks table has changed. I will fix this soon, hopefully this evening. —MisterSynergy (talk) 11:56, 9 June 2024 (UTC)
Okay it is already fixed as it was a relatively simple change. —MisterSynergy (talk) 12:50, 9 June 2024 (UTC)
@MisterSynergy Thanks
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. RVA2869 (talk) 14:21, 9 June 2024 (UTC)

Renaming the Community Wishlist Survey

Hello everyone,

Community engagement around the Wishlist's redesign is still in progress to help make decisions ahead of the relaunch of the survey in July 2024. The revised survey will need a new name that reflects its new direction. You are invited to help choose a name.

There are some early renaming ideas like Wikimedia Opportunities Registry, Wikimedia Collaboration Hub and ImagineWiki. These names may not resonate with you all, hence, please join the discussions and suggest your own name if need be.

Looking forward to hearing from you on the discussion page.

NB: In case you have missed previous discussions and announcements regarding the future of the Wishlist, please see them as bullets below:

On behalf of Community Tech, STei (WMF) (talk) 14:54, 4 June 2024 (UTC)

Using illustrate_wikidata.py to get images from a commonscat ?

Hello, I managed to import images from articles to wikidata objects using

Is it possible to use illustrate_wikidata.py to get images from a commonscat, for example for every subcat of

and add the first (an mostly only one) image from the category to the wikidata objects connected to the commonscats? If yes, what would the parameters?

Thanks a lot! M2k~dewiki (talk) 17:16, 4 June 2024 (UTC)

@PAWS:~$ pwb.py illustrate_wikidata.py -family:commons -lang:commons -catr:"Cultural properties of local significance in Thun (East)"
returns:
>>> File:2023-06-01 Thun Bälliz Brunnen bei44.jpg <<<
commons:File:2023-06-01 Thun Bälliz Brunnen bei44.jpg doesn't have a Wikidata item.
@PAWS:~$ pwb.py illustrate_wikidata.py -family:commons -lang:commons -namespace:14 -catr:"Cultural properties of local significance in Thun (East)"
@PAWS:~$ pwb.py illustrate_wikidata.py -family:commons -lang:commons -namespace:14 -catr:"Category:Cultural properties of local significance in Thun (East)"
does not return anything M2k~dewiki (talk) 17:52, 4 June 2024 (UTC)

Merging two items regarding Ministry of Social Affairs (Indonesia)

Is it possible to merge Ministry of Social Affairs (Q74529320) to Ministry of Social Affairs (Q11046702)? I think it is safe to assume that the scholary research organization is the ministry itself. Hans5958 (talk) 06:07, 9 June 2024 (UTC)

This doesn't sound logical to me, please don't merge different concepts. Sjoerd de Bruin (talk) 11:45, 9 June 2024 (UTC)
If you think these are different, then your edit Special:Diff/2174982241 was wrong. That belongs to Ministry of Social Affairs (Q11046702), and is already on that item (with slightly different capitalisation). - Nikki (talk) 01:52, 10 June 2024 (UTC)
You are correct,   Merged. Sorry, probably needed coffee yesterday! Sjoerd de Bruin (talk) 08:21, 10 June 2024 (UTC)
This section was archived on a request by: Sjoerd de Bruin (talk) 15:33, 10 June 2024 (UTC)

People falsely claiming Native American heritage

See for example: Iron Eyes Cody (Q587113) where he had social_classification=pretendian, it was removed because the term was considered a pejorative. What would be the best way to aggregate people that falsely claimed to have Native American heritage. The original list of about a dozen people came from reliable sources, such as a New York Times obituary. Should we create a new Wikidata entry called "falsely claiming Native American heritage" so it is worded neutrally? Should it be "social_classification=falsely claiming Native American heritage" or something else? Or should it be handled the way it was with Rachel Dolezal (Q20085770) and allow them to be called transracial? See also Sacheen Littlefeather (Q462050) where there is yet another way to model disputed ethnicity, where we add the false claim and deprecate it. I would like a single model where a single simple search term would find all the people. RAN (talk) 13:19, 4 June 2024 (UTC)

I would add statement ethnic group (P172)Native Americans in the United States (Q49297) with qualifier reason for deprecated rank (P2241)hoax (Q190084) and mark it as a deprecated claim. That model is not super easy to query if you want to find all persons with such statement but at least it is doable with existing items and properties. Samoasambia ✎ 13:41, 4 June 2024 (UTC)
More likely it was removed because it was incorrect use of properties. Some vigilantes like to add "occupation" claims on people accused or sentenced of certain crimes. Infrastruktur (talk) 15:08, 4 June 2024 (UTC)
  • They wrote that "pretendian" was a pejorative in a message to me. We also had difficulty with slave_owner and holocaust_victim, and how to model them. Social_classification=slave_owner was the final decision and significant_event=Holocaust_victim and subject_has_role=Holocaust_victim are still both in use, with significant_event givng an error message. --RAN (talk) 15:38, 4 June 2024 (UTC)
This can be closed, it is resolved "disputed Native American heritage" rather than the pejorative pretendian. --RAN (talk) 23:06, 6 June 2024 (UTC)

Are images transfers to WikiData working? (repost from help desk and village pump)

I use Wiki Shoot Me to take photos for Wikipedia while I’m traveling. Typically you can identify articles that need photos by looking for yellow dots indicating Wikipedia articles and larger red circles near by indicating WikiData items without photos (as previously these seemed to sync). In two cases recently I noticed articles with CC-licensed images placed correctly in the lead and appropriately sized that did not have their photos synced with WikiData: National Hotel (Q65056276) and Wet Mountain Valley (Q7989973). I know the page image is being picked up because they display correctly on Special:Nearby using their coordinates: National Hotel and Wet Mountain Valley. It looks like they’re just not making it to WikiData. - Scarpy (talk) 17:15, 4 June 2024 (UTC)

You are free to add them, we do have some automated processes but editors tend sometimes to put non-relevant images as infobox images so we are a bit cautious. Sjoerd de Bruin (talk) 07:56, 5 June 2024 (UTC)
I’m okay doing that with my photos. For articles with existing photos where I can confirm their relevance, is there a tool I can use to import them so the author information is retained? - Scarpy (talk) 04:27, 6 June 2024 (UTC)
WDFIST might help. Sjoerd de Bruin (talk) 08:08, 6 June 2024 (UTC)

Can one do calculations with Wikidata?

Hi,

I am brand new to Wikidata and am wondering whether one can use it for calculations. Here is the idea: we are seeking a way to derive party counts from government descriptions, in our case for European political parties represented in European institutions.

For instance, we would write that the German government has a coalition of the SPD, FDP and Greens. Separately, we would indicate that the SPD is a member of the European PES, that the FDP is a member of ALDE, and that the Greens are a member of the EGP.

Is there a way for this to lead to a counter which would show that the PES, ALDE, and the EGP each have 1 seat in government? This would apply to the Council of the European Union.

This idea is to then simply describe governments of European member states (and update them following elections) and to automatically populate counters in composition bars on pages relating to European political parties.

Thanks! 2A03:1B20:B:F011:0:0:0:A06D 10:24, 6 June 2024 (UTC)

I'm not exactly sure what you're asking. Maybe looking at https://query.wikidata.org/ would answer your question? The wikibase user interface itself won't do calculations but mediawiki instances that pull data from wikibase can. BrokenSegue (talk) 00:43, 7 June 2024 (UTC)

A book with different title on the cover and on the title page.

I created an item for An Elegy on the Death and Burial of Cock Robin (Q126373391), which is a 1820 edition of the poem Cock Robin (Q4019610). On the cover, the book's title is "The Death and Burial of Cock Robin". On the title page, the book's title is "An Elegy on the Death and Burial of Cock Robin". I have put both values in the title (P1476) field for An Elegy on the Death and Burial of Cock Robin (Q126373391). However, when I try to add a qualifier to specify which one is associated with title page (Q1339862) and which one is associated with book cover (Q1125338), I keep running afoul of the property constraint (P2302) on title (P1476) for allowed qualifiers constraint (Q21510851) (not sure how to link it with templates, here's the direct link). What is the correct way to specify this information? Beleg Tâl (talk) 13:25, 6 June 2024 (UTC)

Long list of allowed qualifiers but I think qualifier applies to part (P518) is the best one for this case. –Samoasambia ✎ 23:39, 6 June 2024 (UTC)
Since most catalogs (e.g. WorldCat) seem to use the longer title ("An elegy of on..."), it might be good to set that as a preferred value for title (P1476). Covers of old books often have simpler titles which may omit subtitles, definite/indefinite articles (The, A, An) or other elements. Likewise, running headers at the tops of each page often use an abbreviated form. -Animalparty (talk) 01:20, 7 June 2024 (UTC)

Paul Rhoades

the things who ever wrote about Paul Rhoades is not true. I am his sister. And before you talk about someone get your facts all the bullshit everyone writes is so far out of line. Maybe you shouldn't write about what you don't know. 2604:3DC0:1:AA0D:99AE:D311:6B4A:1862 21:50, 7 June 2024 (UTC)

If what you are saying is true and you are IRL related to Paul Ezra Rhoades (Q109860218) (??), you must've made it sure (before writing here) whether there is something in the Wikidata item besides what is known from the English Wikipedia or from publically available sources. Nothing special, let me guess so?.. We are ready to fix the inaccuracies if the item on very this site contains them and if you are going to point to them being more kindly than now. Have a great evening. --Wolverène (talk) 22:20, 7 June 2024 (UTC)
Probably something in the Wikipedia article or in Find a Grave, not Wikidata. Peter James (talk) 20:29, 8 June 2024 (UTC)

Occupation: neo-Nazi

Can more people please watch Q30961105 Vita Zaverukha . Editor @Yarkovesh adds "Occupation: neo-Nazi" [1] providing a source which is not saying she works as "neo-Nazi" (anybody noticing absurd here?) Manyareasexpert (talk) 22:04, 7 June 2024 (UTC)

'Neo-Nazi' is not a kind of a job or a field of work. Also, she should not be persistently labeled as a Neo-Nazi activist, unless she or her closest allies admit(s) to such a definition. As we know, the propaganda in one of the countries located next to Ukraine claim as 'Neo-Nazi' everyone who fights for the UA Armed Forces, or just gives a helping hand to Ukraine. I mean, this way 'Neo-Nazi' means nothing relevant at all. I agree that that one is an incorrect value for the property. --Wolverène (talk) 22:42, 7 June 2024 (UTC)
Thanks! Manyareasexpert (talk) 22:54, 7 June 2024 (UTC)
Does your soul hurt so much for this girl that you can't leave her alone? Yarkovesh (talk) 15:08, 8 June 2024 (UTC)
Bellingcat says "reported neo-Nazi" in a caption, with a link to the Daily Mail, which is usually better than propaganda but not reliable. political ideology (P1142):neo-Nazism (Q151250) would be a valid statement but would require a better source. Peter James (talk) 20:00, 8 June 2024 (UTC)
We really ought to have a edit filter for these contentious statements Trade (talk) 00:16, 9 June 2024 (UTC)

Millon's Schizoid subtypes

I wanted to make four items for the subtypes listed here but i could not figure what the correct modeling would be. Any suggestions? Trade (talk) 00:18, 9 June 2024 (UTC)

Using Wikidata as an upstream for device information

As part of postmarketOS we track a significant amount of information about the specs of computer hardware, mostly tablets and phones (e.g. the OnePlus 6) . However, since this info is fixed, I've been thinking it probably makes more sense to find a more central datastore and put this info there and to pull from it instead. Found that some of our devices are already in Wikidata. We'd want to add some more fields probably, but a bunch would already be usable for us. Does this seem like a good use of Wikidata? 2A02:168:F912:0:0:0:0:1001 19:42, 29 May 2024 (UTC)

It could be a good use case. The main problem though is that we require information to have references (or at least be referenceable). I'm not clear on where your information is sourced to. Also it would depend on exactly how many new properties you would want made. You may want to consider using https://www.wikibase.cloud/ which I believe would let you federate somehow with wikidata while maintaining your own database separate from wikidata (which you could link bidirectionally to wikidata). If you went that route you wouldn't need to follow our rules about sources or notability. BrokenSegue (talk) 01:07, 30 May 2024 (UTC)
We don't have a rule that all information needs to have a reference. When it comes to specs there's going to be some official documentation that contains the information so it's going to be referencable. Our rules also don't forbid from using the existing postmarketos website as a source.
I would expect that the bigger issue is to think through the data model as when we create properties in Wikidata we create them not optimized for single use-cases like "I need a field in which to put X". ChristianKl ❪✉❫ 11:41, 30 May 2024 (UTC)
The postmarketOS wiki wouldn't be a reference in the scenario I'm proposing, it'd be downstream of Wikidata. My goal would be to put the specs we need in Wikidata so we can remove them from our wiki and instead reference them. However, there are sometimes other places that have this info (GSMArena or the manufacturer's pages, etc.). I think referencing things can be done in many cases.
Could you elaborate on the issue with properties? We mostly only log this info in our wiki so people can find devices that meet their specs, they aren't critical to our project. However, some are like the CPU and GPU. I've seen RAM (one of the properties we log) documented already in Wikidata, so that looks good. CPU and GPU looks good too. But some are missing, and maybe this is what you're talking about. Like I couldn't find a property for the amount of data storage on a device. Nor for things like the type of sensors that they have. If you look at the OnePlus 6 link in my OP you can see a table with the info I'm talking about. 85.195.207.54 15:53, 30 May 2024 (UTC)
The problem is that we don't really have a property for RAM. We have one for memory capacity (P2928) that can be used for both RAM and data storage. That wouldn't be that much of a problem if people would use it as intented and say phone model Xhas part(s) (P527)hard diskmemory capacity (P2928)128 GB and phone model Xhas part(s) (P527)RAMmemory capacity (P2928)8 GB. In practice, you find people saying memory capacity (P2928)128 GB{{{3}}} or memory capacity (P2928)8 GB{{{3}}} and the data we have is messy. This isn't an unsurmountable problem but it takes work to move forward.
When it comes to sensors, has part(s) (P527) would be the way to go. I'm unclear about what you mean with works/broken/partial. If that's a postmarketOS specific category it would likely need a new property. ChristianKl ❪✉❫ 13:12, 1 June 2024 (UTC)
I think everything I need is supported and then some! I created a new tablet. The only two missing properties I ran into were one for "sensor resolution" of the camera sensors and "diagonal" for the size of the display (since those are commonly referenced as diagonal inches). So in general everything looks good!
The RAM problem I solved by using has part(s) as you can see in the tablet item I made. I think it makes sense to break them out as parts with capacities under them. I'll want to engage more with others working in this area to see what might be the best route here.
https://wiki.postmarketos.org/wiki/OnePlus_6_(oneplus-enchilada) shows the info we track on our wiki for reference. What we need is a way to pull all components of a device so that we can track how well it's supported on our end. I don't think that supported attribute should be in Wikidata, but we need a way to map from the components of a device in Wikidata to the way we track status in our system. I think it's possible with the way I've done organized the tablet I added.
I think the hardest part is integration, as it looks like there's no easy way to pull data into a Mediawiki I operate. However, we may move away from that towards a custom website given upstreaming this data to Wikidata removes a ton of the info we're tracking on our side! BasilicumTree (talk) 20:34, 1 June 2024 (UTC)
@BasilicumTree: To note, when adding references use reference URL (P854) rather than official website (P856). I've fixed that in your example item and cleaned up some other bits. I like how you've formatted it overall. — Huntster (t @ c) 21:18, 1 June 2024 (UTC)
https://m.mediawiki.org/wiki/Extension:External_Data works well for my mediawikis, though I do some external json mangling on a filesystem Vicarage (talk) 22:21, 1 June 2024 (UTC)
@Huntster - Thanks for adding more details and correcting some stuff! Glad we're on the right track here! Let me know if I shouldn't ask here, but what about storing manufacturer model numbers for devices? I couldn't find anything for that. I think I'll propose adding a "diagonal" dimension property, since that's so common for describing electronic displays. With that all the device metadata we need looks good!
@Vicarage - Awesome, thanks! I'll check that out.
We also track info on SoCs, for example the MSM8926, where mostly we want to track the status of components (just like with devices). So I created a Wikidata item for it and I think it covers everything. Thought most things are Parts, I didn't see a better way to do it right now. BasilicumTree (talk) 07:51, 2 June 2024 (UTC)
@BasilicumTree: for model number, catalog code (P528) possibly could be used in the form catalog code (P528)12345 applies to part (P518)product code (Q57446692), but it isn't ideal. Would be worth it to propose both model number and diagonal as new properties. — Huntster (t @ c) 12:42, 2 June 2024 (UTC)
Found https://www.wikidata.org/wiki/Wikidata:Property_proposal/part_number which discusses both part number (Q3879409) and product code (Q57446692), though I'm not certain how these are different in practice. Does it make sense to comment on this old thread about my new use case to revisit it? or is there a way to reopen an old property proposal?
I opened https://www.wikidata.org/wiki/Wikidata:Property_proposal/screen_size as well, but found there was already an old proposal closed previously. Figured I'd just leave it as the use case I'm proposing wasn't discussed much previously. BasilicumTree (talk) 10:41, 3 June 2024 (UTC)
@BasilicumTree: I see no reason the part number proposal couldn't be re-opened if you think you can make a stronger argument than the previous proposal. If you decide to, start a new proposal page and consider linking to the previous discussion. — Huntster (t @ c) 20:13, 4 June 2024 (UTC)
How should I start a new proposal page if I think the name of the previous proposal was a good one? Just append a 2 to the original URL for example? BasilicumTree (talk) 05:36, 6 June 2024 (UTC)
An alternative approach I came up with for the Android device codename and part number, is to use name (P2561) with applies to part (P518) and Android (Q94) and product code (Q57446692) respectively. Redmi Note 9 (Q85796390) was already using name (P2561) as well, so seems reasonable. WDYT? BasilicumTree (talk) 17:21, 9 June 2024 (UTC)
@BasilicumTree: My concern is the potential confusion about which product codes applies to which sub-model. Ideally, you'd have property "Product code" with a subproperty like object named as (P1932) providing a free-form field to specify the exact product name the code applies to, if there's multiple. But, if your alternative provides for your needs, then that's fine. As to your first question, yes, just append a "2", such as "/product code 2". — Huntster (t @ c) 23:24, 9 June 2024 (UTC)

Question

I have a table of around 1,800 Australian federal MPs in the below format containing their ID for Parliament of Australia MP ID (P10020). I want to link each to their corresponding wiki data item. Is there a quick way to do this?

Name P10020 ID number Date Of Birth Place Of Birth State Of Birth Country Of Birth Date Of Death Place Of Death State Of Death Gender Party State Electorate Senate State MP or Senator Service History: First Service History: Last Service History: Duration Age
ABBOTT, the Hon. Anthony (Tony) John AC EZ5 1957-11-04 London England Male Liberal Party of Australia New South Wales Warringah Member 1994-03-26 2019-05-18 25 years 2 month(s) and 1 days. 66.6

GMH Melbourne (talk) 05:44, 9 June 2024 (UTC)

I would recommend using OpenRefine. There you can reconcile the data based on the IDs. –Samoasambia ✎ 06:40, 9 June 2024 (UTC)

[PROPOSAL] Link labels, aliases and monolingual text with Lexemes

 
Explanation about connection between labels and lexemes in Wikidata

I don't know if here is the right place to propose it. It would be nice to link item labels, item aliases and monolingual text from statements with a corresponding lexeme. This could be optional, either enter plain text or select a lexeme from the selector. I have no clue about how realistic or difficult to implement it could be. I created an image that I hope explains what I mean. 5628785a (talk) 17:42, 5 June 2024 (UTC)

User:Nikki/LinkLabelsToLexemes.js does that for labels/aliases (but not monolingual text). - Nikki (talk) 05:00, 6 June 2024 (UTC)
Nice work! But still, it would be nice to have it integrated in the Wikidata RDF data model, plus having the possibility of editing the links.--5628785a (talk) 13:37, 6 June 2024 (UTC)
@Danny_Benjafield_(WMDE): What steps do I need to take for the development team to consider this proposal?--5628785a (talk) 11:22, 9 June 2024 (UTC)
Hello @5628785a, thank you for ping'ing me. I would recommend leaving this message up for about a week to give others a chance to comment their thoughts, support and feedback on it.
  • In the meantime, I will take this to my PM to evaluate its feasibility.
  • If there are no objections, and the PM thinks it aligns with our development goals, I will create a Phabricator ticket for it and it will eventually get seen by one of our developers.
  • If it does not align with our development objectives, we will still keep a record of it for future updates to our development goals.
Thank you again, - Danny Benjafield (WMDE) (talk) 09:25, 10 June 2024 (UTC)

Can someone help me better model these events

When I look at various annual shows, they are modeled slightly differently. I have 1914 Westminster Kennel Club Dog Show (Q107637781) and 1912 National Horse Show (Q126392669) to be improved. RAN (talk) 14:26, 7 June 2024 (UTC)

i took a stab at it BrokenSegue (talk) 15:27, 7 June 2024 (UTC)
This has been resolved. --RAN (talk) 16:29, 10 June 2024 (UTC)

Conflation

Can someone help tease apart these two people conflated at Bernard Francfort (Q80651917)? RAN (talk) 18:21, 8 June 2024 (UTC)

I moved the subject of https://www.idref.fr/230217494 to Q126429057; it was only the date of birth and identifier that didn't belong to the original subject. This was probably caused by a conflation in IdRef - the 1904 works link to the author born in 1946. Peter James (talk) 19:17, 8 June 2024 (UTC)
This has been resolved. --RAN (talk) 16:29, 10 June 2024 (UTC)

Wikidata weekly summary #631

 
Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-06-10. Please help Translate.

Discussions

  • Open request for adminship: Kadı - RfP scheduled to end after 14 June 2024 17:51 (UTC)
  • Closed request for adminship: The Squirrel Conspiracy - Closed as successful. Welcome back Squirrel!
  • New requests for permissions/Bot:

Events

  • Next Linked Data for Libraries LD4 Wikidata Affinity Group call June 11, 2024: We have our next LD4 Wikidata Affinity Group Call on Tuesday, 11 June, 2024 at 9am PT / 12pm ET / 17:00 UTC / 6pm CET (Time zone converter). Please join us for a community discussion on SMALL GLAM SLAM Pilot 1 with Ismael Olea. Link to agenda.
  • Celtic Knot Wikimedia Conference, September 25-27, 2024 in Waterford City, Ireland. This conference usually hosts Wikidata-related sessions. You can now propose your contributions to the program until July 14th, and apply for a scholarship until June 30th (full announcement and links)
  • WikiIndaba conference 2024, 4 - 6 October 2024 in Johannesburg, South Africa. This conference typically hosts Wikidata-related sessions. Program submissions 05 - 30 June 2024.

Press, articles, blog posts, videos

Tool of the week

  • Paulina: Data for the Public Domain - Explore the cultural heritage of humanity. Search Paulina by author and discover if they have freely accessible works in the Public Domain.

Other Noteworthy Stuff

  • Propose to transform an existing CSS or Javascript script (i.e. scripts that you can enable in your common.css and common.js pages) into a gadget: Wikidata:Tools/Potential gadgets

Newest properties and property proposals to review

You can comment on all open property proposals!

Did you know?

Development

  • The UnpatrolledEdits gadget now shows a notice when there are older and multiple unpatrolled edits, previously it only showed the notice when the most recent edit was unpatrolled. Please help translate the messages here.
  • Query Service: We are fixing a bug where no examples are shown in the example dialog (phab:T366871)
  • EntitySchemas: We have enabled the new datatype for testing on test.wikidata.org and are preparing the rollout to Wikidata (phab:T365686)
  • Item UI: We fixed an issue where labels were not shown for badges or after making an edit (phab:T366236)
  • Wikibase REST API: We have continued the work on the route for modifying the data of an Item (phab:T342993)

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

Merge Q10267922 and Q113588564

Please merge Q10267922 (pt:Dolo eventual) and Q113588564 (it:Dolo eventuale, et al.). Mathglot (talk) 06:16, 7 June 2024 (UTC)

Courtesy links: indirect intent (Q10267922), indirect intent (Q113588564) —Justin (koavf)❤T☮C☺M☯ 06:20, 7 June 2024 (UTC)
  Done — Martin (MSGJ · talk) 08:47, 11 June 2024 (UTC)

The final text of the Wikimedia Movement Charter is now on Meta

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Hi everyone,

The final text of the Wikimedia Movement Charter is now up on Meta in more than 20 languages for your reading.

What is the Wikimedia Movement Charter?

The Wikimedia Movement Charter is a proposed document to define roles and responsibilities for all the members and entities of the Wikimedia movement, including the creation of a new body – the Global Council – for movement governance.

Join the Wikimedia Movement Charter “Launch Party”

Join the “Launch Party” on June 20, 2024 at 14.00-15.00 UTC (your local time). During this call, we will celebrate the release of the final Charter and present the content of the Charter. Join and learn about the Charter before casting your vote.

Movement Charter ratification vote

Voting will commence on SecurePoll on June 25, 2024 at 00:01 UTC and will conclude on July 9, 2024 at 23:59 UTC. You can read more about the voting process, eligibility criteria, and other details on Meta.

If you have any questions, please leave a comment on the Meta talk page or email the MCDC at mcdc@wikimedia.org.

On behalf of the MCDC,

RamzyM (WMF) 08:44, 11 June 2024 (UTC)

Renaming the Community Wishlist Survey: Vote for your preferred name

Thank you to everyone who has provided feedback on renaming the Community Wishlist Survey. We now have 3 names for you to choose from:

1. Community Ideas Exchange

2. Community Feature Requests

3. Community Suggestions Portal

You are invited to vote for one that works for you. –– STei (WMF) (talk) 15:09, 11 June 2024 (UTC)

Undoing the merger of a ship and its ship class

Yingtan (Q123702206) (a ship, the Chinese frigate Yingtan) was merged with Type 053K frigate (Q10843686) (the class for that ship). They should remain separate, even though they is only one ship in the class. When I try to do this I get enwiki complaints, and am now confused as to how to get one item with the enwiki reference, one without. Vicarage (talk) 23:34, 12 June 2024 (UTC)

@Vicarage: Should be fixed. You have to undo the edits to the item merged into, then undo the item merged. — Huntster (t @ c) 03:23, 13 June 2024 (UTC)

narrowing scopes of field of work

If an organisation studies fortifications in Germany, we can use field of work (P101) fortification (Q324326), but should Germany be a applies to jurisdiction (P1001) for the organisation, or have P101 qualifiers location (P276) or even located in the administrative territorial entity (P131). Or should Germany be a field of work (P101) itself? I've seen all of these used. My preference is a location (P276) qualifier.

Also asked at https://www.wikidata.org/wiki/Property_talk:P101 Vicarage (talk) 08:39, 14 June 2024 (UTC)

Oauth not working for quick statements

I know QS has seen some problems lately and I have seen this before but it seems persistent over 2 days now. Receiving a 403 error on login, no matter what browser. QS itself shows the home screen (which is also not always the case these days). Anyone else seeing this? I suppose I will just wait it out until it works again, as per usual, but I am hoping there might be some quick fix I was unaware of. Thx in advance Jane023 (talk) 09:31, 14 June 2024 (UTC)

I'm experiencing the same issue from I least yesterday.
I opened https://github.com/magnusmanske/quickstatements/issues/55 a few minutes ago. Maybe you can add some useful information there - and the fact that I'm not the only user experiencing this problem may be an useful piece of information for mantainers.
A quick fix would be great, but in https://www.wikidata.org/w/index.php?hidebots=1&hidecategorization=1&tagfilter=OAuth+CID%3A+1776&limit=500&days=7&title=Special:RecentChanges&urlversion=2 it seems that all editions are from a batch started two days ago. Pere prlpz (talk) 10:05, 14 June 2024 (UTC)
Solved https://github.com/magnusmanske/quickstatements/issues/55
Now it works for me. Pere prlpz (talk) 10:10, 14 June 2024 (UTC)
Thanks! It's fixed now for me too. Jane023 (talk) 11:28, 14 June 2024 (UTC)

Multiple constraint violations - identifiers of Abraham added to Ibrahim

https://www.wikidata.org/w/index.php?title=Q1768161&action=history&offset=20240616155553%7C1873416190&limit=100

@Epìdosis: you said you work on "slow cleaning of single-value constraint violations of ISNI (P213);" - maybe you are also interested on other types of Property:P213 constraint violations? Friedrich Kettler (talk) 18:06, 15 June 2024 (UTC)

Yes, I'm interested also in unique-value constraint violations of ISNI for humans; I usually work on Property talk:P213/Duplicates/humans when I have time. For Ibrahim (Q1768161), I have removed some IDs (including ISNI) which pertained to Abraham (Q9181) and not specifically to it. Thanks, Epìdosis 20:45, 15 June 2024 (UTC)

Leap years gregorian dates before Christus

Hi, I wanted to type in "29 feb 1437 before christus"^gregorian calendar there https://www.wikidata.org/wiki/Q4115189#P585 It keeps only with 1st march -1437. Is it a bug or am I wrong? (there is no year 0 and if I follow this logic https://astro101.wwu.edu/a101_leapyear.html#:~:text=Leap%20years%20were%20therefore%2045,out%20of%20every%20four%20centuries 1437BC would be a leap year) ? Bouzinac 💬●✒️●💛 07:42, 16 June 2024 (UTC)

list of headers (beta)

Tool "list of headers (beta)" is not able to recognise few new language codes like igl, kus, bew and dtp. It also can't recognise language codes like dga, gpe, fat, gur, pcm, fon, guw and blk. All these languages are recognised by released version of tool. Who could fix it? Eurohunter (talk) 12:13, 16 June 2024 (UTC)

Double check Q76357807 and Q26857651

John Gordon (Q76357807) and John Gordon (Q26857651) seem to be about the same person and should probably merged. I want a second opinion though, since my proof is an identifier I have applied myself and approximate date of birth. Could someone check it for me? Darellur (talk) 12:28, 18 June 2024 (UTC)

I merged the items; Q76357807 (based on https://www.thepeerage.com/p70972.htm#i709713) and Q26857651 (based on https://www.historyofparliamentonline.org/volume/1754-1790/member/gordon-sir-john-1707-83) describe the same person. Peter James (talk) 21:13, 19 June 2024 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Matěj Suchánek (talk) 12:21, 22 June 2024 (UTC)

Slow menu

Why is whole menu working so slow at Wikidata today? Eurohunter (talk) 18:38, 18 June 2024 (UTC)

What menu? --Matěj Suchánek (talk) 05:47, 19 June 2024 (UTC)
@Matěj Suchánek: Whole page loadings but It's okey now. Eurohunter (talk) 17:52, 20 June 2024 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Matěj Suchánek (talk) 12:21, 22 June 2024 (UTC)

Special:Preferences -> Internationalisation -> Set a local exception for this global preference.

Until now, I could chose/change standard languages (here: English, German, American English and Alemannic). I had to change/replace American English and Alemannic with every new login (!) with languages (French and Italian) what I prefer for working beside of German and English. Annoying, but so what. Now I can't make this replacement anymore. Does anybody has the same or a similar problem?

Working with FF 115.12.0esr AnBuKu (talk) 19:21, 20 June 2024 (UTC)

Stop. Now it work again... curious. Sorry for disturbing AnBuKu (talk) 19:22, 20 June 2024 (UTC)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. --Matěj Suchánek (talk) 12:20, 22 June 2024 (UTC)

Qualifiers for Indicating Orthography

Hi, is there any property to be used as a qualifier for indicating orthographic usage distinctions?

For example, the name of Meinohama (Q11447357) has historical kana orthography (Q1142552) めひのはま and modern kana usage (Q2572881) めいのはま; currently, this is expressed as applies to part (P518)historical kana orthography (Q1142552) and applies to part (P518)modern kana usage (Q2572881) qualifiers for the respective name in kana (P1814) statements. I’d expect there to be a more fitting qualifier than applies to part (P518).

This issue isn’t necessarily specific to Japanese; there are several languages where orthographic conventions have changed over time. In German, for example, some spelling rules (primarily regarding the use of ß vs. ss) were changed some 20–25 years ago (though I don’t know whether there are any items here where both a traditional and a new spelling are represented) and I’ve heard there has been something similar in Danish (regarding aa vs. å). I don’t know whether Norwegian (nynorsk/bokmål) or Greek (dimotiki/katharevousa) are comparable as well. --Data Consolidation Officer (talk) 12:07, 16 June 2024 (UTC)

I don't know about qualifiers, but for German, if you need to explicitly state that something uses pre-reform orthography, monolingual text statements can use the language code de-1901. For Norwegian, Bokmål is nb and Nynorsk is nn, we don't normally use no. - Nikki (talk) 10:34, 17 June 2024 (UTC)

Wikidata - ongoing automated

Does Wikidata have functionality to allow synching of databases similar to EDI and automated interfaces,

The functionality I am used to is that there is

  • At Origin : a trigger job waiting for a change, and creates a change
  • Data cleansing - rules, error handling
  • Mapping- a mapping tool of Origin to Target, reuse of maps from the same system, mapping version, envelopes with sequence numbers,
  • Transmission - path, passwords, encryption, confirmation of receipt, checksums
  • At Target - transmission triggers upload into target, error checking
  • Error checking that database matches

Wakelamp (talk) 03:22, 17 June 2024 (UTC)

List of all language codes

Is there a list of all language codes on Wikidata? I remember there was such a list, but I forgot the name. Eurohunter (talk) 13:27, 16 June 2024 (UTC)

Since you mentioned tools in the thread above I'm going to assume you specifically want the Wikimedia language codes and not any other code such as ISO 639 ones. To get a guaranteed up to date list of the languages you have to use the API: https://www.wikidata.org/w/api.php?action=query&format=json&meta=languageinfo&formatversion=2&liprop=code%7Cautonym%7Cname Recommend caching that for 24 hours in your tool as the data doesn't change often. Infrastruktur (talk) 14:06, 16 June 2024 (UTC)
Also see for example:
which returns a list of unconnected articles per language version. M2k~dewiki (talk) 16:57, 16 June 2024 (UTC)
Wikidata:Project chat/Archive/2024/02#h-List of codes of languages-20240217180000. --Matěj Suchánek (talk) 18:14, 16 June 2024 (UTC)
@Infrastruktur:, @M2k~dewiki:, @Matěj Suchánek: I'm pretty sure there was another well-formated list of all language codes summed in table at Wikidata or Wikimedia similar to this list. Eurohunter (talk) 21:04, 16 June 2024 (UTC)
There is Special:SiteMatrix too, but not all languages have wikis. And not all languages are listed e.g. Bokmål (Q25167). Infrastruktur (talk) 21:09, 16 June 2024 (UTC)
What do you actually want, language code statements on items for languages, languages which have a Wikimedia project, languages with an interface translation, languages supported by Wikidata for labels (or for monolingual text or lexemes, which are separate lists), or something else? - Nikki (talk) 10:12, 17 June 2024 (UTC)
@Nikki: @Infrastruktur: I remember there was a simple list of all possible Wikidata language codes, including Serbian latin (sr-el) or Serbian cyrylic (sr-ec) etc. Eurohunter (talk) 17:21, 17 June 2024 (UTC)

Weekly Summary #632

 
Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-06-17.

Discussions

Events

  • Looking ahead
    • Lexico Days 2024 is coming up. June 28 - 30, there will be a packed programme of presentations, discussions and workshops on Lexicographical data. This is an online event.
    • Wikidata Workshop for Botanists at the XX Intl. Botanical Congress, July 21 - 27, 2024, Madrid, Spain.

Press, articles, blog posts, videos

Tool of the week

Other Noteworthy Stuff

Newest properties and property proposals to review

You can comment on all open property proposals! Did you know?

Development

  • EntitySchemas: We are preparing for the rollout of the new datatype to link to EntitySchemas in statements.
  • Wikibase REST API:
    • We are continuing the work on the route for modifying an Item (phab:T342993)
    • We are working on improving errors and error messages in the API
  • Query Service UI: We fixed a bug. The example dialog was empty and not showing any examples (phab:T366871)
  • We changed the datatype of two Properties to external ID as requested (phab:T367174)

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

Steam Deck unsupported games

Are you ok with if I started adding unsupported (Q117413406) to Steam games?

I need a tool or something that will help me to not see unsupported Steam Deck games in this query:

https://query.wikidata.org/querybuilder/?uselang=en&query=%7B%22conditions%22%3A%5B%7B%22propertyId%22%3A%22P1733%22%2C%22propertyDataType%22%3A%22external-id%22%2C%22propertyValueRelation%22%3A%22regardless-of-value%22%2C%22referenceRelation%22%3A%22regardless%22%2C%22value%22%3A%22%22%2C%22subclasses%22%3Afalse%2C%22conditionRelation%22%3Anull%2C%22negate%22%3Afalse%7D%2C%7B%22propertyId%22%3A%22P8956%22%2C%22propertyDataType%22%3A%22wikibase-item%22%2C%22propertyValueRelation%22%3A%22regardless-of-value%22%2C%22referenceRelation%22%3A%22regardless%22%2C%22value%22%3A%22%22%2C%22subclasses%22%3Atrue%2C%22conditionRelation%22%3A%22and%22%2C%22negate%22%3Atrue%7D%5D%2C%22limit%22%3A100%2C%22useLimit%22%3Atrue%2C%22omitLabels%22%3Afalse%7D

If this is ok, then I'd also add to my query and without compatible with matching unsupported (Q117413406). Now about games that don't feature a Steam Deck tag at all on their steam page, I don't know how I would deal with that. Tips welcome. SuperUltraHardCoreGamer (talk) 20:37, 17 June 2024 (UTC)

What Wikidata property are you using? — Martin (MSGJ · talk) 21:14, 17 June 2024 (UTC)
I'm not using a value in my query, although I figure that I need to use the Steam Deck (Q107542665) value and then also add a qualifier, but I don't know if the Query Builder supports qualifiers. SuperUltraHardCoreGamer (talk) 21:19, 17 June 2024 (UTC)
It sounds like you want to use compatible with (P8956) property to indicate a game is not compatible with some hardware. That seems like a very poor model. William Graham (talk) 21:17, 17 June 2024 (UTC)
Well, do you consider yourself an expert in the field? I need all the help I can get. You own perhaps a Nintendo Switch, Steam Deck, a lot of similar hardware? SuperUltraHardCoreGamer (talk) 21:20, 17 June 2024 (UTC)
If my guess of your intended modeling is correct (you still haven't explained it well), then that it would create a situation where people doing a basic query for compatible with some hardware (i.e. Steam Deck) would get a bunch of values that weren't compatible -- the exact opposite of what they were querying for. William Graham (talk) 21:27, 17 June 2024 (UTC)
I don't understand what you are saying but I'm here to edit and contribute. I think that's what I'm doing. I'm taking from your response you wouldn't like "unsupported" being added so I'll refrain from that. Hope this is what you want. I got what I wanted from my interaction with you and thank you for providing a response. SuperUltraHardCoreGamer (talk) 10:29, 18 June 2024 (UTC)
being an expert here has very little to do with owning a console. BrokenSegue (talk) 02:41, 18 June 2024 (UTC)
Yes, I realized the error of my argument. I think that I will continue with more edits and less talking. My final conclusion is that the topic of whether unsupported (Q117413406) should be added or not, there is no easy solution to that. Perhaps even the existence of the Steam Deck rating system itself is seen as problematic. I am thankful that I got a better idea about whether to add unsupported or not to items. I think at this stage adding them, an editor would have to be very sure about what they are doing. I'll continue with adding playable and verified to games and I will not add unsupported games to any item and I hope that this is considered a contribution. I still feel welcome to edit here. If someone would still like to discuss anything please do so only if you think it will help me to improve things. SuperUltraHardCoreGamer (talk) 10:41, 18 June 2024 (UTC)

  Notified participants of WikiProject Video games

Thank you for bringing this up. Unfortunately for games that are not compatible with Steam Deck there is no accurate modeling yet, although there has been an attempt to create a property that is not suitable in this case as it would be too specific, however there are some participants (including myself) who wouldn't mind to reopen proposal for the inverse property. Regards Kirilloparma (talk) 02:20, 18 June 2024 (UTC)

[BREAKING Change Announcement] Upcoming Changes to Wikibase: new EntitySchema data type

Hi everyone,

This is a breaking change announcement relevant for some Wikibase API users.

What is Changing?

On 2 July 2024, we will enable the EntitySchema data type on Wikidata, and we expect the community to create the first properties with that data type and start using them in statements shortly afterwards. This means that there will be values with the data value type wikibase-entityid containing an EntitySchema ID (with "entity-type": "entity-schema" in the JSON value). However, EntitySchema is not yet a full-featured Wikibase entity type; it is our intention to eventually make it work like other entity types (Item, Property, etc.), but at the moment, using EntitySchema in e.g. the wbgetentities API or Special:EntityData does not work.

Who is Affected?

Code which assumes that IDs found in wikibase-entityid data values can be used with other Wikibase entity APIs may need adjusting.

Other Wikibases instances besides Wikidata are not affected unless they also use the EntitySchema extension and set $wgEntitySchemaEnableDatatype = true.

What You Need to Do

If your code works with statements of arbitrary data types, and looks up entities referenced in values with the data value type wikibase-entityid, you probably want to check that the entity-type is not entity-schema before proceeding. (Note that, if your goal is to display the value, you can instead use the wbformatvalue API for any data type.)

If you use the wbformatvalue API, you should make sure that you also specify the datatype or property parameter (depending on which information you have available; note that specifying both parameters at once is an error). Without this information, not all values can be formatted correctly; in particular, trying to format an EntitySchema value without specifying the datatype or property will result in an error (“An illegal set of parameters have been used”). (Specifying the datatype or property parameter for wbformatvalue has always been advisable, and necessary for some other data value types, but this is the first time it becomes relevant for wikibase-entityid data values.)

As previously announced, the new data type is already enabled on Test Wikidata, so you can try out the behaviour there. (An example item on Test Wikidata with a statement linking to an EntitySchema is human.) If you have any questions or concerns about this change, please don’t hesitate to reach out to us in this ticket (T332157).

Cheers, Lydia Pintscher (WMDE) (talk) 09:23, 18 June 2024 (UTC)

Lexicodays: sign up and contribute to the program

Hello all,

As a reminder, the Lexicodays 2024, online event dedicated to Lexicographical Data on Wikidata, will take place on June 28, 29 and 30, with sessions replicated in different languages and at different times across time zones.

The event will take place both on Zoom and Jitsi, and the access will be free without registration (the access links will be added to the program page). However, if you’re planning to join, we invite you to add your username to the Participants page.

We also remind you that you can contribute to the program until June 20th by adding a proposal to the talk page. You’ll find more information here. We are particularly interested in introductions to Lexicographical Data in different languages, and discussions run by community members on how to improve modelling and documentation in a specific language. You can also present tools or Lexeme usecases.

If you have any questions, feel free to reach out to Léa (Lea Lacroix (WMDE)) or Raisha (Raisha (WSC)).

We’re looking forward to seeing you at the Lexicodays! Lea Lacroix (WMDE) (talk) 10:27, 18 June 2024 (UTC)

Translated books

Should Q126720414 and The Problem of Pain (Q4179147) be merged? It's the same book, just translated into different languages. WhatamIdoing (talk) 15:25, 18 June 2024 (UTC)

No, the items should not be merged. Wikidata have separate items for the various translations and editions of books. You can see one of the items is an edition or translation of (P629) of the other. One item is instance of written work and the other is instance of version, edition or translation. Infrastruktur (talk) 15:30, 18 June 2024 (UTC)
Thanks. WhatamIdoing (talk) 15:45, 18 June 2024 (UTC)

Competence is required issue for prolific editor

I'm a little frightened to see that Буквы (talk • contribs • logs) has over 40,000 edits here, as I find many of their edits to be counterproductive. Issues include use of very poor references, adding links via YouTube video ID (P1651) and URL (P2699) inappropriately to items, linking to copyright violations, and confusing the basic membership properties. I'm hoping someone here has the capability to mentor this user and/or review their edit history. Daask (talk) 12:35, 18 June 2024 (UTC)

Ignoring feedback given on their talk page suggests they are un-mentorable. Infrastruktur (talk) 14:36, 18 June 2024 (UTC)
not responding to feedback is blockable imo. BrokenSegue (talk) 18:06, 18 June 2024 (UTC)
Reading their page makes me think an indef block is needed. Ymblanter (talk) 18:36, 18 June 2024 (UTC)
Well, since they have no prior blocks at least they deserve a warning, so I left a stern one on their talk page. Let's just keep an eye on them for now. Infrastruktur (talk) 06:16, 19 June 2024 (UTC)

Get all values of a Wikidata property from page history

I would like a list of all all values that have every been set for a particular property on a particular entity, specifically Property:P4861#P1630. Is there a query or a tool that can retrieve this information so I don't need to dig through the page history of P4861? This seems like a useful tool to create if not... 15:44, 18 June 2024 (UTC) Daask (talk) 15:44, 18 June 2024 (UTC)

There is a poor man's solution to this. Pressing Ctrl+F on the page history enter "P1630" and make sure "Highlight all" is checked. Values from edit comments might be truncated but at least they aren't hard to retrieve. Infrastruktur (talk) 12:49, 19 June 2024 (UTC)

Biological sequence

Hello everyone,

I am doing some work on inner consistency on Wikidata. One of the items that created the most issues about disjointness was biological sequences. I invite anyone interested to join that conversation here: Talk:Q3511065

Also, I don't know much about different communities on Wikidata, so I would love it if you could forward this to relevant communities. Thanks! Egezort (talk) 07:04, 19 June 2024 (UTC)

@Egezort: I don't know anything about this specific item, but in general if you want to significantly change an item's meaning (or clarify a meaning that may be ambiguous) it would be good practice to "ping" those who have made edits to the item, and at least a sampling of those who have created objects that reference the item (see "What links here" for a list). Also if any Wikiprojects are relevant - in this case perhaps there are some related to genes or other biological entities - they should be contacted. ArthurPSmith (talk) 21:19, 19 June 2024 (UTC)

Unify these two wikidata page of Kafir and Kufr

Please unify these two page of kafir (Q629608) and Kufr (Q13452658). 103.230.106.15 13:01, 21 June 2024 (UTC)

  Not done: These are two different concepts. "Unbeliever", referring to a person, vs. "unbelief", referring to the concept of not believing. — Huntster (t @ c) 17:16, 21 June 2024 (UTC)
Additionally, the items can't be merged because there are wikipedias with two different articles for those two concepts (like azwiki and ukwiki).--Pere prlpz (talk) 19:44, 21 June 2024 (UTC)

Complete sets

Is there a way to represent and to query for complete sets for situations like the following? I want to know what securities (and/or what companies) are in the S&P 500. If I query "SELECT distinct ?company ?companyLabel WHERE { 

 ?company wdt:P361 wd:Q242345.
 SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }

}" then I get 530 results. I want either 503 (securities) or 500 (companies) results. Is there really no way to record that X is the complete list of all securities/companies in the S&P 500 as of June 20, 2024? I don't want to have to do a complicated query for this sort of thing, though if there's an easy way to adjust the query that is not fragile it might be helpful. Relying on updates of the individual items is not reasonable, though.

Basically the same question with regard to recording data. I can get a list of the 500/503 companies/securities currently in the S&P 500. Is there a way to record this as a complete set (in RDF, a bag)? JustHydrogen (talk) 12:37, 20 June 2024 (UTC)

You need to filter out the companies that have been in S&P 500, but are no longer in there. You can do it like this:
SELECT distinct ?company WHERE {  
?company p:P361 ?s.
?s ps:P361 wd:Q242345.
FILTER ( NOT EXISTS { ?s pq:P582 ?end. } )
}
However, there are still to many companies in the result. I guess, there are some companies with outdated statements. --D3rT!m (talk) 17:50, 20 June 2024 (UTC)
Yeah, relying on end time is problematic. It's hard to find that information, while it's easy to find which securities are currently part of the index. Maybe end time can be set to unknown or precision can be set to "century" or "millenium"? JustHydrogen (talk) 18:26, 20 June 2024 (UTC)
I would recommend using unknown value Help rather than extremely broad precisions for something like this. Precisions are not supported in the interface for the query service, and the vast majority of queries that fetch dates use the wrong predicates (such as pq:P582, which loses all precision information, instead of pqv:P582, wikibase:timeValue and wikibase:timePrecision). There are other qualifiers like earliest end date (P8554) and ‎latest end date (P12506) that can be used to describe possible ranges with a lot more flexibility. - Nikki (talk) 09:25, 22 June 2024 (UTC)

Removing redundant 'spamblacklistlog' right from Wikidata-staff

Hi, the spamblacklistlog flag is automatically granted to all the registered users. I noticed that the wikidata-staff usergroup still has it. Can we remove it from them (since they already have it as registered users)? I'd like to point out that nothing changes for those who are part of this usergroup :) Thanks! Superpes15 (talk) 11:23, 21 June 2024 (UTC)

  Support, follows up gerrit:405670 Lucas Werkmeister (WMDE) (talk) 13:25, 21 June 2024 (UTC)
  Comment This could also apply to en:WP:Edit filter helpers (T175684), if I’m not mistaken :) Lucas Werkmeister (WMDE) (talk) 13:28, 21 June 2024 (UTC)
@Lucas Werkmeister (WMDE): Yep yep! I opened this thread after T367683 (so I'll do both in a single patch) :D Superpes15 (talk) 16:16, 21 June 2024 (UTC)
  Support --Matěj Suchánek (talk) 12:20, 22 June 2024 (UTC)

Media rating information

I'm in the need of a way to represent media rating information. For example the rating shown at allsides.com. I propose we represent this as:

assessment
  AllSides Media Bias Rating edit
assessment outcome left-wing
test score -1.3
point in time June 5, 2024
0 references
add reference


add value

Does this make sense? I'm not sure if there are relevant wikiprojects on wikidata that would care about this. @Hearvox: who I believe will care.

BrokenSegue (talk) 03:04, 22 June 2024 (UTC)

I think this makes sense, it's a pretty neat visualisation. I think that there should be a constraint that it can't be with 0 reference. This is both due to it being sensitive information, and also it should be easy to do a reference because the source of information is readily available. Egezort (talk) 06:55, 22 June 2024 (UTC)

Olivetti Valentine Q3881837

How can I indicate two sets of dimensions for the Olivetti Valentine (i.e., both with and without its hard-shell case, which is an integral feature of the design of the object itself)? The source for the information is an entry on the Smithsonian site (see: "Dimensions"). How should this data be entered here? Cheers, Cl3phact0 (talk) 12:22, 23 June 2024 (UTC)

@Cl3phact0: maybe you could enter both sets of dimensions and qualify one set with applies to part (P518) physical container (Q987767) (or similar) BrokenSegue (talk) 14:58, 23 June 2024 (UTC)
I feel like we need an item like "carrying case" that's a little more specific than physical container (Q987767). "container made for carrying objects"? — Huntster (t @ c) 15:28, 23 June 2024 (UTC)
Thank you. I've made the addition using physical container (Q987767) for the time being. Please let me know if there is a better qualifier and I will amend. -- Cl3phact0 (talk) 17:24, 23 June 2024 (UTC)
@Cl3phact0: created carrying case (Q126890836) and added it to Olivetti Valentine (Q3881837) along with a couple of other updates. — Huntster (t @ c) 20:07, 23 June 2024 (UTC)

Thank you both. Another question: Would adding a zero decimal place and using "millimetres" be preferable (per this example) for the "Unit (optional)" information field? -- Cl3phact0 (talk) 16:27, 23 June 2024 (UTC)

@Cl3phact0: I would use the given measurements, no decimal. "100 mm", "330 mm", and "345 mm". Nevermind, I see what you mean. No, using centimetres is fine. — Huntster (t @ c) 17:20, 23 June 2024 (UTC)

Bot blocked?

Hello,

I'm the maintainer of MystBot (talk • contribs • logs) and it seems the bot is now read-only. I tried to find why without success. Can someone know how to check why my bot is now in readonly?

Edit: to add informations, my issue is when I try to interact trough the API. I tried a Bot password and an OAuth 2 token, with high-volume access (bot), Edit pages, Edit protected pages and create, edit and move pages. But everytime I got the message "You do not have the permissions needed to carry out this action.".

Thanks, Myst Myst (talk) 21:18, 21 June 2024 (UTC)

@Myst: looking at the logs I'm not seeing anything suggesting anything was done. no idea. BrokenSegue (talk) 02:51, 22 June 2024 (UTC)
Does changing the User Agent string from "Updating French Population" to something that identifies the operator help? E.g. "MystBot - Updating French Population (User:Myst)". If you run stuff from Wikimedia infrastructure they are probably a bit stricter about this. Infrastruktur (talk) 08:35, 22 June 2024 (UTC)
I found the issue, it seems there's a shadow ban for GitHub IPs. I tried to work from GitHub Codespaces and got the error message. I copied the same code on my computer and got no issue. I hope this will help others. Thanks for your messages @BrokenSegue and @Infrastruktur . Myst (talk) 09:05, 22 June 2024 (UTC)
oh we could maybe make your account ip ban exempt? BrokenSegue (talk) 14:32, 22 June 2024 (UTC)
Hello, Thanks but I don't think it's necessary. It was only because I tried to work remotely and gh codespace was a good way to do it. I've setup my own solution so the issue won't appear again. Myst (talk) 11:41, 24 June 2024 (UTC)

Lexicodays: join the event on June 28-30 - Lexicodays: Ayo bergabung dalam acara pada 28-30 Juni!

- Indonesian version below -

Hello all,

The Lexicodays 2024, online event dedicated to Lexicographical Data on Wikidata, will take place this week, on June 28, 29 and 30!.

The event will take place both on Zoom and Jitsi, and the access will be free without registration (the access links will be added to the program page). However, if you’re planning to join, we invite you to add your username to the Participants page. The event will include sessions replicated in different languages and at different times across time zones.

Here are a few interesting sessions that you will find in the program:

  • Introduction to Lexicographical data and how to model words in Wikidata
  • Discussions about modelling proverbs, sayings, compound words and predicates
  • Presentation of some useful tools
  • Modelling sessions and editathons in various languages of Indonesia
  • Introduction to Abstract Wikipedia and how it will work together with Lexemes
  • Exploring how to generate sentences with Lexemes

Note that most sessions will be recorded and available after the event.

If you have any questions, feel free to reach out to Léa (Lea Lacroix (WMDE)) or Raisha (Raisha (WSC)).

We’re looking forward to seeing you at the Lexicodays!

---

Halo, semua!

Lexicodays 2024 adalah sebuah acara daring yang didedikasikan untuk Data Leksikografis di Wikidata. Lexicodays akan diselenggarakan pada pekan ini, tanggal 28, 29, dan 30 Juni 2024!

Acara ini akan berlangsung melalui platform Zoom dan Jitsi, dengan akses yang terbuka tanpa registrasi khusus (tautan akses akan tersedia pada halaman acara). Meski demikian, jika Anda berencana untuk bergabung, kami mengundang Anda untuk menambahkan nama pengguna Anda ke halaman Peserta. Dalam Lexicodays, kami akan membawakan sesi yang direplikasi ke dalam berbagai bahasa dan berbagai sebaran zona waktu.

Berikut adalah beberapa sesi menarik yang akan Anda temukan di dalam acara ini:

  • Pengantar data leksikografis dan cara memodelkan kata-kata di Wikidata
  • Diskusi tentang pemodelan peribahasa, pepatah, kata majemuk, dan predikat
  • Paparan tentang beberapa alat bantu yang berguna
  • Sesi pemodelan dan penyuntingan dalam berbagai bahasa di Indonesia
  • Pengenalan Abstract Wikipedia dan bagaimana hubungannya dengan Leksem
  • Mengeksplorasi cara membuat kalimat dengan Leksem

Kami akan merekam sebagian besar sesi, dan rekaman sesi dapat diakses setelah acara berlangsung.

Apabila Anda memiliki pertanyaan, jangan ragu untuk menghubungi Léa (Lea Lacroix (WMDE)) atau Raisha (Raisha (WSC)).

Kami sangat menantikan kehadiran Anda di Lexicodays! Lea Lacroix (WMDE) (talk) 10:23, 24 June 2024 (UTC)

Removal of ISNI by admin

https://www.wikidata.org/w/index.php?title=Q37594&diff=prev&oldid=2179820220 - what is this about? User:Epìdosis removed a valid ID. This breaks database-connections, e.g. via OpenRefine. It might be OK for some secondary IDs, but for ISO-IDs that are widely used this causes much more trouble. Especially since it is a fixed lenght ID with no known widely used overlap, i.e. it can be used in regular search fields to find an item (not so for the IDs by e.g. DNB/GND, NTA). Friedrich Kettler (talk) 00:46, 15 June 2024 (UTC)

Reported at Wikidata:Administrators'_noticeboard#Removal of ISNI by User:Epìdosis Friedrich Kettler (talk) 00:50, 15 June 2024 (UTC)

Did you try talking to the other user on their talk page? William Graham (talk) 01:52, 15 June 2024 (UTC)
Hi! This is part of a slow cleaning of single-value constraint violations of ISNI (P213); if an ID has been redirected and has no source, or as only source itself (stated in (P248)International Standard Name Identifier (Q423048)), I usually remove it in order to gradually reduce the amount of items having 2+ ISNIs; if the ISNI is sourced, i.e. it has been imported on Wikidata from an external source, I write to the external source, I wait until it has been corrected in the external source and then I remove it from Wikidata. Keeping clear the lists of constraint violations has multiple beneficial effects for the checking of data quality (cf. par. 3 and 5.2). As of now I have not received any complaint in my talk page for these removals. Anyway, I have no problem in stopping this cleaning if it lacks consensus; let me know. Epìdosis 07:36, 15 June 2024 (UTC) P.S. "This breaks database-connections" is not completely true: a database making matches with Wikidata through ISNI can just make two passages, the first retrieving ISNI in order to check if some ISNIs have been redirected and obtain from ISNI the new ISNIs, and the second retrieving Wikidata in order to check the existence of new ISNIs. --Epìdosis 07:39, 15 June 2024 (UTC)
Both should remain if correct; one of the identifiers should have deprecated or preferred rank (I have been using deprecated rank for redirects as redirect (Q45403344) has instance of (P31):Wikibase reason for deprecated rank (Q27949697) but this conflicts with Help:Ranking which says deprecated rank is for statements that were never correct). Peter James (talk) 11:42, 15 June 2024 (UTC)
So better move to a new property ISNI redirect. But there are also withdrawn identifiers, I deprecated those, since I couldn't verify them. Friedrich Kettler (talk) 13:47, 15 June 2024 (UTC)
@Epìdosis:
  1. How many ISNI redirects have you removed?
  2. "has no source" - this is common for external identifiers
Yes, cleaning up constraint violations is great. How about storing redirects in a new property ISNI redirect, so there is a cleaner P213 and in the new property also redirect targets can be mentioned.
/"This breaks database-connections" is not completely true/ - it is. Try to connect to Wikidata from an ISNI that you have removed from Wikidata - fail! Friedrich Kettler (talk) 13:45, 15 June 2024 (UTC)
The idea of having a specific property for redirected ISNIs might have sense, but I think that the same is not done for any other property as of now, so it would probably need a broader discussion. For the other questions, I need more time to formulate a complete answer but I will have only a few minutes online in the next two days and half; I surely will do it as soon as possible. Good night, --Epìdosis 20:54, 15 June 2024 (UTC)
Another solution would be to have a new qualifier "incoming redirected ID", so the values can directly be attached to the redirect target. The general search will still find them. For ISNI, or any other systems with little overlap in ID values with values from other systems, this would be helpful. Friedrich Kettler (talk) 21:30, 15 June 2024 (UTC)
The property doesn't have a single value constraint though. - Nikki (talk) 10:07, 22 June 2024 (UTC)
Premise: in principle, the issue of how to manage obsolete (especially redirected) external IDs should be addressed through a general policy, but the RfC opened in 2020 became stalled in a few months and is far from reaching any pratical conclusion.
So, in general I think the three main reasons for which we could be interested in keeping obsolete IDs are: 1) historical purposes 2) help in matching with other IDs (especially for highly used IDs, such as VIAF and ISNI) and 3) avoid readdition. The main counter-reasons to the above reasons are: 1) obsolete IDs could be extracted from page histories, and anyway keeping track of the historical evolution of external databases is not a vital scope of Wikidata; 2) if the external database allows converting redirected IDs into valid IDs, Wikidata can ignore redirected IDs (because, if a database A wants to use redirected IDs taken from database B to match with Wikidata, can first use database B to convert its redirected IDs to valid IDs and then use valid IDs to match with Wikidata) and 3) if we make sure that the occurrences in external database of redirected IDs are all fixed, the readdition becomes reasonably impossible (consequence: if an ID has no source, we have no proof that it has any external use, so its readdition is improbable). Further reasons against keeping obsolete external IDs are expressed in the (unanswered) comment by Ivan A. Krestinin in the RfC. I would finally add that there is no consensus about how to keep obsolete IDs, since the most common use is deprecating redirected/obsolete IDs but this is in contrast with the norms prescribing to use deprecation only for never-valid data.
ISNI (P213), like VIAF ID (P214), has no single-value constraint mainly to avoid that users, in order to solve constraint violations, just remove the less relevant IDs instead of keeping them at least until the get merged. However, despite the absence of the constraint, most of the cases in which ISNI has 2+ IDs for the same persons should be effectively fixed in ISNI, since ISNI prescribes keeping multiple IDs only for persons with pseudonyms and in no other cases.
Anyway, in the next months I have in program to work mainly on ISNI unique-value constraint violations and only afterwards return systematically on cases of 2+ ISNIs in the same item; I hope that in the meanwhile some clearer consensus on the topic will have emerged. --Epìdosis 14:00, 22 June 2024 (UTC)
For ORCID which is a similar identifier for individuals I have been doing considerable cleanup by:
if the ORCID is just on the wrong person, move it to the correct one (often happens due to merges that need to be reverted)
if the ORCID is a redirect, set rank to deprecated, with qualifier reason for deprecated rank (P2241) redirect (Q45403344)
if it is just wrong, set rank to deprecated with qualifier reason for deprecated rank (P2241) refers to different subject (Q28091153)
I assume this procedure would be preferable for ISNI also. Identifiers should not be just deleted. ArthurPSmith (talk) 11:43, 16 June 2024 (UTC)
  1. Bad design. If it is "just wrong" move it to a new person. Otherwise what is the logic? Most IDs are wrong on millions of items, why would it stay there?
  2. Regarding using deprecated rank for a working redirect - why? It is still working and correct, opposed to conflated. Help:Ranking#Deprecated_rank "The deprecated rank is used for statements that are known to include errors" - are you editing against community consensus?
"I assume this procedure would be preferable for ISNI also." - no it wouldn't. ISNI that are wrong
  1. should be removed from the item where they are wrong, because it pollutes the item and
  2. moved to a correct item, so one can find out why it is wrong on the other
A human can have several ISNI, because they are identifiers for "identities", not for humans. If an ISNI is only marked as redirect one will not be able to see to which identity the value belongs. So one would need a qualifier "redirects to" and insert there the target value. Elisabeth Pommern (talk) 21:45, 18 June 2024 (UTC)
@ArthurPSmith: This is probably a bit of a derail, but in my experience when items with ORCIDs have a name that doesn't match the ORCID name, I have to to verify/update the object named as for every article with an author statement by reviewing the DOI external identifier. If a lot of them are mixed up with one other person, it's likely a severe enough conflation that requires treating that item as worthy of deletion, and then creating new item or items for the conflated persons. The number of older batch matching that didn't convert the author name string text into an object named as text makes those conflations a lot harder to catch and repair. (Even bigger derail) I use your tool Author Disambiguation and was wondering if there was a way to filter author works by ones missing an object named as. William Graham (talk) 22:20, 18 June 2024 (UTC)
@William Graham: yeah, I've been doing a lot of cleanup like that. I use a WDQS SPARQL query to find author works missing "object named as", but I agree it would be a helpful thing in the tool (right now there's an easy way to get a list of articles with a specific "object named as" value for the author, but not to get a list of ones without that qualifier). I'll look into it! ArthurPSmith (talk) 01:50, 19 June 2024 (UTC)
If you set the redirect to deprecated, you're saying the redirecting ID is wrong. If it's correct but not the preferred ID because it's a redirect, then you should set the non-redirecting one to preferred rank instead. And if that causes constraint violations, the constraints should be fixed (probably by replacing "single value" with "single best value"). - Nikki (talk) 10:19, 22 June 2024 (UTC)

All library-land identifiers (VIAF, ISNI, ORCID, LCCN, etc) are NAME identifiers not person identifiers. If a person writes (or wrote) under pseudonyms, an identifier (with gender and other metadata) should be minted for each. This is the way authority control works in the Western library tradition. Linking them to people in wikidata was a data modelling choice which we continue to pay for, they should have been linked to a Q82799. Stuartyeates (talk) 02:16, 25 June 2024 (UTC)

Wikidata weekly summary #633

 
Here's your quick overview of what has been happening around Wikidata over the last week.
This is the Wikidata summary of the week before 2024-06-24. Please help Translate.

Events

  • Past: The 200th online Wikidata meetup in Swedish was held.
  • Upcoming: Lexicodays, online event dedicated to Lexemes on Wikidata, will take place on June 28-30. It takes place across time zone and both in English and Indonesian. Check the program and find the access links on the event page.

Press, articles, blog posts, videos

Tool of the week

  • Wikidata in Prometheus - Prometheus is a non-commercial image archive for art and cultural studies. It hosts images from a variety of image and media databases and now works can be connected with Wikidata.
  • New Mix'n'match feature: For lists of (full or auto) matches where both the MnM entry and the Wikidata Item have coordinates, it now shows the distance between them in the description. (source)

Other Noteworthy Stuff

  • The Wikidata development team at Wikimedia Deutschland is planning a brief survey to understand the various ways people contribute to the project and identify user contribution patterns. A request has been made for a CentralNotice banner to deploy the survey to a broad audience. Your feedback, comments, and questions on this request are welcome: m:CentralNotice/Request/Wikidata Community Survey 2024
  • The second iteration of the Wikidata:Open Online Course will begin from July 1 until August 11. 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

You can comment on all open property proposals!

Did you know?

Development

  • [Breaking Change Announcement] Upcoming Changes to Wikibase: EntitySchema data type
  • EntitySchemas: We prepared for the release of the new data type to link to EntitySchemas in statements on July 2nd.
  • Mul language code: We picked up the remaining issues before enabling it by default on Wikidata
  • Wikibase REST API:

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

Mix'n'Match scraper help

I'm completely bemused by the scraper feature in Mix'n'Match; would anyone care to kindly walk me through the process for scraping [2] for Avibase person ID (P12837)? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:03, 24 June 2024 (UTC)

Adding USDA Census of Agriculture data to the WIKI platform

I do outreach for the state of Oregon and am part of UDSA-NASS (National Agricultural Statistics Service). At the end of February 2024, we released the 2022 Census of Agriculture dataset that details Farm demographics, income, expenses, crops and livestock data and much more, at the National, State, and county level if publishable. The Census is done every five years, and I reached out last time to WIKI to try and see if there was an automated way for you to populate this information on your pages. In many rural counties, agriculture is the only industry that provides income to people and there is no data on WIKI pages. It would be ideal to search for "wheat", and be able to see the data at many levels where grown in the U.S., etc.. Our website is https://www.nass.usda.gov/AgCensus NASS makes the Census data available in multiple machine-readable formats through downloadable data sets as well as through web API’s. Loshdav (talk) 21:47, 24 June 2024 (UTC)

what data are you imagining people seeing when they search wheat and on what pages? like do you want this on en:Wheat? or on the pages for these rural counties? BrokenSegue (talk) 23:54, 24 June 2024 (UTC)

Regarding two entities of the same institute

There is Eijkman Institute for Molecular Biology (Q1303680) and Eijkman Molecular Biology Research Center (Q114921293), which refers to the same research institute, but under different ownership (and different name while we're they're moving). Should this be merged or not? Hans5958 (talk) 04:43, 25 June 2024 (UTC)

@Hans5958: the two items should probably be linked by replaces (P1365)/replaced by (P1366). Since they have different names and different owners it seems good to have two separate items. ArthurPSmith (talk) 17:59, 25 June 2024 (UTC)

Voting to ratify the Wikimedia Movement Charter is now open – cast your vote

You can find this message translated into additional languages on Meta-wiki. Please help translate to your language

Hello everyone,

The voting to ratify the Wikimedia Movement Charter is now open. The Wikimedia Movement Charter is a document to define roles and responsibilities for all the members and entities of the Wikimedia movement, including the creation of a new body – the Global Council – for movement governance.

The final version of the Wikimedia Movement Charter is available on Meta in different languages and attached here in PDF format for your reading.

Voting commenced on SecurePoll on June 25, 2024 at 00:01 UTC and will conclude on July 9, 2024 at 23:59 UTC. Please read more on the voter information and eligibility details.

After reading the Charter, please vote here and share this note further.

If you have any questions about the ratification vote, please contact the Charter Electoral Commission at cec@wikimedia.org.

On behalf of the CEC,

RamzyM (WMF) 10:51, 25 June 2024 (UTC)

I'm trying to link the article concerning the medical condition Dysphagia, at the Dutch Wikipedia, to the correct Wikidata entry, 623289. On trying to do this, I'm told that the link to nl Wikipedia's entry for Dysphagia, is already in use at 2599000. Q2599000 contains no other interwiki links, they're all on Q623289. Because I've not done much here before, I don't know how to remove the link from Q2599000, or whether I even should. Would someone please take a look and help me out? I don't want to screw this up! Thanks :) DaneGeld (talk) 18:31, 25 June 2024 (UTC)

Hello,
From my point of view, these two objects should not be merged, nor should the link to nl-article for the journal be changed to the other item for the disorder/symptom. After the article nl:Dysfagie about the disorder/symptom has been written, it could be connected to d:Q623289 M2k~dewiki (talk) 19:39, 25 June 2024 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat/Archive/2024/06&oldid=2194258333"