Wikidata:Project chat/Archive/2021/05

Vandalism

There is continued vandalism on the Q63245258 by IP 8.45.42.147. Posting inaccurate information, spamming, and posting contact information. This is not the first time this has happened request removal of edits by IP and page protection. Darkhumor224 (talk) 17:48, 2 May 2021 (UTC)

probably should report to Wikidata:Administrators' noticeboard though I imagine an admin will come by here eventually. BrokenSegue (talk) 19:47, 2 May 2021 (UTC)

Handled at AN. Bovlb (talk) 22:15, 5 May 2021 (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. Bovlb (talk) 22:15, 5 May 2021 (UTC)

Merge

Item Q14522384 (nl) need to merged with item Q2546987 (ca/de/en/es/fr/it/pt). Probably also a name (title) changed used? (From “Xorret del Catí” to “Xorret de Catí”) With kind regards, Pucky (talk) 15:18, 4 May 2021 (UTC) (PS, if wrong posted here, please remove it to where it belongs! I have really no idea!)

• If you want to try it yourself, the gadget mentioned on Help:Merge is the way to do it. --- Jura 19:47, 4 May 2021 (UTC)

@Jura: thanks for the links. I have succesfully done it by myself. Pucky (talk) 05:52, 5 May 2021 (UTC)

Good to hear. Congrats! --- Jura 09:40, 5 May 2021 (UTC)

This section was archived on a request by: --- Jura 09:40, 5 May 2021 (UTC)

Glasgow Subway - one item or two?

There's a disagreement as to whether Glasgow Subway needs one item or two. Could we get more input here please. The discussion, to date, from Request a Query is:

In other news, how exactly does Glasgow subway line (Q106328343) differ from Glasgow Subway (Q506290)? They seem to be *exactly* the same thing.

Anyways, just check Q2546530#P361 and Q2546530#P81. A subway station should be part of a network on a certain subway line. It happens some subway networks can be one lined only, but network different from (P1889) line. --Bouzinac ^{💬●✒️●💛} 14:39, 30 April 2021 (UTC)

@Bouzinac: Strongly disagree. There is a single thing, calling for a single item carrying a plurality of P31 values. The subway - Glasgow Subway (Q506290) - is the line, per its description "underground metro line in Glasgow, Scotland". There is no good reason to have a discrete items carring the rapid transit railway line (Q15079663) and circle route (Q145179) P31 values, when these can & should be on the Glasgow Subway (Q506290). A station can be part of (P361), and have a connecting line (P81) both pointing to the same item; this being the case, can you suggest any other reason which validates the duplicate you've created? --Tagishsimon (talk) 15:14, 30 April 2021 (UTC)

I'm sorry but they are two different concept. A subway line and a subway network. What happens if Glasgow builds a second subway line? Merkland Street subway station (Q6819640)'s part of (P361) cannot nowadays be Glasgow Subway (Q506290) but connecting line (P81)=Glasgow subway line (Q106328343) still true.

Another example in a very different field : Château Perrier (Q28003614) and Château Perrier (Q22979594). Single concepts should be having their own item. In the Glasgow case, they happen to be "almost" the same but not and connecting line (P81) // part of (P361) be having their correct item --Bouzinac ^{💬●✒️●💛} 15:38, 30 April 2021 (UTC)

@Bouzinac: No. A museum and the building it is housed in are indeed distict things: the museum can be uplifted and taken to a different building. In Glasgow there is a single metro line, Glasgow subway. Call it what you like, the line, the subway, the network are the same thing. In this circustance, a single item suffices, and splitting the item serves no useful purpose. If a second line is ever built, we can revisit the question - but this is not very likely. To repeat, a "network" comprising a single line is the same thing as the single line. Merkland Street subway station (Q6819640) is part of (P361) and has connecting line (P81) Glasgow Subway (Q506290) --Tagishsimon (talk) 16:01, 30 April 2021 (UTC)

Disagree again, sorry. Look at the definition of rapid transit (Q5503) : it is a network and possibly can be running buses, subways, suburban trains, not only subway lines per se. --Bouzinac ^{💬●✒️●💛} 16:05, 30 April 2021 (UTC)

Is the subway as 'connecting line' the same as the subway as a rapid transit network? --Tagishsimon (talk) 17:06, 30 April 2021 (UTC)

To me this feels a lot like the eternal debate over whether an island (Q23442) or archipelago (Q33837) needs a separate entity for the coterminous administrative territorial entity (Q56061) -- as we've been discussing most recently for the Balearic Islands. Me, I would say that a rapid transit system deserves a separate entity for its subway line, even if there's only one of them, because the properties you attach to rapid transit systems are different from those you attach to a subway line. (Systems have employees, lines have stations, etc.) —Scs (talk) 19:45, 30 April 2021 (UTC)

• Agree that they seem to be the same thing, and should be merged. If a second subway line is built then maybe it would be worth splitting, but it seems to have been over 120 years since the last one... Thanks. Mike Peel (talk) 19:47, 30 April 2021 (UTC)
• But a counterargument would be that it seems silly to use two essentially different schemas for single-line versus multi-line rapid transit systems. I think this may add needless complexity for both the people who are inputting data, and extracting it. —Scs (talk) 19:53, 30 April 2021 (UTC)
  • In general, fewer items are better, rather than overcomplicating things. Thanks. Mike Peel (talk) 19:55, 30 April 2021 (UTC)
    • Thing is, we may have dueling complexities here. If I had just written some code for enumerating or cross-referencing, say, a rapid transit's lines and stations, and then discovered that it didn't work in Glasgow due to someone's "helpful optimization" of coalescing the line and the system, I might say, "Why did you make this so complicated?" (Also, I'm afraid the "keep the number of entities to a minimum" ship has well and truly sailed...) —Scs (talk) 20:07, 30 April 2021 (UTC)
      • Agreed with dueling complexities. I understand the 'minimum' ship has sailed overall for Wikidata, given ~100m items, but for individual topics it's still a good rule. Thanks. Mike Peel (talk) 08:50, 1 May 2021 (UTC)

Please do not mix carrots and cabbages . If we wish to list (as there https://w.wiki/3GB4) which subway line(s) has subway stations in the UK (as in other countries), inside the P86, you would have a mix of "line [x] of thisCity subway" and "thisCity subway" which does not clearly help the P86 look clean. Plus... there is a project of a second Glasgow subway line...[1]Bouzinac ^{💬●✒️●💛} 20:00, 30 April 2021 (UTC)

If work actually starts on it, or someone writes a Wikipedia article about it, then maybe OK, but while it's still hypothetical it makes less sense. Thanks. Mike Peel (talk) 08:50, 1 May 2021 (UTC)

Wikidata is a supporting tool for langwikis but has its own existence and its own needs too, per WD:N. --Bouzinac ^{💬●✒️●💛} 10:25, 1 May 2021 (UTC)

Change needed in the formatter URL for the articles in Category:UEFA_player_ID_different_from_Wikidata

The issue:

Visit Altin_Byty as an example, here you will find that the link given in the External Links section in the format -> Altin Bytyçi – UEFA competition record. The link given shows that the page does not exist. This could probably be because UEFA changed their website layout. Now, if you visit the above page's Wikidata item page and go to Identifier section -> UEFA Player ID property value 250138550 this will take you to the correct UEFA page of the player. To solve this issue one of the approaches could be to change the formatter URL on the Wikidata property, and the URL in the enwp template as suggested by Mike_Peel.

Any input for this issue is welcome!

Some other pages that have the same issue: Iran Junior, Abbie Magee, Natasha Flint, Mads Bech Sørensen.--ANU Outreachy (talk) 20:08, 30 April 2021 (UTC)

@ANU Outreachy: This doesn't seem to require any action on Wikidata (since our formatter URL works fine); the only issue is at en:Template:UEFA player. Also, the old and the new links don't have equivalent information; see en:Template talk:UEFA player#Template:UEFA player is broken for more on that. If you come up with a solution, that's the best place to continue. Vahurzpu (talk) 03:46, 1 May 2021 (UTC)

@Vahurzpu:Yes, you are right about Wikidata needing no change. I'll continue this discussion on the page you suggested. Thanks! --ANU Outreachy (talk) 09:16, 1 May 2021 (UTC)

Start day and end day for a political office

I would like to show what day and even what time power is transferred in a political office. We have a place to store the value for the length of a term, I want to show the date the term starts. For some positions it begins on January 1, for some positions January 4, some begin the day of an election. I want to avoid changing the 50 entries from showing say "start_date=1950" to "start_date=January 1, 1950" and have the value stored in the entry for the position. See for instance: Mayor of Bound Brook, New Jersey (Q106370185) vs Talk:Q106370185, I tried "start_date=January 1" for the start date at the entry on the position, but we currently do not allow that. Any suggestions? --RAN (talk) 05:42, 2 May 2021 (UTC)

only thing I can think of involves editing all 50 statements. for many offices hand overs can happen on irregular dates (e.g. death/resignation) or the office can be vacant. maybe use bots/automation? BrokenSegue (talk) 05:56, 2 May 2021 (UTC)

Order of statements

At Help:Statements, I split this into

• Help:Statements#Order of properties and
• Help:Statements#Order of statements for a property

Also, as it was somewhat outdated, I updated and expanded it a bit. Please help by improving it further. --- Jura 14:21, 2 May 2021 (UTC)

Capital letter in ticket name

I need an advice regarding to capital letter in English in a ticket name. I can understand that the description can start without capital letter but in my opinion the name of a ticket should generally start with capital leter. Pleas see tomb of Shimon bar Yochai (Q5371188). I was reverted there but not sure what is the correct. Geagea (talk) 21:50, 30 April 2021 (UTC)

I believe you're talking about labels, then the relevant guidance is in Help:Label. Our convention is that both labels and descriptions should be in "mid-sentence case", so (in English and many other languages) they should not start with a capital letter unless they start with a proper name. In this case, I would say that "tomb" is not part of a proper name, but usage seems to vary. If I'm in any doubt about the capitalization of an item label, my usual recourse is to look in Wikipedia and find mid-sentence usage. For example, en:Tomb of the Unknown Soldier uses "Tomb" whereas en:Tomb of Munmu of Silla uses "tomb". I feel that the former is capitalized because it is a title and would not work as a definite description, whereas the latter (and your example) does work as a definite description. Bovlb (talk) 22:26, 30 April 2021 (UTC)

Thank you for the answer. I understand the logic. It's makes things complicated but probably correct. If I will use the Q-number in Commons in a mid of sentence it should not be with capital letter. Geagea (talk) 23:34, 30 April 2021 (UTC)

@Geagea: If you're using the Q template on Commons, be aware that it has a "capitalization" flag. If you want a Q term to be capitalized, you can use capitalization=ucfirst. Bovlb (talk) 20:10, 2 May 2021 (UTC)

Thanks, it's useful info. Geagea (talk) 20:14, 2 May 2021 (UTC)

Apprentice to ...?

How should we record the name of the craftsperson to whom a person was apprenticed? I've been using student of (P1066) with qualifier <subject has role> "apprentice" (see Q18756897#P1066), but that is not a valid qualifier. Should we add the qualifier, or propose a new property "apprenticed to"? - PKM (talk) 21:17, 1 May 2021 (UTC)

I think "subject has role" has a place with this property so I added it to the allowed qualifiers. --SCIdude (talk) 06:45, 2 May 2021 (UTC)

@SCIdude: thanks! PKM (talk) 18:31, 2 May 2021 (UTC)

Batch-copying labels from one language into another

Yesterday I noticed that Bouzinac is batch-copying English labels into French. Is that the proper thing to do? I argued with him that labels should either be a proper translation, or a French transliteration of the original names when necessary. I bring the issue here for better advice. —capmo (talk) 13:57, 1 May 2021 (UTC)

Do you have sources for French translation of each subway stations (roughly ~13954 items) ? --Bouzinac ^{💬●✒️●💛} 13:59, 1 May 2021 (UTC)

So you're saying that a wrong information is better than nothing? Sorry, I can't agree with that. —capmo (talk) 14:15, 1 May 2021 (UTC)

Copying English don't really seem wrong, or at least no more or less wrong than an invented translation (which one, translations are multiple) or translitteration (same remark). I wouldn't copy labels but now that it's done, I wouldn't remove them either. And if you found some reliable source, then just correct the labels (that's the wiki way for decades, improve bit by bit to make things better). Chers, VIGNERON (talk) 22:35, 1 May 2021 (UTC)

(maybe off-topic) It's not wrong but aren't there more important things to do with a bot? --SCIdude (talk) 06:47, 2 May 2021 (UTC)

it's hard to get people to agree about what's "important" here and I try not to judge. though I agree copying labels seems fairly low value in general (and potentially harmful in some cases) BrokenSegue (talk) 12:02, 2 May 2021 (UTC)

• Mistakes are always possible and anyone is free to correct in Wikidata. There are indeed some questions on subway stations :
  • Should they in fact be translated in proper language ? Eg non-French labels for that République - Beaux-Arts (Q400325)
  • For non-latin languages (Asia, etc) subway stations, getting a translation/transliterration helps the reader get what it is about eg Seonjeongneung^(Q46111) is more readable for a French than 선정릉역 in its own language. And helps correct some subways network, eg https://w.wiki/3Gbn
  • If no sources exists for a translation (eg any travel guide, a french written official subway website, etc), then it's better having enlabel-->frlabel than having nothing in frlabel.Bouzinac ^{💬●✒️●💛}
    • I haven't worked it through to a detailed or formal procedure, but I wish that in many cases, and regardless of a user's language preferences, if an entity has a label in only one language, that label would be displayed. There are plenty of cases -- like, say, subway stations in Paris -- where there really is one (local) name, and it's the name anyone's going to use in any language, and seems pretty pointless to have to represent that situation explitly in the database with N identical labels tagged with N different languages. —Scs (talk) 21:22, 2 May 2021 (UTC)

I'd just like to point out that batch copying labels appears to be the norm with respect to Asturian (@YoaR, Amasuela: (and I more than likely missed a few more people doing this) who have been doing this), and thus the discussion above applies to them as well. Mahir256 (talk) 22:35, 2 May 2021 (UTC)

• I'd like to remind one of drawback not having ownlanguage label is that phenomenon in the watchlist (see image)

Bouzinac ^{💬●✒️●💛} 06:41, 3 May 2021 (UTC)

• The policy we follow (Asturian speakers coming from astwiki) is to use the work's label in its original language: film, song, writing, book, etc., unless that work is translated or dubbed to Asturian. In that case, Asturian title is used as label and the original language title as alias. The same applies, for example, to cities: official name unless there's a trustly reference to an Asturian name. This applies only to latin scripts. YoaR (talk) 06:09, 3 May 2021 (UTC)

Linking item to Wikipedia redirect

Hello, I am trying to link TANF Extension Act of 2019 (Q106504757) to the English Wikipedia redirect page w:en:TANF Extension Act of 2019. However, it does not let me (and appears to be following the redirect and trying to add the target of the redirect). How is this done? Thank you! Tol | Talk | Contribs 18:27, 2 May 2021 (UTC)

@Tol: yeah this is a known bug/limitation. the way to do this for now is to temporarily unredirect the enwiki page, link it and then re-redirect it BrokenSegue (talk) 19:46, 2 May 2021 (UTC)

Ah; thank you! Tol | Talk | Contribs 19:46, 2 May 2021 (UTC)

@Lydia Pintscher (WMDE): It's again me. Any update on redirects? There are few threads about it a month from what I can see. Eurohunter (talk) 08:25, 3 May 2021 (UTC)

Create items for category intersections at Commons? Category:Views from automobiles in Queens, New York City (Q104236177)

There was some discussion about this at Wikidata:Requests_for_deletions/Archive/2021/05/01#Q104236733. Apparently, the creator and the closing administrator think we should have items for category intersections like Category:Views from automobiles in Queens, New York City (Q104236177). Currently, there is no item for "automobiles in Queens".

This could mean we will have items for every category on Commons. Seems odd now that Commons moves away from categories.

@Lymantria, Mike Peel:. --- Jura 09:46, 1 May 2021 (UTC)

Correction: I closed the request because there was a (valid) site link and apart from Jura1 as proposer there was no support for deletion for several months. If discussion is needed, here might be a better place than at RfD. Lymantria (talk) 10:22, 1 May 2021 (UTC)

Personally, I'd expect admins to delete or not based on WD:N. It's fairly Common that there is just a person requesting deletion and the deleting admin having to decide based on WD:N. I don't think a contributor would create an item if they assumed it didn't meet WD:N. RfD isn't a good place to discuss if WD:N should be changed (or not applied). --- Jura 16:22, 1 May 2021 (UTC)

• About category for the view from the item (P8933): the correct value for Q18424#P8933 would be "Views from Queens". Similarly, for Manhattan (Q11299), we end up having not just
  Category:Views from Manhattan (Q106675198), but also:
  • Category:Views from automobiles in Manhattan (Q104433315)
  • Category:Views of the Hudson River from Manhattan (Q106341534)
  • c:Category:Brooklyn skylines from Manhattan
  • c:Category:Brooklyn Heights skylines from Manhattan
  • c:Category:Long Island City skylines from Manhattan
• etc. at Q11299#P8933 --- Jura 16:38, 1 May 2021 (UTC)

"we will have items for every category on Commons" - we're getting there. After all, Commons categories are one of the biggest users of Wikidata information in the Wikimedia projects right now (that I'm aware of). There should be no problem with these items. Thanks. Mike Peel (talk) 17:11, 1 May 2021 (UTC)

Except for that the RFC which lead to the adoption of our notability criteria concluded that such categories are not notable.--Ymblanter (talk) 18:52, 1 May 2021 (UTC)

Which RfC? Are you referring to one that predated the infobox? Thanks. Mike Peel (talk) 11:55, 3 May 2021 (UTC)

I have second thoughts, I think I wrongly read WD:N 1.4.b in connection with category for the view from the item (P8933) I will delete the items. Lymantria (talk) 06:35, 3 May 2021 (UTC)

• Thanks. Category:Views from Manhattan (Q106675198) can be kept (it wasn't listed for deletion, I had made it yesterday when I noticed that we were actually missing the one we should have for P8933). --- Jura 10:45, 3 May 2021 (UTC)
• Restored. I was a bit in a hurry this morning. Lymantria (talk) 12:05, 3 May 2021 (UTC)

@Lymantria: What the...? You could have at least pinged me. These items should be covered by 'the item is used in a Commons-related statement' unless someone removed the links. Never mind, the bot will recreate them next time it runs. Thanks. Mike Peel (talk) 11:53, 3 May 2021 (UTC)

@Mike Peel: My apologies for being to much in a hurry to ping you. I understood this morning that you incorrectly used category for the view from the item (P8933) at Manhattan (Q11299), and that I had not taken from the discussion earlier (while I didn't read it for the first or second time). It concerns views from Manhattan (Q11299), not from vehicles to Manhattan (Q11299). Recreation of course doesn't solve that. Lymantria (talk) 12:05, 3 May 2021 (UTC)

@Lymantria: Given that I both proposed and populated the property, and am using the info on Commons in the infoboxes (which are now broken in these categories as a result of the deletions), and have already explained why it's not incorrect usage in the (closed) deletion discussion (not perfect, true - could be improved - but not incorrect), care to reconsider again...? Mike Peel (talk) 12:13, 3 May 2021 (UTC)

Not until the scope bounderies are clear, now there seems to be no limit. "Views from..." seems reasonable, I agree with Jura that "views from ... to..." and "views from cars in ...." at least need more discussion and it is quite questionable if we want all those claims in items. It is potentially endless. Lymantria (talk) 12:19, 3 May 2021 (UTC)

A discussion like we just had in the deletion debate, which you closed as no consensus...? Mike Peel (talk) 12:25, 3 May 2021 (UTC)

Well, that lacked participants. I think it would need a new property, wouldn't it? Lymantria (talk) 12:52, 3 May 2021 (UTC)

Over 3,000,000 usages of taxon name (P225)

WikiProject Taxonomy has more than 50 participants and couldn't be pinged. Please post on the WikiProject's talk page instead.

According to List of properties/Top100 taxon name (P225) is used more than 3,000,000 times. --Succu (talk) 18:21, 1 May 2021 (UTC)

• Congrats! --- Jura 10:46, 3 May 2021 (UTC)

Wikidata weekly summary #466

Here's your quick overview of what has been happening around Wikidata over the last week.

• Events
  • Past: Wikidata+Wikibase office hour happened on April 28th. See notes here (English).
  • Upcoming: International Museum Day, May 3-18, including a Wikidata competition
  • Upcoming: Basics about SPARQL queries live on Twitch and in French by Vigneron, May 4 at 18:00 CEST
  • Upcoming: Scholia - Open Bibliometrics for Researchers webinar on Zoom, May 5 at 10h30 UTC (free, but registration needed)
  • Upcoming: LIVE Wikidata editing #42 - YouTube, Facebook, May 8
  • Upcoming: Online Wikidata meetup in Swedish #61, May 9
  • Upcoming: the next Wikidata bug triage hour will take place on May 17th on the topic of quality constraints
  • Upcoming: Wikimedia Hackathon, May 22-23. The call for proposals for the program is now open until May 9th for the main track (May 19th for the open rooms) More information

• Press, articles, blog posts, videos
  • Blogs
    • WBStack Infrastructure - current deployment and architecture of wbstack.com
  • Videos
    • Mix'n'match workshop in (Italian) - YouTube
    • SPARQL #Wikidata back to basics (in French) - YouTube
    • Wikidata Lab XXVIII: Metadata applications (a technical training on the process of metadata applications development) - YouTube
    • Upload workshop (in Dutch) - datacleaning, reconciliation, upload, embed metadata with exiftool & Upload images with Pattypan and link with Wikidata.
    • LIVE Wikidata editing #42 - YouTube, Facebook
    • Overview of all LIVE Wikidata editing episodes including topics and tools used to make search easier

• Tool of the week
  • Wikinegata is a platform for browsing interesting negations about Wikidata entities. (Overview video)

• Other Noteworthy Stuff
  • Template:Item classification and Template:Item documentation now include more generic queries for classes: it include the number of subclasses, the number of instances, the number of instances by class, the list of instances and the list of most frequent properties for items of this class.
  • TP organization now includes generic queries for items of class school.
  • Over 3,000,000 usages of taxon name (P225)

• Did you know?
  • Newest properties:
    • General datatypes: field of usage, artist files at, accessibility statement URL, degrees day, Beirut Arab University's Libraries title ID
    • External identifiers: J! Archive player ID, CofE archives name ID, HERO ID, GLEI RAL, Archdiocese of Liverpool parish ID, Yukon Archives authority record ID, CofE archives place ID, NC Highway Historical Marker Program ID, National Historical Museums of Sweden agent ID, Australian Thesaurus of Education Descriptors ID, Enzyklopädie des europäischen Ostens ID, Reallexikon zur Deutschen Kunstgeschichte ID, Oregon Flora Image Project ID, Digital DISCI ID
  • New property proposals to review:
    • General datatypes: Clubhouse account, Danmarks Tekniske Kulturarv book ID, hat Gedenkort, Secondary Archive artist ID, date of probate
    • External identifiers: LMIC musician ID, DC Books store book ID, ctext data entity ID, SAIA authority ID, AdServio school ID, Apple Music label ID, MacArthur Fellows Program ID, Encyclopedia of China Online Database ID, DHLE, APA Dictionary of Psychology entry, Scholarpedia article ID, Biology Online Biology Dictionary entry, Biblioteca di Santa Sabina ID, Biblioteche della Custodia di Terra Santa a Gerusalemme ID, Universal equine life number, Auschwitz Prisoners Database ID, Nevada SHPO marker ID, Sigla ID, Bing Entity ID, light characteristic, Lexikon der österreichischen Provenienzforschung ID, Identificativo Polo bibliografico della Ricerca, LTit person ID
  • Query examples:
    • List number of albums (Q482994) by language (P407) in descending order (Source)
    • Map of Scottish council areas (Source)
    • Databases with a SPARQL endpoint, sorted by number of ids known by Wikidata (Source)
    • List of actors and actresses who died during 2020 (Source)
  • Newest database reports: new screenwriters

• Development
  • Entity Schemas now have syntax highlighting for viewing (phab:T238831, example)
  • Reviewing a patch that will make it possible to use templates on d:MediaWiki:Wikibase-SortedProperties. This will for example make it possible to show labels automatically for each Property ID. Thanks, Luca! (phab:T280787)
  • Evaluated the interviews and other research we did around improvements for lexicographical data
  • Worked on/fixed small remaining bugs in the Query Builder (phab:T280505, phab:T279928, phab:T279945)
  • Continuing to work on evaluating and addressing scaling issues of the Query Service
  • Provided input to a research team working on a potential new and improved Property Suggester
  • Wikibase: we are completing the final tasks necessary to prepare the Wikibase Spring release and expect to publish new versions of the tarball and Docker images on or before May 15, 2021

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.

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Suggested and open tasks!
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Lea Lacroix (WMDE) 15:45, 3 May 2021 (UTC)

We built two tools to help editors get a more complete picture of the data quality on Wikidata

Hi everyone,

This is to announce that over the past month we started to look at ways to help us all get a better understanding of the quality of Wikidata's data in a specific area of interest. For this purpose we worked on building two tools; an Item Quality Evaluator and a Constraint Violation Checker - both of these tools are now available at:

• Item Quality Evaluator
• Constraint Violation Checker

Data quality on Wikidata has many aspects. The constraint violations and ORES quality scores that these tools use are two helpful indicators of certain aspects of quality that we hope will be helpful for you.

As you may know, Wikidata’s data quality is very unevenly distributed - some areas are very well maintained and others not so much. We only currently provide ORES quality scores on a global and per-Item level. This has two effects, however:

• Editors taking care of a specific area of Wikidata want to improve that area but currently don’t have an easy way to find the Items with the lowest quality they can focus their time on in order to raise the quality of that area.
• Re-user of Wikidata’s data are usually only interested in a subset of Wikidata’s Items and by extension the quality of that subset. It is currently hard for them to know what quality level they are getting for their subset of interest.

To address this issue we put together two small tools. The Item Quality Evaluator is a simple website that provides ORES quality scores for a list of Items in Wikidata. The Constraint Violation Checker is a small command-line script that retrieves the number of constraint violations and ORES scores for a list of Items for further analysis.

How does the Item Quality Evaluator tool work?

You provide it with a list of Item IDs or a SPARQL query and then it'll get the ORES score for each of them as well as the average score over all the Items you provided in a nice webpage. This way, you can more easily identify the Items in an area you are interested in that have the lowest quality and improve them.

How does the Constraint Violation Checker script work?

When you run it, it outputs a CSV file with the number of statements, the number of constraint violations for each severity level, the number of sitelinks to all projects and to Wikipedia and the ORES score for each of those Items.

Why didn't we integrate the constraint violations data into the Item Quality Evaluator?

We want to do that in the long-term but right now it is not possible because the constraint violation data is not easily accessible and retrieving it takes several hours to run for a large list of items.

Please try these tools and let us know if you encounter any issues. If you want to provide general feedback, feel free to let us know.

Cheers, -Mohammed Sadat (WMDE) (talk) 16:26, 20 April 2021 (UTC)

I tried the Item Quality Evaluator – it’s indeed a good way to find items to work on. However, the main problem with ORES scores is that they overvalue the mere existence of descriptions. --Emu (talk) 18:10, 20 April 2021 (UTC)

yeah I tried two items where I subjectively thought one was better than the other and found the tool disagreed basically because of the description. I added a totally uninformative description (just the name of the P31 value) and it shot up. Still a useful tool though. Wonder how it compares with just Wikidata:Recoin. BrokenSegue (talk) 18:52, 20 April 2021 (UTC)

Recoin is a completeness indicator based on similar items. It has its merits, but it has little to do with data quality, i.e. if the data provided is properly referenced (and the references match the statements they are referencing). To my knowledge, there isn’t a really useful tool that focuses on data quality in that sense yet. --Emu (talk) 23:23, 20 April 2021 (UTC)

@Mohammed Sadat (WMDE): Took a quick look at the Item Quality Evaluator and it looks interesting. However, I would request that a unique logo/favicon be used -- distinguishable from the Wikidata project logo -- so that it's more clear this is a tool and not core functionality. William Graham (talk) 16:40, 27 April 2021 (UTC)

Thanks for that suggestion William Graham. -Mohammed Sadat (WMDE) (talk) 09:04, 28 April 2021 (UTC)

• Was there some community request to develop the "Item Quality Evaluator"? In which part of the project plan were these included and how much time was spent developing these? Can you provide us with links to the relevant documentation so we can read about it? Thanks. --- Jura 16:50, 27 April 2021 (UTC)

Hello Jura! There was no direct community request per se, but we outlined that in the roadmap. We wrote in the 2021 development plan that we will be providing a tool to help assess the quality of a subset of Wikidata's Items. Please see the Roadmunk for more details. -Mohammed Sadat (WMDE) (talk) 09:28, 29 April 2021 (UTC)

• Hello, what's the difference between ORES and Recoin (Q50320796) ?--Bouzinac ^{💬●✒️●💛} 09:38, 29 April 2021 (UTC)
  • @Bouzinac: Recoin checks what kind of statements similar items have and then estimates the completeness of a given item. Say an item about a philosopher doesn’t have statements that other items about philosophers typically have: That would result in a low Recoin score. It’s purely based on statements in similar items and therefore 100% deterministic, that is, humans make the rules, the computer just computes.
  • ORES uses machine learning (that is, computer magic) to automatically determine the quality of an item. It also uses statements, but also descriptions and other information. It’s not deterministic, so it’s not always clear why a certain ORES score is computed (which has positive and negative consequences).
  • Both Recoin and ORES try to give you a ballpark figure about data quality, but they are computed very differently and focus on different things. --Emu (talk) 14:35, 30 April 2021 (UTC)

• It's unclear to me where the training data for ORES comes from. References seem to make little to no difference whatsoever, even though they are vital for any real use of the data.

Personally, I noticed only when I actually wanted to use some data in work projects how important references actually are. It's incredibly frustrating to have all these statements and no way to verify them. This wasn't readily apparent when I was just browsing around, before, and it seems to me that mindset may be reflected in the training data. It's frustrating to see even non-trivial data still being added without references today. I wouldn't complain if all such data were to be deleted overnight. I'd advocate for making it impossible or difficult to add more of it now, at least in volume and starting with sensitive properties. And I'd absolutely expect a tool focussing on "quality" to put proper referencing front and center. Karl Oblique (talk) 12:43, 4 May 2021 (UTC)

Translations needed for updated Discover section

You may have noticed that the Discover section on the Main Page has been recently updated, featuring a new WikiProject after several years. Unfortunately this means a lot of translation work is needed based on the new English text, so feel free to contribute translations for this. --Btcprox (talk) 14:47, 3 May 2021 (UTC)

It's too much work to translate every time there's a change, so could you please design it to be static content? Afaz (talk) 15:15, 3 May 2021 (UTC)

The description for the featured WikiProject can't really be static in every language though, as far as I'm aware. Would be nice if there were some magic tool/bot that at least laid the foundations down with some machine-assisted translation or something. But I doubt completely omitting the description would be helpful here. Btcprox (talk) 23:28, 3 May 2021 (UTC)

• Thanks for changing it (and announcing that it changed). I think it had been up for months till I noticed that the previous one was there. --- Jura 09:06, 4 May 2021 (UTC)

Scientific papers' labels in other languages than English

I wonder if this is the correct practice to copy an English label to other languages ? Like in Liver sinusoidal endothelial cells are a site of murine cytomegalovirus latency and reactivation (Q37333761) Asturian and Dutch labels are copies of the English one. Following this practice we'll end up with hundreds of identical labels. Maybe translations would be better idea ? Kpjas (talk) 10:28, 20 April 2021 (UTC)

• At least, the automatic fall-back to English can provide the same. No need to copy 30 millions paper labels to 200 languages

What is bad, is that English translations of non-English titles are copied as well. --- Jura 10:34, 20 April 2021 (UTC)

@Kpjas: why would this be incorrect? Think about specific edition of book, the title is the same in all languages (with latin alphabet obviously), same for most name of people. « we'll end up with hundreds of identical labels », this is already very often the case. Not efficient but is there an other way to do it? Cheers, VIGNERON (talk) 06:13, 27 April 2021 (UTC)

With millions of edits that are not very productive (they don't add any new information) I would consider this practice to be a waste of Wikidata's workforce time and (Quickstatements') resources. Some central (software) mechanism would be more practicable IMO. Kpjas (talk) 16:06, 27 April 2021 (UTC)

• How bad would it be for Wikidata to have a " special fall-back label" field for label with precedence to English? E.g., in order of priority: current language -> fallback special label --> English . Most cases would be the same, but perhaps better models non-English works. TiagoLubiana (talk) 14:03, 27 April 2021 (UTC)
  • @TiagoLubiana: such fallback could be useful but this is not solving the problem at hand here. I - repectfully but strongly - with @Kpjas: claim that « they don't add any new information », there is an information in saying "I explicitely states that the label is the same in these languages" and this is very different from a fallback which is more or less "I have no idea what the label is in your language, just take this one based on a more or less accurate global rule". For instance, think about Berlin (Q64) where the label in a lot of languages is "Berlin" but this is not random and you can't use a fallback (or a very cleverly tailored one). You can also think about Romeo and Juliet (Q83186) (where labels should be different, a work title is translated) and Romeo and Juliet (Q19101569) (most but not all labels should be the same, a edition title is not translated, but it could be transcripted or transliterrated). Obivously scientific papers are close the this last example. Cheers, VIGNERON (talk) 09:13, 28 April 2021 (UTC)
    • I think the label of the item for the city of Berlin and the work Romeo and Julia are off topic. --- Jura 19:42, 4 May 2021 (UTC)
• @TiagoLubiana: For papers, the general fall-back should be the title. When used as a reference in an article, in most languages, I think that should be displayed anyways. The problem seems to be that some Wikipedias don't make correctly use of this and might expect the French label and display nothing if it isn't present (instead of starting out with the title and eventually falling back to English). So yes, most of the time, there is no use to copy the English translation of a Spanish paper to Dutch and Asturian. --- Jura 19:42, 4 May 2021 (UTC)

D-A-CH (Q1151241)

How to add statement for "Area: Europe"? Eurohunter (talk) 07:48, 4 May 2021 (UTC)

• It seems lit refers to different areas in English and (of all languages) German. --- Jura 09:09, 4 May 2021 (UTC)

@Jura1: I see it the same way you do. I guess the data object should be split up, right? --Gymnicus (talk) 14:39, 4 May 2021 (UTC)

What do you mean? Eurohunter (talk) 19:24, 4 May 2021 (UTC)

@Eurohunter: If you look at the German article D-A-CH and the Spanish article Europa germanoparlante (english: German-speaking Europe), than you can see that the article is about different things. In principle, one could even say that the statement D-A-CHsubclass of (P279)German-speaking Europe applies. --Gymnicus (talk) 20:11, 4 May 2021 (UTC)

I just noticed it and I will divide it. Eurohunter (talk) 20:20, 4 May 2021 (UTC)

If Q1151241 is made about the word, maybe a third item about these three countries as a group should be created. --- Jura 20:47, 4 May 2021 (UTC)

Irena sendler

Who were her parents  – The preceding unsigned comment was added by 216.56.51.66 (talk • contribs).

@216.56.51.66: According to Irena Sendler (Q151932), her father was Stanisław Krzyżanowski (Q61911671). More information is available at en:Irena Sendler. Bovlb (talk) 16:41, 4 May 2021 (UTC)

Data Donation from "Open Editors" (Editors from Scholarly Journals)

Hello,

I have a data-collection project underway called "Open Editors". It used webscraping to collect data about almost half a million researchers who are in the editorial boards of ca. 6.000 scholarly journals. I plan to scrape regularly (annually over the next few years) so that the data get updated.

I would love the data to be freely available, not just with a CC0-license and a CSV-file (on GitHub), but at Wikidata, so that the data can be linked extensively.

However, I am too new at Wikidata; I lack the knowledge on how to do proceed.

Thus, may I ask, what I shall I do in order to initiate a data donation? Is the dataset even suitable for such a venture?

Thank you!

Andrepach (talk) 08:56, 5 May 2021 (UTC)

Nice. The journal link can be used as reference, as you also recorded the date when you visited it.

https://www.wikidata.org/wiki/Wikidata:Data_donation --SCIdude (talk) 09:11, 5 May 2021 (UTC)

Call for Election Volunteer

Hi everyone,

Voter turnout in prior board elections was about 10% globally. We know we can get more voters to help assess and promote the best candidates, but to do that, we need your help.

We are looking for volunteers to serve as Election Volunteers. You can read more about this role here: https://meta.wikimedia.org/wiki/Wikimedia_Foundation_elections/2021/2021-04-29/Call_for_Board_Elections_Volunteers

Election Volunteers should have a good understanding of their communities. The facilitation team sees Election Volunteers as doing the following:

• Promote the election in their communities’ channels
• Organize discussions about the election in their communities
• Translate messages for their communities

Do you want to be an Election Volunteer for Wikidata or any of the Wiki projects, and connect your community with this movement effort? Check out more details about Election Volunteers and add your name next to the community you will support in this table or get in contact with a facilitator. We aim to have at least one Election Volunteer for Wiki Projects in the top 30 for eligible voters. Even better if there are two or more sharing the work.

If you have any questions or comments regarding this role please reach out to me or any of the board governance facilitators.

Best,Zuz (WMF) (talk) 09:27, 5 May 2021 (UTC)

Add 270,000,000 triples for last names and first names of people to papers?

Currently we have 135,555,066 statements with author name string (P2093), mostly on items about scholarly papers.

The following proposals:

• Wikidata:Property_proposal/Author_last_names
• Wikidata:Property_proposal/Author_first_names

propose to complete that with two more qualifiers/triples, each. That would be 270 million more triples on query service.

While there may be some benefit to it, I think we should be able to come up with a better solution. --- Jura 10:55, 3 May 2021 (UTC)

These have been in discussion since last year, and are necessary to be able to reformat 'First Middle Last' as 'Last, First Middle' within en:Template:Cite Q at least - with the current setup it is impossible to know what is part of the first/last name and what isn't. They finally got marked as ready for creation yesterday, and now you start a discussion here??? Mike Peel (talk) 12:02, 3 May 2021 (UTC)

• I don't see the size question addressed in the discussion and it's fairly unrelated to the proposals as such. --- Jura 12:30, 3 May 2021 (UTC)
• I believe these should only be added where a bibliographic reference clearly makes the separation into first and last, which in my view is likely to be only a tiny fraction of the total. ArthurPSmith (talk) 17:40, 3 May 2021 (UTC)
  • What leads you to believe that? The problem on Wikipedia this attempts to solve isn't limited to these. Besides most author name strings are trivial to split into "last name" and "first name". Also, doesn't the source for most entries (Pubmed) split them for most names? --- Jura 05:27, 4 May 2021 (UTC)
• Instead of complaining about size of two links to existing items added, think about the size needed for the author strings. In principle they could be deleted after first/last are added, and you would gain space. --SCIdude (talk) 07:15, 4 May 2021 (UTC)

• Well, yes, but, mainly no. The size of the string stored pales into insignificance against the size of the triples created to store strings, and, moreover, the proposal is for qualifiers of the P2093 statement, which would not work very well if the P2093 statement was deleted. --Tagishsimon (talk) 07:56, 4 May 2021 (UTC)
• Indeed, you might want to re-read the proposal. BTW, it's two per author (P50) or author name string (P2093) statement. So the total is probably 310,000,000 triples. --- Jura 08:00, 4 May 2021 (UTC)

So yes, 310M new triples, adding roughly 2.4% to the number of triples in WD, which is equivalent to 2 months of normal triple growth. It's unlikely the query service will care very much from a reporting perspective. The main pain arises in the RDF serialisation; but iirc that was recently substantially improved? And otoh, we probably should be here to make WD data usable, which CiteQ does well. WD is only going to get larger and its data more Baroque. I'm not convinced the argument for restraint, in this instance, is made. --Tagishsimon (talk) 08:29, 4 May 2021 (UTC)

• At the risk of being late to this discussion, I am missing some acknowledgment/reasoning for going with what seems to be a rather untypical data structure. The straightforward data model would link papers to items for authors. Any possibly needed properties for formatting their names would then be added to those items. The advantages are, obviously:

• Name strings are only recorded once, simplifying any corrections and saving storage space and triplets otherwise wasted on redundant information
• Item references (integers) use less storage space than strings, further reducing storage requirements
• Author items link between that author's papers, allowing the data to be used in the way all other data is used, such as by querying etc.

I get that it isn't entirely obvious how to distinguish between multiple authors with the same name, but:

• The sources for the current data usually do link to author pages, either specific to a publication, at the author's institution, or at one of meta-services (researchgate etc)
• When I started in academia, it was common practice to search one's name and find some variation of name/middle initial(s)/nickname that was unique
• Subject matter, publication date, language, and names of collaborators could all be used to heuristically decide if two names reference the same person
• For the purposes outlined above, i. e. formatting of names on citations, both extreme cases would still work flawlessly: collapsing all authors of the same name into a single item, or creating separate items for every author name on every paper.

Sorry of I missed a previous discussion of these issues. Karl Oblique (talk) 12:28, 4 May 2021 (UTC)

@Karl Oblique: Yes, the general plan is to replace author name string (P2093) with author (P50) statements where possible; however this does not capture how an author's name is represented as an author of a particular work which is the question here, and why at least in some cases these qualifiers unfortunately are still needed. ArthurPSmith (talk) 20:01, 4 May 2021 (UTC)

• The main assumption seems to be that LUA on English Wikipedia can't read all the authors items correctly. Oddly, it seems to work out on ruwiki and few other wikis using the same module as ruwiki. --- Jura 12:14, 5 May 2021 (UTC)

Statement for list

What is the statement to make for example list of tallest buildings in list of tallest buildings (Q1779466) so I can list all buildings under one statement? I have asked about it but gave wrong example so I got missed answers. Eurohunter (talk) 19:28, 4 May 2021 (UTC)

Are Wikipedia lists copied to Wikidata? --SCIdude (talk) 09:15, 5 May 2021 (UTC)

@SCIdude: I think no but what do you mean exactly? If data here is for use by Wikipedia I can imagine it could be used for tables across all Wikipedia versions. Eurohunter (talk) 10:18, 5 May 2021 (UTC)

No. If you have a Wikipedia list article, the articles listed should each have a Wikidata item with the same P31 value. So use the query to get all items. Second, your question: why not make Wikipedia lists by bot from Wikidata list? No one makes and maintains Wikidata lists, because the items will have P31/P279 and you just query for them to get a list. Finally, one could have the idea e.g. to make a Wikipedia list by using a Wikidata query, the problem is that in most cases there will be much more Wikidata items than Wikipedia articles, so most of the links in the Wikipedia list will be red. However, it is possible to show only those with article. --SCIdude (talk) 14:00, 5 May 2021 (UTC)

As to the original question, try:

SELECT ?item ?itemLabel (MAX(?height) as ?maxheight)
WHERE 
{
  ?item wdt:P31/wdt:P279* wd:Q18142.
  ?item wdt:P2048 ?height.
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
GROUP BY ?item ?itemLabel
ORDER BY ?maxheight

Try it!

Qualifiers and statements

I think sometimes qualifiers for statements can be repeat as statements. For example you can use country (P17) as statement and as qualifier for other statement in one item. So sometimes I don't know if I should use something as statement or qualifier. Is it correct? Eurohunter (talk) 22:22, 4 May 2021 (UTC)

Depends on the statement. No way you can generalize it. --SCIdude (talk) 09:14, 5 May 2021 (UTC)

@SCIdude: So what if we have country (P17) for statement then there is statement for product certification (P1389) and country (P17) as qualifier. I know it's not the best example because in this case it can be used to distinguish product certification (P1389) between countries but for sure there are other examples where it looks like repeated and it is probably performer (P175) if we use it as qualifier for instance of (P31). Eurohunter (talk) 10:24, 5 May 2021 (UTC)

Requiring References in QS

Probably a controversial proposal but anyone have thoughts on requiring all statements added through QS/similar batch tools to have references? Looking through the recent history it's clear that these changes could all have references but the user just opted not to do it. A few examples: [2] [3] [4] [5] [6] [7] [8]. Alternative similar ideas would be to apply this restriction only to larger batches or to make users click through a scary warning if they aren't adding references.

I recognize this might sometimes produce redundant or obvious references but that is far better than having no idea if you can trust a statement and shouldn't be hard to do.

BrokenSegue (talk) 13:10, 4 May 2021 (UTC)

• Labels cannot get references... So... I'd be against that idea (good faith idea, by other ways). Another problem, if you would batch copy country (P17)=France all coordinates that are obviously objects whose coords are well inside France, how would you do that if you were to require a reference? --Bouzinac ^{💬●✒️●💛} 13:55, 4 May 2021 (UTC)

  inferred from (P3452)geographic coordinate (Q104224919)? That being said, I think that example needs references more than most of BrokenSegue's examples, because you could plausibly run into a scenario where you find out that the coordinates are wrong and you need to know whether that makes the country invalid as well.

  That being said, instance of (P31) and external identifiers are often self-sourcing, unless you're doing something weird (either having some really specific non-obvious type for the item or using some sort of heuristics or cross-referencing for the identifier). In those cases, the source of the information is pretty much irrelevant, and adding references really only serves to juice the reference statistics without helping data consumers. Vahurzpu (talk) 15:45, 4 May 2021 (UTC)

• I like the idea of encouraging references in batch jobs, but I am also nervous about the strong version of this proposal. Perhaps start with properties that have a citation needed constraint (Q54554025)[9]. I often feel that we could use better tools to validate QS batches. How about some sort of QS Lint that previews the violations that will be reported by the existing error checking? Bovlb (talk) 16:37, 4 May 2021 (UTC)

  @Bovlb: My guess is that such a linter would be much harder to implement than a blanket restriction and implementation effort is an important consideration. BrokenSegue (talk) 16:43, 4 May 2021 (UTC)

  CC @Amir Sarabadani (WMDE), Lucas Werkmeister (WMDE). Bovlb (talk) 17:16, 4 May 2021 (UTC)

• @Bouzinac: Labels/descriptions are not statements (I think) so would be exempt here. And yeah your example should have a reference for sure and is a good example why we should have this rule. BrokenSegue (talk) 16:41, 4 May 2021 (UTC)

• @Vahurzpu: I think unless you are creating the item then the instance of (P31) is not self-sourcing. It's probably sourced from wikipedia or some external identifier or from the label. Even if you are creating the item it should be easy to find a source that, say, Florida Dental Association (Q5461307) is an organization (though maybe it's pointless). As for external identifiers I think you either imported from that external-DB (so just say it was stated in that DB) or you joined from one DB to another (so say its from the first DB). I would be ok exempting new item creation from this rule though. BrokenSegue (talk) 16:41, 4 May 2021 (UTC)

It's difficult enough as it is to keep wikidata synched with article creation on language wikipedias. Adding a new hurdle for that process will not be helpful. A rule which acts as a perverse incentive - e.g. to add less than useful references merely to make progress - also not helpful. Bottom line is that unreferenced statements are what they are: unreferenced, and therefore less complete & trustworthy than well-referenced statements. Users can decide for themselves whether to use/trust unreferenced statements. References are lovely but so is the completeness of wikidata sitelinks to WPs. Why exactly should the latter suffer because of your particular interest in the former. --Tagishsimon (talk) 18:16, 4 May 2021 (UTC)

@Tagishsimon: I'm sympathetic to the concern that this would burden users but your example seems particularly non-problematic. If you are syncing wikipedia to wikidata the reference often just says "imported from wikipedia". It's really easy. I agree people adding bad references is a risk. But for large batch people edits should be able to succinctly express how the statements were arrived at with minimal effort. I don't see how this proposal would hurt "completeness of wikidata sitelinks to WPs" since sitelinks are unreferenced. BrokenSegue (talk) 19:54, 4 May 2021 (UTC)

• I looked at some of the batches you mentioned above and their main source seems to be a Wikipedia import. For these, merely adding "imported from" can be interesting, but in general isn't much help. Also, [10] had some problems references wont solve.
  For batches adding P31, not sure if references help much: if P31 needs a reference, one is probably using the wrong value or the item has some basic problems. --- Jura 20:07, 4 May 2021 (UTC)

  @Jura1: yeah the batches I picked weren't the best they were just the arbitrarily chosen recent batches that didn't have references. I could be convinced P31 doesn't need a reference but I do think "imported from" is much better than nothing (especially if it's paired with a date). I also would hope some bad batch jobs wouldn't be run at all because of the difficulty in making a reference. BrokenSegue (talk) 17:26, 5 May 2021 (UTC)

url formatter

Any reason that this url formatter doesn't seem to be working ? Property:P9505#P1630. Jheald (talk) 14:02, 5 May 2021 (UTC)

• @Jheald: Works now. For some reason there's a delay of some number of hours before url formatters take effect in the UI. You may have to purge items that don't show the link yet. ArthurPSmith (talk) 17:18, 5 May 2021 (UTC)

What Json Fields are Nullable?

I'm working on a library for parsing JSON of Wikidata Entities into a more native format in a strongly typed language (OCaml). Because this language is strongly typed, any fields that are sometimes null have to explicitly be marked as only optionally containing data; when accessing this data using my library, people will have to explicitly deal with the case that no data is present before the code will compile. I've read through the Wikibase JSON Format Documentation a number of times but I keep getting tripped up by fields being nullable that I thought weren't. For example, the property coordinate location (P625) of St John's College (Q691283) is a globe-coordinate with a null precision, but precision wasn't listed as being optional in the documentation. Is there any canonical list of fields that are nullable? I would just mark everything as being optional except that makes it really annoying to work with my library, especially considering there are many fields that are almost certainly never null (like the text field of monolingualtext). --ImpossiblyNew (talk) 04:38, 5 May 2021 (UTC)

• Wikidata:Contact_the_development_team might be the better place for question about Wikibase documentation.

A possible explanation for your sample [11] might be that it was added years ago and, while the format evolved, not all data on Wikidata was updated to match that. --- Jura 09:25, 5 May 2021 (UTC)

• Thanks! Will do --- ImpossiblyNew (talk) 22:51, 5 May 2021 (UTC)

References

Is there any way to copying references between items? Eurohunter (talk) 19:22, 5 May 2021 (UTC)

@Eurohunter: Preferences > Gadgets > enable DuplicateReferences Vahurzpu (talk) 19:28, 5 May 2021 (UTC)

@Vahurzpu: Yes but this tool moving reference just from one statement to another in one item and I need to copy references from one item to other items. Eurohunter (talk) 19:45, 5 May 2021 (UTC)

I now realize that I misread your question. I don't know of tool that does this, but maybe someone else does. There's always the option of creating an item for the reference and linking it with stated in (P248), assuming that makes sense for the reference in question. Vahurzpu (talk) 21:00, 5 May 2021 (UTC)

To my knowledge there is no simple way, which is another glaring reason most statements aren't referenced. When a reference doesn't exist as a fully self-contained item (and I don't believe every citation warrants a dedicated item down to page number), I use MoveClaims tool (User:Matěj Suchánek/moveClaim.js) to copy a referenced statement to the target item (even if it has no relevance beyond the shared reference), then modify the statement and/or reference as needed. -Animalparty (talk) 22:18, 5 May 2021 (UTC)

How to indicate place of origin for a hyphenated ethnic group?

There are many instances of ethnic group (Q41710) that are essentially combinations of two distinct places, regions or countries. For example Taiwanese Canadians (Q7676603), Hong Kong Canadian (Q5894321), Canadian Americans (Q5029681), or Scottish Americans (Q3476361). In each case people came from one place to another and their place of origin gave them (and sometimes their ancestors) a distinct ethnic identity in the new place. I would like to find a good and consistent way of indicating for these ethnic groups both the current place of residence and the place of origin. And then for example I would like to be able to use Taiwan (Q865) -> Canada (Q16) to look up Taiwanese Canadians (Q7676603). How might I be able to indicate this? I see country of origin (P495) but this doesn't seem to like being applied to an ethnic group. It may also not be flexible enough to include diaspora communities that aren't from countries (e.g. Tibetan Canadians (Q7800410) or African Americans (Q49085) where neither Tibet nor Africa are countries). Any advice would be greatly appreciated! Nate Wessel (talk) 13:31, 3 May 2021 (UTC)

Why exactly does country of origin (P495) "[not] seem to like being applied to an ethnic group"? At first blush you shouldn't be getting error messages since ethnic minority group (Q2531956) is one of the values explicitly allowed to an item with the property, and the allowed targets seem flexible enough (Tibet (Q17252) is a valid one, as is Africa (Q15)). Circeus (talk) 18:36, 5 May 2021 (UTC)

I'm not sure. I see a warning on the country of origin (P495) statement that I added to Taiwanese Canadians (Q7676603). And also to the one I just tried adding to African Americans (Q49085). "Entities using the country of origin property should be instances or subclasses of one of the following classes (or of one of their subclasses), but Taiwanese Canadians currently isn't: Product... ". Nate Wessel (talk) 17:48, 6 May 2021 (UTC)

Actually, I think indigenous to (P2341) may be exactly what I've been looking for. Nate Wessel (talk) 18:18, 6 May 2021 (UTC)

Family names used as middle names

I just encountered a problem at Bob Herman (Q106690802) that I've come across several times now. The individual's name is Robert Dunton Herman. We have Dunton (Q37503615) as a family name, but Dunton isn't really a given name. However, our normal way to mark middle names is to put them as a given name with qualifier series ordinal = 2. When I try to do this, it gives me a exclamation mark error, complaining that I'm using a family name as a given name. How should we resolve this? It doesn't seem right to create an entry for "Dunton" as a given name, since it's not. It also wouldn't be good to set given name (P735) to accept family names, though, as that would lead to a lot of errors. And entering the data as Given name = Robert, Family name = Dunton (ordinal 1), Herman (ordinal 2) wouldn't be right, either, as that'd make it seem like he has a two-word last name. {{u|Sdkb}} ^talk 20:30, 4 May 2021 (UTC)

Especially in the English naming tradition, which is widely used in places such as Ireland, Canada, Australia, and the United States, people are allowed to give almost any given name to their children they please. Later, adults are free to change their given name to almost any names they please. So if some parents gave their child the first given name "Robert" and second given name "Dunton", then both of those are first names, even though some of Robert's ancestors may have used "Dunton" as a family name. These exclamation point errors are constraint violations. Constraints are not right rules; they are merely hints that the value might not be correct. It is often necessary to ignore them. Jc3s5h (talk) 21:13, 4 May 2021 (UTC)

I think you need more detail to know if its a family name or not. Does one of his parents have surname "Dunton"? If so, I'd say he has two family names. Ghouston (talk) 01:35, 5 May 2021 (UTC)

According to Prabook, it's the maiden name of his mother, so I'd say it's a family name, like any double-barrelled surname. Ghouston (talk) 01:40, 5 May 2021 (UTC)

• The solution was to create a QID for "Dunton" as a given name, even if it is unique to this person. That is how we handle someone with a given name that was a family name of a maternal ancestor. The most famous example is "Johns Hopkins". --RAN (talk) 04:56, 6 May 2021 (UTC)

Items on ghost names (taxonomy)

I recently discovered that the name 'Coenagrion exornatum' (Selys, 1872) was removed from the World Odonata List. It didn't take me very long to find out why: the name appeared not to represent an accepted species, but was a misprint for Coenagrion ecornutum (Selys, 1872). The 'name' first appeared in 1890 in the paper in which Kirby created the genus Coenagrion. After that, it started to live a life of its own, popping up in databases next to Coenagrion ecornutum as if they were both names for accepted species. At the latest in 2010 it was noted that the name was only a misprint, when Jin Whoa Yum et al. commented on the name. Here one can find a pdf of their paper, the statement is on p. 45. 'Names' of this type attract the attention of taxonomists because they lack everything an available name has: there is no nomenclatural type associated with it, there is no bibliographic reference to a protologue, and if there is one, the name can't be found there; there are no distribution data, in general there is nothing that indicates that a species with this name actually exists.

I tried to get rid of this piece of disinformation in Wikimedia by asking for speedy deletion in the projects that have an article with this name, giving the arguments of course. In some cases the article was indeed deleted, but on the Polish Wikipedia, they changed the name into a redirect, as if this ghost name were a synonym. I also tried to make clear in the Wikidata item that this is not the name of an accepted species but a misprinted name. I changed the authority from (Selys, 1872) into Kirby, 1890 because that's the place where the name first popped up. And I tried to add the above mentioned pdf as a reference for all of this. That however, appeared one step too far for me.

As this is only one example of literally hundreds of thousands of cases, and I guess it's important to take appropriate action if an article or an item suggesting it is the name for an accepted taxon appears to be disinformation, I'd like some advice on how to best tackle this in Wikidata. Most important: how to give a reference to a paper or other scientific work if the author of that reference is not recognized by Wikidata, and hence the reference refused, but there is a pdf or other source available online. 77.164.133.132 01:35, 4 May 2021 (UTC)

This is a prime example of the schizophrenic way Wikidata approaches taxonomenclature. It would be just fine if wikidata could handle names that do not correspond to accepted taxa (not just misspellings, but also things like replaced homonyms and other objective/homotypic synonyms), but Wikidata is incapable of doing so in any meaningful way without causing a huge amount of warnings. I gave up work in that area entirely a while ago because of that. Circeus (talk) 18:46, 5 May 2021 (UTC)

It is not clear from what you write where your problem is. You write "I tried to add the above mentioned pdf as a reference for all of this": it is not forbidden to give an URL to a PDF as a reference to a statement so why did you not succeed? Also which statements did you try to add, please point us to these. --SCIdude (talk) 07:34, 6 May 2021 (UTC)

First of all: thanks for answering. The most practical problem is this. In the statement 'taxon name' (it is of course not a taxon, it is a misprinted name, but more on that later), under 'reference', I tried to add a link to the pdf of the paper of Jin Whoa Yum et al. (2010), because in that paper (p. 45) that claim is made: "Coenagrion exornatum [misprint] (Selys): Kirby, 1890: Syn. Cat. Neur.-Odon., London: 150" (and as soon as one has that hint, one can look up Kirby's paper and compare with Selys's publication, and realize Yum et al. are right). I was unable to create that reference, probably because of my inexperience with adding references in Wikidata.

The other problem is that I have no idea how to cope with a 'taxon name' that in fact is no name at all. It should be possible to have an item for the misprinted name 'Coenagrion exornatum', but without all the claims that it is a taxon or a taxon name. The only useful knowledge about that name is that Kirby made an error when he meant to refer to Coenagrion ecornutum. Nothing more, nothing less. But because 'Coenagrion exornatum' has the form of a taxon name, it seems that there are all kinds of mechanisms that want to have it taken up as the name of (in this instance) a species. With the risk that sooner or later it pops up as a direct child of Coenagrion, as it did before; it was even often listed next to Coenagrion ecornutum as if both names represented accepted species. And then all the work that contributors (i.c. I) have done to sort this out will have been in vain. 77.164.133.132 00:49, 7 May 2021 (UTC)

Subclass of heritage designation

listed historical resource (Q15203884) is heritage designation by the city of Winnipeg, Canada. Buildings added to the Winnipeg List of Historical Resources (Q106714820) up to 2014 have a classification of grade I, II, or III, which affects their level of protection, but items added since do not (or they have grade “N/A”). It is important to record this, but I’d rather not create three or four new designations to capture this, but rather keep listed status in one place and add a qualifier. Is there an existing property or qualifier suitable for this? —Michael Z. 18:48, 5 May 2021 (UTC)

• You could qualify statements like Q7885387#Q7885387$6e117367-4e14-d5e6-a7b5-78fe4a978942 with criterion used (P1013)? --- Jura 06:48, 7 May 2021 (UTC)

  The general criteria used to determine designations and grades are separately listed here, but the specific criteria for each designated property are not listed explicitly (maybe some can be inferred from each property’s report). So that’s not quite right, but that property led me to subject has role (P2868), which sorta kinda works if I create four items representing the “roles” Grade I, II, III, and N/A. Does this make sense?

  The alternative is to add three or four subclasses (“N/A” could be added to explicitly contrast with “no data,” and the encompassing superclass ideally becomes empty).

  Which approach is better? My instinct is to have a binary quality of designated or not, and add the grade as a qualifier only, but the implementation is feeling like a kludge. It would feel odd if this municipal designation were more complicated than the provincial and federal ones, but maybe it just is what it is. I guess subclasses is more natural in Wikidata and allows the most fine-grained application of data in the long run.

  I want to decide on this modelling before I start adding a lot of items and statements. —Michael Z. 14:05, 7 May 2021 (UTC)

  I'm not involved in heritage description so I do not understand why criterion used (P1013) with one of four items named like "Winnipeg List of Historical Resources classification grade I" is wrong, because it sounds fine to me. Can you please explain? --SCIdude (talk) 16:07, 7 May 2021 (UTC)

  Criteria are the standards or basis for an evaluation, and its result may be a designation (with or without a grade). This is the normal general meaning, and also used specifically by the city of Winnipeg: “Heritage Values are the architectural & historic significance of a resource and are based on the following criteria: AGE - Its importance in illustrating or interpreting the history of the city or a neighbourhood; PERSON . . . CONTEXT . . . STYLE . . . LOCATION . . . INTACTNESS.” Source(expand “learn more”). —Michael Z. 20:21, 7 May 2021 (UTC)

It's not very clear, your personal preference aside, why you are not following the established pattern seen, for instance, for England and Wales with Grade I listed building (Q15700818), Grade II listed building (Q15700834) &c and for Scotland, category A listed building (Q10729054), category B listed building (Q10729125) &c, all used as main heritage designation (P1435) values. This report provides counts of use. Were you to persist with using a qualifier, object has role (P3831) would be more appropriate than subject has role (P2868) IMO. criterion used (P1013) is useful when modelling the criteria used for something. Here the various grades are not in themselves a criteria, but rather the result once criteria have been applied. --Tagishsimon (talk) 16:26, 7 May 2021 (UTC)

Because I was not aware of those. Thank you. —Michael Z. 20:21, 7 May 2021 (UTC)

George Sand (Q3816)

What's the best way to add sex or gender (P21) = male (Q6581097) to the item?

Once added, we will have to set rank to deprecated, but that's another question. --- Jura 12:29, 6 May 2021 (UTC)

She liked to wear men's clothes but in what sense could she be regarded as "male"? — Martin (MSGJ · talk) 20:55, 6 May 2021 (UTC)

I had mostly in mind facts Wikidata knows about, i.e. authorship under pseudonym. --- Jura 06:43, 7 May 2021 (UTC)

Indexing

How long does it take for a wikidata item to be indexed by a search engine? Or is that up to the people who run the search engine? CanadianOtaku ^{Talk Page} 01:15, 7 May 2021 (UTC)

that is up to the search engine people. BrokenSegue (talk) 02:12, 7 May 2021 (UTC)

• You can run a test yourself, create a new QID and search in Google for it every day. Generally it takes about 30 days for new items in Wikidata to be indexed. The 30 days window gives us a chance to weed out fake entries. --RAN (talk) 16:18, 7 May 2021 (UTC)

Property for 2016 mirror(?) of Wikipedia

Currently there is Wikidata:Property_proposal/English_Everipedia_ID open for discussion. I'm not really sure what to think of it.

w:Everipedia#Content_and_users notes "as of May 2019, most or all Everipedia articles originating as Wikipedia articles, including those never edited on Everipedia, had not had updated Wikipedia content applied since 2016". I wonder if it's that site where I occasionally end up when looking for articles deleted from enwiki.

Anyways, I think the discussion could use more input. In the meantime, samples mostly pointing to copies of Wikipedia have been removed. --- Jura 06:41, 7 May 2021 (UTC)

I think Everipedia is a terrible idea, and no one should associate with it. -Animalparty (talk) 04:41, 8 May 2021 (UTC)

Langwiki watchlist vs Wikidata watchlist

Hi, following a tense discussion with someone anti-Wikidata from enwiki, I wonder if there is possibility for an enwiki user, watching [Article X] on enwiki, to see if something has changed in its Wikidata item [on the enwiki watchlist] ?--Bouzinac ^{💬●✒️●💛} 12:06, 13 May 2021 (UTC)

Just discovered that parameter in the langwiki watchlist filters

. --Bouzinac ^{💬●✒️●💛} 12:13, 13 May 2021 (UTC)

This section was archived on a request by: --- Jura 08:39, 14 May 2021 (UTC)

Why I can't Create item with Brandon See Name?

https://orcid.org/0000-0002-4769-4383 2401:4900:4638:BB7C:C441:26E4:B983:820B 18:58, 15 May 2021 (UTC)

Answered at WD:AN. Bovlb (talk) 02:35, 16 May 2021 (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. Bovlb (talk) 02:35, 16 May 2021 (UTC)

GND and ZDB identifiers for journals

I have a question on how to link to journals with the ZDB and GND. I have Nature Methods (Q680640) which is recorded in these two datasets:

• https://zdb-katalog.de/title.xhtml?idn=026529807
• http://d-nb.info/026529807

However I do not find a property for which identifier "026529807" works. Instead, there is ZDB ID (P1042) which has identifier 2163081-1 and using the formater URL creates the following link http://ld.zdb-services.de/resource/2163081-1 which redirects to https://zdb-katalog.de/title.xhtml?idn=026529807 . So it seems to me that identifier "026529807" is preferred across GND and ZDB but I cannot link to it from Wikidata while the ZDB ID (P1042) identifier "2163081-1", to which we can link, seems to be redirected to the other identifier. Can someone explain what is going on and whether one identifier should be preferred over the other? Is there a property with a formater URL which works for "026529807"? I am just confused here. --Hannes Röst (talk) 16:33, 6 May 2021 (UTC)

This seems quite mysterious. Google doesn't find anything other than this conversation linking 026529807 with an "IDN" identifier. Do you have any contacts at ZDB who could explain what IDN means? ArthurPSmith (talk) 15:04, 7 May 2021 (UTC)

It’s beyond complicated. GNDs also have IDNs, which are called PPNs (Pica-​Produktions-Nummer) in other contexts. They are causing all sorts of troubles because sometimes you can only use the GND, sometimes only IDN/PPN, sometimes both and sometimes none, depending on the catalogue a library is using. I never really figured out the logic behind that, maybe @Kolja21, Wurgl, Raymond, Unukorno, Silewe: can help? --Emu (talk) 19:42, 7 May 2021 (UTC)

Like explained here "d-nb.info" are links for single editions. For ID 026529807 use DNB edition ID (P1292). --Kolja21 (talk) 20:08, 7 May 2021 (UTC)

PS: IDN = Identifikationsnummer. Explication in German. --Kolja21 (talk) 20:20, 7 May 2021 (UTC)

In short: If the link starts with d-nb.info/gnd/ it is a GND-Number. If there is no /gnd/ in the link, it is that IDN/PPN. Another hint: GNDs do never start with a zero. --Wurgl (talk) 20:47, 7 May 2021 (UTC)

So should we propose a new property for the IDN, or is it already covered somehow? ArthurPSmith (talk) 20:59, 7 May 2021 (UTC)

In deWP, we use the ISSN for magazines, as you can see in the Infobox of de:Nature Methods --Wurgl (talk) 21:20, 7 May 2021 (UTC)

It seems that the ISSN links also into the ZDB, but then what are the circumstances where we would need ZDB ID (P1042), is that if there is no ISSN? Also it seems that the ISSN search reveals two results: [12] and [13] so its unclear how to handle that, should we link both ZDB links? --Hannes Röst (talk) 14:24, 10 May 2021 (UTC)

Share your IP Masking comments and suggestions

Hello colleagues,

Due to global trends about user data collection and use, the Wikimedia Foundation will be masking IPs to protect editors' privacy but would also be building tools to ensure we are able to continue fighting vandalism and other abuse in the absence of IP addresses. We would like to know, how will IP Masking impact you? Also which tools will you need to be able to effectively govern the projects in absence of IPs?

Kindly read more about the project and the tools we are currently working on, you can offer critique, you can also suggest your own. Please use the talk page for this.

Best regards,
Anti-Harassment Tools Team
STei (WMF) (talk) 12:36, 10 May 2021 (UTC)

Wikidata weekly summary #467

Here's your quick overview of what has been happening around Wikidata over the last week.

• Events
  • Ongoing
    • Wikidata contest for International Museum from May 3-18 2021
  • Upcoming
    • OpenStreetMap TW x Wikidata Taiwan Taipei (Q1867) Meetup 2021-05-10
    • Basics about SPARQL queries live on Twitch and in French by Vigneron, May 11 at 18:00 CEST
    • Online Wikidata meetup in Swedish #62, May 16
    • Wikidata Bug triage hour about constraints, May 17
    • COSCUP 2021 Call For Papers now open
    • Wikimedia Taiwan x NCKUHis Digital humanities Wikidata Workshop National Cheng Kung University (Q706708), 2021-05-29 ~ 2021-05-31

• Press, articles, blog posts, videos
  • Blogs
    • WBStack setting changes, Federated properties, Wikidata entity mapping & more (covering some of the recent UI and setting changes that happened on WBStack in the past months by Addshore
    • Academic ancestor graphs from Wikidata
  • Papers
    • Roderic D. M. Page, Wikidata and the Bibliography of Life, doi:10.1101/2021.05.04.442638
    • Friederike Ehrhart, et al. Aresource to explore the discovery of rare diseases and their causative genes (Q106708178), doi:10.1038/S41597-021-00905-Y
  • Videos
    • SPARQL #Wikidata​ retour aux bases #3 - YouTube
    • Wikidata, Linked Data… all the data! Knowledge representation for everybody - YouTube
    • Wikidata Nigeria tutorials on YouTube - How to contribute to Wikidata, add statements for streets named after a person
    • SPARQL Wikidata tutorial (in Portuguese) - YouTube
    • LIVE Wikidata editing #42 - YouTube, Facebook

• Tool of the week
  • User:Nikki/Ranker.js adds a link to the Ranker tool next to every property on an entity page.

• Other Noteworthy Stuff
  • The Wikibase spring release is now available! This new release is compatible with MediaWiki 1.35 and it contains new features: Federated Properties, WikibaseManifest & Wikibase Pingback.
  • May 2021 Query Builder updates: We finished usability testing of new features and incorporated feedback from users including people with visual impairments and RTL languages. It is now possible to query for dates and we're also looking into making the Query Builder discoverable from the Wikidata Query Service.
  • Template:Generic queries for filmmakers is a new wikidata template which defines generic SPARQL queries specific for filmmakers.
  • Template:Generic queries for occupations is a new wikidata template with generic queries for items of items such as occupations or professions
  • Wikimedia Foundation 2021 Board Elections has been announced. Please sign-up as an Election Volunteer if you'd like to support the elections. Election Volunteers serve as a bridge between the Elections Committee, the facilitation team and the movement.
• Did you know?
  • Newest properties:
    • General datatypes: Digital Atlas of Idaho URL, identifier shared with lexeme, audio transcription
    • External identifiers: MyBIS species ID, Beirut Arab University's Libraries title ID, Gardens of the Roman Empire ID, Ultime lettere di condannati a morte e di deportati della Resistenza italiana person ID, NBM authority ID, MileSplit ID, Mixcloud ID, Forbes (Russia) profile ID, am.hayazg.info ID, bridgesport.ru player ID, APA Dictionary of Psychology entry, The Draft Review ID, Nevada SHPO marker ID, IUCN Green List ID, National Association of Teachers of Singing member ID, Danmarks Tekniske Kulturarv book ID, Auschwitz Prisoners Database ID, Biology Online Biology Dictionary entry, Biblioteca di Santa Sabina ID, Senate of Romania person ID, Chamber of Deputies of Romania person ID, LMIC musician ID, Scholarpedia article ID, Historic Hawai‘i Foundation place ID, Digital Library of Armenian Literature author ID, Den Danske Ordbog article ID, Den Danske Ordbog idiom ID, OpenCorporates register ID, Biblioteche della Custodia di Terra Santa a Gerusalemme ID, IBSF competition ID, SAIA authority ID, Football Association of Norway Club ID, music austria ID, Secondary Archive artist ID
  • New property proposals to review:
    • General datatypes: official podcast, Danish redlist ID, Velocity Relative to Earth, athletics program, North Carolina session law
    • External identifiers: vedidk ID, MyBIS protected area ID, COG ID, Badok ID, Biographical Dictionary of Chinese Christianity person ID, DTB-Gerätturner-ID, Encyclopedia of Renaissance Philosophy ID, UK Renewable Energy Planning Database ID, University of Washington Campus Map ID, Australian Music Centre composer ID, Romanian Ministry of Foreign Affairs - diplomatic mission IDs, SOUNZ work ID, Canadian Music Centre Composer Showcase ID, Repositório da Produção USP Person ID, Online Archive of California finding aid ID, SOSBrutalism ID, Microlepidoptera.nl ID, OSDN project, SOR bird ID, Companies Registration Office (Ireland) Registration Number, ToateAnimalele ID, Muziekencyclopedie ID
  • Query examples:
    • List of French firms without SIREN id (P1616) ordered by number of sitelinks with search links in annuaire-entreprises‧data‧gouv.fr : the query makes it easy to find the SIREN number (P1616) (source Property talk P1616)
    • Number of works per year by researchers supervised by Lars Kai Hansen (source)
    • Count of sitelinks of Nigerians on Wikidata (Source)
    • 30 largest cities with female mayor (Source)
    • Recent locations of boundary stones in Upper Lusatia (see pictures by clicking on the dots) (Source)
    • Types of items in Australia that don't have identifier properties (Source)

• Development
  • Omaha-Ponca language is now available for monolingual text properties. (phab:T265296)
  • Added a meaningful error message when trying to use Special:EntityData with a Lexeme subentity like L123-F1 in cases where the Lexeme L123 was redirected to another Lexeme (phab:T257494)
  • Changed the “type” and “value type” constraints to ignore deprecated values (phab:T170401)
  • Working on rendering empty claims in JSON as `claims: {}` instead of `claims: []` (phab:T241422)
  • Investigating some issues with page_props missing on Commons wiki after adding sitelinks to Commons categories (phab:T280627)
  • Removed Google Knowledge Graph Id (P2671) and Wolfram Language entity code (P4839) from the Property Suggestions as they are usually not useful suggestions (phab:T280779)

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.

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 13:21, 10 May 2021 (UTC)

Update Ancient History Encyclopedia

Hello! I was wondering whether someone with more knowledge about Wikidata than I could update Ancient History Encyclopedia (https://www.wikidata.org/wiki/Property:P9000)? The publication recently rebranded to World History Encyclopedia, and all links should now point to https://www.worldhistory.org/$1 instead of https://www.ancient.eu/$1. Is it possible to change the name and URL accordingly? Thanks!

should be done. thanks for the tip. BrokenSegue (talk) 02:33, 12 May 2021 (UTC)

"manual" update of constraint violations pages

Is there actually a way how you can make the KrBot2 that it should please refresh the page Wikidata:Database reports/Constraint violations/P2991 again? --Gymnicus (talk) 15:24, 10 May 2021 (UTC)

No. KrBot2 updates are a pretty heavy operation. The bot operator processes an offline dump to update these reports every couple of days. —MisterSynergy (talk) 15:33, 10 May 2021 (UTC)

@MisterSynergy: Interestingly, the KrBot updated the page right now. How did it come about now? --Gymnicus (talk) 15:36, 10 May 2021 (UTC)

Well, that's unusual. Maybe you got a special treat by the operator? Usually KrBot2 makes these updates, not KrBot. —MisterSynergy (talk) 15:40, 10 May 2021 (UTC)

I started update procedure manually. This can be done for small reports (less than ~2000 items). Direct access to Wikidata is used in this case. This makes many requests to Wikidata engine, so it can not be used in regular basis unfortunately. — Ivan A. Krestinin (talk) 15:50, 10 May 2021 (UTC)

For some of the constraints, there is the option to run the queries on property talk pages. This should give the same or similar results. --- Jura 06:24, 12 May 2021 (UTC)

single (Q134556) or musical work (song) (Q2188189)

Today I was looking at wikidata item Mag ik dan bij jou (Q19696999). This item descibes a beautiful song of the dutch performer Claudia de Breij. It is labeled as instance of single (Q134556), in my opninion it should be labeled as musical work (Q2188189). A single is descibed as "type of music release usually containing one or two tracks". Musical work is described as "musical work of art" or "piece of music" My interpretation: a single is something you put on your record player. The musical work is the song itself, the creative work.

What do you think? JohnBoers (talk) 07:07, 12 May 2021 (UTC)

In my experience the modelling of musical works in Wikidata is highly inconsistent/undocumented. Wikidata:WikiProject_Music lays out some intended modelling, but it isn't currently widely followed/enforced in practice. There's also some confusion I've ran into (archived discussion here) in the past around the modelling of the fundamental items, see musical work (Q2188189) vs composed musical work (Q207628). --SilentSpike (talk) 11:05, 12 May 2021 (UTC)

• @JohnBoers: You are right with your interpretation. It seems that the title may refer to both: a single (as indicated in the Dutch Wikipedia infobox) and a song (as indicated in the description). The best way would be to split the item into one item for the song (with music brainz work id) and one item for the single. You may look at Wikidata:WikiProject_Music#Composition_properties/Wikidata:WikiProject_Music#Release_properties or (for instance) Boys Don't Cry (Q1823033)/Boys Don't Cry (Q62054656) as a reference. Also pinging @Moebeus: - in case I forgot something. - Valentina.Anitnelav (talk) 12:49, 12 May 2021 (UTC)
• @JohnBoers: There should be separate item for single, song and each release version of single so German CD single etc. See Angels Ain't Listening (Q91933505), Angels Ain't Listening (Q93373704) and Angels Ain't Listening (Q96000540). Eurohunter (talk) 13:39, 12 May 2021 (UTC)

Merging Multiple Items (WMSE immport of libraries)

Hello!

I recently noticed there are four entries for the same public library in Findlay Ohio and looked into merging them.

• Q69961220
• Q69961218
• Q69487490
• Q30289487 - Notably uses the full name instead of an abbreviation. Unsure if this should be merged with the others or not due to slight differences (I'm 99% sure that on the ground, these are one and the same, but maybe there's some library nuance I'm missing?)

However I got an error when I tried to use the merge tool, and noticed that these items refer to themselves anyway, so I figured I would ask a more experienced user first so I didn't mess anything up.

Thank you for your time! Mbrickn (talk) 00:55, 12 May 2021 (UTC)

The labels & descriptions used for the first three were arguably suboptimal, but the P31 property specify they are, respectively, a bookmobile, a main library and a library network - all imported from the same source, the Public Libraries Survey 2017. They are not duplicates. The fourth (described variously as an archive organization / cultural instituton) might be a duplicate (of the main library or the network), but might equally be a discrete sub-entity worthy of an item. For now I've made it part of the network, which precludes it being merged. I think there's little more to do here, sadly. --Tagishsimon (talk) 01:16, 12 May 2021 (UTC)

@Mbrickn, Tagishsimon: Sadly thousands of libraries were imported from that data source without a much diligence to see if there was an existing entry in Wikidata. I've had to merge dozens of these in the past. In this case I merged Findlay-Hancock County Public Library (Q30289487) with the "library network", which is the top-level organization that the associated identifiers and website point to - also fixed the name to match what is on the library website. ArthurPSmith (talk) 16:50, 12 May 2021 (UTC)

• @Alicia Fagerving (WMSE): fyi --- Jura 18:16, 12 May 2021 (UTC)

Thank you for your explanation and assistance! ---Mbrickn (talk) 18:58, 12 May 2021 (UTC)

ballot initiative

It seems that for ballot initiative winner (P1346) is used to indicate vote outcome. See for example https://www.wikidata.org/wiki/Q21812812#P1346, however it seems that winner (P1346) was not designed for this and indicates the winner of a competition, an awardee etc. Is there a better property or would it make sense to extend the definition of winner (P1346) to include ballot initiatives? I think the English (winner) and German definition (Sieger) dont make a ton of sense in the context of ballot initiatives. --Hannes Röst (talk) 17:32, 12 May 2021 (UTC)

Plural units

This might be a somewhat fussy/low-priority task, but it's always irked me a bit that we describe the cost of something as "47 United States dollar" or the height as "47 foot" or the area as "47 acre". We do have lexemes that seem to record the plural forms of these units, e.g. acre (L15846); would it be hard to get those connected so that plural units are displayed properly as plural? {{u|Sdkb}} ^talk 02:19, 7 May 2021 (UTC)

As far as I'm aware, in English and Dutch we do not use plural in these constructions. For other languages I do not know, but the English examples you give here are syntaxically correct to me. Edoderoo (talk) 05:41, 7 May 2021 (UTC)

We'd say "the cost is 47 dollars" or "the campus is 48 acres", not "the cost is 47 dollar" or "the campus is 47 acre". {{u|Sdkb}} ^talk 17:53, 7 May 2021 (UTC)

The way units are used depends on the language. For instance, "three metres" in German is "drei Meter", using the singular form. It would be a nice project to develop a tool which renders grammatically correct quantity expressions for various languages using lexemes. Toni 001 (talk) 08:03, 8 May 2021 (UTC)

Wikidata is mainly for machine. Grammar no matter. Machine read data, third party user modify format as user want. All good. -Animalparty (talk) 21:04, 7 May 2021 (UTC)

• frwiki has a module that renders this correctly for French. --- Jura 12:18, 13 May 2021 (UTC)

should i merge artist and artist commonswiki category?

when i try to add commonswiki site link on Linda McCartney (Q228899), it says interwiki conflict with Category:Linda McCartney (Q8591290). earlier i raised similar question on interwiki conflicts chat. however, i request you to suggest best way to resolve this issue. Gi vi an (talk) 07:00, 12 May 2021 (UTC)

@Gi vi an: A short answer is "no". We usually keep distinct items for concepts and their Wikimedia categories. Vojtěch Dostál (talk) 08:25, 12 May 2021 (UTC)

You can try to merge the two with the merge gadget. The resulting error message should explain it too. --- Jura 12:14, 13 May 2021 (UTC)

Undergrad research topic

Hi! I am a Wikipedian and an undergrad database management student and was wondering if someone could recommend a Wikidata- or Wikipedia-related research topic I could pursue for my coursework. Also, where would I look for papers and such on this topic? (I need to be able to cite academic sources.) Thank you much! Datumizer (talk) 03:46, 13 May 2021 (UTC)

Google Scholar with "Wikidata" gives 3k hits, not enough? --SCIdude (talk) 07:10, 13 May 2021 (UTC)

Importing from dbpedia

I can't find any modern discussion of the idea of importing data from dbpedia (and also yago). There's some really old and extremely old RFCs but nothing in the last few years that I can find. What would the community reception to these various concepts be (assuming that we properly annotate all the statements as "imported from dbpedia").

1. make a tool that lets users approve suggested imports of statements
2. automatically import missing instance of (P31)s
3. automatically import diverse properties (e.g. duration (P2047), language of work or name (P407), genre (P136), official website (P856), country (P17), etc)

Imagine enriching Fly (Jessica song) (Q40761569) with some of the content of [14] (or other such pairs).

It would be similar to our infobox imports but through an intermediary. Would a Bot RFP for some property be a good place to start? Are there suggestions

BrokenSegue (talk) 05:09, 13 May 2021 (UTC)

• Essentially, it's data from Wikipedia and its infoboxes. dbpedia's parsing is more advanced than that of Harvesttemplates and a few other tools. Accordingly, I think similar prudence is advised. Harvesttemplates generally works well in fairly focused imports. --- Jura 12:25, 13 May 2021 (UTC)

Logic follows another path; as the dbpedia's parcing is more advanced that of our own tools, given that it freely available we will improve our quality by making use of Dbpedia. Thanks, GerardM (talk) 14:42, 13 May 2021 (UTC)

Time to seriously investigate if WD or WP is more up-to-date? --SCIdude (talk) 14:59, 13 May 2021 (UTC)

Almost certainly WP for anything that can't be automatically kept up to date which is where we have an edge. BrokenSegue (talk) 15:43, 13 May 2021 (UTC)

You are forgetting one major detail. DBpedia consolidates what is available in Wikipedias, Wikipedia is one project at a time. Thanks, GerardM (talk) 15:47, 13 May 2021 (UTC)

• The data quality isn't extremely good. Might be good enough to import some data to item here that are nearly empty, but please don't import any data to mature items. Tools like https://item-quality-evaluator.toolforge.org/ and recoin can help you evaluate the quality of the item. Multichill (talk) 16:41, 13 May 2021 (UTC)

  @Multichill: do you know if there's a way to query that tool to find the low quality items? BrokenSegue (talk) 17:37, 13 May 2021 (UTC)

  @BrokenSegue: number of statements give an indication, see for example https://w.wiki/3KdQ . Not sure if and how ORES is exposed in the API otherwise what might be usable in combination with a SPARQL query. I recall having conversations about maturity of items before, but I'm not sure if we ever wrote it down. Might be useful to document with some pointers for reference for future tools and/or bots. Multichill (talk) 18:26, 13 May 2021 (UTC)

  Not sure how ORES would help you with this.

  I think the main problem could be instance of (P31). Wikipedia articles can have infoboxes on several aspects and they might all end up on the same dbpedia page. --- Jura 21:33, 13 May 2021 (UTC)

justice of the Supreme Court of Canada (Q843020)

This item seems to conflate (1) lists of justices of the Supreme Court of Canada in various wikipedias; and (2) the position of justice of the Supreme Court of Canada—that is, a value of position held (P39). To de-conflate, I was thinking I'd repurpose this item to correspond solely to meaning/use (2) (to avoid having to rejigger all the items that link to it in that role) and create a new item corresponding to meaning/use (1). Does that sound reasonable, or is there something else we should do in this kind of scenario? AleatoryPonderings (talk) 15:45, 13 May 2021 (UTC)

That's a good plan. Lots of P39 uses of the item. --Tagishsimon (talk) 15:52, 13 May 2021 (UTC)

List all items with a starting letter

Hi, I'd like to list all given name (Q202444) starting with the letter P (Q9946) (in alphabetical order). Can someone tell me how to do this? --Bruder Vio (talk) 16:23, 13 May 2021 (UTC)

Here's a query for items that are Q202444 (https://w.wiki/3KcM), and here's one that includes all subclasses of given name (https://w.wiki/3KcP).

I hope that gives you what you were looking for. If not, you can adjust the query by going to the toolbar to the right of the results and clicking "Edit SPARQL". If you get stuck or have any questions, just give a shout!

--Quesotiotyo (talk) 17:33, 13 May 2021 (UTC)

Thank you very much, this helps! --Bruder Vio (talk) 18:44, 13 May 2021 (UTC)

Annoying merge limit

I tried to merge from Q61171795 to Q8644509. I had to remove all decriptions because of conflicts (taking a minute or two), but the page would not be saved because of an anti-abuse limit. Utfor (talk) 20:25, 13 May 2021 (UTC)

"removing all decriptions because of conflicts" isn't a thing. You wasted your time. I've merged the two items; not sure what the anti-abuse issue was about. --Tagishsimon (talk) 21:12, 13 May 2021 (UTC)

• What function did you use? --- Jura 21:26, 13 May 2021 (UTC)

Regex issue with Central Index Key (P5531)?

While working on Enbridge (Q1339966), I noticed that Central Index Key (P5531) threw an error when I put in the (apparently) correct value of 895728 for this company. I suspect the error has something to do with the fact that Enbridge is a foreign private issuer according to the rules of the U.S. Securities and Exchange Commission (Q953944). Is there something to fix here? AleatoryPonderings (talk) 16:16, 12 May 2021 (UTC)

• Seems to require zero-padding. Bots can fix that. --- Jura 18:01, 12 May 2021 (UTC)

• In so far as the link - https://www.sec.gov/edgar/browse/?CIK=895728 - works, the possibility is that WD's insistence on 10 digits is incorrect? --Tagishsimon (talk) 07:52, 13 May 2021 (UTC)
  • Possible, but that would mean Wikipedia's description is incorrect too: see "The numbers are ten digits in length." at w:Central_Index_Key.

That a partial key can be used to link one database doesn't mean it's correct.--- Jura 12:12, 13 May 2021 (UTC)

In so far as EDGAR specifies that the CIK: for ENBRIDGE INC is "895728" (expand the 'Company Information' header - https://www.sec.gov/edgar/browse/?CIK=895728), we can conclude that w:Central_Index_Key is making it up as it's going along, and our padding is a cargo cult. --Tagishsimon (talk) 23:18, 13 May 2021 (UTC)

• Feel free to "sofixit" ;) --- Jura 08:37, 14 May 2021 (UTC)

Zero-padding fixed it. Good to know for next time. AleatoryPonderings (talk) 15:47, 13 May 2021 (UTC)

• I added an autofix at [15]. It takes a few days till a bot fixes them. --- Jura 21:29, 13 May 2021 (UTC)

Cleaning up WD:Do not merge

I don't know a better place to ask for, so I'm asking here: Would it be useful to check the Do not merge pages for expired DNM's (i.e. merged or deleted items) and remove those? I don't know if it is worth the time and/or storagespace to clean up expired sets. I think a bot should be able to do such task relatively quick. Q.Zanden questions? 21:38, 13 May 2021 (UTC)

In my opinion all do not merge pages should be deprecated in favor of different from (P1889).--GZWDer (talk) 01:33, 14 May 2021 (UTC)

I don't really know what they are used for (beyond the bots mentioned there), but having the information (also) as statement does sound useful. --- Jura 08:38, 14 May 2021 (UTC)

Tool request: Users can enter an ISBN to see if a Wikidata item exists, if not it makes a new one based on the data available (works like 'Cite' tool on Wikipedia)

Tracked in Phabricator
Task T282719

Hi all

I would really love a tool that worked a bit like the 'Cite' on Wikipedia, that can tell you if there's already an item for an publication with an ISBN and if not it goes to get the data to make a new one. The process of using it would be something like:

1. User enters an ISBN on a page and it says if there is an item on Wikidata which has this ISBN
2. If there is already an item which uses this ISBN the tool suggests extra statements to add that the user just clicks to add them. The tool gets the data from the same place the Cite tool on Wikipedia does.
3. If there isn't already an item using this ISBN, the tool prefills a form for the new item which the user click to create. It then looks for any item on Wikidata with the same name and author to find other editions and then connects them together using which ever statement is needed.

Is this possible/realistic? Would be a really nice thing to have. I'm sure there could also be an option to enter multiple ISBNs but I don't know what's the best layout for that.

Also how could I propose this as a project for the Wikimedia Hackathon? I don't know if there's a category for ideas from non programmers? Should I write it up as a phabricator task and add some tags?

Thanks

--John Cummings (talk) 11:37, 12 May 2021 (UTC)

There was plan to add Citoid support on Wikidata (phab:T199197), and a working version has already existed on https://test.wikidata.org/ for quite a while, but it seems the deployment was somehow stalled. --Stevenliuyi (talk) 12:45, 12 May 2021 (UTC)

Thanks Stevenliuyi, I've asked what the issue is. --John Cummings (talk) 12:01, 13 May 2021 (UTC)

This would be amazing. It absolutely boggles my mind that the powers-that-be of Wikdiata haven't recognized that one of the solutions to the problem of millions of unreferenced statements is making references easier to generate and add. -Animalparty (talk) 21:49, 12 May 2021 (UTC)

Glad you like it Animalparty, if you could add your support to the phabricator task that would help. Also if you know anyone who could make it that would be amazing. --John Cummings (talk) 12:01, 13 May 2021 (UTC)

@Fnielsen: Lucie Kaffee suggested I ask you, any suggestion? John Cummings (talk) 18:01, 13 May 2021 (UTC)

@John Cummings: Thanks for the suggestion. I have added it as a Scholia issue. I am wondering where we would get the metadata from? Are there databases with a CC0 license? For instance, Worldcat. — Finn Årup Nielsen (fnielsen) (talk) 10:51, 14 May 2021 (UTC)

Fnielsen thanks very much, do you know what databases exist or where I could possibly find a list of them? I'm happy to look for licenses. --John Cummings (talk) 11:52, 14 May 2021 (UTC)

Grant request: Nigerian Sports Ambassador on wikidata

i proposed a project on putting Nigerian Sports Ambassador on wikidata. Your advice will be appreciated. the link is https://meta.wikimedia.org/wiki/Grants:Project/Rapid/kid_keen_47/Notable_Nigerian_Sport_Ambassadors#Resources. --Kid Keen 47 (talk) 20:50, 14 May 2021 (UTC)

Member of a First Nation

What’s the right statement to describe a member of a First Nation (also called an Indian band, Indian reserve, etcetera)? It is a cultural community, not an ethnic group.

Related: the description of member of (P463) says not to use it for a social group, but not what to use. There is also human social group (Q874405) and social community (Q4430245), but they aren’t defined with precision. —Michael Z. 02:32, 10 May 2021 (UTC)

@Mzajac: this was discussed pretty recently. maybe the old conversation will help some Wikidata:Project_chat/Archive/2021/04#Wikidata_properties_for_tribes? BrokenSegue (talk) 04:15, 10 May 2021 (UTC)

Thanks. Tagging user:*Treker, who was planning to propose a property. national citizenship (Q42138) may be a good model for this.

For general info, a Canadian First Nation, a First Nation band (Q2882257), is not an ethnic group or sub-group. Some have only dozens of residents. Some have multiple Indian reservation of Canada (Q155239) associated with them, and also traditional lands beyond their boundaries. Membership in a First Nation is separate from residence there: one can have either or both. Most, but not all members are registered under the Indian Act (Indian Register (Q2095049)). Inuit and Métis people do not have this arrangement. (I am no expert; just sharing the basics I’m aware of.) —Michael Z. 15:24, 10 May 2021 (UTC)

@Mzajac: I am still planning on proposing a tribe propery (and maybe two separate properties for federally recognized tribes of the US and First Nation bands of Canada), but I want to a really good job of it and since I'm a bit sick right now I will likey wait until I have the energy in a few days. I think it's absolutely a thing that's needed for Wikidata.*Treker (talk) 19:09, 11 May 2021 (UTC)

Thank you. I don’t know much about US tribes, but it would be beneficial if a generalized property could work for membership in Indigenous groups everywhere, and perhaps specific subclasses added if and when necessary – otherwise this exercise will just be repeated again and again. Recently Canadian First Nations have been establishing that they legally exist beyond the borders of Canada.[16] There are also Indigenous peoples in hundreds of countries in Oceana, Australia and New Zealand, Lapland, Crimea, the Philippines, etc. —Michael Z. 19:21, 11 May 2021 (UTC)

There is some info from WikiDataCon 2019 on this, for example Smallison's talk and the subsequent [17]. I can't find the info for the user group for some reason. There are also a number of Wikiprojects that should be brought into ths convo: WikiProject Indigenous peoples of North America, Canadian Aboriginal Languages Wikipedia Coordination, Indigenous Languages and Knowledge on Wikimedia Projects Toolbox, etc. Dropping us a line at the Inari Saami or the Northern Saami wikipedia would be much appreciated so we can participate in the convo. Pinging Amqui too. -Yupik (talk) 21:49, 14 May 2021 (UTC)

Bots using Labels to Potentially Misgender Humans

I have been excluding "sex or gender" from items I create for humans intentionally when I do not know the gender identity of the person. A bot by Jura has been going through and adding given names to items for people whose labels match the label for a given name. Often, these are defined as "male given name" or "female given name". While the descriptions of these names qualify them as "usually" meant for male or female people and seems benign enough, the statements "subclass of" "given name" "of" "female human" or "male human" allows the person's sex or gender to be inferred, potentially incorrectly. Once these statements have been made, another bot by Lockal comes through and adds a sex or gender statement which may or may not be accurate. Here is an example. It is likely that most of the statements both bots generate are correct (it was correct in this example). However, I also think the situation of both these bots working simultaneously is heavily biased towards cisgendered people, especially those in cultures where unisex names are commonplace. In this example, I do not know the person's gender identity and the statements the bots have made could have misgendered this person. I did some poking around on Wikidata to see if this is a major discussion somewhere and couldn't find anything besides some specific cases where people were cleaning up misgendered items. Is there a way for a conversation to be had about these gender-assumptions we're making? Or, to weigh the pros and cons of untethering given names from gender in Wikidata? I can see how, when a person's gender is known, having a given name that reflects their gender could be cool, but that is accomplished by P21 which is widely used so I don't think the benefits outweigh the harm that could be done by misgendering people on Wikidata. --Crystal Clements, University of Washington Libraries (talk) 20:41, 13 May 2021 (UTC)

These edits are definitely incomplete. They should include based on heuristic (P887) inferred from person's given name (Q69652498) as a qualifier or reference in order to track provenance of these statements. Editors can then add further evidence as it might surface in any given case, e.g. self identified sex or gender, gender-specific styles ("Mr."/"Mstr." vs. "Mrs."/"Miss" or whatever). The gold standard is of course self-identification of preferred gender, but realistically that's going to be exceedingly rare for pre-20th century humans, and still uncommon afterwards.

Why identify sex or gender at all if it can't be reasonably determined? --Crystal Clements, University of Washington Libraries (talk)

That's a very reasonable question wrt. Wikidata:Living people. Inferring plausible gender from given name is far from foolproof, given that, e.g. the gender specificity of personal names can change over time and across cultures, and exceptions can always exist. For what it's worth, the main argument for recording this sex or gender (P21) data for living people at all has been that people will want it in order to compute gender representation statistics wrt. authors, researchers etc. as well as more general statistics relating to Wikidata itself, and having Wikidata try to infer the data for reusers might be better than the alternative of everyone trying to do this in different and perhaps problematic ways. It's not clear that this should override our more general policy wrt. privacy-sensitive data as it relates to present-day humans.

Yeah this is bad. Are either of these bot actions approved? They aren't happening on bot accounts but if they are regular batch tasks they probably need to be approved. BrokenSegue (talk) 01:12, 14 May 2021 (UTC)

I don't know anything about the bot approval process, so I don't know. I know it happens semi-regularly. How does one find out BrokenSegue? --Crystal Clements, University of Washington Libraries (talk) 01:37, 14 May 2021 (UTC)

we could look through the history of bot approvals but probably best just to ping the two people and wait for feedback. If they went through the bot approval process I would've asked them to at the least provide references which would help unwind this. @Lockal: @Jura1: BrokenSegue (talk) 01:55, 14 May 2021 (UTC)

@BrokenSegue, Clements.UWLib:, don't understand why you call gender in these items as unsourced/unknown. James Freese is linked to materials from a member of the International Botherhood of Electrical Workers and described in a various IBEW Local 46 sources as a male. James M. Smith is linked to "James M. Smith audio recordings and papers", where again, he is described as a male. Also I don't do any bot works with P21, this upload was targeted to specific subset. --Lockal (talk) 08:46, 14 May 2021 (UTC)

@Lockal: The issue isn't with any particular item it's with the general approach. Also, if this wasn't an automatic action how did you generate the subset? Did you manually vet it? The line between bot and "large batch action" is kinda blurry and people don't seem to agree when approval is needed. Do you regularly do this? BrokenSegue (talk) 16:03, 14 May 2021 (UTC)

@BrokenSegue, Lockal: Right, the issue isn't necessarily with an item, it's with the approach. Lockal, would you be amenable to adding references to sex or gender (P21) claims in the future, especially those using batch processes? If you're manually vetting the batches, it should be easy to do. --Crystal Clements, University of Washington Libraries (talk) 16:19, 14 May 2021 (UTC)

Ok, I agree. I usually add references with external identifiers, if available, and vetting the batches in various ways (there were batches deduced from pronouns, deduced from birth place, because, well, it is legally impossible to get female name in Russia if you are a male). Sorry if I bothered you, I am just a part of language culture that considers gender as a "common knowledge" (as with P31=Q5 - just go to any external identifier and expect to see that information). For now I have no plans to deduce gender from names, but if I get some, I'll add some extra details to make statements more clear. --17:07, 14 May 2021 (UTC)

@Lockal: Thank you, this seems like a good plan/resolution to me. --Crystal Clements, University of Washington Libraries (talk) 19:54, 14 May 2021 (UTC)

• Our bot policy says: "Add sources to any statement that is added unless it has been agreed the data is 'common knowledge' in which case the bot should state where the information has been copied from." I therefore do agree that the bot shouldn't add unsourced claims. I however think based on heuristic (P887) inferred from person's given name (Q69652498) is reasonable.

The motivation for listing gender is that it's required for forming grammatically correct sentences in many languages. Wikidata exists for people from different cultures and some cultures do need gender to make statements in their languages. Just because some Anglo people don't like explicit statements about gender doesn't mean we should declare those statements generally unwelcome and prefer the cultural values of that Anglo group over others. ChristianKl ❪✉❫ 15:21, 14 May 2021 (UTC)

I agree that the main issue here is the lack of references in both edit batches. I will, again point people to my proposal at Wikidata:Project_chat/Archive/2021/05#Requiring_References_in_QS. BrokenSegue (talk) 16:03, 14 May 2021 (UTC)

@BrokenSegue: I like the idea of requiring references for a defined subset of properties when using tools like Quickstatements, but not for all statements wholesale. That would become repetitive and burdensome really quickly. As others point out, identifiers and P31 statements are self-referencing. For the purpose you were going for, are property constraints requiring references sufficient? Since the discussion you're pointing to is archived, it seems I can't comment on it directly. --Crystal Clements, University of Washington Libraries (talk)

@ChristianKl: I see your point about languages, but I reject the notion that all people in any culture can be crammed into a binary conception of gender. And, more to the point, I don't think it's a good practice to infer someone's gender identity based on their label alone. Could this problem be solved by adding a reference requirement to sex or gender (P21)? --Crystal Clements, University of Washington Libraries (talk) 16:19, 14 May 2021 (UTC)

People are not being crammed into a binary conception of gender; WD supports a wide array of values for P21. Whereas I understand some of the concerns expressed above, I'd favour seeing an evaluation of evidence of a problem before we reach for a solution. I note that gender is not something, for most individuals, for which easy references exist, beyond 'inferred from x', and I question the utility of that sort of reference; not least it does not solve the problem, but merely requires the user to codify the basis of their P21 evaluation; which is to say, if subjects are being misgendered, then in the future they would be misgendered with a reference. --Tagishsimon (talk) 20:14, 14 May 2021 (UTC)

the value of the reference is not that it merely exists but that it tells you how it was determined. this way someone later on can decide if some means of inference is acceptable to them. in that way providing the reference actually could weaken the impact of the statement i.e. "oh this was just guessed from their first name" BrokenSegue (talk) 20:33, 14 May 2021 (UTC)

I agree with what BrokenSegue says above, and also want to point out that this issue is stemming from assumptions being made about a person's gender identity based on their given name. So, while there are a wide array of options for values of P21, the only ones I've seen get assigned based on label alone, or based on nothing at all, are "male" or "female". --Crystal Clements, University of Washington Libraries (talk) 22:42, 14 May 2021 (UTC)

This has come up every once in a while in the Wikimedia LGBT+ user group, but no solution has been found because the people doing it don't seem to consider it a problem. (There are also more people than those listed above doing this.) Perhaps they can understand that this is problematic from a legal perspective: there are countries that do not consider the gender binary relevant for various reasons, including ones where gendered languages are spoken. So IMO we should not be misgendering people based on something trivial like a first name. Moreover, it should not be included as a constraint violation in properties either, since this just makes this autogendering more appealing to get rid of the constraint violations. -Yupik (talk) 22:18, 14 May 2021 (UTC)

@Yupik: I'm glad this issue has come up somewhere, and disheartened to hear that those doing it don't consider it a problem, when people have told them "hey, this is a problem". I agree with you wholeheartedly that P21 should not be included as a constraint violation. I just sent an email out to the mailing list about this, and am hoping that a productive conversation can be started in whatever the appropriate channels are. Is Project Chat the ideal place to bring these concerns? Communication channels are overwhelming in number. --Crystal Clements, University of Washington Libraries (talk) 22:42, 14 May 2021 (UTC)

tl;dr, but I'm not sure anyone has claimed that 'it' is not a problem, for any of the values of 'it' that readers hold dear. There are a range of different interests in play, such as the reasonable insistance that all gender statements are accurate / evidenced / referenced versus the reasonable wish to be able to produce by gender stats given the scale of biog items; or the reasonable wish to get things right, from the start, versus the view that with enough eyeballs, all bugs are shallow and mistakes / poor assumptions will be fixed in reasonable time. --Tagishsimon (talk) 09:53, 15 May 2021 (UTC)

Change property while keeping the values

I noticed some items that use an incorrect property for several statements. If I wanted to fix that manually, I would need to remove all the values and add them again with the correct property. This can be a lot of work for example for Amsterdam Airport Schiphol (Q9694) which uses connecting line (P81) for 21 different destinations instead of scheduled service destination (P521). Is there an easier way for that like a tool that just changes the property for all statements? --PhiH (talk) 06:23, 15 May 2021 (UTC)

@Pasleim: Data Gamer ^play 08:41, 15 May 2021 (UTC)

@PhiH: Move Claims 2 is probably what you are looking for. It adds a "move" button to the statement and you can copy or move the statement to another item or property. You find it in this list: Wikidata:Tools/Edit_items. - Valentina.Anitnelav (talk) 09:58, 15 May 2021 (UTC)

Thanks, that makes it a little easier. Unfortunately it's not possible to move all statements at once. --PhiH (talk) 10:20, 15 May 2021 (UTC)

See list

Please see Wikidata:WikiProject every politician/European Union/Q8880/positions. In the last column there is an option (see list). I have tried to do the same to Wikidata:WikiProject every politician/Cyprus/Cyprus Goverment/positions but I wasn't able. I have already created the lists. For example, Wikidata:WikiProject every politician/Cyprus/Cyprus Goverment/positions/Q65600632. Data Gamer ^play 08:39, 15 May 2021 (UTC)

First, both tables look completely borked, printing class='wd_p2389' into columns rather than values. I think (see list) may be provided only where there is a counterpart page in the form https://www.wikidata.org/wiki/Wikidata:WikiProject_every_politician/European_Union/officeholder/Q8882 - so, for instance, there is not such a page at https://www.wikidata.org/wiki/Wikidata:WikiProject_every_politician/European_Union/officeholder/Q651703 and so the Vice-President of the European Commission (Q651703) position gets no (see list).

It doesn't seem particularly helpful to have PositionHolderHistory lists squirreled away under the EveryPolitician subfolder, in so far as the natural place for such lists is on the talk pages of the positions. Nor do I know how such pages are created. It's possible @Teester: may be able to help, having been active in this area.

I presume it is the /row page which is borking the table, but I lack the fu to work out what's going wrong. --Tagishsimon (talk) 09:43, 15 May 2021 (UTC)

Thanks. I have found the problem. It must be in the form **/officeholder/Q** .Data Gamer ^play 09:49, 15 May 2021 (UTC)

Tm

Hi. The user Tm insits on adding names in Portuguese in the English section of Q3375706. Could someone stop him? --Lojwe (talk) 23:37, 4 May 2021 (UTC)

And what about you deleting sourced alternative names in Portuguese, for several weeks? Tm (talk) 23:41, 4 May 2021 (UTC)

Those names are incorrect. They should be deleted too, but, as you are difficult to deal with, I prefer to go step by step. --Lojwe (talk) 23:49, 4 May 2021 (UTC)

Yes, ironically, those names are "incorrect names" by your own words, but so much wrong, that "Empreendimento Hidroeléctrico do Douro Internacional / Picote" is the name given by the portuguese state DGPC - Directorate-General for Cultural Heritage, "Aproveitamento Hidroeléctrico do Douro Internacional - Picote" is the name given by the portuguese Association of Architects or EDP, the electric utility that owned this dam and Aproveitamento Hidroeléctrico do Douro Internacional is the name used by one of the construction companies or " Empreendimento Hidroeléctrico do Douro Internacional" is used by the tourist route "Rota da Terra Fria" made by the association of the municipalities "Associação de Municípios da Terra Fria do Nordeste Transmontano". But who are they to know better than you? Tm (talk) 00:13, 5 May 2021 (UTC)

Perhaps as a compromise, Lojwe, you could stop your close policing of the addition of Portuguese language aliases as Portuguese language aliases; aliases are mainly useful as aids to discovery via search, and so in general more is better ... and Tm, you could stop adding Portuguese language aliases as English language aliases, since if they also exist as Portuguese language aliases then they will be found via search irrespective of their absence from the English language alias list. --Tagishsimon (talk) 05:32, 5 May 2021 (UTC)

• Aren't native labels fairly common as aliases (at least) in English? The main oddity here it seems to be that it might add company names to what can be seen as a geographic feature. --- Jura 09:38, 5 May 2021 (UTC)
• Do not remove Portugal names in this case from aliases. If they are "original name" for certain place or work then they bacame "common" alias for name in English or other language and should be keeped across all languages as aliases. Eurohunter (talk) 10:28, 5 May 2021 (UTC)

@Eurohunter: The user TM insists on introducing Portuguese names in the English section. He's exhausting. Can someone do something about it? --Lojwe (talk) 06:42, 11 May 2021 (UTC)

@Lojwe: Yes and that's what we wanted (original names in Portugal for Portugal places in English alias and all languages). Did read what I wrote above? Eurohunter (talk) 13:26, 11 May 2021 (UTC)

And user Lowje insists in deleting sourced native names or changing its spelling claiming a Wikidata policy that does not exist, more than one place or removing labels like "Linha Internacional de Barca d'Alva-La Fregeneda a La Fuente de San Esteban" that are the name of the article in the portuguese wikipedia. Tm (talk) 18:43, 11 May 2021 (UTC)

@Eurohunter: The name of this Portuguese place is Bemposta. Barragem (pt) is Dam (en) in English. That's what I complain about. I am not sure about what you meant before. --Lojwe (talk) 17:34, 11 May 2021 (UTC)

@Lojwe: Yes so "Dam" for label and "Bemposta" for alias in english. Eurohunter (talk) 18:19, 11 May 2021 (UTC)

The name of this damis not "Bemposta", but of the the civil parish (see Q816392) were this dam is located. Tm (talk) 18:43, 11 May 2021 (UTC)

Yes, the dam is named after the parish. Bemposta is the name of the place. Barragem is not a name of a place, is a word said Dam in English. --Lojwe (talk) 19:57, 11 May 2021 (UTC)

And yet you continue with your crusade of deleting sourced names. Tm (talk) 19:11, 13 May 2021 (UTC)

@Eurohunter: As all you can see, this User is repeating names just because he wants to always be right and impose his editions. This is madness... Here he insits on putting a name in Catalan in the Spanish section, here he insists on using a Spanish name in the French section, here he insists on writing Espanã in Catalan, instead of the correct way: Espanya... He does not even check what he's doing, just undoes what I do. Please, someone stop this disruptive and obsessive editions. --Lojwe (talk) 19:17, 13 May 2021 (UTC)

First, french, spanish and catalan are not my native languages and given that you are constantly deleting names when i´am editing, it is obvious that i can make this kind of mistakes, but of course you dont mention that the example of catalan ocurred today and yet i i had corrected the mistake in catalan two days ago but given your pattern of behaviour it is not expected that you disclose fully what has happened. Tm (talk) 19:24, 13 May 2021 (UTC)

And when you say that i "insists on using a Spanish name in the French section" I did not know that line in spanish is written ligne, i always tought that line in spanish was written as línea. How ironic, even more ironic given that it was you that added this name to the french section Tm (talk) 19:29, 13 May 2021 (UTC)

And about the use of the spanish España instead of the catalan Espanya, again you conveniently forget to say that corrected my honest mistake. Tm (talk) 19:32, 13 May 2021 (UTC)

• @Lowje: Trying to modify a portuguese description added\edited by me (a portuguese and portuguese native speaker], when you are a native spanish speaker, when i tell you that said description is perfectly correct and yet you try to modify it is uncanny, but now insulting me and saying that should read about obsessive-compulsive disorder, after calling me obssesive, is saying that i have said disorder. Not mentioning that this is an insult and demeaning to people that have this affliction, tell me that i have this disorder is an personal insult. Consequences should be taken by this unwarrented insult, to me and to other people. Tm (talk) 22:16, 15 May 2021 (UTC)

Get the number of results of a structured search in Lua

Hello

Suppose I want to get the number of results of this structured search https://m.wikidata.org/w/index.php?search=haswbstatement%3AP57%3DQ50764&title=Special%3ASearch&profile=default&fulltext=1&ns0=1&ns120=1.

Does anyone know if it's possible to get this using Lua? PAC2 (talk) 20:21, 15 May 2021 (UTC)

I guess this issue https://phabricator.wikimedia.org/T78171 is related to my problem but maybe there is something more recent. PAC2 (talk) 20:43, 15 May 2021 (UTC)

Q7215596 and Q9720642

Should the two data objects Category:Alkaline earth metals (Q7215596) and Category:Alkaline earth metals (Q9720642) be merged? --Gymnicus (talk) 07:35, 20 May 2021 (UTC)

Yes. Done. --Tagishsimon (talk) 07:41, 20 May 2021 (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) 08:41, 22 May 2021 (UTC)

request to import data from project: "Cheung Chau Piu Sik Parade"

We want to import data to WikiData from our project: Cheung Chau Piu Sik Parade

Here is the project link:

https://digital.lib.hkbu.edu.hk/hkcraft/piusik/index.php?lang=EN

Here is the dataset:

https://docs.google.com/spreadsheets/d/1iUVrHNsXVmn94IygtZYj0-foeUg9yvdOcwQ_V-CQbto/edit?usp=sharing

Thank you for your suggestions.

• Wikidata is not about uploading your CSV file but Wikipedia has it's own structure. To upload data to Wikipedia you have to think about how the information can be expressed in Wikidata's data structure. Items are about more then just label and description. ChristianKl ❪✉❫ 11:17, 7 May 2021 (UTC)
• We just want to do data donation, how can we start? --Hkbulibdmss (talk) 06:19, 10 May 2021 (UTC)

What if we first convert the spread sheet to triples. Can Wikidata import triples directly? --Justin0x2004 (talk) 12:20, 17 May 2021 (UTC)

User profiles, wikidata and allow to have links to other profile languages

Hello.

Can we officially allow (vote) a user to create a wikidata page only for the purpose of linking to profiles in different languages? Current it is not officially strictly allowed.

For example, I have a lot of posts on skwiki and hrwiki (plus, of course, enwiki), so if someone opens my profile, they would see that I also have profiles on another language wiki.

I mean to officially enable this (red in the picture) on wiki profiles.

✍️ Dušan Kreheľ (talk) 08:59, 8 May 2021 (UTC)
✍️ Dušan Kreheľ (talk) 00:19, 9 May 2021 (UTC)

It would be nice if wikidata could take care of that. At the moment there is mw:Extension:Cognate, so I wonder if it could be repurposed to link between user pages in different wikimedia wikis.--MathTexLearner (talk) 15:23, 8 May 2021 (UTC)

Proposed 4 years ago at phab:T168792. --Izno (talk) 07:05, 17 May 2021 (UTC)

You need to manage this locally via oldschool interwikilinks. This is not going to happen via Wikidata. —MisterSynergy (talk) 10:28, 9 May 2021 (UTC)

If it was possible, it would probably be nice to connect userpages via Wikidata! --Koreanovsky (talk) 10:59, 9 May 2021 (UTC)

I understand that the proposal involves creating a Q for an editor. I am against that idea. It will be great when we can have "global user pages" but creating Qs for editors is not the way. B25es (talk) 15:23, 9 May 2021 (UTC)

We already do have global user pages. However, that gives you the same content on every wiki, which you may not want (for instance, my Wikidata userpage has stuff about my Wikidata editing, while my Commons userpage has stuff about photography). Vahurzpu (talk) 16:15, 9 May 2021 (UTC)

@B25es: You also have some arguments/reasons why this is not good?

✍️ Dušan Kreheľ (talk) 23:09, 9 May 2021 (UTC)

Qs are about subjects (there used to be an old and often repeated sentence in Spanish "personas, animales o cosas", of course here we have also ideas, abstract concepts, facts, events, lands, classes of viruses...) that are relevant (worth to be mentioned) in this project. My turtle isn't and I am not either. Therefore, no Q shall be made about me (or my turtle). If at some point in time I happened to be of interest (for instance, if I run for alderman of my town hall, I think we have to be inclusive) then a Q could be made about my person.Dušan Kreheľ

If global user pages are not good enough, they should be improved. But adding Qs about subjects that do not merit it or -even worse- do not want them, that's not the way to solve the problem. I know of fellow users who have Qs because of being notable in some way: being a relevant member of WMF or a chapter, for instance. And I can't help wonder "do I really want to know who is this person's father?" -father/mother/place and date of birth/alma mater are pretty common properties about any person. Because Qs are to be filled with Ps and those filled with info. That's the nature of this project. And I really don't feel like we should have (y)our personal information here exposed as if we were Q181715, Q76754, Q57359, or Q196527.

I see your point, but the answer is not a Q for every editor. B25es (talk) 06:30, 10 May 2021 (UTC)

Dušan Kreheľ, create such a page in metawiki (link to your user page) which will act as global user page. There you can add hints to wikis where you are usually active. (Edit while still writing: I noticed that Vahurzpu already pointed to this feature.) This page will be displayed on all your user pages in Wikimedia universe for which you do not have a dedicated user page created, but only if you have at least once logged in and your account is existant in this project. You can take my user page here in Wikidata as example and see, how this may look. If there is some content on page, but you want to get the global page displayed request a local deletion. If you do want to add this information only into your userpage on Wikidata: I used the templates {{User SUL Box}} and {{BUser}} (the latter twice). — Speravir – 00:09, 11 May 2021 (UTC)

• I think the easiest solution here would be on the software side - allow old-style interwiki links (like we had before Wikidata) to work on user pages. Guettarda (talk) 13:59, 11 May 2021 (UTC)

  Don't these old-style interwiki links still work? I can't really test it, as I have only a global user page on meta. —MisterSynergy (talk) 14:07, 11 May 2021 (UTC)

  They indeed still work. And this feature even works in preview of wikieditor (flavour of 2010). — Speravir – 00:34, 12 May 2021 (UTC)

• Against: Not all partitions are important to move.--Arbnos (talk) 01:58, 17 May 2021 (UTC)

Description of templates

I just tried to merge Q26105412 and Q10976602, but the attempt was blocked due to conflicting descriptions in various languages. It seems most of the conflicting names are of the type "Wikipedia template" vs "Wikimedia template". I am wondering whether the former type can be considered obsolete (or are there cases where "Wikipedia template" works, but not "Wikimedia template"?), and if so, whether a bot could run over and fix this across Wikidata. --2A02:587:B946:8D35:F8E0:13E0:66F5:E873 10:09, 9 May 2021 (UTC)

Don't know what the problem was. I've just merged them. No bots needed. --Tagishsimon (talk) 10:30, 9 May 2021 (UTC)

Thanks. Might be s problem only when using the merge special page. --2A02:587:B946:8D35:F8E0:13E0:66F5:E873 12:00, 9 May 2021 (UTC)

In general whenever you get an error message and want help with it, it makes sense to copypaste the error message. That's true on Wikimedia and also when you ask for help elsewhere on the internet.

In this case, it would be possible that there's some rule that doesn't allow non-autoconfirmed users to make certain merges. ChristianKl ❪✉❫ 22:01, 9 May 2021 (UTC)

Not 100% certain on this, but as I believe I've run into this at least once with Special:MergeItems, this may be a quirk of how the special page works. The way most editors merge (I assume) is with the merge gadget, which has specific logic to make it ignore description conflicts. It's just that unregistered users have no way to enable the gadget. Vahurzpu (talk) 01:34, 11 May 2021 (UTC)

I got the same problem when I trided to merge something by bot - confict of descriptions (Wikimedia/Wikipedia category...) JAn Dudík (talk) 12:03, 17 May 2021 (UTC)

Special:MergeItems tells people to use the gadget. Given that there is some consensus that IPs shouldn't merge items, maybe we could just de-activate the special page. --- Jura 12:25, 17 May 2021 (UTC)

Putting a wikidatapage in edit mode via the URL

In Wikipedia it's possible to add a new section using the URL. e.g.: https://en.wikipedia.org/w/index.php?title=Talk:Wikidata&action=edit&section=new

Is there any equivalent fow Wikidata to adda new property? Something like: https://www.wikidata.org/w/index.php?title=Q76846397&action=edit&statement=new&property=P98

I'm looking to use it on these tables. T.Shafee(evo&evo) (talk) 01:27, 14 May 2021 (UTC)

• You can link to a property or a statement on an item (if it exists): Q76846397#P98 or Q76846397#Q76846397$f990e906-4c7d-37bb-c785-9d3462283995. --- Jura 14:22, 14 May 2021 (UTC)
• You can link to QuickStatements, passing new statements through URL. This is, by the way, how PetScan, Scholia, MREID resolver and few user-scripts work - it also protects from creating duplicate statements. --Lockal (talk) 10:26, 17 May 2021 (UTC)

Should subclasses be included in P31 “instance of” relations?

For instance, enterprise (Q6881511) has relation subclass of (P279) to business (Q4830453) “business”. Up until now, Cloudflare (Q4778915) “Cloudflare” had statements instance of (P31) enterprise (Q6881511) and instance of (P31) business (Q4830453). Should this be the state of things? To me, it seems like it shouldn’t be, which is why I removed the less specific relation. After all, wouldn’t the other case entail adding all superclasses to an item?

If any of the two is specifically preferred, maybe a bot should be made to correct deviations.

 – The preceding unsigned comment was added by Theanswertolifetheuniverseandeverything (talk • contribs).

• @Theanswertolifetheuniverseandeverything: see Help:Basic_membership_properties#subclass_of_(P279):

  subclass of (P279) is transitive property (Q18647515), that means if an item A is an instance of class B, and class B is a subclass of class C, item A is implicitly also an instance of class C. There is no general need to add a statement for the relation A→C to Wikidata.

  --SilentSpike (talk) 11:56, 17 May 2021 (UTC)

@SilentSpike: I feel this isn’t communicated well, “transitive” means that rel(a,b) & rel(b,c) imply rel(a,c), whereas this is rel1(a,b) & rel2(b,c) implying rel1(a,c). Also, it feels like this is something that could be automated, by making a bot that removes instance of (P31) statements that are implied by other statements. Thanks, though! Theanswertolifetheuniverseandeverything (talk) 12:04, 17 May 2021 (UTC)

• I had the same thought on reading it now too. May have a go at cleaning that up later if nobody else does. --SilentSpike (talk) 12:16, 17 May 2021 (UTC)

Reminder: Share your comments and suggestions on IP Masking

Hello Wikidata community, it's a brand new week, I hope you are all well. This is about IP Masking engagement on Wikidata.

The Anti-Harassment Tools team (we're here) wants to hear from you about IP Masking. We want to understand how the project will impact you as an editor. Also, we want to know which other tools you will need to be able to effectively protect the project pages in the absence of IPs. Please read more on the IP Masking project here.

And then, let us know your thoughts on the talk page here. Have a good week! – STei (WMF) (talk) 10:20, 17 May 2021 (UTC)

Wikidata weekly summary #468

Here's your quick overview of what has been happening around Wikidata over the last week.

• Discussions
  • New request for comments:
    • Separating "citations" from all Wikipedia articles by using Wikidata
    • IP Masking Engagement
  • Closed request for comments:
    • Allow for Wikidata items to be created that only link to a single Wikimedia Commons category (Wikidata notability discussion). Outcome --> no change to WD:N
    • Inverse constraint on cause-and-effect properties. Outcome --> constraints were removed

• Events
  • Ongoing:
    • Data literacy snacks - Talk about "Wikibase knowledge graphs for data management & data science" on 23rd of June. For registration, send e-mail to infoberd-bw.de
  • Upcoming
    • SPARQL queries live on Twitch and in French by Vigneron, May 18 at 18:00 CEST
    • Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Mahir Morshed will be discussing Lexemes in Wikidata; Agenda, May 18th.
    • May 21-22, 2021 [18] Boston Rock City: Explore Wikidata and Learn About Local Music: Boston Public Library is partnering with Harvard Library for a guided exploration of Wikidata and local music history. Join us for two days of music and Wikidata editing; no prior experience or punk cred necessary! This public event is free to all and will take place via Zoom; please register in advance. The subject of this project is the Arthur Freedman Collection, and audiovisual archive that captures over four decades of Boston rock music performances. We’ll provide: instructions, tools, data sources, visualizations, optional Discord chat, and a soundtrack. If you have questions, please contact Harvard Library staff member Peter Laurence at laurenc@fas.harvard.edu.
    • Online Wikidata meetup in Swedish #63, May 23
    • OpenStreetMap Taiwan x Wikidata Taiwan Taipei (Q1867) Meetup 2021-06-07 Mozilla Community Space Taipei (Q61752245).

• Press, articles, blog posts, videos
  • Papers
    • Hiba Arnaout et al, Negative Knowledge for Open-world Wikidata (full text link)
  • Videos
    • LIVE Wikidata editing #44 - YouTube
      • Link to all the Wikipedia Weekly Network/Live Wikidata Editing sessions by Ainali and Abbe98
    • Wikidata, Wikimedia Commons und Wikipedia bearbeiten 2021/001 (in German) - YouTube
    • SPARQL #Wikidata retour aux bases #4 - YouTube
    • How to use Wikidata to list nearby tourist places on a web page (in French) - YouTube
    • How to add lexemes to Wikidata (in Swedish) - YouTube
    • How to edit library data in Wikidata (in Italian) - YouTube
    • Editing the drawings in the Gambara Bovardi collection at the Levi Foundation in Venice on Wikidata (in Italian) - YouTube

• Tool of the week
  • User:Lucas Werkmeister/hyphenation-point.js is a user script that replaces any | characters with U+2027 HYPHENATION POINT when editing hyphenation snaks.

• Other Noteworthy Stuff
  • 20k+ DOIs of Chinese language scientific journal articles have now been added to WD, thanks to scraping->validation->matching->quickstatements workflow built by Stevenliuyi (via a WikiCite eScholarship)
  • Template:Annotate QID (currently on en. & de.Wikisource) allows names and other terms in texts to be semantically annotated with the equivalent QIDs. sv.Wikisource has a similar template.
  • Template:Item documentation displays Template:Generic queries for occupations for items of class occupation (Q12737077) and Template:Generic queries for filmmakers for items with occupation (P106) filmmaker (Q2526255)
  • Wikimedia Foundation 2021 Board Elections has been announced. Please sign-up as an Election Volunteer if you'd like to support the elections. Election Volunteers serve as a bridge between the Elections Committee, the facilitation team and the movement.

• Did you know?
  • Newest properties:
    • General datatypes: identifier shared with lexeme, audio transcription, counterpart position, earned run average, official podcast, diel cycle, intended background color, scope note
    • External identifiers: LMIC musician ID, Scholarpedia article ID, Historic Hawai‘i Foundation place ID, Digital Library of Armenian Literature author ID, Den Danske Ordbog article ID, Den Danske Ordbog idiom ID, OpenCorporates register ID, Biblioteche della Custodia di Terra Santa a Gerusalemme ID, IBSF competition ID, SAIA authority ID, Football Association of Norway club ID, music austria ID, Secondary Archive artist ID, Editorial Freelancers Association member ID, MacArthur Fellows Program ID, representatives1821.gr ID, Memento Vienna person ID, universal equine life number, Encyclopedia of China Online Database ID, Indiana State Historical Marker Program ID, Apple Music label ID (US version), bio.se movie theater ID, MyBIS protected area ID, Dialnet thesis ID, hPSCreg cell line ID, Michigan State University Library Comic Art Collection Record Number, LTit person ID, JECFA number, Badok ID, Sigla ID, DCinemaToday company ID, CEV coach ID, CEV team ID, Encyclopedia of Renaissance Philosophy ID, Biographical Dictionary of Chinese Christianity ID, AdServio ID, PeakVisor peak ID, PeakVisor range ID, PeakVisor area ID, PeakVisor park ID, Anime Filler List show ID, Anime Filler List episode slug, Australian Music Centre composer ID, Danish 2010 redlist identifier, synonymer.se ID, SOUNZ work ID, vedidk ID, Microlepidoptera.nl ID, UNITER Award person ID, sense on DHLE
  • New property proposals to review:
    • General datatypes: infects, setlist, oral history at, DIVA author ID, DIVA record ID, type of lens
    • External identifiers: ToateAnimalele ID, Muziekencyclopedie ID, CDep.Ro NGO ID, causesanti.va ID, Adevărul topic ID, bathingWaterIdentifier, Scenic Washington scenic drives and road trips ID, Bodleian Archives & Manuscripts ID, cIMeC.Ro Museum ID, Newspaper Genre List ID, Styria Museum ID, What Works Clearinghouse study ID, WUA author ID, hush.am person ID, Archive Alsharekh person ID, Douban series ID, RomArchive IDs, Moths and Butterflies of Europe and North Africa ID, Scholasticon person ID, Japan PlayStation Software Database ID, WMF lang code
  • Deleted properties: iFixit repairability score (P7478)
  • Query examples:
    • Number of species belonging to the different IUCN conservation categories (Source)
    • List of Wikimedia language codes (Source)
    • Plant genera that honor women (Source)
    • Poets whose fathers are lawyers (Source)
    • Phrase-book for types of food (mapping Catalan and English) (Source)

• Development
  • Fixed the entity usage dashboards that no longer showed data due to technical issues. It tracks how much data from Wikidata is used on the other Wikimedia projects. (phab:T279762)
  • Configured the Property Suggester to not suggest Google Knowledge Graph ID (P2671) and Wolfram Language entity code (P4839) (phab:T280779)
  • Investigated remaining issue with updating the page_props table on the client wikis, which is confusing some bots making use of that table (phab:T280627)
  • Fixed an issue in the Query Builder where it got confused when adding several conditions with the same Property (phab:T279945)
  • Working on tracking the number of edits per namespace over time (phab:T281356)
  • Working on fixing a bug where old revisions of Items have edit buttons but should not (phab:T281587)
  • Fixing an issue where value suggestions are not showing all values that are defined in the property constraint (phab:T280650)

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.

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Near 6,100 items have the Template:Item documentation in their talk page. Help deploy this template.
  • Help write the next summary!

Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 15:17, 17 May 2021 (UTC)

Ciaotou District

Hey- there seems to be a problem in the interface between Wikidata and Wikimedia Commons. On this Wikimedia Commons page [19], Ciaotou is listed in the Infobox as being in "Kaohsiung, Kaohsiung County, Taiwan". That infobox takes its data from the Wikidata page [20]. However, Kaohsiung County does not exist any more- it should appear as "Kaohsiung, Taiwan". I am not experienced with Wikidata- how can I fix this problem? Thanks for any help. --Geographyinitiative (talk) 17:13, 18 May 2021 (UTC)

• It comes from the statements at Q708216#P131. I set the current one to preferred rank: [21]. This avoids the display of historic entities by default. --- Jura 18:10, 18 May 2021 (UTC)

Great job and thanks for the explanation- now I can do this by myself if I see this again. The issue is solved. --Geographyinitiative (talk) 12:01, 19 May 2021 (UTC)

Wikidata book, invitation

We wrote the very first version of the book "Programming Wikidata for youth and students". LaTeX source code is available on GitHub: componavt/wd_book. If you are interested in participating in the writing of this book, please write to me (andrew.krizhanovsky at gmail.com).

I am teaching a course at Petrozavodsk State University, the results of this course are presented in the Wikiversity project Research in programming Wikidata and in this book. Therefore, I hope that this book will be updated and replenished with new materials every year. --Andrew Krizhanovsky (talk) 18:26, 19 May 2021 (UTC)

Interwiki prefix for Mix-n-match catalogs

A proposal at m:Talk:Interwiki_map#Mix-n-match_catalog. It would allow links like

• mixnmatch:2050 for https://mix-n-match.toolforge.org/#/catalog/2050
• mixnmatch:3788 for https://mix-n-match.toolforge.org/#/catalog/3788

--- Jura 09:29, 17 May 2021 (UTC)

Relatedly: {{Mix'n'match catalogue}}. Jean-Fred (talk) 10:48, 17 May 2021 (UTC)

• The template still uses the old URL. It changed last year, see Q28054658#P856. --- Jura 10:55, 17 May 2021 (UTC)

  Yes, I’m aware the URL changed − and redirects from the old one work just fine. But fair enough  Done Special:Diff/1422868953. Jean-Fred (talk) 16:50, 17 May 2021 (UTC)

  • In my opinion Mix'n'Match would be a tool that would eventually be succeeded in the long future. Magnus once developed a Version 2 of Mix'n'Match (which is now unmaintained), and we may have another workflow to do so (though not in the foreseeable future).--GZWDer (talk) 16:05, 17 May 2021 (UTC)
    • Not sure how version are numbered, but isn't this (currently) version 2? It uses Wikibase contrary to its predecessor. --- Jura 07:48, 20 May 2021 (UTC)

• It has gone live. The prefix that is being used is mixnmatch:. I updated the two samples in my initial comment. Enjoy. --- Jura 07:48, 20 May 2021 (UTC)

Changing KML File for :Q4532801 (Essex Street)

For reasons I cannot explain the KML file for Essex Street is set to Template:Attached KML/Avenue A (Manhattan) when it should be: Template:Attached KML/Essex Street (Manhattan).

I have attempted to change the value, but the Essex Street (Manhattan) value is not accepted.

As you can see from the below, there are three subpages for Template:Attached KML/Essex*

• w:Special:PrefixIndex?prefix=Attached+KML/Essex&namespace=10

These are the three subpages:

1. Attached KML/Essex Railroad
2. Attached KML/Essex Street
3. Attached KML/Essex Street (Manhattan)

However, whenever I try to change the value of the KML file statement on for Q4532801 the only values that appear for the string: "Template:Attached KML/Essex " are, I mean, is:

Attached KML/Essex Railroad

Hoping to be able to set the KML file statement to the appropriate file: Attached KML/Essex Street (Manhattan)

Hoping someone can also tell me why I am having this problem,

tia,

--CmdrDan (talk) 07:13, 20 May 2021 (UTC)

The wikipedia KML page needed to have a wikidata item created for it. P3096 takes the QId of the item. --Tagishsimon (talk) 07:21, 20 May 2021 (UTC)

lexemes: links to lexemes

It's now possible to link to a search for lexemes with the prefix lexemes:

Sample: lexemes:link.

To search for every word in a comment, one could do: It's now possible to link to a search for lexemes with the prefix

This should be possible on any Wikimedia wiki.

There are a few similar prefixes available for other resources: googledefine:, acronym:, dict:, dictionary:, onelook:, drae:, dpd:, mwot:, mwod:, revo:.--- Jura 08:12, 20 May 2021 (UTC)

Page update

Hi all,

I have a project that needs updating. They company has changed names and as a result URL.

Is it safe enough to just suggest the change without risking losing the listing? I am brand new to it all and really don't want to break any rules.

Thanks  – The preceding unsigned comment was added by Startup Local (talk • contribs) at 04:53, May 20, 2021‎ (UTC).

@Startup Local: If it's just a name change and otherwise the same, then please update the label to the new name, and leave the old name as an alias. Also the new official website (P856) should be added with preferred rank; you could add a end time (P582) qualifier to the old official website (P856) statement also, but generally we don't delete valid website URls even if they've changed. official name (P1448) statements with appropriate date qualifiers would also be useful. ArthurPSmith (talk) 13:05, 20 May 2021 (UTC)

Please give feedback on whether to add a references function to Structured Data on Commons

Hi all

WMF are considering adding references to Structured Data on Commons (which uses Wikibase like Wikidata does) and are collecting thoughts at this link. If you think having references in structured data may be helpful please add any thoughts, it doesn't have to be long at all. DONT WRITE THEM HERE THEY WONT SEE THEM.

Thanks

--John Cummings (talk) 10:40, 20 May 2021 (UTC)

• Isn't that really a question for Commons?

The only problem the absence of references on Commons generated for Wikidata so far is that a bot operator attempted to add qualifiers instead of references to Wikidata (as that's what they want to do at Commons). Discussion at Wikidata:Requests_for_permissions/Bot/METbot. --- Jura 10:45, 20 May 2021 (UTC)

I think question is asked it in commons and this was notification that this is relevant and you are welcome to discuss. I think that I had similar problem that I needed to store information where data is coming. Mostly how it was generated (by human, by AI, by derivative from GLAM, GPS etc) --Zache (talk) 11:36, 20 May 2021 (UTC)

• The problem for Wikidata is that we need to be aware of such differences if they exist. Commons should do whatever is most useful for them. --- Jura 11:58, 20 May 2021 (UTC)

Single value constraint

Tracked in Phabricator
Task T283229

Yle topic ID (P8309) can have multiple same values which are distinct when language code is defined. Ie, ID+LANGUAGE_CODE combinations are unique. (example item: Q6348774) However, currently this will throw a warning because the single value constrain. One simple solution is to remove single-value constraint (Q19474404) constrain and leave distinct-values constraint (Q21502410) for enforcing the uniqueness. There is also rather many of such cases so it would be easier to edit constrain than data if we want to keep the url-formatters working.

So, I am asking if it is OK just to remove the single value constrain or is there better solution to this? There is also phab:T283229 in Phabricator. --Zache (talk) 11:33, 20 May 2021 (UTC)

• Check out Property:P8447#P2302 for an example using separator (P4155), though I'm not sure I understand your explanation exactly --SilentSpike (talk) 11:42, 20 May 2021 (UTC)

• If they go on the same item, is there any advantage of including the language?

For Q6348774#P830, one could just add both qualifiers to the same statement. --- Jura 12:04, 20 May 2021 (UTC)

• Yle topic ID (P8309) is, to my understanding, always available in both Finnish and Swedish. Therefore, there is no reason to specify on the statement level whether the identifier is available for a specific language. Users can access both languages by selecting a correct formatter url from P8309. I think in this case the language qualifiers and duplicate values should be deleted from items that use them. --Shinnin (talk) 12:27, 20 May 2021 (UTC)

Not all of the topics have content in all languages and language code may be used for detecting if there is actual content with that language. For example, some of the topics will have content only in Finnish, some in Swedish and some have content in both languages. --Zache (talk) 12:46, 20 May 2021 (UTC)

Creating Main page for ms-arab

A few days ago, "ms-arab" has been added as a new interface language for Wikidata. The main page is linked to لامن اوتام. Shouldn't it be linked to Wikidata:لامن اوتام instead? I have translated Wikidata:Main Page into ms-arab. --Tofeiku (talk) 05:41, 19 May 2021 (UTC)

The “mainpage” interface message probably needs to be translated into that language – compare e.g. MediaWiki:Mainpage or MediaWiki:Mainpage/ar (locally overridden messages, have a page history) with MediaWiki:Mainpage/ms-arab (default MediaWiki message, has no local page history). One of the interface admins ought to be able to do it. Lucas Werkmeister (WMDE) (talk) 10:27, 20 May 2021 (UTC)

Done that, but https://www.wikidata.org/wiki/Wikidata:Main_Page?uselang=ms-arab doesn't show https://www.wikidata.org/wiki/Wikidata:Main_Page/Content/ms-arab because {{int:lang}} is ms, not ms-arab, and I don't know why. Pinging Amir, in case he's available and can enlighten us. Comments from other editors are also welcome. --abián 19:34, 20 May 2021 (UTC)

Nikki finally  fixed it. --abián 19:39, 20 May 2021 (UTC)

URL add request

Is https://www.thecollectionbook.info/ eligible for Microsoft Windows (Q1406) as reference URL (P854)? --93.35.184.189 10:18, 20 May 2021 (UTC)

Can you describe in a bit more detail what you are trying to do? If there's a piece of information documented on that website that supports a statement on Microsoft Windows (Q1406) then I guess it could be used as a reference, yes, but it wouldn't be applicable as a general statement on that item. ArthurPSmith (talk) 17:02, 20 May 2021 (UTC)

Unanswered question

Why my question is still without answer? --2001:B07:6442:8903:6C0E:2ABA:7A5C:9860 13:10, 20 May 2021 (UTC)

• Maybe it's explained in the comment you were asking about? --- Jura 13:18, 20 May 2021 (UTC)
  • @Jura1: where is the comment? --93.35.184.189 13:35, 20 May 2021 (UTC)
    • More importantly: where is the question? 15:49, 20 May 2021 (UTC)
      • here --93.35.184.189 15:51, 20 May 2021 (UTC)

Cihan university

hello I'm ahmad. duhok, there is an official university in iraq, namely world. And the University is the oldest English-speaking private university in this area, and in the end, can there be someone to help me, let's all just be done. The official website of university Home page of website . --Ahmadkurdi44 (talk) 16:29, 20 May 2021 (UTC)

• @Ahmadkurdi44: I updated Cihan University-Duhok (Q106916672) with some additional statements - I assume it is a part of the existing entry for Cihan University-Erbil (Q18347698)? Please add anything additional you are aware of to either of those items. ArthurPSmith (talk) 16:58, 20 May 2021 (UTC)

Unsourced African Americans

There are 16010 items with ethnic group (P172)=African Americans (Q49085). Most are correct, there are some instances imported via The Distributed Game. One of the instance, Matthew Barzun (Q5566787), as I know, have no African American ancestry. This game is still online.--GZWDer (talk) 08:37, 15 May 2021 (UTC)

• How can we improve the situation? What's the current view on P172 claims in Wikidata? Do they need no longer need a reference? --- Jura 11:34, 16 May 2021 (UTC)

So you found a potential error. That is to be expected. You fix it. Thanks, GerardM (talk) 11:49, 17 May 2021 (UTC)

• I'm fine with a cleanup of unreferenced statements as well. @GZWDer: how to do you want to proceed? --- Jura 09:42, 21 May 2021 (UTC)

Join the new Regional Committees for Grants

Dear all,

We hope this email finds you well and safe. The COVID 19 situation continues to affect many of us across the globe and our thoughts are with everyone affected. We are also aware that there are several processes currently in progress that demand volunteer time and we do not want to add more work to anyone's plate.

We do want to draw your attention to our new Regional Committees for Grants though as they are an opportunity for you to have an active say in the future of our Movement!

📣 So today, we invite you to join our new Regional Committees for Grants! 📣

We encourage Wikimedians and Free Knowledge advocates to be part of the new Regional Committees that the WMF Community Resources team is setting up as part of the grants strategy relaunch [22]. You will be a key strategic thought partner to help understand the complexities of any region, provide knowledge and expertise to applicants, to support successful movement activities, and make funding decisions for grant applications in the region.

👉Find out more on meta [23].

Regional Committees will be established for the following regions:

• Middle East and Africa
• SAARC [24] region (Includes Afghanistan, Bangladesh, Bhutan, India, the Maldives, Nepal, Pakistan and Sri Lanka)
• East, Southeast Asia, and Pacific (ESEAP) region
• Latin America (LATAM) and The Caribbean
• United States and Canada
• Northern and Western Europe
• Central and Eastern Europe (CEE)

👉All details about the Committees and how to apply can be found on meta [25]. Applications have to be submitted by June 4, 2021!

If you have any questions or comments, please use the meta discussion page [26].

Please do share this announcement widely with your Network.

Best wishes,

JBrungs (WMF) (talk) 06:26, 21 May 2021 (UTC) on behalf of the Community Resources Team

College or High School

hello, i'm Ahmad. Is it possible to create (wikidata item) for a college or high school? thanks --Ahmadkurdi44 (talk) 15:09, 21 May 2021 (UTC)

Yes, most colleges or high schools will be notable under WD:N. Please be sure to provide high-quality sources so we can be sure that the information is correct. --Emu (talk) 16:12, 21 May 2021 (UTC)

Karzan Hisham | Youtuber

Hi. I'm Ahmad.. Before I create a (wikidata item) I will prepare a project chat here, the person I will create is a famous youtuber in iraq-duhok city, as well as a social media phenomenon. Is it ok to leave a social account link? I made a chat project to avoid mistakes or mistakes.. thank you --Ahmadkurdi44 (talk) 15:36, 21 May 2021 (UTC)

I’m not sure what’s your question. You created a duplicate of Karzan Hisham (Q104970662) which I now merged. The item seems fine to me. --Emu (talk) 16:08, 21 May 2021 (UTC) 

Yes I searched before I wrote it, I couldn't find it, then I knew when I made a mistake, there is a duplication, the name was spelled wrong, and now yes everything is fine, I'm sorry for duplication --Ahmadkurdi44 (talk) 20:52, 21 May 2021 (UTC)

Problem with the table and the InteGraality

Hello. Wikidata talk:WikiProject every politician. Click on the table at the section "Statistics", for any country for any property, https://integraality.toolforge.org/ gives error. I have to go to page Wikidata:WikiProject every politician/Statistics, to click to the property I want to have the results. Data Gamer ^play 12:41, 15 May 2021 (UTC)

@Data Gamer: Integraality’s developer here. First off, I’m exceedingly unlikely to just notice posts on Project chat if not pinged :)

Yes, that’s a known limitation. You need to use that link from the page itself, not any transclusions of it. I’m afraid I’m not aware of any good solution to avoid that.

Jean-Fred (talk) 10:13, 20 May 2021 (UTC)

@Jean-Frédéric: Hello. Before Project chat I had added the same question to Wikidata talk:WikiProject every politician#Problem with the table and the InteGraality, 4,5 months ago. I didn't check for developer. I have just noticed the problem and asked for a solution. Thanks. Data Gamer ^play 15:59, 20 May 2021 (UTC)

@Data Gamer: No worries :)

I have tried to address a bit issue by providing a hopefully clearer error message. Hope that helps! Jean-Fred (talk) 20:59, 22 May 2021 (UTC)

New batch mode(s) in Ranker tool

The Ranker tool (announced a few months ago) now has several batch modes – see query+individual mode for an example or the documentation for details. Thanks to @Vojtěch Dostál for suggesting this! Lucas Werkmeister (talk) 11:45, 23 May 2021 (UTC)

Setting end time for former campus of McEvans Warriors K-12 School (Q38252046)?

Concerning: Q38252046

Shaw High School moved from 214 Dean Blvd. Shaw, MS 38773 (33°35'43"N, 90°45'59"W, seen here) to 421 North Hwy 61N, Shaw, MS 38773 (33°36'38.63"N, 90°45'58.50"W, seen here), the building of McEvans Elementary School, circa September/October in 2019, due to a deterioration in the building of the former high school. In 2020 the high and elementary were collectively renamed McEvans Warriors K-12 School.

I am trying to set an end date to the coordinates for 214 Dean Blvd. but for some reason Wikidata won't let me set 2019 as an end time. How do I do this? I want to make 421 North Hwy 61N the primary location.

Thanks, WhisperToMe (talk) 14:18, 23 May 2021 (UTC)

You seem to have managed it? --Tagishsimon (talk) 14:48, 23 May 2021 (UTC)

It was quite straightforward. Any info on Thomas McEvans II (Q106949979) would be nice. --- Jura 15:10, 23 May 2021 (UTC)

@Jura1: Thank you so much for your help! Something I notice at en:McEvans Warriors K-12 School is that the selected red still reflects the old campus and not the new one. A similar issue is happening at en:West Bolivar High School which is West Bolivar High School (Q38250684) (I was able to set end and start times for the respective campuses) WhisperToMe (talk) 15:40, 23 May 2021 (UTC)

Supercentenarians vs. mythical supercentenarians

I brought this up once before, but I don't think we found a satisfactory answer for all entries. How can we distinguish documented_supercentenarians vs. claimed_supercentenarians? Should we create "claimed_supercentenarian" or "undocumented_supercentenarian"? I am doing cleanup at Wikidata:Database_reports/unmarked_supercentenarians. We add "significant event (P793)=supercentenarian (Q1200828)" to legitimate supercentenarians, but how do we mark people claiming to live more than 120 years like Sreeman Tapaswiji Maharaj (Q94506405). We solved biblical people by making them like Noah (Q81422) and adding "human biblical figure", so they get excluded by not being human. --RAN (talk) 18:53, 23 May 2021 (UTC)

add sourcing circumstances (P1480) allegedly (Q32188232) to either the birth/death date? BrokenSegue (talk) 19:47, 23 May 2021 (UTC)

Ontology and Querying

Hey, Anyone who reads this please Respond as soon as possible I have to Submit a Project-Based On Ontology On BioDiversity, I am Asked to write Competency Questions on BioDiversity, which our Ontology could Answer, But as I am all new to this I can write questions on BioDiversity But I don't get How to Make Ontology of it. Please guide me by making the Ontology process or suggest any video. I am working to get an Internship from it.  – The preceding unsigned comment was added by 7gaurav (talk • contribs).

Q97 is unusable now

Just to note that Atlantic Ocean (Q97) is now unusable, since it contains a ridiculous number of tributaries and basin countries. I've blacklisted it in the Commons infobox for the 'category combines topics' case, but commons:Category:Atlantic Ocean is still having problems. Thanks. Mike Peel (talk) 08:54, 21 May 2021 (UTC)

• The number of basin countries doesn't really strike me as problematic (94). Less convinced by the inclusion of tributaries (601). --- Jura 10:02, 21 May 2021 (UTC)

Concur. From en.wiki (my emphasis): "A tributary[1] or affluent[2] is a stream or river that flows into a larger stream or main stem (or parent) river or a lake.[3] A tributary does not flow directly into a sea or ocean.[4]". P974 statements should be removed entirely from Q97, after checking that each item has a mouth of the watercourse (P403) statement. If 94 basin countries is problematic, the problem is with the Commons infobox b/c they are unavoidaby basin countries. --Tagishsimon (talk) 10:38, 21 May 2021 (UTC)

P974 statements are being removed from Q97; all the items have P403s pointing to Q97. --Tagishsimon (talk) 10:59, 21 May 2021 (UTC)

But Commons is still broken. An issue with basin country is that de wiki seems to think the Atlantic Ocean includes inland seas such as the Mediterranian. en wiki thinks the Med is excluded. So right now we have a large number of arguable basin countries - Italy, Libya &c. @Gymnicus: FYI. --Tagishsimon (talk) 11:47, 21 May 2021 (UTC)

Isn't that what things like determination method (P459), based on heuristic (P887), criterion used (P1013) are for? Circeus (talk) 12:12, 21 May 2021 (UTC)

@Mike Peel, Jura1, Tagishsimon: The error clearly comes from the neighboring countries and not from the tributaries. You just have to Pacific Ocean have a look. There are no problems with the large number of tributaries. I cannot say exactly why such a problem occurs with neighboring countries. But I am assuming that it looks with the structure of the info box. For example, if you look at the commons category of Baltic Sea, you can see that "consists of" gives you the option to collapse it very quickly. In contrast, this does not seem to exist in neighboring countries. Maybe this is the problem. --Gymnicus (talk) 12:17, 21 May 2021 (UTC)

The workings of the infobox itself is really a problem for Commons to sort out. --- Jura 12:20, 21 May 2021 (UTC)

Issues with the infobox I can sort out, the problem is that this sort of limit is *continously* hit. It generally seems to be related to items that link to country items. It's a general problem whenever trying to use Wikidata information in MediaWiki. Thanks. Mike Peel (talk) 14:10, 21 May 2021 (UTC)

At commons:Category:Atlantic Ocean it was 'basin country' that was the issue, I've now capped that at 20 and it works. However, that's not really a good long term solution since it's 20 random countries... Thanks. Mike Peel (talk) 14:13, 21 May 2021 (UTC)

Isn't there a function that loads labels instead of the entire item? That could help you with country items (we did reduce a few months back, but they keep growing). If the list is cut, maybe an indicator that there is more could point to the Wikidata item's relevant section. --- Jura 14:28, 21 May 2021 (UTC)

Fairly sure it is using that function already ('getLabel'), it only loads the full item for the main topic once at the start. Thanks. Mike Peel (talk) 15:42, 21 May 2021 (UTC)

Why would it fail on the 94 basin country statements, but not on the 601 for tributaries? --- Jura 06:28, 22 May 2021 (UTC)

Good question. The code is the same. Must be to do with Lua back-end or Wikidata itself. Thanks. Mike Peel (talk) 10:30, 24 May 2021 (UTC)

Wikidata weekly summary #469

Here's your quick overview of what has been happening around Wikidata over the last week.

• Events
  • Past
    • HackaLOD Online: Estimating the interest of art relationships with Wikidata - YouTube
  • Ongoing
    • #1Lib1Ref Campaign by IFLA Wikidata Working Group (May 15 - June 5)
      • #1Lib1Ref Campaign in Italy, as part of the IFLA Wikidata Working Group campaign (May 15 - June 5); more than 10k references have already been added (see the dashboard for more details)
  • Upcoming
    • The next Wikibase live session is 16:00 UTC on Thursday 27th May 2021 (18:00 Berlin time). Everyone is welcome to come and share out about your project or what you're working on around Wikibase.
    • 27/05 (17h UTC): Wikidata Lab XXIX: Roundtripping process with Ederporto, Pharos e Susannaanas (in English), on YouTube
    • SPARQL queries live on Twitch and in French by Vigneron, May 25 at 18:00 CEST
    • LIVE Wikidata editing #45 - YouTube, Facebook, May 29 at 18:00 UTC
    • Online Wikidata meetup in Swedish #64, May 30
    • LD4 Wikibase Working Hour: The history, present and future of WBStack & WBaas (Wikibase as a service) 27 May 2021, 1PM Eastern US. Please fill in this form to register!

• Press, articles, blog posts, videos
  • Blogs
    • KELM: Integrating Knowledge Graphs with Language Model Pre-training Corpora. Wikidata was used to generate sentences to train a language model.
    • An Introduction to Knowledge Graphs
  • Videos
    • Wikimedia Hackathon 2021 - Main track - Saturday 22
    • Curating bibliographic metadata of scholarly publications: demo of Wikidata-based Scholia workflows
    • Demo of Ordia, a Wikidata tool to visualize lexicographic information from Wikidata
    • Adding references to Wikidata items, as part of #1Lib1Ref campaign (in Italian)

• Tool of the week
  • User:Jon Harald Søby/compact items.css is a stylesheet that shrinks the vertical space items take up on your screen, reducing the need to scroll to get an overview of an item. (screenshot)

• Other Noteworthy Stuff
  • The prefix [[lexemes:]] allows to link to a search for lexemes on any Wikimedia wiki. Sample: lexemes:describe (project chat announcement).
  • The wikidata-lang JS module got a major update, and now makes accessible pre-generated mappings between Wikidata ids, Wikimedia language code (P424), ISO 639-1 code (P218), ISO 639-2 code (P219), ISO 639-3 code (P220), and ISO 639-6 code (P221), that can also be used by non-JS programs by fetching the desired JSON. Examples:
    • mapping of Wikimedia language codes to Wikidata ids
    • mapping of ISO 639-2 to Wikimedia language codes
  • Wikidata-related projects that have been developed/improved during the Wikimedia Hackathon 2021:
    • User:Lucas_Werkmeister/Ranker - Finished and announced the batch modes for the Ranker tool, allowing users to edit the ranks of statements in Wikidata or Structured Data on Commons in bulk
    • Wikidata Lexeme Forms: Portuguese modal adverb - Deployed support for Portuguese modal adverbs in the Wikidata Lexeme Forms tool
    • User:Jon Harald Søby/addSenseImage.js - User script to add images to sense statements on lexemes
    • Wikidata:Tools/Enhance user interface#identifierInput.js - fixing a bug in IdentifierInput.js gadget for Wikidata to better handle when a property has no format restraints

• Did you know?
  • Newest properties:
    • General datatypes: type of lens, oral history at, official map URL
    • External identifiers: The Criterion Collection film ID, Lexikon der österreichischen Provenienzforschung ID, Apple TV movie ID, Canadian Music Centre Composer Showcase ID, causesanti.va ID, Muziekencyclopedie ID, North Carolina session law, #SOSBrutalism ID, Online Archive of California finding aid ID, Museums in Styria ID, Bodleian Archives & Manuscripts person ID, SOR bird ID, ToateAnimalele ID, Polo bibliografico della ricerca entity ID, Polo bibliografico della ricerca author ID, OSDN project, Scholasticon person ID
  • New property proposals to review:
    • General datatypes: music for work, in sense, academic calendar type
    • External identifiers: Romanistenlexikon ID, Buzer.de law identification, senato.archivioluce.it person ID, Apple TV show ID, Apple TV episode ID, Australian Music Centre work ID, fondoambiente.it ID, Unified book number, GLEI ELF, RBF event ID, Poetsgate poet ID, Badkartan.se ID, Book Owners Online person ID, ifixit device ID, Price One Penny Author ID, Price One Penny Publisher ID, Price One Penny Work ID, Medical Institution Code, AlternativeTo software ID, RoBasketballFed IDs, Online Coins of the Roman Empire ID, bathingWaterIdentifier, Enciclopedia della Matematica ID
  • Query examples:
    • Danish idioms (Source)
    • Map of coronavirus research organizations active from before 2020 (Source)
    • Scholarly articles about COVID-19 with "Wikipedia" in the title
    • 20th-century UK parliaments with count of father/mother who were MPs (Source)
    • The tallest known female politicians (Source)
    • Writing systems/characters and their year of appearance (Source)
    • Nocturnal animals based on diel cycle (Source)
  • Newest database reports: Doctor Who episodes (new series)

• Development
  • Designing and planning for the first version of a tool to compare Wikidata's data against other databases and find mismatches that might need fixing
  • Looking into unit conversion for the Commons Query Service (phab:T281468)
  • Improving RDF export performance problems for very large Items (phab:T281272)
  • Fixed entity suggestions not showing all Items defined in that Property's constraint (phab:T280650)
  • Removed edit buttons that had reappeared on old revisions of Items where they shouldn't be (phab:T281587)

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.

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 15:44, 24 May 2021 (UTC)

Entity context prediction

Hi, I'm writing to share an experiment we were working on for a student capstone project sponsored by Wiki Education. We were inspired by (and are indebted to) the prior work by Balaraman et al. on ReCoin (Wikidata:Recoin). We were interested in exploring whether it would be possible to predict an entity's type by comparing its set of properties to the properties typical of existing types. The work is experimental, but we observed initially encouraging results that suggest it could be a useful approach. Additional details will be available in the paper "Context Matrix Methods for Property and Structure Ontology Completion in Wikidata" that will be published as a proceeding in IEEE SIEDS 2021. Thanks! -- Jag2j (talk) 22:41, 25 May 2021 (UTC)

@Jag2j: is a link to a pre-print/pdf possible? I'd be interested in reading about it. BrokenSegue (talk) 01:24, 26 May 2021 (UTC)

Splitting the statue and character of Manneken Pis (Q152072)

Manneken pis (Q152072) is one Q-item at the moment. But the statue is also a folkloric figure with his own legends ans stories to why it exist who it represents etc. I think it would be helpful to split the character and the statue.

It would. Go to it. --Tagishsimon (talk) 20:22, 25 May 2021 (UTC)

Could you do it? I'm not that good at splitting items Jhowie Nitnek 20:46, 25 May 2021 (UTC)

@Joeykentin: I had a go at splitting the item. I created a new item for the character and linked all relevant items to it with main subject (P921)Manneken Pis (Q106987619). I also linked Manneken Pis (Q152072) to all its copies. I moved the statements from Manneken Pis (Q152072) that didn't belong anymore (and removed one case of ancient vandalism). The only "link" that didn't survive the split, was the sibling relationship, which didn't really make sense. Now there is Jeanneke Pis (Q152360)inspired by (P941)Manneken Pis (Q152072). --Azertus (talk) 15:08, 26 May 2021 (UTC)

People with year only births that I can find full dates for

I had someone create this for me: tinyurl.com/o26zc83 It looks for USA people missing full birthdays and I scour the WWI and WWII draft registration to find their full birth date, where we only have the birth year entered. The search can no longer be used since we imported year-only birth information and uploaded them as duplicate values. Can someone modify it so it ignores humans where one of the values is already the full birthday, even though the second value is the year-only birth information? --RAN (talk) 05:03, 26 May 2021 (UTC)

@Richard Arthur Norton (1958- ): This should be what you are looking for: https://w.wiki/3PXS Vojtěch Dostál (talk) 18:28, 26 May 2021 (UTC)

• Perfect, thank you! --RAN (talk) 18:39, 26 May 2021 (UTC)

Duplicated items for ancient Chinese politicans

@GZWDer:Some items about ancient Chinese politican is automatically imported from China Biographical Database(China Biographical Database (Q13407958)) ,but some duplicated entries are imported as new item,not merged into existing item created for zhwiki article.

Some examples below:

Duplicated items

Item for zhwiki	Item imported from database
Xie Zheng (Q22099264)	Xie Zheng (Q45544579)
Xie Chen (Q18659280)	Xie Chen (Q45697756)
Wang Yonghe (Q16925826)	Wang Yonghe (Q45544975)
Wang Yonghe (Q15932340)	Wang Yonghe (Q45529303)

Maybe there are more items not merged.Please check these items and figure out which are duplicated.--Jingkaimori (talk) 13:48, 26 May 2021 (UTC)

Those items are created by User:Fantasticfears.--GZWDer (talk) 16:49, 26 May 2021 (UTC)

Problem is very much on the margins. 20 items, 10 duplicate sets. Equally, label differences between items having the same CBDB are concerning. --Tagishsimon (talk) 17:20, 26 May 2021 (UTC)

== Chinese help needed : 换乘站^(Q1147171) and 轉乘站^(Q10544770) ==

Thanks for disambiguating these two items Bouzinac ^{💬●✒️●💛} 14:35, 26 May 2021 (UTC)

QuickStatements API cannot write date statements?

Copied from Help_talk:QuickStatements

Following up on this earlier note, I've tracked down the problem to the QuickStatements API and dates. It seems specifically that the QuickStatements API cannot write date statements. I've tried with and without quotes (%22) around the date. See the examples below (I've blanked out my token; Find yours here if you want to test):

• This works (without quote marks): https://quickstatements.toolforge.org/#/v1=Q4115189%09P580%09+2010-01-01T00:00:00Z%2F11
• API fails (without quote marks): https://quickstatements.toolforge.org/api.php?action=import&submit=1&format=v1&batchname=&username=Evolution_and_evolvability&token=#######################################&data=Q4115189%09P580%09+2010-01-01T00:00:00Z%2F11
• API fails (with quote marks): https://quickstatements.toolforge.org/api.php?action=import&submit=1&format=v1&batchname=&username=Evolution_and_evolvability&token=#######################################&data=Q4115189%09P580%09%22+2010-01-01T00:00:00Z%2F11%22

Can anyone spot a workaround (please reply at Help_talk:QuickStatements)? It seems a pretty important feature to be missing. T.Shafee(evo&evo) (talk) 01:30, 27 May 2021 (UTC)

@Evolution and evolvability: isn't there an example of using a date right in the manual: Help:QuickStatements#Add_statement_with_qualifiers ? Does that not work for you? BrokenSegue (talk) 04:28, 27 May 2021 (UTC)

oh I see you are talking explicitly about the API. Is the API meant to be used in the way you are proposing? Why not just talk to wikidata directly? BrokenSegue (talk) 04:38, 27 May 2021 (UTC)

@BrokenSegue: I've been using the Quickstatemenst API to build the WikidataR package, since R data frames seem very compatible with the quickstatements 'v1' format (and the QS API documentation was more approachable than that of the WD API). The QS API seems to work for everything except dates so I was hoping it'd be possible to find a workaround for that aspect. I'm keen to avoid having to re-write the whole R package to use a diferent API format. T.Shafee(evo&evo) (talk) 08:56, 27 May 2021 (UTC)

Having a ID, how to get QID (massively)

I have a list of IDs of one identifier, more specifically: Property:P627, I want to find the correspondent qid for each of them. There are 13K items on the list, that is why I do not want to do this manually. Can you help me, thank you. Rodrigo Tetsuo Argenton (talk) 23:55, 27 May 2021 (UTC)

@Rodrigo Tetsuo Argenton: you can use a query like https://www.wikidata.org/w/api.php?action=query&format=json&list=search&srsearch=haswbstatement:P627=40966 to get the qid of a particular value of IUCN taxon ID (P627). You could also use SPARQL to dump all the values of that property and the corresponding QIDs. BrokenSegue (talk) 03:25, 28 May 2021 (UTC)

Try Multi-BEACON (Q92076515). --- Jura 06:57, 28 May 2021 (UTC)

135652 statements is not too much, you can just download https://query.wikidata.org/#SELECT%20%3Fitem%20%3Fvalue%20%7B%20%3Fitem%20wdt%3AP627%20%3Fvalue%20%7D as CSV and then something like =INDEX('query'!A:A, MATCH(A1,'query'!B:B,0)) in Excel/other app. --Lockal (talk) 07:27, 28 May 2021 (UTC)

Highway Overpass

construction of an overpass highway was finished recently, and I didn't see any information or sign either, is it possible to create a (wikidata item) for highway overpass? --Ahmadkurdi44 (talk) 12:06, 28 May 2021 (UTC)

If it satisfies WD:N. WD has at least one: Muradpur Flyover (Q31728736) though perhaps lacks a more appropriate P31 value. --Tagishsimon (talk) 12:09, 28 May 2021 (UTC)

Q6286385

At Joseph Quick (Q6286385), for instance, when I find that English Wikipedia has an error and it was imported, I just delete it. Another editor says I should keep it and deprecate the value. I find one or more a day using various error and omission searches. Which represents best practices? I am blocked from making the corrections at English Wikipedia but I make the correction in the other language Wikipedias. --RAN (talk) 18:57, 27 May 2021 (UTC)

Deprecation decreases the likelihood that the erroneous value will be reimported. So the question is, do you feel lucky? --Tagishsimon (talk) 20:53, 27 May 2021 (UTC)

• I thought that the bot importing data from Wikipedia only added a value if there was no reference already in place, does anyone remember which bot is responsible, so we can check to see how it works. --RAN (talk) 21:16, 27 May 2021 (UTC)

There are many routes by which WP data is imported into WD, including multiple bots. Presumably the history of the item will answer your question for this instance? --Tagishsimon (talk) 21:26, 27 May 2021 (UTC)

I agree it is practically a bug of the bot if existing statements are not checked. Careless programmers do such things. Give them hell. --SCIdude (talk) 06:24, 28 May 2021 (UTC)

• I suppose it depends how many times you want to correct them. At Wikipedia, editors like to re-do the same edit a hundred of times. Some people like to do that even here, even though Help:Ranking should teach them the opposite. --- Jura 06:46, 28 May 2021 (UTC)

We probably should not be importing year-only values when we already have a full-date value. About 1/4 of the birth-year year-only values are calculated based on the age reported in an obituary, and are off by a year. We also need to uprank the full-date values automatically so that the year-only values stop appearing as duplicates in infoboxes. --RAN (talk) 13:23, 28 May 2021 (UTC)

• Someone mentioned that there was/is a bot performing the uprank procedure, but I have not seen evidence of it yet. --RAN (talk) 17:03, 29 May 2021 (UTC)

Ambiguity in year of birth based on the census

At Tatzumbie DuPea (Q106862833) I had exact years of birth for the person based on each census entry. My reasoning is that we know her exact day of birth and we know the exact date that the census was taken. The census only tells us the person's age on the day of the census. If we know the day they were born, it is easy to calculate the exact year of their birth claimed in the census. In this case in each census Tatzumbie DuPea (Q106862833) claimed a different year, making themselves older each census, especially when she was an adult filling in the information herself, instead of a parent. Another editor changed my entries and added in ambiguity. That ambiguity would only exist if we did not know their day of birth. For Tatzumbie DuPea (Q106862833), her day of birth has remained the same in all known documentation for her, so it is mathematically certain to calculate her claimed birth year when given her claimed age stated in the census. I want to reverse the ambiguity added by the other editor. The other editor has not responded, and deleted my message. What do you think, is my math correct? --RAN (talk) 13:14, 28 May 2021 (UTC)

The item has an exact date which is identifical to your exact date, afaics, and which has the same reference, albeit shorn of some detail, which is regrettable. Is there a problem still worth worrying about? --Tagishsimon (talk) 15:47, 28 May 2021 (UTC)

My argument is that the ambiguous dates from the census are incorrect mathematically, and my exact years from the census were correct. Yes, it is worth worrying about, since it will be repeated each time I use this method where we know the day a person was born, but there is ambiguity about the year. It is a simple math question, so it should be easy to figure out who is correct and who is incorrect, once you understand the concept. --RAN (talk) 00:31, 29 May 2021 (UTC)

Can always hope that someone comes along to teach me this esoteric calendar maths concept. If you must pursue this approach it would be worth referencing your calculated date with based on heuristic (P887) pointing to an item explaining the calculation basis. In the instant case there does not seem to be an ambiguity to be cleared up. --Tagishsimon (talk) 00:48, 29 May 2021 (UTC)

• Again, what I am looking for is which of the two arguments is mathematically correct, which is still not being answered, which is why I am assuming you are not following the concept, which is why I keep trying to rephrase it. Perhaps it would be best if we heard from more people. --RAN (talk) 16:56, 29 May 2021 (UTC)

Listing items without a translated main label

Hi. I hope this is the correct place to ask. I made a query to list all norwegian ships, but I'm interested in changing the query so that it will only list items for which there are no labels available in the language "norsk bokmål" (nb). How do I do that? Thanks in advance.

#Norske skip (registert eller opererer i Norge)
SELECT ?item ?itemLabel ?start ?end ?manufacturer ?manufacturerLabel ?imo ?mmsi ?dnvgl WHERE {
  ?item (wdt:P31/(wdt:P279*)) wd:Q11446.
  { ?item wdt:P8047 wd:Q20. }
  UNION
  { ?item wdt:P17 wd:Q20. }
  OPTIONAL { ?item wdt:P729 ?start. }
  OPTIONAL { ?item wdt:P730 ?end. }
  OPTIONAL { ?item wdt:P176 ?manufacturer. }
  OPTIONAL { ?item wdt:P458 ?imo. }
  OPTIONAL { ?item wdt:P587 ?mmsi. }
  OPTIONAL { ?item wdt:P5006 ?dnvgl. }
  SERVICE wikibase:label { bd:serviceParam wikibase:language "nb". }
}

Try it!

--Infrastruktur (talk) 23:55, 28 May 2021 (UTC)

Wikidata:Request a query is a better venue. Like this:

#Norske skip (registert eller opererer i Norge)
SELECT ?item ?itemLabel ?start ?end ?manufacturer ?manufacturerLabel ?imo ?mmsi ?dnvgl WHERE {
  ?item (wdt:P31/(wdt:P279*)) wd:Q11446.
  { ?item wdt:P8047 wd:Q20. }
  UNION
  { ?item wdt:P17 wd:Q20. }
  OPTIONAL { ?item wdt:P729 ?start. }
  OPTIONAL { ?item wdt:P730 ?end. }
  OPTIONAL { ?item wdt:P176 ?manufacturer. }
  OPTIONAL { ?item wdt:P458 ?imo. }
  OPTIONAL { ?item wdt:P587 ?mmsi. }
  OPTIONAL { ?item wdt:P5006 ?dnvgl. }
  SERVICE wikibase:label { bd:serviceParam wikibase:language "nb". }
  filter not exists {?item rdfs:label ?itemLabelnb. filter(lang(?itemLabelnb)="nb")}
}

Try it!

--Tagishsimon (talk) 00:04, 29 May 2021 (UTC)

Tracked in Phabricator
Task T195178

• For items of a given property, you could use complex constraint label language (Q102746314). --- Jura 09:36, 29 May 2021 (UTC)
  • Never noticed that one. I mentioned it on phab:T195178. Multichill (talk) 12:36, 29 May 2021 (UTC)
  • Interesting. If I understand that correctly, it's used to express a permanent expectation that entities with a certain property should have a localized label? And also that the talk page template will tag entities which don't meet the expectation with a category? More to the point, would you say this is suitable to add to Kulturminne ID (P758) as one would expect norwegian labels there? --Infrastruktur (talk) 13:10, 29 May 2021 (UTC)
    • Probably yes, except that with Norwegian, I'm never sure if it should be nb or nn or both.
      You'd get a (daily) report like the one at Wikidata:Database reports/Complex constraint violations/P5080 for Norsk biografisk leksikon ID (P5080). The queries on property talk pages can also be run directly. There is a summary for nb at missing/nb that works as long as there are not too many properties requiring nb (we don't have one for en).
      The intro is at Help:Property constraints portal/Label language --- Jura 13:25, 29 May 2021 (UTC)

Chat merge?

I have proposed a merge of the Danish, Norwegian and Swedish Project Chats on Wikidata:Bybrunnen! 62 etc (talk) 19:27, 29 May 2021 (UTC)

Performing a merge

Hello. I am an active editor on the English Wikipedia, but not nearly as experienced in Wikidata so I need a bit of help. I noticed the Wikidata items Q106623313 and Q45819340 are for the same person. How do I merge them? Link20XX (talk) 00:03, 30 May 2021 (UTC)

@Link20XX: Done, thx. --Tagishsimon (talk) 00:04, 30 May 2021 (UTC)

Howto: see Help:Merge#Gadget; in this case a redirect sitelink needed to be removed from one of the two items. --Tagishsimon (talk) 00:06, 30 May 2021 (UTC)

TMDb ID, batch #55696

@Josh404: Referencing by Freebase absolutelly doesn't makes sense (btw. if sourced from Freebase then why stated in (P248): The Movie Database (Q20828898)?) and what is the point referencing TMDb ID by TMDb itself? Eurohunter (talk) 10:14, 30 May 2021 (UTC)

you can find likely context for this at Wikidata:Requests for permissions/Bot/Tmdbzhbot. I'm guessing it's a copy and paste error? And there is a point to the reference. It indicates that the ID was deduced by looking at the TMDb API using the key given. As opposed to, say, imported from wikipedia or stated in some third party source. All non-trivial statements optimally would be sourced. Batch should probably be fixed or reverted. BrokenSegue (talk) 13:41, 30 May 2021 (UTC)

Hi, as @BrokenSegue mentioned, we were trying to come up with a reference format that implied this was looked up on The Movie Database (Q20828898) but using a Freebase ID (P646) not the TMDB movie ID (P4947). The association is not stated anywhere in a Freebase Data Dumps (Q15241312). Any better suggestions for better reference format? Happy to make changes and fix up any references. Josh404 (talk) 17:44, 30 May 2021 (UTC)

@Josh404: I'm a little confused what keys you used to look up the data? Sometimes it's freebase IDs and sometimes it's IMDb? Why does Samson and Gert (Q3470967) have three references on TMDB TV series ID (P4983)? Is it saying all three lookup mechanisms return the same thing? If so then yeah this is probably correct. BrokenSegue (talk) 21:49, 30 May 2021 (UTC)

Yes, for TMDB TV series ID (P4983) may have up to three cross references listed in the TMDb backend. In the Samson and Gert (Q3470967) case, resolving the item's Freebase ID (P646), IMDb ID (P345) and TheTVDB series ID (P4835) all resolved to the same TMDB TV series ID (P4983). But there could potentially be a conflict where resolving a Freebase ID (P646) and IMDb ID (P345) lead to different TMDB TV series ID (P4983). Usually these means there's duplicate entities on the TMDb side, but I hoped to record the method that produced each statement. Here's a link to the API documentation for the lookups. Let me know if there's a better way of expressing this in the reference format. Josh404 (talk) 22:00, 30 May 2021 (UTC)

Oh, ok this all seems fine then (if a bit verbose). BrokenSegue (talk) 23:51, 30 May 2021 (UTC)

first appearance (P4584) for sport

Is there version of first appearance (P4584) for sport? So Aston Martin in Formula One (Q25412511) was created probably before 1957 but first appearance (P4584) occurred in 1959. Eurohunter (talk) 12:44, 30 May 2021 (UTC)

significant event (P793) with first appearance (Q8563381) and a date qualifier? --Tagishsimon (talk) 13:34, 30 May 2021 (UTC)

Duplicated property

P9413 (P9413) is an exact duplicate of BLPL author ID (P1473). No one noticed it before creating!? Lugusto (talk) 17:15, 30 May 2021 (UTC)

Duplicate created by @UWashPrincipalCataloger:. --Tagishsimon (talk) 17:22, 30 May 2021 (UTC)

They seem to be described in a very different way. If so, information from the new one can be merged/moved. P1473 didn't grow much since its creation. @Epìdosis, TiagoLubiana, Thierry Caro, Gerwoman: who requested/supported creation of P9413. --- Jura 07:44, 31 May 2021 (UTC)

@555, UWashPrincipalCataloger, Tagishsimon, TiagoLubiana, Thierry Caro, Gerwoman: @Jura1: Everything migrated to BLPL author ID (P1473) and duplicate property deleted. Thanks for noticing, --Epìdosis 10:24, 31 May 2021 (UTC)

Wikidata weekly summary #470

Here's your quick overview of what has been happening around Wikidata over the last week.

• Discussions
  • Closed request for comments:
    • Cleaning up the ontology of anonymous. Outcome: New model adopted, documentation updated.

• Events
  • Past
    • Wikibase Community User Group monthly meetings- May 2021
    • How to add references on Wikidata (# 1Lib1Ref 2021) - working hour (2)
    • SPARQL #Wikidata divers
      • Session du mardi 18 mai
      • Session du mardi 25 mai
  • Upcoming
    • SPARQL queries live on Twitch and in French by Vigneron, June 1 at 18:00 CEST
    • Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Affinity Group Co-facilitators will recap the last year, introduce plans for the coming year, and receive suggestions from the community for future sessions.; [27], June 1st.
    • Online Wikidata meetup in Swedish #65, June 6
    • Meta meeting of the Wikibase Community User Group, to solve issues related to its affilation to the Wikimedia Foundation, June 9
    • Wikidata Bug Triage Hour about quality constraints, June 17

• Press, articles, blog posts, videos
  • Papers
    • Mapping of ImageNet and Wikidata for Knowledge Graphs Enabled Computer Vision
  • Videos
    • Wikidata Lab XXIX: Roundtripping process
    • Use of VanderBot Wikidata API writing script (testing)
    • LIVE Wikidata editing #45 - YouTube, Facebook

• Tool of the week
  • User:So9q/ordia-link.js - is a script to add a link to Ordia in the Tools section on items.

• Other Noteworthy Stuff
  • Call to participation in interview study to building a recommender system that can help improve the editing experience in Wikidata: Researchers at King's College London develop a personalized recommendation system to suggest Wikidata items for the editors based on their interests and preferences. The researchers are inviting volunteers to interview them about their current ways to choose the items you work on in order to understand the factors that might influence such a decision.
  • dewiki considered, but rejected the introduction of local short descriptions to replace those from Wikidata
  • User:Nikki/LexemeEntitySuggester.js was improved to now
    • automatically suggests the existing senses/forms when using demonstrates sense/form
    • automatically suggests items (based on the lemma matching the label or an alias) when using item for this sense
    • and searches for lemmas exactly matching the input when using synonym, antonym, hyperonym or pertainym

• Did you know?
  • Newest properties:
    • General datatypes: district heating grid
    • External identifiers: DiVA authority-person, CDep.Ro NGO ID, WUA author ID, hush.am person ID, Moths and Butterflies of Europe and North Africa ID, What Works Clearinghouse study ID, PoetsGate poet ID, Repositório da Produção da USP person ID, ctext data entity ID, Australian Music Centre work ID
  • New property proposals to review:
    • General datatypes: Martian coordinates, gobbledygook
    • External identifiers: Nevada Women's History Project ID, AADFI member ID, Bod-Inc Online author ID, Erfgoedkaart ID, Price One Penny Periodical ID, Price One Penny Library ID, composers.am person ID, armradioarchive.am person ID, Armeniapedia ID, Biographical Encyclopedia of Astronomers ID, AZGS Document Repository ID, electronic Essential Medicines List medicine ID, PAS member ID, ℒoviℱm Top Songs ID, 20th Century Chinese Biographical Database ID, Dizionario Biografico dell'Educazione (1800-2000) ID, BIU Santé image bank ID, cadastral plot in France, Internet Game Database developer ID, allabolag.se person ID, Olschki author ID
  • Query examples:
    • People with bird-like surnames in Czech (Source)
    • Properties used to link from preprints (Q580922) to scholarly articles (Q13442814) (Source)
    • Birthplace of Spanish poets (Source)
    • UK Parliaments since 1801 with number of members, number of distinct member-terms, and count of missing seats/parties. (Source)
  • Newest database reports: Fresnel lenses of lighthouses

• Development
  • Italian Wikiversity used Lua on their Recent Changes SpecialPage via overwriting a MediaWiki message. Our code used to not expect that, now it does. (phab:T283240)
  • Updating the panel that tracks Wikidata edits over time in different namespaces to include all namespaces (phab:T281356)
  • Working on adding a new constraints type for Lexemes (phab:T200689)
  • Working on designs for improving Special:NewLexeme
  • Working on designs for the system to find mismatches between Wikidata's data and other databases
  • Fixing some malformed globe-coordinate precisions in the database (phab:T283576)

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.

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 13:15, 31 May 2021 (UTC)

Can't enter family name for a Croatian swimmer

Hi! I succeeded to add some data about some people (has statement: instance of human). Data I could add inclue label and description in several languages, statements on gender, date of birth etc., but I was unsuccesful with others for the same persons: family name, father, mother...

When I add statement and start writing "father" in the property name field (or "mother", or "parent", I get property name offered, and accepted, but when I try to enter actual data (e.g. full name, family name, as apropriate)h into value field, I get message "No match was found" on redish background (and can't publish).

I suppose I am violating a constraint, but don't see where and how I can find what constraint is in question, and what to do about it. I went through tutorials on items and properties (again, to remind myself of details). I see for every property where values were accepted, there already existed the necessary value on drop-down list. In my case, for family name, father's or mother's names in question - that needed to be entered - were not yet on the list (were Slovenian, Chroatian etc.).

When I tried to enter "birth name" property (also the value should exist both because articles with that name already exist in WP in several languages, and so label in Wikidata with that name should already, I get additional small window a bit below, with text: "Language (mandatory):". When I enter "Chroat (hr)", there is no info what to do next, just an X that supossedly closes this little window is still available (and we can imagine what happens after that, because there is no info).

I click the x and little window closes. Click to Publish "button" is now accepted, but data is not saved. The background of statement area becomes (different areas different niances of) red, and message apears:

Could not save due to an error.

"Croatian (hr)" is not a known language code."  

I could guess why language code could be needed, but to my best knowledge hr language code is valid, so there must be something else.

Where do I find description of what is the problem, and how to deal with it? If such a description doesn't exist yet, how to help create in? --Marjan Tomki SI (talk) 23:39, 20 May 2021 (UTC)

@Marjan Tomki SI:. Can you please provide the Q number for the item (or one of the items) where you are having this problem? A more experienced editor may be able to identify if there is a problem with the item that is preventing your edits. From Hill To Shore (talk) 01:02, 21 May 2021 (UTC)

@From Hill To Shore:: Can do. Pattern seems repeatable (for a class of situations, not only this one).

Example: Karla Šitić (Q6372461);

• Adding statement for property birth name and value Karla Šitić gave results as described above.
• Adding statement fo property family name with value Šitić gives situation, where you can't publish and background is slightly red (and I suspect constraint is violated).
• Adding another language spoken with value English, gets published (I removed it again, because I suppose she is fluent in English, but didn't check it now).
• Adding statement for property family name with value Johns (family name) gets accepted and published (as a test, and I removed it immediately after again),

Provisional conclusion: only already known values can be entered for properties with behaviour described. I need info where I can find rules and procedures for entering new family names etc.

I also released (to be sure, also closed browser window for) Karla Šitić (Q6372461) to evade possible additional problems with concurrent editing (such problem set was encountered with editing theme/section on a Wikipedia page; revert recovered from unwanted effects, but detailed description of that is not of interest right now). --Marjan Tomki SI (talk) 07:55, 21 May 2021 (UTC)

• Maybe you omitted to create an item for the family name?  Done now: Šitić (Q106920449). --- Jura 08:32, 21 May 2021 (UTC)

@Marjan Tomki SI: I have added the new family name item Šitić (Q106920449) (which Jura created) to Karla Šitić (Q6372461). There are many family name items that still need to be created and I usually end up making a few per month for the human (Q5) items that I work on. If you can't find an item in the drop down list it either means one hasn't been created yet or there is one but it is missing the label in your language. Ideally you should locate an existing item and add your own language label but if you can't spot one with a quick search, just create a new item for what you need. If you have created a duplicate, someone will come along in the future and merge the duplicates. From Hill To Shore ([[User talk:|talk]]) 19:21, 21 May 2021 (UTC)

• @Jura1: @From Hill To Shore: Thanks to both of you, that was what I needed. I supposed there is a constraint (you can't enter something somebody hadn't already verified to be correct for the domain of allowed values), but didn't find that described, neither in tutorial, nor in help. I'd like some of you "old salsts" to check if help/tutorial item about that exist.

If it does not, I first intend to work with this some more. I have several tens of items to create (got reliable sources already collected that I couldn't enter up to now), and also to add material to same articles in several languages, and before that, some sailing to teach ;-)

When I get used to adding that (both optimal way and with other possible glitches), I might try to create a proposition for one or more such help topics for beginners (adding items, constraints... possibly linked to apropriate glossary items). Much thanks to both for this info. --Marjan Tomki SI (talk) 06:47, 25 May 2021 (UTC)

• Conclusion: There seems to be a general, implicit requirement for at least some classes of variables' values, that property with that value can't be published without related item with that value having been created first.

For seasoned insiders - who kow why it is so and what the procedures are (what to do, and how, and in what order, and how violations of procedure are presented to the user) seem to be a no-brainer (everyone knows that, right?). For a beginner that should (IMO) be introduced (tutorial or help item). If such material already exists, I'd like a link to it (to see why I failed to locate it, and see if it makes sense to me while still a novice). If it doesn't exist, I'd like to get in contact with anybody willing to help create it. --Marjan Tomki SI (talk) 21:24, 31 May 2021 (UTC)

Undergrad research topic

Hi! I am a Wikipedian and an undergrad database management student, and was wondering if someone could recommend a Wikidata- or Wikipedia-related research topic I could pursue for my coursework? Also, where would I look for papers and such on this topic? (I need to be able to cite academic sources.) Thank you much! Datumizer (talk) 03:46, 13 May 2021 (UTC)

Google Scholar with "Wikidata" gives 3k hits, not enough? --SCIdude (talk) 07:10, 13 May 2021 (UTC)

Sorry for the delay, I did not realize topics got moved so quickly on this board.

I am interested specifically in Wikidata:WikiProject Climate Change. I guess I can go ask there. Datumizer (talk) 02:30, 21 May 2021 (UTC)

• Maybe this meets your interest and the project requirements: you could try to build visualizations changes in glacier sizes. This might require creating and completing items about glaciers with suitable source(s). I don't think we have that many historic sizes of glaciers. A basic map is at Wikidata:SPARQL_query_service/queries/examples#Glaciers_map --- Jura 10:04, 21 May 2021 (UTC)
  • Thanks! I don't actually have to work with the data myself (sorry I wasn't clear). Just investigate how other people are using the data and related tools. Are professionals currently utilizing Wikidata in their climate research work, for instance? Datumizer (talk) 06:47, 26 May 2021 (UTC)
• As well extracting map layers for geo-projects,

There's family tree info:

https://www.entitree.com/en/family_tree/Kanye_West

Wikidata has a million academic articles, on entitree look for "main subject" or "main topic". Maybe your looking for academic paper showcase: https://m.youtube.com/playlist?list=PLhV3K_DS5YfLQLgwU3oDFiGaU3K7pUVoW Allknowingroger (talk) 16:52, 31 May 2021 (UTC)

Deactivate Special:MergeItems

To merge items, Help:Merge advises users to use the gadget.

Despite this, it seems we frequently get complaints from contributors trying to merge items with the above feature. Most recently:

• May 9: Wikidata:Project_chat#Description_of_templates
• May 13: Wikidata:Project_chat/Archive/2021/05#Annoying_merge_limit (likely)

As there are not really any cases where the speical page is helpful, I think we should de-activate it here on Wikidata. --- Jura 06:23, 23 May 2021 (UTC)

• I think it is the no-Javascript fallback option for item merging. If it does not work as desired, it should rather be fixed. —MisterSynergy (talk) 06:48, 23 May 2021 (UTC)
• I vaguely recall a dev's view that it works how it's meant to work. It's just not working for Wikidata's contributors.

As it probably works for non-Wikidata installations of Wikibase, simply deactivating it here should be sufficient. --- Jura 07:06, 23 May 2021 (UTC)

• What exactly is not working or what exactly is Special:MergeItems doing wrong? --LydiaPintscher (talk) 18:08, 23 May 2021 (UTC)
  • Apparently, users like the two complaining above couldn't merge items, whereas a new user who asked about merging instantly managed to do it with the gadget (see Wikidata:Project_chat/Archive/2021/05#Merge). I think it has something to do with users being required to edit descriptions prior to merging. Nothing necessarily wrong, just not of much use at Wikidata with descriptions in hundreds of languages. Normally, the code of the merge gadget should indicate how to improve it (not that the merge gadget couldn't be improved further, but that's another question). --- Jura 18:27, 23 May 2021 (UTC)
• Wikidata is already largely unusable without JavaScript; the situation should be improved, not further degraded. The answer for the difference is in line 808 of the gadget, and the comment suggests that the gadget’s behavior is the original one, Special:MergeItems has changed since. —Tacsipacsi (talk) 12:04, 24 May 2021 (UTC)

Not sure if this is the only difference. As editing statements isn't meant to be possible without Javascript, it seems odd that we should have a merge tool that works without. --- Jura 16:09, 24 May 2021 (UTC)

@Jura1: Is it a goal that statements should not be edited without JS? (Where is it documented?) I really hope that it isn’t; rather, this restriction just happened to be, without a conscious decision of WMDE/WMF, and it should be fixed (this is what I mean by improving the situation) instead of dropping even more non-JS solutions. And if there are any other differences, they should be fixed as well. —Tacsipacsi (talk) 12:23, 27 May 2021 (UTC)

It was discussed not too long ago on Wikidata:Contact the development team. Merging sometimes requires editing statements afterwards, so inciting users who can't edit statements to merge items doesn't sound like a good functionality. --- Jura 12:36, 27 May 2021 (UTC)

• We don't want people who aren't using Wikidata much and thus not understanding how policies well to go and randomly merge items. If there are users who don't want to activate JavaScript and thus won't edit statements I don't think they should go around merging items.

I would prefer WMDE to use modern webtechnology instead of slowling down their development work to keep Wikidata useable without JS and having heared any reasoning why it would be worthwhile to not make that tradeoff. ChristianKl ❪✉❫ 18:35, 31 May 2021 (UTC)

Can Wikidata reduce lingual bullying by big four (FAGA)?

Hello,

I'm curious about how the big four (Facebook, Amazon, Google, Apple) use locations - and to what extent they use Wikidata. In particular, I wonder how to reduce and ideally prevent lingual bullying in the form of "digital ethnic cleansing" through promoting only one language version of place names that exist in many languages.

A related issue is the "benevolent spelling cleansing" of place names. Some are misspelt, some are duplicates. That type of cleansing should happen, and be promoted.

Places with names in several languages. E.g. Finland has many bilingual municipalities with official names in two languages - evident on road signs, maps, etc. However, if you try to tag a photo in Instagram (part of Facebook) with the Swedish name "Hagalund", it will show it as "Tapiola" - which is quite unfair to the person that identifies with the Swedish name of the district (I have my phone set to English in this case). This is a form of lingual bullying where Information Technology could make multilingual names easy, instead of working as a way to simplify and ignore a language and culture.

Duplicates and misspellings. E.g. Instagram (part of Facebook) is full of locations with odd variations. Some locations are misspelt, some are duplicates, some are wrongly placed. A municipal in Finland called "Espoo" in Finnish has two separate ID:s: 214575438 is "Espoo, Finland" and 653710146 is "Esbo, Etelä-Suomen Lääni, Finland". Two IDs for the same place feels unnecessary, and the latter is a mix of Swedish and Finnish, which should be corrected to be completely either Swedish or Finnish - but how and where?

Wikidata FAGA-properties? I have found properties in Wikidata such as Instagram location ID P4173, Facebook Places ID P1997 and Google Maps Customer ID P3749. There are not a lot of entries for these property (see IG location count by country), but it does wake my curiosity how these properties are used by FAGA themselves. Does anyone know if these are pushed out from Facebook and Google into Wikidata? Does Facebook and Google load these back in? Does it make sense to fill IDs out for as many Wikidata objects as possible to have a chance of improving location information?

Thanks for thoughts on this. Robertsilen (talk) 07:51, 26 May 2021 (UTC)

I don't think we know the answers to most of these questions. I would guess they don't use those identifiers (since they already hold links to us) but I don't know. Best bet is to find someone inside those companies who can answer or perform an experiment and wait for them to re-ingest us. BrokenSegue (talk) 18:21, 26 May 2021 (UTC)

• Somehow the argument seems self-contradictory: it's noted that only one version for a place is used (in which GUI language?), OTOH multiple identifiers for the same place are also mentioned. Somehow both cases end up being presented as a problem caused by data users (or contributors?) in rather harsh terms.

As far as Wikidata goes, we did add a requirement at Help:Label/fr#Références that references for the labels should be available and we shouldn't merely reflect some typographic convention at Wikipedia. --- Jura 20:13, 26 May 2021 (UTC)

• @Jura: The two issues are not contradictory, but related. Lingual bullying and spelling mistakes. Lingual bullying is about disallowing correct usage, and to correct that may require changed functionality in some system (eg. having options where there are currently none). Spelling mistakes are about simple textual bugs, and to correct that only requires one to know where the basic text is in Wikidata, from which FAGA takes their data. Robertsilen (talk) 09:35, 27 May 2021 (UTC)

• There is a fully operational patent from Google, which describes how Google extracts facts (including names) from various sources. It includes a number of unspecified things like "human evaluator to determine the trustworthiness of a particular fact"; though such interventions are rare in real life. Many places are connected to Google Knowledge Graph/Freebase; there is a UI for owning and editing places (yet another patent). As for quality, you should not expect a high quality of labels in Google Maps, because one of the sources of labels is Google Translate & dummy transliteration. "Does it make sense to fill IDs ..." - right now at least for Google there is no need to. Google uses different algorithms to map places to Wikidata/Wikipedia. Just set correct labels here, in Wikidata, and everything should be fine. --Lockal (talk) 21:02, 26 May 2021 (UTC)
  • @Lockal: Do you work for Google? --Succu (talk) 21:37, 26 May 2021 (UTC)
    • @Succu:, no, otherwise I would be bound by an NDA, even though all this information is either described many times in various blogs or can be trivially discovered from page source. There is an observation component too. For example, take a look at Shilovo (Q1147452) Russian settlement. There is a Czech translation copied from Wikidata to [28] (Šilovo). Therefore Šilovo is displayed as a label in Czech Google Maps. Now look at Lashma (Q4255487) - a settlement nearby. There is no Czech label in Wikidata, so there is no label in GKG too[29], and Czech Google Maps fallbacks to English label[30]. Now you are free to set Czech label to Lašma, and after few weeks Google should reindex Wikidata and pull a new label to GKG and show it in Google Maps. --Lockal (talk) 07:34, 27 May 2021 (UTC)
      • @Lockal:, could you recommend any particular blog-URLs? I have found a couple by googling on the topic, but I feel there must be more good explanations and examples like the one you mentioned here. Thank you, this is very valuable! Robertsilen (talk) 11:10, 27 May 2021 (UTC)
        • @Robertsilen: Bill Slawski wrote a simpler explanation of Entity Extraction patent with some extra links. There are no direct articles about Wikidata->Google connection, but I sometimes I make webarchive snapshots of Google Search: examples for changing labels are David Cameron and Takano Hayato. --Lockal (talk) 12:24, 27 May 2021 (UTC)
• I talked two years ago with someone working on the team in Google. Google's knowledge graph is developed by hundreds of programmers and thousands of contractors. While they do source some data from Wikidata there's a lot of work involved on Google's side.

Knowledge graph isn't a Google project on which a few dozen programmers work but an important cornerstone of Google's strategy.

Having better data at Wikidata that's considered to be good by big tech companies is likely to be incorporated by them but there's enough human judgement on their part by people who are generally not publically talking about their decisions that it's hard to predict how any given change on Wikidata will trickle down into their projects. ChristianKl ❪✉❫ 18:57, 31 May 2021 (UTC)