Wikidata:Project chat/Archive/2021/09

From Wikidata
Jump to navigation Jump to search

Wwwyzzerdd for Wikidata: Public Launch

Awhile back I advertised an upcoming extension that would make editing wikidata from wikipedia easier. After a long delay it's ready to be tried out if anyone is interested. Here's a demo video from the last post I made about it.

There's a few known issues but I think it's at a point where I'd like some feedback. I've used it a bunch to import facts from Wikipedia directly into Wikidata (e.g. [1]).

You can install it in Firefox or Chrome:

Or you can install it from source on github. Do note that currently it only supports enwiki but if there's interest I can make it work more broadly.

I'm also considering advertising its existence on enwiki's forums but unsure if they care about data being structured.

BrokenSegue (talk) 22:11, 24 August 2021 (UTC)

This looks good, and I'll give it a try, but I'm curious why it's a browser add-on, and not a Wikipedia user script? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:53, 25 August 2021 (UTC)
First impressions are it's very useful and also easy to use. One change I would like is not to suggest ID properties when the relevant link is a subject with a QID. For example, for an actor, I type "cast" and you offer me "cast member", which is good, but also "CastingVideos ID" and "Casting show ID", which are not. Also do not offoer to duplictae an existing property (if the selected item is already a cast member, do not offer that again). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:10, 25 August 2021 (UTC)
@Pigsonthewing: Thanks for the feedback! That's a good idea though I'll have to see how easy it is to identify such properties as being invalid. Honestly I didn't consider a user script but I think I am using browser features that would be unavailable to a user script (e.g. caching data between loads to make the script more responsive). BrokenSegue (talk) 15:25, 25 August 2021 (UTC)
Looks very nice, @BrokenSegue! How feasible would it be to have it pick up references for selection/copying? I get the impression people who are solely on enwiki wouldn't have much gusto for adding structured data. If it picked up the references too, that might be a different case. I'd say give it some time before advertising it there until you've had time to work on the known bugs/missing features.
It's already really useful in its current state. I think this extension could be big for Wikidata. It's great for filling out items with 1 or zero statements, but also for hunting for the last missing links on an almost "complete" item. --Azertus (talk) 10:55, 25 August 2021 (UTC)
@Azertus: thanks for the feedback. Reference copying/parsing is definitely on my to-do list. One thing I'm unsure of is what the best user interface for that would be. Would appreciate any thoughts if you had them. I'm also unsure how east it is to go from reference HTML to a structured reference in wikidata. Yeah, there's definitely still bugs to fix and optimizations to make. BrokenSegue (talk) 15:25, 25 August 2021 (UTC)

I have created Wikidata:Wwwyzzerdd. If BrokenSegue is agreeable, I suggest further feedback be discussed on its talk page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:45, 26 August 2021 (UTC)

sounds good. thanks! BrokenSegue (talk) 20:57, 26 August 2021 (UTC)
@BrokenSegue: can you enlighten us about the name? Is it named after (P138) something? ;-) --Azertus (talk) 16:21, 27 August 2021 (UTC)
ETA: I think I just got it, is it wizard (Q580334) (or magician (Q2488257))? --Azertus (talk) 16:25, 27 August 2021 (UTC)
it's named after this fictional character. they're too obscure to have a wikidata item it seems. BrokenSegue (talk) 04:01, 28 August 2021 (UTC) but yeah meant to be a reference to the concept of "wizard" but with an unused name BrokenSegue (talk) 04:02, 28 August 2021 (UTC)
www.yzzerdd.com (Q108367925). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:25, 1 September 2021 (UTC)

Replacement of National Library Board Singapore ID

We will be replacing National Library Board Singapore ID (P3988) with new identifiers some time next year. I've a couple of questions on how to proceed to replace the old identifiers in Wikidata:

1) Do we proceed first to make the changes directly in National Library Board Singapore ID (P3988) by amending the formatter URL? Or do we need to inform the Wikidata community through the page Wikidata:Property proposal/National Library Board Singapore ID (https://www.wikidata.org/wiki/Wikidata:Property_proposal/National_Library_Board_Singapore_ID)?

2) How do we replace all the identifiers that have been in use in Wikidata entities? Do we delete the old identifiers first and add in the new identifiers, or can we overwrite the old identifiers with new ones directly using QuickStatements?

Appreciate your advice on the above questions. Thank you!  – The preceding unsigned comment was added by Nlbkos (talk • contribs) at 04:42, August 31, 2021‎ (UTC).

How can I add language?

Hello. I wanna add name of the item Dvach (Q60455989) in Ukrainian language (Btw, it is the same as in Russian). How can I do this?  – The preceding unsigned comment was added by HareGovorittKrishna (talk • contribs) at 10:56, August 31, 2021 (UTC).

@MSGJ: You can permanently override the languages that show up in the labels/descriptions box by using the Babel userboxes on your userpage to set languages you know. If you don't want to do this or are adding a label/description in a language you don't know, enable the "labelLister" gadget in your preferences. That will give you a "Labels list" tab next to the "view history" tab; you can use the "edit" button in the dialog to enter labels/descriptions/aliases for any arbitrary language. Vahurzpu (talk) 01:56, 1 September 2021 (UTC)
Not my post! That would be HareGovorittKrishna. But goood answer — Martin (MSGJ · talk) 08:10, 1 September 2021 (UTC)

Should I ignore the value constraint in Q104891511?

Anglo-Somali War - The Somali Dervish Movement I THE GREAT WAR 1921 (Q104891511) is a YouTube video (Q63412991)] published by The Great War (Q30598122). How come that there's a value constraint warning in this case? Should I use different properties? Tetizeraz (talk) 12:59, 31 August 2021 (UTC)

In this instance, fixing the underlying cause, which was that youtube channel was not a subclass of publisher, is the better way to go. That's done. --Tagishsimon (talk) 13:04, 31 August 2021 (UTC)
Also reminder that using a template in the question heading means that users cannot navigate to the section direct from watchlists or the page history; please do not use tempates in question headings. --Tagishsimon (talk) 13:06, 31 August 2021 (UTC)
Heading fixed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:24, 1 September 2021 (UTC)

Wikipedia article and Wikidata item

How can I change the number of a Wikidata item for a Wikipedia article? I want the link to lead not to a redirect, but to the correct Wikidata item, otherwise the Interwiki's are not visible in the article. Specific example: en:Izyum–Barvenkovo offensive--Nicoljaus (talk) 19:45, 1 September 2021 (UTC)

You seem to have solved that one before asking the question. In general, remove the offending sitelink in wikidata and add the correct sitelink. Sometime, a merge will be in order. --Tagishsimon (talk) 20:11, 1 September 2021 (UTC)
I'm sorry, but I don't understand. I did a merge, but the redirect (Q106012490) remains. Because of this, the link from the Wikipedia article goes to this redirect, and the interwiki's do not appear (and I cannot add them manually). It will somehow go away by itself, you just have to wait?--Nicoljaus (talk) 21:13, 1 September 2021 (UTC)
NP. The redirect items does still exist, and bounces the WD user to Izyum-Barvenkovo Offensive (Q4198896). The EN Wiki article now also points to Q4198896 - https://en.wikipedia.org/w/index.php?title=Izyum%E2%80%93Barvenkovo_offensive&action=info and the interwiki links on the EN article are present and correct. If they're missing from either of the other two language versions, a purge of the article pages will sort it out. --Tagishsimon (talk) 21:18, 1 September 2021 (UTC)
And yes, 21:11 - 21:13 ... put that down to latency somewhere in the system. --Tagishsimon (talk) 21:29, 1 September 2021 (UTC)
interwiki links on the EN article are present and correct -- It happened just a couple of minutes ago! More recently, "Wikidata item" link from the En article led to Q106012490, not to Q4198896. Thank you, apparently you just need to wait a bit.--Nicoljaus (talk) 21:30, 1 September 2021 (UTC)

"Select for merging" cannot be switched off

I accidentally clicked on "Select for merging". How do I get rid of the blue sign? --HarryNº2 (talk) 17:01, 26 August 2021 (UTC)

I found a solution: Switch on and off Merge via Special:Preferences#mw-prefsection-gadgets. Does anyone know any other solution? I use Firefox as my browser. --HarryNº2 (talk) 17:42, 26 August 2021 (UTC)
If you switch Merge in Special:Preferences on again, the blue symbol is there again after a while I don't want to have to empty the Firefox cache if possible. --HarryNº2 (talk) 18:26, 26 August 2021 (UTC)

brigadeiro (Q2914862) has three main ingredients. Two of them can be swapped. How I structure this on Wikidata?

For this confection, you may use cocoa powder instead of chocolate powder, and some recipes allow you to switch from butter to margarine. Additionally, sprinkles are optional, how do I structure all this information? Tetizeraz (talk) 19:19, 27 August 2021 (UTC)

I've added sprinkles, with an appropriate qualifier. Substitutability is harder. I'm not sure that has part(s) (P527) is a great choice for the ingredient list. Suspect has listed ingredient (P4543) or made from material (P186) might be better. Wikidata:WikiProject_Food/Properties#Other_properties specifies P186 and does not seem to have heard of P4543, which is odd. --Tagishsimon (talk) 15:44, 28 August 2021 (UTC)
optional (Q59864995) is a quality (Q1207505), so should it use has characteristic (P1552) instead? AntisocialRyan (Talk) 17:39, 28 August 2021 (UTC)
Yes, that probably works better. --Tagishsimon (talk) 17:41, 28 August 2021 (UTC)
There's list of values as qualifiers (Q23766486) + disjoint union of (P2738). --Infovarius (talk) 13:25, 2 September 2021 (UTC)

Q56236334

Q56236334

Hi, guys, and sorry if the question is in a wrong place or stupid one: not an active and experienced contributor here. We have this item Q56236334 that is used a source of the place of living of some people in Russia. It is highly used as @Marat-avgust linked it to lots of people as a proof of their address. Eventually, it is used as a source in Wikipedia via lists of people generated by @ListeriaBot, but it is not a reliable or even allowable source, as I think. I tried nominating it for deletion but @Emu suggested to discuss it here first. So, if you look to the history of this item, you would see frequent edits of the source address (zhytil.rosfirm.info, jutel.rosfirm.info, gytely.rosfirm.info and so on), the site is migrating and it is not an official source: it is based on the leakages of personal data of people living in Russia (we have various sites with telephone numbers, addresses, names and so on) and in my opinion it should have been even blacklisted (though it is migrated and the block wouldn't be sufficient). I am not unlinking this item myself as it would be a big set of changes. I want to hear the feedback, please. Rubin16 (talk) 12:21, 31 August 2021 (UTC)

Moved to Wikidata:Administrators' noticeboard § Q56236334: Lockal (talk) 10:02, 1 September 2021 (UTC)
  • Isn't that called a "telephone directory" or a "city directory", a paper version for my city is thrown into my driveway once a year and then tossed into the garbage bin. --RAN (talk) 12:50, 2 September 2021 (UTC)
    • No, this is a union of leaked databases. For example, it also contains information about me, and this information is wrong, and it replicates the same mistake that exists in my medical insurance card (which I don't even care to fix, because why I should provide a correct data about me if medical institutions are not able to keep it private). --Lockal (talk) 13:30, 2 September 2021 (UTC)

New Reply tool

Hi, I think we should install/enable the new Reply tool on this Wiki. WDYT?--So9q (talk) 05:53, 2 September 2021 (UTC)

@So9q It’s already installed (I’m using it right now), you just need to enable the beta feature. Lucas Werkmeister (talk) 06:46, 2 September 2021 (UTC)

Tool to bulk replace long-hand citations with items

On, for example, Cornelius James Field (Q108309703), there are many statements with identical references, using:

stated in (P248)=Brooklyn Eagle (Q4974820)
publication date (P577)=20 September 1915 Gregorian
page(s) (P304)=18

That citation source now has its own, more fully populated, item, Cornelius J. Field Dies of Typhoid (Q108321601).

Is there a tool that will (semi-)automatically replace each of the above citations with:

stated in (P248)=Q108321601

on the former item, or better on all (or a given set of) items?

Or would someone like to make one? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:31, 30 August 2021 (UTC)

Did you ever find a way to do this in an elegant way? One way would be a series of SPARQL queries and associated set of Quickstatements – one set of QS to add the new reference, and another set of QS to delete the old one. - Fuzheado (talk) 17:43, 3 September 2021 (UTC)

Is it possible to set up a private wikidata instance?

I would like to use wikidata to make some data editable by humans & computers, but I want to have full control over who can edit it. Is it possible to set up a private instance of wikidata, the same way it's possible to set up a private instance of mediawiki?

See mw:Wikibase.--GZWDer (talk) 16:35, 3 September 2021 (UTC)

Rename a page with a typo

Q100698451 has a typo in its title. I don't know what to do about this, as I don't see an option to move or rename a page. I couldn't find anything in the documentation either. Thanks. Cryptic-waveform (talk) 19:44, 3 September 2021 (UTC)

@Cryptic-waveform: On items in Wikidata, there is no concept of moving like on Wikipedia. Instead you just edit the labels to correct the item name. I have gone ahead and fixed the spelling on the English label for Pannal War Memorial plaque (Q100698451). --William Graham (talk) 20:10, 3 September 2021 (UTC)
Thank you. Cryptic-waveform (talk) 23:31, 3 September 2021 (UTC)

Duyfken Point, Queensland

These two items need to be merged, but can't be because of (near-identical) articles at cebwikipedia: Duyfken Point (Q21912564) and Duyfken Point (Q21924713). There's also Q21643279 which is a disambig page for the two and should be deleted (along with its cebwikipedia page) after the merge. I'm not sure what the protocol is for this sort of thing — it seems messy to just unlink one of the ceb pages, but also I don't know about how to raise a merge request on that wiki (it's not my language). Sam Wilson 01:06, 4 September 2021 (UTC)

Generally, I think, mark up one or the other with permanent duplicated item (P2959) and/or Wikimedia permanent duplicate item (Q21286738). AFAIK cebwiki is a lost hope which we route around. --Tagishsimon (talk) 01:11, 4 September 2021 (UTC)
Simply you may merge them into one page and merge the items.--GZWDer (talk) 01:27, 4 September 2021 (UTC)
@GZWDer: Okay, done, and I also suggested that the disambig page be deleted.
@Tagishsimon: I look forward to the time when Wikifunctions will make this sort of bot-generated content unnecessary! Sam Wilson 05:28, 4 September 2021 (UTC)
@Tagishsimon, Samwilson: permanent duplicated item (P2959) isn't applicable as cebwiki doesn't have multiple pages on the same topic in different scripts or languages. instance of (P31)=Wikimedia duplicated page (Q17362920) would have been the item to use. See Help:Merge#Mark_as_duplicate --- Jura 09:09, 4 September 2021 (UTC)
@Jura1 Good to know, thanks. Sam Wilson 09:56, 4 September 2021 (UTC)

Is there a way to find out how many times a specific website is referenced on Wikidata?

Hi all

I guess this is a query service question? I'm trying to find out if there is a way of knowing how many times a specific website (a whole domain not a specific url) is used on Wikidata.

Thanks

--John Cummings (talk) 13:31, 4 September 2021 (UTC)

WD stores the URL as a triple, but does not store the domain as triple. That suggests that a plain SPARQL report would have to look at all URLs in the triplestore and filter them based on a pattern. I don't think that will be possible in WDQS b/c timeout; but it would, presumably, be possible on a local instance of WD.
It's possible that the MWAPI search service could be used within a SPARQL report to find items with the domain string, but I think that route would only work up to whatever the MWAPI result-set limit is (and I have vague concerns about its reliability / completeness).
As a trivial example of the latter, here's an MWAPI search for "ibm.com". In practice some more SPARQL testing that "ibm.com" is being found within URL property values would probably be called for.
SELECT DISTINCT ?item ?itemLabel 
WHERE {
  hint:Query hint:optimizer "None".
  SERVICE wikibase:mwapi {
    bd:serviceParam wikibase:api "Search";
                    wikibase:endpoint "www.wikidata.org";
                    mwapi:srsearch "ibm.com".
    ?item wikibase:apiOutputItem mwapi:title .
  }
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
Try it!
--Tagishsimon (talk) 13:43, 4 September 2021 (UTC)
The search engine is a bit too generous. The first hit, IBM's Watson Group signs up genomics partners (Q86501788) does include "IBM" and ".com", but not "ibm.com". Ainali (talk) 14:35, 4 September 2021 (UTC)
@John Cummings: If you don't care about context, Special:LinkSearch is your friend. If that's okay but you need to restrict to item namespace, you could try a variant of quarry:query/41024 with the database set to wikidatawiki_p. Vahurzpu (talk) 16:09, 4 September 2021 (UTC)

As far as I know are in Wikidata more people involved who do editing through their job than in other Wikimedia Projects. Wikidata is interesting for librarians as far as I know. According to the Terms of Use of the Wikimedia Foundation it is needed to disclose if you do a paid edit. There are different kind of possibilites how to do it. In Wikidata in most cases it is from my point of view possible on the talk page or through a List at your user page where you list what edits are paid edits. There is as far as I know not a comment field to write it into that it is an paid edit so that it is visible in the page history. From my point of view diclosing paid edits is an important rule and please pay attention to it. I prefer if it is visible in the version history of an item. Do you think that it is possible to create a Tag Paid Editing so that it is possible to mark paid edits. And a tool so that people can add the Tag to their edits afterwards for manual edits and a script that can be acitvated that the tag is added automatically to every edit.--Hogü-456 (talk) 13:09, 5 September 2021 (UTC) moved from Wikidata:Forum -- Reise Reise (talk) 13:21, 5 September 2021 (UTC)

@Reise Reise: For a long time there has been a requests for comment that goes in this direction. Maybe that might interest you. Alternate disclosure policy --Gymnicus (talk) 13:32, 5 September 2021 (UTC)
It doesn’t help the case of the RfD that the guy who started it is now indefinitely banned from DE.WP for, well, it’s complicated, but mostly paid editing stuff … --Emu (talk) 17:56, 5 September 2021 (UTC)
There’s a script to alter the edit summary: User:Lockal/EditSum.js. It’s probably easy to modify it so you don’t have to enter the paid edit disclosure every time. --Emu (talk) 17:56, 5 September 2021 (UTC)

Different results in wikidata / wikipedia-search?

A general search for the string "Stroop" on the german wikipedia-page resulted in to entries for the family name of "Jürgen Stroop" and "John Ridley Stroop". A search on wikidata with the query: SELECT * WHERE { ?PersonA wdt:P734 wd:Q21508811. } gave just one result ("Jürgen Stroop"). How can this difference be explained? Thanks in advance!

A family name (P734) property value has not been added to the item for John Ridley Stroop (Q706672) b/c no-one has got around to it. --Tagishsimon (talk) 14:07, 5 September 2021 (UTC)

Question about Wikipedia:Template:Wikidata

Hi, please see my question on Wikipedia here. Winston (talk) 21:00, 5 September 2021 (UTC)

Need Help to Choose a Specific Qualifier

Within an item - type concert tour, there is a Statement = performer where are listed the bands in the tour. I'd like to add a Qualifiers to each band which specify the musicians that played in the band during that Tour. What Qualifier to use?

I think about identity of object in context or has quality but I'm not sure...

Link: Rock Never Stops Tour 2003 (Q108399051) --MrPanyGoff (talk) 20:34, 4 September 2021 (UTC)

There is a technique that maps a RDF triple to a single sentence, then you can see clearer which qualifiers you need to choose. For example, he married Mary in 2009 so we have a qualifier P580 here.  A l p h a m a  02:58, 5 September 2021 (UTC)
participant (P710)? --Tagishsimon (talk) 13:27, 5 September 2021 (UTC)
I've tried qualifier participant but it gives me a message that: "participant is not a valid qualifier for performer". You know, the case is: Item=Concert Tour -> Statement Performer=Band Name -> Qualifier Participant=Musician/band member--MrPanyGoff (talk) 08:18, 6 September 2021 (UTC)

The Data Quality Days are starting soon (September 8-15)

Hello all,

The Data Quality Days, eight days of community events focused on data quality, are starting on Wednesday, September 8th, and there are plenty of very interesting sessions taking place! Many thanks to everyone who proposed a topic and took the lead to facilitate a discussion or a workshop.

Here are a few examples of events that will take place (you can see the full schedule here):

  • Data quality: what is it and why is it important?
  • EntitySchemas and Shape Expressions on Wikidata
  • How can we incorporate feedback from our biggest data re-users at scale?
  • Integration of the Czech authority files with Wikidata
  • Editing livestream and editathon on property constraints
  • Editathon to improve Help:Ranking and Help:Deduplication
  • Overview of the ontology issues on Wikidata
  • Increasing data quality by increasing Wikidata's visibility on other wikis
  • Bug Triage Hour on data quality and maintenance
  • Presentations of various patrolling and quality tools (ORES, ProWD, Item Quality Evaluator, SpeedPatrolling, Constraint Violation Checker, WikidataComplete...)

The events are taking place online (most of them on the open source tool Jitsi). Most of them are not recorded but notes will be taken. No registration is needed, you can simply add your name to the participants list if you want to tell others that you are interested. It is still possible to add sessions in the schedule if you want to take care of a discussion or workshop. There's also a Phabricator board where you can add the projects you plan to work on.

We're looking forward to discuss data quality and tools with you! If you have any questions, feel free to reach out to me. Lea Lacroix (WMDE) (talk) 07:30, 6 September 2021 (UTC)

How do we add sitelinks to incubator site pages like this? https://incubator.wikimedia.org/wiki/Wp/enm/Among_Us AntisocialRyan (Talk) 00:39, 6 September 2021 (UTC)

It's not possible, see phab:T54971. The problem is that now you can only have one link to a project regardless of how the project is actually structured. Wikimedia Incubator URL (P9748) exists as a workaround. --Matěj Suchánek (talk) 10:07, 6 September 2021 (UTC)

Wikidata weekly summary #484

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Other Noteworthy Stuff
    • User:SuccuBot has made its 100.000.000th edit. It is the first user account in Wikidata to reach this milestone.
    • In the frame of a Google Summer of Code project a new tool, called WikidataComplete was created. The tool smoothly integrates in the Wikidata UI and proposes new statements extracted by machine learning algorithms. Editors are asked to either approve or reject them. To activate it check here for a short tutorial check here. Any feedback is welcome here.
  • Development
    • Continued work on the Mismatch Finder. We are now working on creating the page where mismatches will be listed for review.
    • Worked on support for "separators" parameter for distinct value constraints (phab:T277855)
    • Made it possible to restrict constraints to certain entity types (phab:T269724)
    • Added a new constraint type to ensure that the Item has a label in a particular language (phab:T195178)
    • Added a button for the Query Builder to query.wikidata.org to make the Query builder discoverable (phab:T276210) - integration in the example dialog is still in progress (phab:T280229)
    • We started work on some behind-the-scenes improvements to the way Wikipedia and the other Wikimedia projects are notified about a change that affects their articles. (They need this notification so the article can be purged and show the latest data from Wikidata again. It is also required for showing the edit in the watchlist and recent changes on those wikis. This should have no visible impact for editors but is needed maintenance work.

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.

merge reverted

My merge of Q15768656 and Q55310741 was reverted without comment. As a result, about thirty articles have been disassociated from Commons. Because I was reverted without comment, I don't know if I did something incorrectly or if the reverter is just an ass. If anyone cares, please take a look. Thanks, Featous (talk) 13:47, 6 September 2021 (UTC)

I think the merge was correct.--Ymblanter (talk) 14:22, 6 September 2021 (UTC)
Categories and their topics are usually not merged. --SCIdude (talk) 14:29, 6 September 2021 (UTC)
For Commons categories it is usual practice, we only do not merge them when there is also a Commons gallery present.--Ymblanter (talk) 18:52, 6 September 2021 (UTC)
@Succu: As this was your edit, you may wish to comment. From Hill To Shore (talk) 19:14, 6 September 2021 (UTC)
A taxon item was merged with a category item. This is wrong. --Succu (talk) 19:23, 6 September 2021 (UTC)
I think we should clean out category items that only have a sitelink to Commons are just linked with topic's main category (P910). --- Jura 19:33, 6 September 2021 (UTC)

The 2022 Community Wishlist Survey will happen in January

Hello everyone,

We hope all of you are as well and safe as possible during these trying times! We wanted to share some news about a change to the Community Wishlist Survey 2022. We would like to hear your opinions as well.

Summary:

We will be running the Community Wishlist Survey 2022 in January 2022. We need more time to work on the 2021 wishes. We also need time to prepare some changes to the Wishlist 2022. In the meantime, you can use a dedicated sandbox to leave early ideas for the 2022 wishes.

Proposing and wish-fulfillment will happen during the same year

In the past, the Community Tech team has run the Community Wishlist Survey for the following year in November of the prior year. For example, we ran the Wishlist for 2021 in November 2020. That worked well a few years ago. At that time, we used to start working on the Wishlist soon after the results of the voting were published.

However, in 2021, there was a delay between the voting and the time when we could start working on the new wishes. Until July 2021, we were working on wishes from the Wishlist for 2020.

We hope having the Wishlist 2022 in January 2022 will be more intuitive. This will also give us time to fulfill more wishes from the 2021 Wishlist.

Encouraging wider participation from historically excluded communities

We are thinking how to make the Wishlist easier to participate in. We want to support more translations, and encourage under-resourced communities to be more active. We would like to have some time to make these changes.

A new space to talk to us about priorities and wishes not granted yet

We will have gone 365 days without a Wishlist. We encourage you to approach us. We hope to hear from you in the talk page, but we also hope to see you at our bi-monthly Talk to Us meetings! These will be hosted at two different times friendly to time zones around the globe.

We will begin our first meeting September 15th at 23:00 UTC. More details about the agenda and format coming soon!

Brainstorm and draft proposals before the proposal phase

If you have early ideas for wishes, you can use the new Community Wishlist Survey sandbox. This way, you will not forget about these before January 2022. You will be able to come back and refine your ideas. Remember, edits in the sandbox don't count as wishes!

Feedback

  • What should we do to improve the Wishlist pages?
  • How would you like to use our new sandbox?
  • What, if any, risks do you foresee in our decision to change the date of the Wishlist 2022?
  • What will help more people participate in the Wishlist 2022?

Answer on the talk page (in any language you prefer) or at our Talk to Us meetings.

SGrabarczuk (WMF) (talk) 00:23, 7 September 2021 (UTC)

Duplicates in taxon common name (P1843) with different capitalization

I found duplicates of taxon common name (P1843) with different capitalizations on the same item. The lower case names seem to come from the same import: Belgian Species List (Q64007131)

For example Water Rail (Q185099) lists Water Rail (English) and water rail (English), râle deau (French) and Râle d’eau (French), waterral (Dutch) and Waterral (Dutch)

Is this intentional or should this be fixed by a bot?--DarthBrento (talk) 13:57, 4 September 2021 (UTC)

Can I get free data? Here

Please lm begging you guys

sure have some data gratis: "94VVS362kIMBsiqLRr1ckIuh3wX14CBlYd6SoYXz3YaBb85LcA72QNA4qmH7jN" BrokenSegue (talk) 18:40, 5 September 2021 (UTC)
Sorry I had to encrypt your data BrokenSegue since it was copyrighted. Totodu74 (talk) 14:25, 7 September 2021 (UTC)

Ticketmaster ID is limited to US subsidiary

Ticketmaster artist ID (P7354) works for 1/27 locations (discussion) - Coagulans (talk) 19:26, 7 September 2021 (UTC)

Merge request

Hi all

Q4945235 and Q63016451 appear to be the same person, could someone who is able merge them please.

Thanks

--John Cummings (talk) 12:39, 8 September 2021 (UTC)

✓ Done, --Esteban16 (talk) 19:53, 8 September 2021 (UTC)

Youtube channel name (Property:P1810)

Hello

The item Q1190282 has a youtube channel, but its name is not given: no property 1810.

The link to the youtube channel is: https://www.youtube.com/channel/UC76_vWaI6_-cU-77e2Kl3_w whose name (as seen on youtube itself) is "Independence National Historical Park".

So if I understand correctly, I can add the property P1810 by clicking on "edit -> add qualifier", and give the value "Independence National Historical Park".

Correct ?  – The preceding unsigned comment was added by Laurent.Claessens (talk • contribs).

This would be my first contribution to wikidata; so I prefer to be sure.

@Laurent.Claessens: Yup that sounds right. You will select subject named as (P1810) as the qualifier type and then will type the name. BrokenSegue (talk) 19:54, 8 September 2021 (UTC)

Shared accounts in Wikidata

Hello! I work as a librarian at the National Diet Library, Japan, and I would like to ask details on shared accounts in Wikidata.

My colleagues and I are currently considering of registering data from our library to Wikidata. At first, we were thinking of creating an account and share it among us, so that we could provide data in a consistent manner, as part of our duty as a public institution.

However, we learned that there is an explicit rule in Wikipedia that forbids shared accounts. Wikipedia:Sockpuppetry

Role accounts: Because an account represents your edits as an individual, "role accounts", or accounts shared by multiple people, are as a rule forbidden and blocked.

Though we couldn’t find the same rule on Wikidata, and several national libraries like the National Library of Australia and Bibliothèque nationale de France seem to provide identifiers as an organization, we were not able to determine whether or not we can create a shared account on Wikidata. Wikidata:Data donation Wikidata:Project_chat/Archive/2019/11#Wikidata:Alternate_accounts_and_shared_account

Thus, we would like to ask three questions:

  1. Is it possible for me, as a librarian of the National Diet Library, to create an institutional account and share it with my colleagues?
  2. If it is possible, are there any procedures for me to take?
  3. Are there any precautions in providing data from both an institutional account and a private account?

Mmmichi (talk) 02:49, 3 September 2021 (UTC)

@Mmmichi: That project chat discussion is pretty old at this point but seems like back then there was a generally favorable view towards organizational accounts. Our rules are not the same as english wikipedia. Presumably if you follow Wikidata:Alternate accounts things would be fine. That said other organizations that have contributed to wikidata have used individual accounts with flags in the username indicating they are members of the organization. Is there a reason that wouldn't work for you? BrokenSegue (talk) 10:08, 3 September 2021 (UTC)
Previous discussions indicate that we purposefully didn't adopt Wikipedia's rule here and allow institutional accounts shared by multiple people. At the same time Wikidata:Alternate accounts gives some guidance. Generally, link from the personal accounts to the institutional account to disclose affiliation and don't engage in discussions with both the personal and the instituational account. ChristianKl ❪✉❫ 11:18, 3 September 2021 (UTC)
@BrokenSegue: @ChristianKl: Thank you very much for your kind advice! I'll consult with my colleagues, with reference to the proposed information. Mmmichi (talk) 08:12, 9 September 2021 (UTC)

Property proposals aren't quick so we might be losing contributions

I started a [property proposal](https://www.wikidata.org/wiki/Wikidata:Property_proposal/EPA_Facility_Registry_Service_ID#Motivation) and I kind of stalled out because I wasn't sure how long it might take to get approved and created. I have QuickStatements files ready to insert but I realized they would be better if I included an external identifier (hence the property proposal).

But I think there is a principled way to allow my QuickStatments file to include unique identifiers that doesn't involve waiting on a property proposal.

What if we create one generic property "uniquely identified by" then with a qualifier one can reference the identifier entity. So for example:

Aqua Ohio - Ashtabula (Q108226439) "uniquely identified by" 110009614051 .

With qualifier: named by (P3938) Facility Registry Service ID (Q108442534) .

or With qualifier: approved by (P790) Facility Registry Service ID (Q108442534) .


The goal of this would be to allow contributions where a unique identifier is known but the user doesn't have the time or interest in creating a new property.

Justin0x2004 (talk) 13:23, 7 September 2021 (UTC)

    • @99of9: What I am proposing here is an identifier property that can be used without the need to wait on a property proposal. I think this would increase the number of unique identifier in use. What do you think? Justin0x2004 (talk) 00:34, 8 September 2021 (UTC)


WikidataCon update - Program of the first day and Wikidata birthday

visual of the WikidataCon 2021

Hello all,

The WikidataCon, the conference dedicated to the Wikidata community and co-organized by Wikimedia Deutschland and Wiki Movimento Brasil, is taking place online on October 29-31, around the theme “a sustainable future for Wikidata”. In this update, we are very excited to share with you the first announcements about the program of the event!

On October 29th, the first day of the conference, you will discover a program of keynotes and round table discussions carefully curated by the organizing team. Knowledge equity, Abstract Wikipedia, the technical challenges of the Query Service, and an overview on how Brazilian cultural institutions use Wikidata, are some of the topics that will be presented during this first day. We will also have various celebrations related to Wikidata’s anniversary that will allow us to celebrate achievements of the community and discover new projects. You can have an overview of the program of Day 1 here.

On the next two days of the conference, the program will be made of presentations, discussions and workshops coming directly from the participants. We will have several thematic tracks split during three time slots, to allow people from various time zones to attend. The content of these tracks will be proposed by the Wikidata community. This process will start at the beginning of October. More information will be added on this page in the next few weeks.

To support us in running this very ambitious event, five organisations are sponsoring the WikidataCon. You will find a description of the sponsors here. Some of these organizations are already benefiting from the amazing content of Wikidata, and their contribution to the conference is one of the ways they can engage more with the community and support the future of the project.

October is also the celebration of Wikidata’s ninth anniversary, as the project was officially started on October 29th, 2012. Every year, community members work together on birthday presents that will be showcased during the WikidataCon. You will find the ninth birthday page here, and you can already think about a birthday present you would like to prepare.

Last but not least: the registration for the conference will start on September 15th. More information will be added on the Attend page at the time.

Thanks for reading this update! You can find out more about the WikidataCon on this page, and read the previous updates on the talk page. If you have any questions or suggestions, feel free to reach out to us by leaving a comment on the talk page or contacting info@wikidatacon.org.

For the WikidataCon organization team, Lea Lacroix (WMDE) (talk) 17:52, 9 September 2021 (UTC)

Best practices for nicknames

See Elisa Eberhard Anheuser (Q102357214). Should we embed nicknames in parenthesis, or alternative names in parenthesis or quotation marks, as the main name in a QID? --RAN (talk) 13:34, 9 September 2021 (UTC)

Novels: Different objects for translations?

Hello, I just noted that for the novels of the Remembrance of Earth's Past (Q29841269), different objects exist. E.g. for the first novel of the series, there is The Three-Body Problem (Q607112) as possibly main object, and 三体 (Q87346656) for the Chinese original version, and The Three-Body Problem (Q54810596) for the English translation. Is this really desired? Shouldn't it rather be solved with attributes? If this is really desired, then I think also for films, there should be different objects for dubbed versions. However, those would never be connected to a wikipedia article as you wouldn't write a separate article only for a dub.  – The preceding unsigned comment was added by User:Christian140 (talk • contribs) at 9. september 2021 kl. 15:01‎ (UTC).

@Christian140: See Wikidata:WikiProject Books for the distinctions made here between works and their editions and translations. I'm not saying this example has been following our standards, but that's what it should be based on. Wikidata:WikiProject Movies/Properties is the analogous page for films, and includes some info on how we should indicate dubbing. We follow a community consensus approach which is so far slightly different in these two cases. ArthurPSmith (talk) 15:57, 9 September 2021 (UTC)
Okay, thanks. --Christian140 (talk) 09:02, 10 September 2021 (UTC)

Notability of (Wikimedia) tools and meta-documentation in general

Hi. So I have the misfortune of liking to edit in a field that has recently proved to be a bit controversial. I believe items about all kinds of tools we (can) use to edit, view, reuse and reason about Wikimedia projects have a place on Wikidata. And I'm not the only one interested in adding those items. At the time of writing, there are over 200 instances of Wikimedia tool (Q63213147). For example, as I noted during the opening session of the Data Quality Days 2021 (Q108461073), correctly tagged tools (using main subject (P921)), can be queried to find tools relevant to one's field of interest. My other arguments can be found in the discussions below.

User:Gymnicus and User:So9q oppose the existence of the items on technical grounds (notability). Since there's such a large dichotomy between theory and practice, I believe this is a case where our notability policy needs amending or an exception. User:Bluerasberry had the same idea in trying to amend the notability criteria. It's obvious (to me) the community finds value in these items. To illustrate the scope of the "issue", if we were to make a concerted effort to add items for tools, I think the number would run in the hundreds, maybe up to a thousand, but not much more.

There exists a perception (misguided, IMO) that the only reason for adding the tools, is to allow items for Wikimedians to be created. Those discussions only serve to muddy a quite simple issue. The notability policy is intentionally vague. We should clarify it so that sitelinks on Meta-Wiki (see point 1.9) about tools, scripts and bots are valid or that Wikimedia tools in general deserve a place on Wikidata. In most places eating your own dog food (Q3033752) is a good thing and I have no clue why we shouldn't describe ourselves (meta-documentation) in the same way as we do the outside world.

I am writing here to get some more eyes on the notability discussion and to request ideas on how to move forward. I don't have any experience in guiding a discussion of this magnitude. Maybe an RfC is in order? Regardless of the outcome all of the above, I'd like to start a WikiProject Meta-documentation (or something of that nature) to discuss all the ways we can improve our meta-documentation. Anyone interested in that may contact me. --Azertus (talk) 22:26, 9 September 2021 (UTC)

  • Support establishment of WikiProject Management of Wikimedia data will be a perpetually recurring issue and the establishment of a WikiProject is the conventional way to manage conversations which are likely to be ongoing for years. I said more at User_talk:Azertus#WikiProject_for_Wikimedia?. Blue Rasberry (talk) 22:40, 9 September 2021 (UTC)
  • I oppose any formal rule that would create a double standard between Wikimedia projects and other projects. It would set a dangerous precedent if independent references are no longer needed. We should be extra careful in our coverage of ourselves and avoid any suspicion that we are somehow more lenient if a Wikimedian or a Wikimedia project is the subject. --Emu (talk) 23:08, 9 September 2021 (UTC)
  • Well perhaps. Equally WD was established to support & interact with other WMF sites, which is why WD finds, for instance, category and template pages on WPs notable. Unsure in what sense that does not establish as foundational the 'double standard between Wikimedia projects and other projects'. --Tagishsimon (talk) 23:22, 9 September 2021 (UTC)
  • True, but nobody outside Wikipedia cares about categories or templates, so it’s not a problem if you create notability out of thin air by creating categories. But it’s hard to justify why Wikimedians should be eligible for a Wikidata item without proper independent references but volunteers from other projects are measured against a higher standard. On a side note: I feel we had some sort of an informal “don’t create, don’t ask to delete“ policy for those items until recently. It maybe wasn’t the worst policy and I’m not happy about the conflict. But formally declaring a difference is a different case. --Emu (talk) 23:56, 9 September 2021 (UTC)
  • I feel like the cat's out of the bag with respect to not giving special notability consideration to WM-things. We have tons of web page (Q36774) and community project (Q5155040)s that meet notability standards only by virtue of being WM-related (wikiproject's and wikipages). If having the item fulfills some WM-related need then I think we should keep them. So for example having a Wikidata project page should suffice (and then structural needs to get to the creator of the wiki-project if we care). In reality our deletion standards are already totally busted since you can use "structural need" to include virtually any person by chaining relatives off people with wiki articles. BrokenSegue (talk) 06:08, 10 September 2021 (UTC)
    The property maintained by WikiProject (P6104) sort of depends on items for WikiProjects. If it can only be used for the one or two that have reached external notability, it is quite useless. Ainali (talk) 11:49, 10 September 2021 (UTC)
  • I think the notability of items about tools was questioned when I started creating them in 2015, but the outcome seems to have been that they were kept. What would be different now? --- Jura 11:22, 10 September 2021 (UTC)
  • Thanks for bringing it up here also, so the wider community can chip in, and for agreeing to pause creating new similar items while the discussion is ongoing :)
I look forward to seeing if this will result in a change of our notability criteria. Side note: I might be a bit biased since I'm both a tool author and user script author. I personally don't have a problem with items for tools, but we should have a clear policy and draw a line between what is included and what is not. Does an old unused user script (no backlinks) merit an item? What is the definition of tool? Is a small gist in Github or paste in Phabricator enough to warrant an item?--So9q (talk) 12:12, 10 September 2021 (UTC)

Is there an easy way to check for Wikidata items from an English Wikipedia article with lots of redlinks?

Hi all

Today I wrote an English Wikipedia article for the Accessible Books Consortium which has a large number of red links (maybe 100 or so) to organisations who work on making publications more accessible. One thing I've done to try and make these organisations easier to identify is to add a column to the tables for a Wikidata link. My question is is there some kind of tool that I can use to extract these red links and match them to whichever already have Wikidata items?

Thanks

--John Cummings (talk) 15:56, 10 September 2021 (UTC)

You can always try with the linked items tool, if the labels are similar on Wikidata you may get a few hits. Ainali (talk) 16:19, 10 September 2021 (UTC)
Thanks very much, 68 hits, a great start. --John Cummings (talk) 16:32, 10 September 2021 (UTC)

Call for Candidates for the Movement Charter Drafting Committee ending 14 September 2021

Movement Strategy announces the Call for Candidates for the Movement Charter Drafting Committee. The Call opens August 2, 2021 and closes September 14, 2021.

The Committee is expected to represent diversity in the Movement. Diversity includes gender, language, geography, and experience. This comprises participation in projects, affiliates, and the Wikimedia Foundation.

English fluency is not required to become a member. If needed, translation and interpretation support is provided. Members will receive an allowance to offset participation costs. It is US$100 every two months.

We are looking for people who have some of the following skills:

  • Know how to write collaboratively. (demonstrated experience is a plus)
  • Are ready to find compromises.
  • Focus on inclusion and diversity.
  • Have knowledge of community consultations.
  • Have intercultural communication experience.
  • Have governance or organization experience in non-profits or communities.
  • Have experience negotiating with different parties.

The Committee is expected to start with 15 people. If there are 20 or more candidates, a mixed election and selection process will happen. If there are 19 or fewer candidates, then the process of selection without election takes place.

Will you help move Wikimedia forward in this important role? Submit your candidacy here. Please contact strategy2030(_AT_)wikimedia.org with questions.

This message may have been sent previously - please note that the deadline for candidate submissions was extended and candidacies are still being accepted until 14 September 2021. Xeno (WMF) 17:16, 10 September 2021 (UTC)

Help looking over a Wikidata item

Hi! Would someone be interested in looking at Hayden Bridge (Q107778411) to help check for mistakes/develop the page? Thank you! Best, Tyrone Madera (talk) 18:45, 10 September 2021 (UTC)

Server switch

Read this message in another language • Please help translate to your language

The Wikimedia Foundation tests the switch between its first and secondary data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster. To make sure everything is working, the Wikimedia Technology department needs to do a planned test. This test will show if they can reliably switch from one data centre to the other. It requires many teams to prepare for the test and to be available to fix any unexpected problems.

They will switch all traffic back to the primary data center on Tuesday, 14 September 2021.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

You will be able to read, but not edit, all wikis for a short period of time.

  • You will not be able to edit for up to an hour on Tuesday, 14 September 2021. The test will start at 14:00 UTC (07:00 PDT, 10:00 EDT, 15:00 WEST/BST, 16:00 CEST, 19:30 IST, 23:00 JST, and in New Zealand at 02:00 NZST on Wednesday, 15 September).
  • If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

  • Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
  • We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule. There will be more notifications about this. A banner will be displayed on all wikis 30 minutes before this operation happens. Please share this information with your community.

SGrabarczuk (WMF) (talk) 00:45, 11 September 2021 (UTC)

Talk to the Community Tech

Read this message in another language • Please help translate to your language

Hello!

As we have recently announced, we, the team working on the Community Wishlist Survey, would like to invite you to an online meeting with us. It will take place on September 15th, 23:00 UTC on Zoom, and will last an hour. Click here to join.

Agenda

Format

The meeting will not be recorded or streamed. Notes without attribution will be taken and published on Meta-Wiki. The presentation (first three points in the agenda) will be given in English.

We can answer questions asked in English, French, Polish, and Spanish. If you would like to ask questions in advance, add them on the Community Wishlist Survey talk page or send to [email protected].

Natalia Rodriguez (the Community Tech manager) will be hosting this meeting.

Invitation link

See you! SGrabarczuk (WMF) (talk) 03:03, 11 September 2021 (UTC)

User spamming nudes

User:NudistPhotographer seems to be solely interested in spamming items with photographs that do not add encyclopedic value. As far as I can see, these are all pictures taken by them. (see https://commons.wikimedia.org/wiki/Special:Contributions/NudistPhotographer ) Wikidata is not a photo webhost; perhaps this should be made to stop? -- The Anome (talk) 13:21, 12 September 2021 (UTC)

@The Anome: This may be. But doesn't the topic belong more on Wikimedia Commons? --Gymnicus (talk) 13:36, 12 September 2021 (UTC)

Merge request (José Lemery e Ibarrola)

Hello and good evening. Requesting that José Lémery (Q20581227) be merged with José Lémery (Q11051292) as the entries refer to the same person. Won't attempt to merge them since the process is a bit complicated (conflict between labels and descriptions). -Ianlopez1115 (talk) 14:38, 10 September 2021 (UTC)

→ ← Merged --Matěj Suchánek (talk) 08:44, 13 September 2021 (UTC)

Just in case anyone's bored right now

I've just done some fixes to the Wikidata game to match Wikidata items with Commons categories, and add the sitelinks here (and later, Wikidata infoboxes will be auto-added to the categories!). It should be faster than before, and not give error messages any more. There's currently plenty of tiles queued up and waiting for decisions! Thanks. Mike Peel (talk) 18:34, 10 September 2021 (UTC)

Far from bored, but this is fun! :) It works smoothly. I'll spread the word. Vojtěch Dostál (talk) 19:55, 10 September 2021 (UTC)
@Mike Peel A little idea: I often like to improve items and categories about places near me. It would be cool if you could add filtering by country :). Vojtěch Dostál (talk) 20:54, 12 September 2021 (UTC)
@Vojtěch Dostál: Thanks! tldr: I'll think about it, but unlikely that I'll be able to implement this soon.. Unfortunately, the main cause of it being a little slow at the moment is that it has to check each item for freshness (does the category still exist? does the wikidata item still exist? Has one of them been matched up with a different page in the meantime?), and while I can add in extra filters as part of that process (before, for people/taxons), it gets even slower (has to check more items before listing them). So I'd need to either make the last-minute checks asynchronous, or cache more data in the local database, both of which would be significant changes. Thanks. Mike Peel (talk) 06:36, 13 September 2021 (UTC)

[SIGNIFICANT CHANGE] String Unicode normalization on saving an edit

Hello,

This is an update to our previous announcement about data value normalization when saving edits.

We’d like to announce an additional significant change in this area.

Together with the previously announced normalization of Commons media values, we also implemented Unicode normalization of string values (regardless of data type, i.e. for properties of data type string, external identifier, URL, etc.): they are now always saved in Unicode Normalization Form C (NFC, aka Normalization Form Canonical Composition). Note that, just as for Commons media normalization, this only applies to new edits, and existing data in Wikidata could still be in non-normalized form.

Cheers, Lucas Werkmeister (WMDE) (talk) 12:24, 13 September 2021 (UTC)

Wikidata weekly summary #485

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Upcoming:
      • WikidataCon update: you can now check in the program of the first day of the online conference
      • Transbordados: WikidataCon's preconference for Latin America - September 14, 21 and 28 (21h UTC) - with simultaneous translation for Portuguese and Spanish, via YouTube - set of events to discuss Wikidata and decoloniality, knowledge organization and digital dissemination of collections in Latin America contexts. Join us!
        • 14/09 - Towards a decolonial wiki: overflowing knowledge from the Latin American horizon - speakers: Amanda Jurno (Wiki Movimento Brasil), Bianca Santana (journalist, writer and activist) and Silvia Gutiérrez (El Colégio de México) - watch it in PT-BR / ES
        • 21/09 - The universe of libraries: Wikidata and the multiplication of knowledge potencies - speakers: Lilian Viana (GLAM das Bibliotecas da USP) and Maurício Genta (Wikimedia Argentina e Biblioteca Nacional da Argentina) - watch it in PT-BR / ES
        • 28/09 - Digital collections and Wikidata: organizing a network of knowledge - speakers: Evelin Heidel (a.k.a. Scann; Wikimedistas do Uruguai) and Karen Worcman (Museu da Pessoa) - watch it in PT-BR / ES
      • Demo of the Query Builder live on Twitch and in French by Vigneron, September 14 at 18:00 CEST
    • Ongoing:
      • Data Quality Days - several sessions happened over the past days and more are coming this week. Recordings, slides and notes are linked in the program
    • Past:
      • Forex - 36C3 Wikipaka WG: Live querying: let’s explore Wikidata together! - YouTube
  • Tool of the week
    • Wwwyzzerdd for Wikidata is a browser extension that allows you to view and edit Wikidata information from Wikipedia (demo video). Install it in Firefox or Chrome
  • Other Noteworthy Stuff
    • Face The Facts mobile app allows you to scan election posters and see the true facts about politicians.
    • Wikidata now has over 150,000 Senses on Lexemes!

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.

Interested in participating in a user interview for Toolhub Project?

Hi all! We want to do individual interviews with folks from the Wikidata community to learn how editors discover and use tools. We will then use these results towards Toolhub, a platform to catalog the various software tools used in the Wikimedia movement. Toolhub is going to be launched soon, in a month or so from now. We want Toolhub to have features that meet your needs ultimately. If you are interested in participating in a user interview, please reply to this thread and share a link to a talk page on your preferred language wiki, and we will then follow up with you. Cheers, SSethi (WMF) (talk) 21:16, 13 September 2021 (UTC) (On behalf of the Toolhub team)

Mix'n'match error tag

A Mix'n'match error tag associated to mw-undo should be created. There are a lot of such errors. - Coagulans (talk) 06:52, 14 September 2021 (UTC)


Guidance for checks after upload

At Help:Checks after upload, a list drafted during Data Quality Days.

Most contributors are fairly rigorous and might not need it, but this can help to double check some points.

What do you think of it? --- Jura 09:36, 14 September 2021 (UTC)

I could certainly make use of such a checklist. As a fairly new user I'm possibly in the target audience as well. While reading through the checklist I wondered what it means to check for constraint violations on Query Service. Does it simply mean to read over the item to check for constraint violations, or does it imply some kind of action "on Query Service"? In the latter case a link to a more detailed explanation would be helpful. -- Abuluntu (👨🏼‍💻💬) 09:52, 14 September 2021 (UTC)
  • Good points. The feature is still not quite stabilized AFAIK so there isn't much of a documentation about it. See e.g. phab:T201150.
The constraints reports listed further down will do that more thoroughly. --- Jura 10:57, 14 September 2021 (UTC)

Books

I have my doubts about how to make book items. For example, Orhan Pamuk's book Yeni Hayat is itemized under its English translation " The New Life (Q31720)". Publisher etc belong to the translation, and not to the original one in Turkish. I added a "version, edition, or translation (Q3331189)" as "instance of" but am still confused: TR Wikipedia speaks about the book in Turkish and I guess other WPs speak about the version/s in their own languages. In the "essence" they are all about one same book, but Wikidata "data" should include -I guess- original publication place, language and date, publication in other languages/countries, their dates etc. Am I wrong? Maybe these data exist in other book items, but I took this as an example. Maybe I am talking about things we already have and I ignore or maybe we need some more elements to elaborate book items better. Am I speaking bs (nonsense :)? --E4024 (talk) 15:28, 14 September 2021 (UTC)

Explained at Wikidata:WikiProject Books#Bibliographic properties. Design goal seems to be one item for the work, and one each for editions/publications of the work. --Tagishsimon (talk) 15:39, 14 September 2021 (UTC)

Yet another question concerning splitting video game under the same name in the same serie but with different engine/gameplay

Hello (again)

I've been editing (again) The Legend of Spyro: A New Beginning (Q2578009). This entry concern the four different version of the game : The home console one (those that the people usually refer to when speaking of the legend of spyro), the DS one, the GBA one and the J2ME one. All of those have different gameplay, for example, the J2ME and GBA are 2D side scroller, while DS and home console ones are 3D.

However, they share the same position in the series. currently, I used the property platform (P400) to specify to which version a statement apply, but that seems a pretty bad (and ugly) idea, in particular if someone want to make something based on those data.

On another side, the entry on multiple site (including on The Cutting Room Floor (Q55635148)) use a different page for each version. But that's not the case of Wikipedia, which regroup all of those in the same page (thought they almost exlusively write about the home console version).

Thank - Marius851000 (talk) 06:05, 14 September 2021 (UTC)

Did some research: that has already been discussed at Wikidata_talk:WikiProject_Video_games#Handling_multiple_Minecraft_editions. I guess I'll take a similar approach (thought I risk to end up with series of series of video game Marius851000 (talk) 07:54, 15 September 2021 (UTC)

Help to fix locked item

Wikipedia page of "Assembly language" (Q165436) should link to translation page "ඇසෙම්බ්ලි භාෂාව" instead of "එසෙම්බ්ලි භාෂාව" in Sinhalese language. The page is locked, I can't change it. what should I do? can someone do it for me? --IC9999 (talk) 02:52, 15 September 2021 (UTC)

✓ Done Karl Oblique (talk) 08:07, 15 September 2021 (UTC)

Q108524859 vs Q12798037

Please have a look: Osypenko (Q108524859) vs Osipenko (Q12798037). Thx, HarryNº2 (talk) 05:50, 13 September 2021 (UTC)

They have the same spelling indeed, but different pronunciation. More comment needed from User:Бучач-Львів. --Infovarius (talk) 07:45, 16 September 2021 (UTC)
HarryNº2. Hi! Sorry for google-translate. To the words Infovarius it is also necessary to add that these surnames are written in different alphabets - Ukrainian and Russian, respectively. --Бучач-Львів (talk) 07:56, 16 September 2021 (UTC)
For surnames, we generally just add the script. --- Jura 09:59, 16 September 2021 (UTC)

A few question concerning Wikidata

Hello.

I just started editing wikidata (I mean, in addition of a few small edit I made a while ago). I mainly added credit for dub in The Legend of Spyro: A New Beginning (Q2578009).


1. Is there a recommended way to handle inverse property (P1696) ? This could usually have things that could be automated. For exemple, I both added Cyril (Q108537541) with the property characters (P674) to The Legend of Spyro: A New Beginning (Q2578009) and The Legend of Spyro: A New Beginning (Q2578009) with the property present in work (P1441) to Cyril (Q108537541). In addition, Cyril (Q108537541) is present as character role (P453) of Jeff Bennett (Q311103), voice actor (P725) of The Legend of Spyro: A New Beginning (Q2578009). That quite a bunch of duplicate entry. Is there a recommended way to handle them.

2. All of that made quite a bunch of data... I wonder if there is some simple way to generate a table from it, using wiki syntax (it would probably need some condition and stuff like that). But if I understand correctly, it will be one of the feature of Abstract Wikipedia (Q96807071)... So just need to wait {{Q:Q105576416}} implement this, and I'll probably be able to do something on not wikilambda or self-hosted wikilambda (or write a python script).

3. After some editing, I received welcome notification from many wikipedia. I figured that was because my edit made it to their wikipedia (like [3], where I added the game engine). Just wanted to made sure you are aware of what I consider an issue.

4. Is it okay to put the game as a source for it's dubber, when present in the credit ( via stated in (P248) ) ?

5. Is it okay to use imported from Wikimedia project (P143) when manually imported (I was unable to find official credit, but the french wikipedia give a list of voice actor. They don't have any source, and found conflicting other research on a few actor. I wasn't able to verify or deny these via data-mining either).

6. Is there some tool to make semi-automated edit/faster edit. For example, having to add template model that apply to every character present in the work is a bit long when they are the same for every new one.

Thank -- Marius851000 (talk) 20:55, 13 September 2021 (UTC)

@Marius851000 To answer your questions in order:
  1. I'm not aware of anything that handles this, though someone else might be. Part of the issue is that there are some inverse properties that don't really need copying because they're unbalanced and copying would put a huge number of statements on some items, or because they have a complex situation (such as child (P40), which could have either father (P22) or mother (P25) as its inverse)
  2. If you're making a table, you're going to want to use the query service. If you know SPARQL (Q54871), you can use the interface at https://query.wikidata.org; if you don't, you can follow the button at the top to the brand-new query builder. If you want to have the results on a continuously-updated wiki-page, you can check out User:ListeriaBot.
  3. Yes, that's typical.
  4. Yes, assuming that the information is verifiable by looking at the game itself (e.g. it's in the credits)
  5. Yes, though it's not good practice. If you have conflicting information from multiple sources, you can indicate this with the ranking system with appropriate qualifiers.
  6. QuickStatements is commonly used for semi-automated editing. If you know the edits you're going to make, you should be able to translate them into the QuickStatements input format, which handles the API mechanics of actually making the edits. Vahurzpu (talk) 00:38, 14 September 2021 (UTC)

Power outages documented?

If an area has a bunch of people who get affected by power outages do the outages and the length of time of the outages get added on Wikidata or does an invidiual interested in this start their own Wikibase instance and run it privately? Oduci (talk) 14:06, 15 September 2021 (UTC)

This looks like quite complex dataset. Every year, there will be a new number for each region. Additionally, you could have several data values each month, for example: 30% of inhabitants of region A had power outage for 2 days or more, 15% of inhabitants had outage for 1 day or more... Therefore, in my humble opinion, it's better to store this data elsewhere, such as in Tabular Data on Commons Vojtěch Dostál (talk) 13:12, 16 September 2021 (UTC)

Inappropriate alias?

Could you read this thread, please? Do you think that "Prince Firouz Nosrat-ed-Dowleh III" is a valid alias or not? Thanks. Emijrp (talk) 17:57, 15 September 2021 (UTC)

That must be some misunderstanding... A simple search for "Prince" returns >37,000 results. And while there are many where it's not a person's label on the first pages, it quickly turns into a *Who's Who* of European Royalty. My SPARQL attempts keep timing out with more a LIMIT > 5000, but I'd estimate there is a 6-digit number of labels and aliases that include *Prince*, and we haven't even started with the Viceroys. Apart from the normative power of the factual, it just makes sense to include the title when it is commonly used when referring to the person. A random article about the royal family I just found includes the title when the name is first mentioned, in image captions, and in tabular data. For someone such as Queen Elizabeth, The Queen Mother (Q10633), little is left of their commonly-used label/name if you take out all titles. "Elizabeth The"? Karl Oblique (talk) 20:08, 15 September 2021 (UTC)
Any string (subject to BLP considerations) that reasonably might be supposed to be used to refer to an items subject, should be considered valid as an alias, since the purpose of the alias is to facilitate discovery of the item from such strings. I note the thread Emijrp pointed to: the OP there has notions about what is & is not a proper, valid alias, built on preconceptions rather than on any evidence of understanding the functions of aliases in the WD environment. --Tagishsimon (talk) 20:22, 15 September 2021 (UTC)

[notification] All village of Taiwan is imported from Taiwan government dataset

Hi all, all village (Q7930614) in Taiwan (Q865) including the future one, which use Code of Household Registration and Conscription Information System (Taiwan) (P5020) is all on Wikidata. Some Wikidata Taiwan (Q65555605) member linked Village item to Taiwanese indigenous peoples (Q216839) Q55747241. Maybe some duplicated item still not merged due to someone imported from Chinese Wikipedia, the other one imported from government dataset. Maybe some day will deal with the abolished village which exist before digital record document, like 大豐里, 麗山里 Nangang District (Q271073), Taipei (Q1867). Supaplex (talk) 10:08, 16 September 2021 (UTC)

Discourage adding descriptions to scientific articles?

Hi, I just saw this QS batch. It adds descriptions to a number of scientific articles in ast. This increases the number of triples BlazeGraph (BG) has to handle while adding no knowledge at all. Given our current situation with bots being opposed (see 1) despite them adding actual knowledge to the graph I think we should either discourage this kind of batches or simply exclude the descriptions from WDQS at this point to lower the total number of triples BG has to handle until a replacement is in place. WDYT?--So9q (talk) 09:40, 15 September 2021 (UTC)

  • I don't think we should restrict our editorial efforts because of such technical constraints. If the infrastructure is not capable enough to handle the load, WMF/WMDE should invest some money and make it fit; in order to do so, there needs to be some pressure sometimes… :-) —MisterSynergy (talk) 10:33, 15 September 2021 (UTC)
Still, it's such a waste. Why not simply browser-display the P31 value in the resp. language as description whenever it is not set? --SCIdude (talk) 15:19, 15 September 2021 (UTC)
BTW. I'm curious as to how well optimised the wikibase use is on mediawiki. Some entities appears to get prefetched, does this include «Cite Q» citations as well? Or is it just the entities that are linked via sitelinks that get prefetched? And how does the software identify what to prefetch? --Infrastruktur wdt:P31 wd:Q5 (T | C) 11:50, 15 September 2021 (UTC)
lots of QS edits add (close to) zero knowledge. it's hard to draw a line to decide which are worthless. Should we stop this current running job: https://quickstatements.toolforge.org/#/batch/64277 ? BrokenSegue (talk) 16:06, 15 September 2021 (UTC)
Just because it's hard to draw a line in any continuous value doesn't mean you cannot say anything about the extremes. Example: we cannot say which exact grain of sand makes it a beach. But we can say it's not a (sand) beach when there is absolutely no sand, and it definitely is such a beach if all you see is water, sky, and sand. If someone were to, say, add and remove the same statement from the same entity over and over again, in multiple independent QS sessions, I'm sure there would be little disagreement to nicely asking them to find a new hobby. The above isn't that, and blocking well-intentioned contributions sounds like bad policy. But, maybe, one could nudge people to more meaningful endeavours. It isn't just server time that's wasted, it's the contributors' as well. One idea would be to either just hide edit counts beyond what's needed to categorise users into three or four experience levels. Or, maybe, there are alternative measures that include some notion of the usefulness by, for example, giving more gold starts for rarely-used properties. Or adding up the contributions' cumulative improvement in that item score I saw somewhere (Recoin?). Karl Oblique (talk) 20:24, 15 September 2021 (UTC)
What exactly is your point, Karl Oblique? --Succu (talk) 20:55, 15 September 2021 (UTC)
It shouldn't be *banned*, but discouraged. If people are motivated by their stats (possibly a wrong assumption on my part), changing the stats offered to better align with project interests might work. And as far as I can tell, the performance problems couldn't be immediately solved even if money were no concern. Therefore, and also just by general principle, the attitude of actively not caring about performance problems, or even welcoming them to create pressure, is surprising. Karl Oblique (talk) 21:41, 15 September 2021 (UTC)
I see no evidence people do this to up their edit count. It is very hard to make a rule about what we should be adding and what we shouldn't. BrokenSegue (talk) 22:21, 15 September 2021 (UTC)
I think it would be good to abolish the batch tool. Too many false information is added by those batches and most of it probably will never get corrected. It is also a great mistake multiplier. E.g. many Korean names items on wikidata are wrong. Most Korean names are gender neutral. Only a few have an associated gender. However, on wikidata, many of those actually unisex names are either categorized as female or male name. So, sometimes batches are running that at a gender to items of people that carry the name. And by this, some men become women on wikidata while some women become men. The mistakes only become more and a bot or batch cannot correct all these mistakes. Those batches lead to more mistakes and thus more work for real people. But the amount of mistakes is already so big, even when getting rid of those batches and have active users trying to fix it, it will take decades. --Christian140 (talk) 06:23, 16 September 2021 (UTC)
abolishing the batch tool is going too far. there's lots of good uses of it. I argue we just need to require references for things added with it. If someone adds a gender based on a first name we can later know that it was done incorrectly and undo it. or at the very least know not to trust it. BrokenSegue (talk) 18:53, 16 September 2021 (UTC)
Given the current systems, I suppose there isn't really a way around it.
I do find the label in "ast" (copy of "en") more problematic. --- Jura 10:03, 16 September 2021 (UTC)

Item fix request

Is there someone that can kindly change official website (P856) from http://www.femexfut.org.mx/#/ to https://fmf.mx/ on Mexico men's national football team (Q164089)? Many thanks in advance!!! --93.34.225.13 16:26, 16 September 2021 (UTC)

Hello!

On behalf of the Wikimedia Foundation's Legal department, I am asking for input on our current process for handling BLP-related requests that are sent by email to privacy@wikidata.org.

I have asked on the talk page of the BLP policy.

I do not think this question quite qualifies as an RFC or an administrator's noticeboard post, but please spread the word to anyone who may be interested in the matter. Thank you! BChoo (WMF) (talk) 22:02, 16 September 2021 (UTC)

Middle initial property?

Hi. If there's a person whose middle initial is known but not their middle name, is there a property that should be used to store the initial? Thanks DemonDays64 | Talk to me 00:24, 17 September 2021 (UTC) (please ping on reply)

Duplicate?

Is Q29383381 a duplicate of Q58398507? Or do they both serve a different purpose? --Mbrickn (talk) 20:22, 16 September 2021 (UTC)

I was almost completely certain that they should be merged, but found Talk:Q4167836#Usage and, after checking, found a great many of such corresponding pairs of items. They are linked via category's main topic (P301) and topic's main category (P910). I believe commons categories were moved into the items at some point, connected by Commons category (P373)? Categories, and maybe lists as well, would seem to work well as a second (/third) set of sitelinks. But whoever came up with the status quo probably spend more time thinking about it, and there's some snag I'm missing. Karl Oblique (talk) 21:55, 16 September 2021 (UTC)
I think they can be merged in this case. The zh sitelink should be on the main item, and a separate category item isn't required when there's only a Commons cat. Ghouston (talk) 10:38, 17 September 2021 (UTC)

Item fix request

Is there someone that can kindly change official website (P856) from http://www.femexfut.org.mx/#/ to https://fmf.mx/ on Mexico men's national football team (Q164089)? Many thanks in advance!!! --2001:B07:6442:8903:A98F:701C:9EEA:74D1 15:30, 17 September 2021 (UTC)

Done. --Tagishsimon (talk) 19:25, 17 September 2021 (UTC)

Geocoordinates

For Agen Warehouse (Q28035251), the geocoordinates are sourced from en-wiki (which has them correct) but when I use the coordinates from Wikidata they are off by several blocks. Is there a way to fix this, or are geocoordinates in Wikidata only accurate to some small number of decimal places? (Please ping me if responding, I'm rarely on Wikidata these days.) - Jmabel (talk) 18:51, 17 September 2021 (UTC)

@Jmabel: Both WD and WP coordinates seemed to resolve to the same place for me, both in terms of the parameters listed on the geohack page, and the pushpin on ACME mapper. WD coordinates are stored with a precision value, the use or effects of which I'm not familiar. In my experience P625 values default to Precision: ±0.00001° but in the case of Agen Warehouse (Q28035251), the precision was specified at, from memory, ±0.015° ish. Long story short, I've deleted the existing coords and added them again to ±0.00001° precision. Does this solve the issue you see? --Tagishsimon (talk) 19:22, 17 September 2021 (UTC)
@Tagishsimon: Yes. So it was simply a matter of someone (User:GZWDer (flood)) explicitly stating an insufficient precision. Got it. - Jmabel (talk) 22:16, 17 September 2021 (UTC)
And that's apparently a bot. I wonder why it assumed such a low precision? - Jmabel (talk) 22:17, 17 September 2021 (UTC)

Q108571821, “items on Wikidata” option does not appear in the article sidebar.

Why Q108571821 in IDWP, the “items on Wikidata” option does not appear in the article sidebar? --NengDorla (talk) 22:59, 17 September 2021 (UTC)

Possibly a cache issue somewhere. The link is there now. --Tagishsimon (talk) 23:17, 17 September 2021 (UTC)

Not sure whether to merge two items

There are two items, Template:Incomplete (Q5873067) and Template:Incomplete (Q17392254), which I'm not sure whether to merge. They seem to be items for the same template, and I know s:es:Plantilla:Incompleto (linked to Template:Incomplete (Q5873067)) has the same functionality as s:en:Template:Incomplete (linked to Template:Incomplete (Q17392254)), but there are also some cases of duplication, e.g. b:zh:Template:Incomplete and b:zh:Template:未完成. —CalendulaAsteraceae (talk | contribs) 23:39, 17 September 2021 (UTC)

Capitalization of common names of organisms

Is there a policy somewhere on recording common names of animals, plants, and other organisms in labels? I ask because there is a wide divergence of practice, and when I recently changed some labels to remove uppercase, one insistent editor reverted all of my changes. Commonly used style manuals in English say not to capitalize common/vernacular names of organisms unless there is a proper noun in the name.

For example, The Chicago Manual of Style says:

For the correct capitalization and spelling of common names of plants and animals, consult a dictionary or the authoritative guides to nomenclature, the ICN and the ICZN, mentioned in 8.119. In general, Chicago recommends capitalizing only proper nouns and adjectives, as in the following examples, which conform to Merriam-Webster's Collegiate Dictionary: 

  Dutchman's-breeches
  jack-in-the-pulpit
  mayapple
  Cooper's hawk
  rhesus monkey
  Rocky Mountain sheep

The International Committee on Taxonomy of Viruses (ICTV) says: The first letters of words in a virus name, including the first word, should only begin with a capital when these words are proper nouns (including host genus names but not virus genus names) or start a sentence. Single letters in virus names, including alphanumerical strain designations, may be capitalized. ... Examples: 

  Isolates of dengue virus 2 were obtained ....
  Detection of West Nile virus in human serum ....
  Salmonella phage SE1 was isolated ....
  Sida ciliaris golden mosaic virus (SCGMV) causes ....
  Aphids transmit potato virus Y (PVY)

Numerous other websites for English names give the same advice, for example https://www.dailywritingtips.com/when-to-capitalize-animal-and-plant-names/, https://projects.ncsu.edu/cals/course/zo150/mozley/nomencla.html, https://mostlybirds.wordpress.com/2015/12/09/should-common-names-of-species-be-capitalized/, and https://grammar.yourdictionary.com/capitalization/capitalization-of-animal-names.html.

Is there, or could/should there be a written policy on capitalization of common names? UWashPrincipalCataloger (talk) 21:24, 17 September 2021 (UTC)

This is a common mistake by German-language people that think they have a good grasp on English (I'm one myself but I think I've passed this lesson). --SCIdude (talk) 09:41, 18 September 2021 (UTC)

linking airplane crashes to victims

Do we have a way to link airplane crashes to victims? plane crash near Formia of April 30, 1938 (Q108595147) had Jakob Friedrich Bollschweiler (Q1679021), Xhafer Villa (Q29863774) and Othmar Krainz (Q55684069) and others among its victims, but I couldn’t find a good way to link them. I know that there are still many modeling problems for death, but maybe there’s some sort of workaround until we resolve those? --Emu (talk) 21:41, 18 September 2021 (UTC)

participant (P710) and victim(s) (P8032) are both used:
Query: 
SELECT ?instance_of_aircraft_crash ?instance_of_aircraft_crashLabel ?property ?propertyLabel ?person
{
  ?instance_of_aircraft_crash ?p ?person.
  ?property wikibase:directClaim ?p .
  ?instance_of_aircraft_crash wdt:P31/wdt:P279* wd:Q3002150 .
  ?person wdt:P31 wd:Q5 .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" . }
}
Try it!
Also different ways are used link the victim to the airplane crash. The most common are
Query: 
SELECT ?person  ?property ?propertyLabel ?qualifier ?qualifierLabel ?instance_of_aircraft_crash ?instance_of_aircraft_crashLabel
{
  ?person wdt:P31 wd:Q5 .
  ?person ?p ?statement .
  ?statement ?pq ?instance_of_aircraft_crash .
  ?property wikibase:claim ?p .
  ?qualifier wikibase:qualifier ?pq .
  ?instance_of_aircraft_crash wdt:P31/wdt:P279* wd:Q3002150 .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" . }
}
Try it!
and
Query: 
SELECT ?person  ?property ?propertyLabel ?instance_of_aircraft_crash ?instance_of_aircraft_crashLabel
{
  ?person wdt:P31 wd:Q5 .
  ?person ?p ?instance_of_aircraft_crash .
  ?property wikibase:directClaim ?p .
  ?instance_of_aircraft_crash wdt:P31/wdt:P279* wd:Q3002150 .
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" . }
}
Try it!
I cannot say what is best or recommended. --Dipsacus fullonum (talk) 01:17, 19 September 2021 (UTC)
Thank you, that helped a lot! --Emu (talk) 10:27, 19 September 2021 (UTC)

Merge Syzygy pages Syzygy (Q54364) and Syzygie (Q2377241)

Syzygy (Q54364) and Syzygie (Q2377241) should both refer to the same disambiguation pages. A possible conflict is that they both have a different Wikipedia entry in Deutsch:

- Syzygy (Q54364) refers to https://de.wikipedia.org/wiki/Syzygy while

- Syzygie (Q2377241) refers to https://de.wikipedia.org/wiki/Syzygie

The correct Deutsch translation is Syzygie. 92.136.171.9 14:06, 19 September 2021 (UTC)

  • It's a Wikidata item for disambiguation pages of Wikipedia versions with a given title.
No translation is actually being done.
See Wikidata:WikiProject Disambiguation pages/guidelines for details. --- Jura 14:17, 19 September 2021 (UTC)
My remark on the translation was solely meant to advise on the compatibility conflict. « Disambiguation items in Wikidata exist only to provide interlanguage links »: this is exactly the problem here as the interlanguage link of the disambiguation pages are incorrect/missing. 92.136.171.9 15:28, 19 September 2021 (UTC)
The two items don't refer to the same disambiguation pages.
If you have a look at Wikidata:WikiProject Disambiguation pages/guidelines, you will notice that Q54364 needs some fixes to follow it.
If Wikipedia should display other interwiki links, this needs to be resolved at Wikipedia. They can do that based on said to be the same as (P460) statements. --- Jura 15:33, 19 September 2021 (UTC)

Züleyha Tan (Q19950682)

Alguién con toda buena voluntad pero poca atención hizo su art en ES:WP como Züleyhan Tan (sic). Su nombre es Züleyha Tan (Q19950682). Como me expulsaron de esa Wikipedia por solo demostrar sus errores -aunque con otro pretexto- yo no lo puedo cambiar. ES:WP no me interesa mucho, pero la gente de mi querido país, Turquía, sí. Gracias de antemano. --E4024 (talk) 15:53, 17 September 2021 (UTC)

✓ Done, E4024. I moved it to Züleyha Tan.--Esp1986 (talk) 16:21, 19 September 2021 (UTC)
Muchas gracias Esp1986! (Note: Muchas gracias means thank you very much; in Spanish.) Saludos cordiales. --E4024 (talk) 22:18, 19 September 2021 (UTC)

Is there a way to get the total number of references to a website on Wikidata? (Query service times out)

Hi all

I'm encouraging an organisation to share data on Wikidata, they have a huge amount of data which could be really useful. I want to collect some metrics for them before and after on how many references there are on Wikidata to their website. NavinoEvans has tried to make Wikidata queries for it but it just times out.

I've also tried using the same trick I use on Wikipedia which uses a search tool here.

Does anyone know of any other approaches we could use or if I'm doing something wrong? I just want a count of all the references on Wikidata to WIPO.int

Thanks very much

--John Cummings (talk) 15:51, 16 September 2021 (UTC)

@John Cummings: You can use the list=exturlusage (eu) API call to list all items (i.e. pages in namespace 0) with links to the website. It lists all different URLs to the website from each item, but it doesn't tell how many links there is from each item to the same URL. Neither does it tell if the link is from a reference, qualifier or statement value.
If the number of results is less than 10.000, you can get the count with a SPARQL query using MWAPI.
You can also make same search from the special page Special:LinkSearch. Dipsacus fullonum (talk) 20:23, 16 September 2021 (UTC)
@Dipsacus fullonum: Would you mind putting together an illustrative SPARQL query using MWAPI, Df? I think we have too few examples SPARQL/MWAPI examples to study, & I'm afraid I find the documentation opaque. thx. --Tagishsimon (talk) 20:28, 16 September 2021 (UTC)
Dipsacus fullonum thanks very much, I don't have a technical background so I don't understand how to use these tools, I tried using Special:LinkSearch before but what works on Wikipedia (linked above) doesn't work on Wikidata, would you be able to create the search term for wipo.int and I'll write some instructions somewhere so people can do it in future? John Cummings (talk) 21:43, 16 September 2021 (UTC)
@John Cummings, Tagishsimon: John, you linked to a normal search (Special:Search using CirrusSearch), not to Special:LinkSearch which works fine for Wikidata items. Here is a query finding statements in items that have references containing URLs to wipo.int. I only included the http and https protocols, but other protocols can be added by adding more MWAPI calls to the SPARQL UNION. The query will give incomplete results for websites where the API calls would give more 10.000 results. 
# Find item statements with references containing external links to wipo.int using http and https protocols
SELECT ?item ?itemLabel ?property ?propertyLabel ?value ?valueLabel ?reference_URL
WITH
{
  SELECT DISTINCT ?item
  WHERE
  {
    {
      # Find items with https URLs
      SERVICE wikibase:mwapi
      {
        bd:serviceParam wikibase:endpoint "www.wikidata.org" .
        bd:serviceParam wikibase:api "Generator" .
        bd:serviceParam mwapi:generator "exturlusage" .
        bd:serviceParam mwapi:geuprop "title" .
        bd:serviceParam mwapi:geunamespace "0" .
        bd:serviceParam mwapi:geuprotocol "https" .
        bd:serviceParam mwapi:geuquery "*.wipo.int" .
        bd:serviceParam mwapi:geulimit "max" .
        ?item wikibase:apiOutputItem mwapi:title .
      }
    }
    UNION
    {
      # Find items with http URLs
      SERVICE wikibase:mwapi
      {
        bd:serviceParam wikibase:endpoint "www.wikidata.org" .
        bd:serviceParam wikibase:api "Generator" .
        bd:serviceParam mwapi:generator "exturlusage" .
        bd:serviceParam mwapi:geuprop "title" .
        bd:serviceParam mwapi:geunamespace "0" .
        bd:serviceParam mwapi:geuprotocol "http" .
        bd:serviceParam mwapi:geuquery "*.wipo.int" .
        bd:serviceParam mwapi:geulimit "max" .
        ?item wikibase:apiOutputItem mwapi:title .
      }
    }
  }
} AS %get_items
WHERE
{
  INCLUDE %get_items
  ?item ?prop ?statement .
  ?property wikibase:claim ?prop .
  ?property wikibase:statementProperty ?ps .
  ?statement ?ps ?value .
  ?statement prov:wasDerivedFrom ?reference .
  ?reference ?refprop ?reference_URL .
  FILTER CONTAINS(STR(?reference_URL), "wipo.int/")
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" . }
}
Try it!
--Dipsacus fullonum (talk) 07:50, 17 September 2021 (UTC)
Update: I changed the query, moving the MWAPI service calls to a named subquery using the DISTINCT modifier in order to get each statement only once. --Dipsacus fullonum (talk) 09:57, 17 September 2021 (UTC)
Very nice! I agree with @Tagishsimon: that the mwapi documentation is lacking. A while back I created a section for illustrative queries at Wikidata:SPARQL_query_service/queries/examples/advanced#Mediawiki_API. --Azertus (talk) 17:18, 17 September 2021 (UTC)
I wrote some documentation and explanation for reference searching in Wikidata:SPARQL_query_service/query_optimization#A_query_that_has_difficulties. --Lockal (talk) 07:40, 20 September 2021 (UTC)

How to improve precision of dates (sample: died 20th century)

Please see Help_talk:Dates#How_to_improve_precision_of_dates. --- Jura 08:31, 20 September 2021 (UTC)

Is not being able to see or query labels of deleted items a problem?

I dive in and out of editing Wikidata as a user, and recently came across some entities that I wanted to check to see if they had existed before. My thinking was that perhaps a user had created them, they got deleted for some reason at some point, potentially the user blocked and then later down the line a new user recreated them. Is there any existing tooling around this problem? Is this a problem? Or am I just imagining thing? ·addshore· talk to me! 19:51, 13 September 2021 (UTC)

@Addshore: It is a bit of a problem, compared to the language wikipedias where the "label" is also the way the deleted item is identified. Wikidata can't do that obviously since our item identifiers are not labels. I believe admins often add a label to their message when deleting, but I don't think there's any tooling around it. Might be useful, yes. ArthurPSmith (talk) 16:57, 14 September 2021 (UTC)
Depending on the admin deleting it (or the script the admin is using?), this is visible on the deletion log. At least for items one creates, this is sufficient. --- Jura 10:01, 16 September 2021 (UTC)
This idea came to my mind once in the past. Indeed, there is no way (known to me) to search for data of deleted items (in fact, any wiki pages in general). --Matěj Suchánek (talk) 16:10, 16 September 2021 (UTC)
Yeah, I don't think there is any way of doing this right now. In the future it might be possible to generate a dataset every now an again that could be helpful though. If this becomes available I'll have a play around and see what I can come up with. ·addshore· talk to me! 10:03, 20 September 2021 (UTC)

Item fix request

Is there someone that can kindly change official website (P856) from http://www.femexfut.org.mx/#/ to https://fmf.mx/ on Mexico men's national football team (Q164089)? Many thanks in advance!!! --2001:B07:6442:8903:7824:6311:54B2:93FD 07:14, 17 September 2021 (UTC)

Looks like User:Tagishsimon took care of it for you. ArthurPSmith (talk) 16:43, 20 September 2021 (UTC)

Wikidata weekly summary #486

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Press, articles, blog posts, videos
    • Videos
      • Mapping the Scottish Reformation - using Wikidata, Wikipedia's sister project - YouTube
      • OpenSym 2021: WDProp: Web Application to Analyse Multilingual Aspects of Wikidata Properties - YouTube
      • Wikipedia Weekly Network - LIVE Wikidata editing #53 (user scripts and gadgets that can help you edit) - YouTube


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.

Merge

Q6408072 and Q55616660 are same. please Merging these page. thanks.M.Nadian (talk) 10:00, 23 September 2021 (UTC)

done BrokenSegue (talk) 14:12, 23 September 2021 (UTC)

Change request

Can someone please change the szlwiki link in Q54181 to "Ślōnske wojewōdztwo" and in Q54171 to "Ôpolske wojewōdztwo"? The current pages connected to it are redirects. --Jowomgodom (talk) 19:04, 25 September 2021 (UTC)

✓ Done--Ymblanter (talk) 19:35, 25 September 2021 (UTC)

New Streaming Updater for Wikidata Query Service in production 18 Oct 2021

Hello all,

Thank you again for your all recent thoughts and feedback with regard to the recent Wikidata: Query Service (WDQS) scaling update Aug 2021, and for everyone who has responded to the WDQS user survey. As part of our ongoing work to scale WDQS, we will begin shipping the new Flink-based Streaming Updater from test servers to production on 11 October 2021, with the entire data transfer process expected to finish by 18 October 2021.

The primary goal of this new Streaming Updater is to reduce update lag, and throttling, of edits to Wikidata: going from an average of 10 edits/second to an average of 88 edits/second. We are excited that this is almost a 9x improvement in our ability to make sure that Wikidata Query Service has the freshest updates from Wikidata, a priority that many of you ranked highly in the recent survey. Additionally, the new update process will lessen the impact on Blazegraph itself by moving diff reconciliation away from the service. This update process will be more stable as a result, with more use cases like un/deletes handled correctly.

In order to minimize risks of failure during the rollout of the Streaming Updater, we will be moving individual servers over one at a time. During the anticipated 7 days this data transfer process will happen (11-18 Oct), it is possible that some users will see inconsistent behavior or other bugs while querying. While we encourage these bugs to be filed, please note that it may be difficult for the Search team to accurately diagnose the source of these errors due to the nature of the process. We hope for a seamless transfer, of course, in which users will not notice any errors during the switchover.

We previously announced the new Streaming Updater being released to test servers in March 2021; the changes announced there will now be effective for all WDQS users effective 18 Oct 2021.

The changes that allow the new Streaming Updater to reduce update lag comes with two notable changes, which have the potential to break current usage and workflows:

  1. Blank nodes in Wikidata have been skolemized. From a user perspective, (1) queries using isBlank() will need to be rewritten; (2) queries using isIRI/isURI will need to be verified; (3) WDQS results will no longer include blank nodes.
  2. Constraint Fetching -- specifically wikibase:hasViolationForConstraint -- will be temporarily disabled until we are able to expose constraint violations in a more production-ready way.

For more details on these changes, please refer again to our prior announcement.

We find it encouraging that the new Streaming Updater has not caused major relevant issues in the last six months while it has been on https://query-preview.wikidata.org/. We understand these changes may not be optimal for everyone. However, we believe the ability to greatly reduce Wikidata’s edit lag will be a beneficial improvement for all editors.

We’re excited to ship the new Flink-based Streaming Updater to production, and believe this is a significant step in scaling Wikidata and WDQS. As always, we encourage you to report technical problems and/or leave general comments/feedback here in Project Chat.

Best, WMF Search & WMDE – The preceding unsigned comment was added by MPham (WMF) (talk • contribs).

Owen Pierce Thompson at Wikipedia

Should w:Owen Pierce Thompson be fast deleted without debate? --RAN (talk) 12:22, 20 September 2021 (UTC)

That is no concern for Wikidata. Please keep Wikipedia discussions at Wikipedia. --Dipsacus fullonum (talk) 13:10, 20 September 2021 (UTC)
Deletion from English Wikipedia usually ends up with deletion from Wikidata, so a concern for me. --RAN (talk) 13:26, 20 September 2021 (UTC)
In this case, I don't think the item should be deleted. If it does, you should complain loudly, because it seems to be well-linked to other items, has a Commons category and several interesting identifiers. Vojtěch Dostál (talk) 13:33, 20 September 2021 (UTC)
Q7114601 shouldn't be problematic. --- Jura 13:40, 20 September 2021 (UTC)
I "converted" the obituary available at Commons to statements. Not sure though what's the best way to quote it though. Probably make an item for it and use that. --- Jura 14:49, 21 September 2021 (UTC)

F-droid Wikidata project? - Can I add similar applications to Vanilla Music (Q104403685) from the F-Droid repository?

Can I add similar applications to Vanilla Music (Q104403685) from the F-Droid repository?(I noticed no Wikidata items linking to it other than a list about games though I know Vanilla Music is not a game, it's a music player).

If yes, I might want to add(in no particular order):

  • "Raag", music player
  • "Music Player GO"
  • "Apollo", music player
  • "Simple Music Player"
  • "Odyssey Music Player"
  • "Auxio", music player
  • "BlackHole", music player
  • "Finamp", music player
  • "Odeon", music player

I did not find any of these in Wikidata. Also who here is interested in adding data related to F-Droid apps or knows any Wikidata project related to either F-Droid or Android apps? Oduci (talk) 19:24, 21 September 2021 (UTC)

@Oduci: those all seem like fine additions to wikidata. BrokenSegue (talk) 19:51, 21 September 2021 (UTC)

P26 (spouse) and preferred rank and no value

If I currently query WDQS for the spouse (P26) of Brad Pitt (Q35332), I will get two results. However, Brad Pitt is divorced and NOT married at the moment. Therefore, the query should return zero results. In my opinion, there should be another spouse with 'no value' and preferred rank. That way, all the information is there and the aforementioned query gives the correct result (namely, that Brad Pitt is not currently married). After manually checking some items it seems to me that it is not currently handled like this. The problem occurs with other items in the same way. The spouse property seems to mean 'everybody who this person was ever married to', even for truthy/direct Wikidata. Can anybody please explain why it is not handled the way I propose? --Graue70 (talk) 13:59, 17 September 2021 (UTC)

I tend to agree that the item is missing a spouse of <no value> which is of preferred rank. I've done the same for the heritage designation of items that have had a heritage listing removed: normal rank with start and end dates for the listing claim, preferred rank for <no value> with a start time, such that a truthy query yields the currently valid result. --Tagishsimon (talk) 14:03, 17 September 2021 (UTC)
I see a problem with using "no value" for spouse. How will you prove the statement? A person could have gotten married in secret, and how to prove that it didn't happen? It is more reliably to just see that no statements for spouse have time qualifiers for the present time, and then conclude that noting is known about the present state. Dipsacus fullonum (talk) 15:04, 17 September 2021 (UTC)
Perhaps. Claims with no reference are what they are; users can rely on them to the extent they wish. They're suboptimal, but so too is a query result which suggests a truth which is false. For spouse, there may well be sources that explicity state the subject is single; and if not, then a reference inferred from (P3452), for instance, inferred from timeline of events (Q81204096), will throw some more light on the situation. Meanwhile, many statements are friable, and just as we do not know the subject has not got himself remarried in secret, nor do we know one way or another whether the the status of millions of other claims might without our knowledge have changed. --Tagishsimon (talk) 15:28, 17 September 2021 (UTC)
You do have a valid point. But using ranks may also give unexpected query results. Many of the questions in Wikidata:Request a query over time have been from users who didn't get the results they excepted because they didn't consider ranks (usually using the wdt: prefix when they really wanted all non-deprecated values). Dipsacus fullonum (talk) 15:47, 17 September 2021 (UTC)
By the way, is the current marriage status of a person really more important than previous values? If you have been married for a number of years but are no longer, does it not say as much about the person as the current single status? I have no particular objections to a "no value" value, but do not think it should have preferred rank. Dipsacus fullonum (talk) 16:31, 17 September 2021 (UTC)
Just a note: setting any current value (or "no value") as a "preferred rank" could have the unfortunate effect of excluding all "normal-ranked" values (e.g. spouses) from queries (according to Help talk:Ranking#Rank_and_sparql), and infoboxes such as Template:Infobox Wikidata (Q108290953) (deployed on millions of Wikimedia Commons categories). Granted, this latter may be more of a problem with Commons than Wikidata, and the Wikidata Infobox template has plenty of problems, but if queries or infoboxes only provide highest ranked values, then care should be taken to ensure other data isn't needlessly hidden, such as the many husbands of Elizabeth Taylor (Q34851). -Animalparty (talk) 20:27, 17 September 2021 (UTC)
Sure, but ideally the care will be taken by template authors looking at p:/ps: property paths rather than wdt: paths, if they want all the values. I guess it comes down to whether or not we think a currently true value should be awarded preferred rank when other historic values exist at normal rank, such that truthy=contemporary --Tagishsimon (talk) 20:39, 17 September 2021 (UTC)
Please do not use no value for a property that contains other values. This is never correct. --Quesotiotyo (talk) 21:41, 17 September 2021 (UTC)
It can be correct with appropriate qualifiers for when "no value" is valid. Dipsacus fullonum (talk) 21:46, 17 September 2021 (UTC)
Could you please point to an example? I am unable to think of any case where this would be appropriate. --Quesotiotyo (talk) 22:30, 17 September 2021 (UTC)
If a person was married to person A from 2003 to 2007, was single from 2007 to 2011, was married to person B from 2011 to 2020, and is single from 2020 to now, you could have the statements:
to give a complete picture of the person. However I think they would all be equally important to the description of the person so I wouldn't give the any of them preferred rank. If someone wants to know the current spouse, they should query for statements without a end time (P582) qualifier. Dipsacus fullonum (talk) 05:24, 18 September 2021 (UTC)
While I do not believe that this was the original intent of no value (see mw:Wikibase/DataModel#PropertyNoValueSnak and the last comment at Wikidata:Project_chat/Archive/2017/01#Never_married_persons), it does indeed seem to be the best way to model a definitive negative value for a specified subset. I also realized that it might be necessary to use both no value along with another value when modeling conflicting sources, e.g. if some sources state that a person was never married in his or her lifetime but other sources indicate that the person was married at some point. I retract my claim about it never being correct, so long as the no value statement is differentiated by either a qualifier or ranking and that there is a source attached which definitively states the negation.
--Quesotiotyo (talk) 18:12, 18 September 2021 (UTC)
This speaks to a fundamental unresolved (and probably unsolvable) philosophical question of Wikidata: when does it ever end? In theory, items can never stop accumulating data, as statements can be endlessly added, refined, and subdivided to reflect status and attributes at any identifiable point in time (e.g. number of children on 1 Jan 1900 = 1. Number of children on 2 Jan 1900, also = 1. Number of children on 1 Jan 1901= 2. But following a death the following week, Number of children on 10 Jan 1901= 1, etc. ad infinitum). In practical terms, well, what's practical for the pedant is impractical cruft for the common user. A discussion about the "end game" or future utility of Wikidata (will it be a place accessible to humans or just robots?) needs to be had elsewhere. -Animalparty (talk) 22:18, 18 September 2021 (UTC)
  • spouse (P26) has some specific aspects other properties may not have:
    • It may be desirable to differentiate living people from others.
    • The information may not be available for living people. So the presence or absence of P26 might not be that useful.
    • Once a person is dead, preferred rank isn't of much use.
    • In general, "no value" is more useful for deceased persons as it's easier to make a definite statement.
    • I suppose we could have a statement: Brad Pitt (Q35332) P26 = no value, qualified with point in time (P585) = 1999 using a reference: "10 most [..] bachelors of the year 1999".
--- Jura 14:02, 19 September 2021 (UTC)
I suppose if someone is really ambitious and into tedious cruft, one could make a bot that goes and adds "no value" of spouse to every human who died before the age of 1. How about that? That would be technically true (save for perhaps some odd instances where an infant is culturally married before they can walk), but functionally redundant and meaningless. One could also add number of children (P1971) = 0 and occupation (P106) ="no value" to every dead baby in royal genealogies. One could also indicate that Hammurabi (Q36359) has "no value" for LinkedIn personal profile ID (P6634), as well as every human who died before the year 2000. But why? When does it stop? -Animalparty (talk) 05:36, 20 September 2021 (UTC)
For deceased people worth checking for "novalue" or custom value to add, I think Wikidata:Database reports/top missing properties by number of sitelinks/P26 would be the better list to start with. --- Jura 05:43, 20 September 2021 (UTC)
I updated the report (it hadn't been running in years). It now stops at 85 sitelinks minimum and date of death (P570) after 1500. --- Jura 23:20, 21 September 2021 (UTC)

False constraint violation

The properties of Stephanie Devillé (Q9345692) are showing type constraint violations despite the item being of the correct type (instance of (P31) human (Q5)). What's happening there? --Sod25 (talk) 18:52, 21 September 2021 (UTC)

There are several statements with "deprecated" rank that probably should not be deprecated. You can read more about ranks at Help:Ranking. --Lydia Pintscher (WMDE) (talk) 19:07, 21 September 2021 (UTC)
Weird; deprecated ranks, as created in 2013 [5]. I've set them all to normal rank - Sod25, that should sort the issue out. Let us know if not. --Tagishsimon (talk) 20:18, 21 September 2021 (UTC)
Yes now fixed, thanks to you both. It would be good if properties with a deprecated ranking had "(deprecated)", linked to Help:Ranking, next to their values, which would make it easier to spot them when skimming a page and also make the ranking system more discoverable for new users. --Sod25 (talk) 04:27, 22 September 2021 (UTC)

Nominate your favorite Wikidata projects for the WikidataCon community awards

Hello all,

The Wikidata ecosystem is a huge galaxy of exciting content, tools, projects, powered by the communities as well as organizations working with the software and the data. For seven years, people are gathering, starting projects, developing tools, improving the editors' workflows, filling various gaps, working all together to give more people more access to more knowledge.

In the frame of the WikidataCon 2021, we are organizing the WikidataCon community awards to celebrate the work of people and groups involved in Wikidata, and highlight some projects nominated by the community.

Until October 10th, you can participate and nominate one or several Wikidata-related projects that you like, that are useful for you or for the community. Such a project can be for example: a community gathering or other initiative that led to great results (WikiProject, event, editathon…), a tool (gadget, script, external tool…) or any other action that led to improving Wikidata’s data, the workflow of its editors or the outreach.

The nomination process is taking place publicly and collaboratively on this talk page. You can also help improving the description of projects that are already nominated. After October 10th, the awards committee will select a few projects that particularly caught their attention, and will present them during the Wikidata community awards ceremony taking place during the first day of the WikidataCon.

In order to reach out to the broader audience as possible, feel free to share this message on the talk pages, social media groups or other channels where you are active and people from various groups and experiences on Wikidata can participate. Thanks in advance for your help! Cheers, Lea Lacroix (WMDE) (talk) 08:53, 22 September 2021 (UTC)

Make a wiki item for an institute

Greetings to everyone, I'm here to know the truth (wikipedia item) is against the law to do the institute as a subject? So.. Can I make an item for an institute? If the answer is yes. Will you help me with the ready-made template.. --Ahmadkurdi44 (talk) 18:54, 22 September 2021 (UTC)

Wikidata birthday: participate in a birthday present!

Hello all,

As you may know, Wikidata was launched on October 29, 2012, and every year in October, we celebrate the anniversary of the project with birthday wishes, events and cake. As we will celebrate the 9th birthday of Wikidata this year, we wanted to share with you how you can get involved in this event!

1. Prepare a birthday present

Every year for the birthday, people prepare some presents for the Wikidata community. These presents can be useful, fun or interesting: a new Wikidata tool, a new WikiProject, a logo or another piece of art, a blog post, an important community discussion… they can be worked on alone or in collaboration with other people.

If you have ideas for a Wikidata birthday, now is the perfect time to start thinking about it, and finding other people to work with you! Once the present is ready to be announced, you can add it to this page. If you’re looking for inspiration, you can check what was done for the previous anniversaries in 2015, 2016, 2017, 2018, 2019, 2020.

If you would like to present your gift to the community, you will also have the opportunity to present it during the birthday celebration at WikidataCon 2021. More information will follow soon.

2. Attend the online WikidataCon 2021

The WikidataCon 2021 will take place online on October 29-31, and gather the Wikidata community around its theme, a sustainable future for Wikidata.

Feel free to check the program, the side events, the onsite gatherings, the registration, how to get involved, and the program Reimagining Wikidata from the margins.

3. Join or organize other events

Other events will take place onsite or online around the WikidataCon. For example, you can check:

  • The side events of the conference (events related to Wikidata and Wikibase that are not necessarily organized by the WikidataCon organizers and take place before or after the conference);
  • The preconference Transbordados, a series of events and trainings that will take place online, in Spanish and Portuguese;
  • If the local health measures allow it, some people will organize onsite gatherings to attend the WikidataCon together;
  • You can also organize a birthday event with your community or in your area: if so, feel free to add details on this page;
  • To connect with other people organizing Wikidata-related events, feel free to join the Wikidata Events Telegram group.

If you have any questions or need support, feel free to contact me or to write a message on this talk page.

Looking forward to interacting with you all around the Wikidata birthday!

Best regards, -Mohammed Sadat (WMDE) (talk) 08:25, 23 September 2021 (UTC)

Constraint for "qualifiers should co-exist"?

relevant date for copyright (P9905) has just been created (hooray!). This property is used a qualifier on copyright status (P6216) statements. However, it is only meaningful when a determination method or standard (P459) is also given.

The following query shows items where relevant date for copyright (P9905) is used, but at least one of determination method or standard (P459), applies to jurisdiction (P1001) or public domain date (P3893) is not given: 

# Editions with a copyright status that has a relevant date but not a determination method
SELECT DISTINCT ?work ?workLabel ?methodLabel ?whereLabel ?relevantDate ?pdDate WHERE {
  ?work wdt:P31/wdt:P279* wd:Q3331189 .
  hint:Prior hint:gearing "forward".

  ?work p:P6216 ?statusStatement .
  ?statusStatement pq:P9905 ?relevantDate.
  OPTIONAL {
    ?statusStatement pq:P459 ?method .
  }
  OPTIONAL {
    ?statusStatement pq:P1001 ?where .
  }
  OPTIONAL {
    ?statusStatement pq:P3893 ?pdDate.
  }
  MINUS {
    ?statusStatement pq:P459 ?where .
    ?statusStatement pq:P1001 ?method .
    ?statusStatement pq:P3893 ?pdDate .
  }
  SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}
Show results

But, is there are way to formally specify such a constraint with property constraint (P2302)? Inductiveload (talk) 14:01, 23 September 2021 (UTC)

request merge

I merged w:Domain (mathematical analysis) and w:Region (mathematical analysis). Request a merge of Q7308961 and Q11235244. See w:Wikipedia:Teahouse#About wikidata after the merge is complete. thanks!--SilverMatsu (talk) 22:45, 23 September 2021 (UTC)

@SilverMatsu: The sitelinks to the Portuguese Wikipedia, pt:Região (topologia) and pt:Domínio (análise complexa), are also blocking a merge. Ghouston (talk) 02:44, 24 September 2021 (UTC)
Ghouston Thank you for letting me know.--SilverMatsu (talk) 04:04, 24 September 2021 (UTC)

name of unit for P1350 / P1351

The number of matches played/races/starts (P1350) & number of points/goals/set scored (P1351) are two properties for non-discussible concept. However, its definition is open to show different meanings depending on each sport vocabulary; I mean, match, race, ... goals, points, tries, etc.. Both properties don't accept units, so there is no space to express what the quantity represents. I need to know what the value represents when I recover info from sport related items. Probably, this information should be a statement of sport (or discipline) item, or may be at competition level item. In any case, which property may I use to indicate the meaning of P1350/51 for each specific case?. Thanks, CC. @Lucas Werkmeister:. Amadalvarez (talk) 10:43, 24 September 2021 (UTC)

Chowdhury (2 different entries)

Chowdhury (Q1068345) has been mixed up. I am not sure if to keep it as a disam page or as a family name item. Someone introduced Chowdhury (Q108667148) as a family name. Certainly we need two items but clean up is needed. --E4024 (talk) 02:41, 25 September 2021 (UTC)

Machinetranslated labels and descriptions

It is pretty unlikely that Wikidata would ever have good coverage with translations so would it be possible to pre-populate titles and descriptions at least for the most common languages as a failback? It may be feasible to generate those for other languages as well but for usability English would be most useful.

Technically this could be implemented so that there would be additional information if the label/description is machine translated and what is the source language and when it is created. Same kind of data could be used for storing information if the label/description is just blindly copied from other languages or generated. --Zache (talk) 06:34, 18 September 2021 (UTC)

I agree. It might well be that empty labels / descriptions in the browser UI cause some people to make impulsive bot runs to fill the fields. If P31 values are present they might be better candidates for the description to show, because they are manually translated. --SCIdude (talk) 09:30, 18 September 2021 (UTC)
No. Once Abstract Wikipedia is a thing every item may have a "multilingual" label and description.--GZWDer (talk) 15:28, 18 September 2021 (UTC)
The default description of an item would generally be the label of its P31 value. So I don't really see a need to try to machine translate something. The bot for Dutch descriptions works fairly well with that.
I'm not really sure what machine translations you would want to insert as English labels. --- Jura 13:51, 19 September 2021 (UTC)
In example in Wikidata there is ton of database generated items which are unlikely to be translated manually. Example Salmisaari industrial area (Q31163706) . One solution is to generate descriptions/labels using some rules via bots, but there is still same problem than with machine translations. We need to able to differentiate which ones are human edited and which are not to know which ones can be overwritten in later time by better method. --Zache (talk) 12:31, 25 September 2021 (UTC)

I would like to add ineligible for copyright protection (Q61005058) to copyright status (P6216) because I think that none of the existing values (copyrighted; not yet determined; unknown value; public domain; copyrighted, dedicated to the public domain by copyright holder; orphan work; no known copyright restrictions) really represent this. There is "public domain", but in my opinion this value covers too many possible situations to be an accurate description. "copyrighted, dedicated to the public domain by copyright holder" is also listed in here even you could argue that "public domain" would represent the same thing. Can I just add it or is there any procedural I should follow?
Link to the discussion on the talk page: Property_talk:P6216#Adding_ineligible_for_copyright_protection
--D-Kuru (talk) 14:04, 20 September 2021 (UTC)

I think this would be described by
Specifically, "ineligible for copyright" is a route to being in the public domain (a copyright status), but it is not, in itself, a copyright status.
I feel your pain in trying to get a solid answer on the schema for this though, since I have basically very similar questions that I can't get an answer to. Inductiveload (talk) 15:08, 20 September 2021 (UTC)
@Inductiveload: Would also work for me. But wouldn't this apply to copyrighted, dedicated to the public domain by copyright holder (Q88088423) as well? --D-Kuru (talk) 09:40, 21 September 2021 (UTC)
Quite possibly. That said, both copyrighted, dedicated to the public domain by copyright holder (Q88088423) and ineligible for copyright protection (Q61005058) are subclasses of public domain (Q19652) (see the graph, so actually your proposal sounds correct (or at least...consistent with the incomplete schema currently used). Inductiveload (talk) 09:47, 21 September 2021 (UTC)
There is in fact a significant legal distinction between merely ineligible works and works dedicated to the public domain as the latter may still have moral rights (Q1057599) attached in some jurisdictions. Circeus (talk) 12:13, 25 September 2021 (UTC)

Usage of filmography

While editing Our Gang (Q1218784) I realized that the property filmography (P1283) has constraint suggestions which made me assume that the property should only be used with humans. Is that true or are the constraint definitions wrong? The reason I added film series (Q24856) to the valid types of the property is because it already had animated film series (Q56884562), but everything else in the property page make me think that the usage of the property in Our Gang (Q1218784) isn't an expected one. --Agabi10 (talk) 14:48, 23 September 2021 (UTC)

I think Our Gang filmography (Q3745457) should be added to Category:Our Gang (Q13280014) as list related to category (P1753). --Christian140 (talk) 16:18, 23 September 2021 (UTC)

That doesn't answer the question about whether filmography (P1283) should be used only with persons or not though... --Agabi10 (talk) 08:51, 24 September 2021 (UTC)

How to indicate misspellings and other linguistic errors?

So we have Leaf gas exchange and chlorophyll fluorescence in relation to leaf angle, azimuth, and canopy position in the tropical pioneer tree, Macaranga conifera (Q39095649), which contains the string "cholorphyll", which is a misspelling of chlorophyll (L318035). I was wondering how such misspellings could best be handled and thought that having a lexeme like (L594138) might be useful if we have properties to annotate them according to the type of linguistic error and with a pointer to the linguistically correct variant. I think I have seen previous discussions of such issues but did not find any right now, so opening a new thread here. --Daniel Mietchen (talk) 15:24, 24 September 2021 (UTC)

I think there was a discussion about misspellings in Wikidata talk:Lexicographical data some time ago, when it was proposed to use forms for misspelled variations of a word, but that seemed like the wrong approach after all. Creating separate lexemes may be ok when there are common misspellings; I'm not sure if this one would count though! ArthurPSmith (talk) 17:06, 24 September 2021 (UTC)
If you want to make sure that someone using the proper spelling will find the entry, add the properly spelled word to "main_topic" even though it is a minor_topic, that way it will show up in Google and Wikidata with the proper spelling, when searched. --RAN (talk) 19:28, 25 September 2021 (UTC)

coach (Q1588072)

coach (Q1588072) appears to be a messed up conflation, especially when considering the articles it is linked to. - Jmabel (talk) 01:40, 26 September 2021 (UTC)

How do we handle archives that are housed in a museum?

At Bernhard Hans Schwerin family archive (Q61993417) the start and end time of the archived papers predate the building of the museum so we get an error message. I looked at other archived papers entries and they omit start and end dates for the papers. Any suggestions? --RAN (talk) 19:42, 25 September 2021 (UTC)

@Richard Arthur Norton (1958- ) @Quesotiotyo: seems to have been working on the item in the meantime, so just a general remark: museum building (Q24699794) gets built while museum (Q33506) is an institution (independent of its buildings) and an inception date. An archive can be part of museum (Q33506). Theoretically, if the archive and museum are under one roof, both institutions can also be marked with uses (P2283) : specific museum building (Q24699794). Vojtěch Dostál (talk) 15:57, 26 September 2021 (UTC)
  • Thanks! It looks like it was resolved by using "start of covered period" and "end of covered period". I will try and add it to a few more, so that it can act as a model. --RAN (talk) 17:21, 26 September 2021 (UTC)

Item edit request

Please, delete current logo and add File:Logo Toyota.svg as logo image (P154) on Toyota (Q53268). Thanks in advance!!! --2A04:4E41:1F:24:0:0:84DE:1D32 20:14, 25 September 2021 (UTC)

See above. Please do not post the same request twice. --Tagishsimon (talk) 19:41, 26 September 2021 (UTC)

Item edit request

Please, add File:Logo Toyota.svg as logo image (P154) on Toyota (Q53268). Thanks in advance!!! --2001:B07:6442:8903:241D:5935:B203:71FD 09:42, 24 September 2021 (UTC)

There is already a logo defined. Are you asking for it to be replaced? I'm not keen on all the whitespace around the one you suggest. — Martin (MSGJ · talk) 10:14, 24 September 2021 (UTC)
@MSGJ: yes I am asking for replace. The whitespace is not my suggestion, it is from official logo and should be not removed... --2001:B07:6442:8903:B0B8:406:C574:895 10:49, 24 September 2021 (UTC)
I have zero confidence that the new file is the "official logo", nor that the whitespace is needed. The file was created by some guy on the internet. The file does not obviously match the detail of ANY Toyota websites I've looked at. In the corner of my room, the bullshit detector is parping softly. --Tagishsimon (talk) 19:44, 26 September 2021 (UTC)
@Tagishsimon: It does appear to be the Toyota logo (see https://www.toyota.com/brandguidelines/logo/#toyota) though the excess whitespace is probably not specifically part of it. Notably, the top left of https://toyota.com has a rather tighter crop. More likely the whitespace of this exact SVG is set so the image doesn't change size on that particular page when you flip from horizontal to vertical layout. It's also common for a brand to require a certain amount of negative space around a logo, though this page doesn't explicitly seem to say it. Again, I don't really feel that's part of the logo itself. Inductiveload (talk) 20:39, 26 September 2021 (UTC)
It might well be the logo of Toyota Motor Sales, U.S.A., Inc., but it is not used on the global site - https://global.toyota/en/ - afaics. The item in question is for the global company, not for its US subsidiary. --Tagishsimon (talk) 21:02, 26 September 2021 (UTC)
In that case it does rather appear that the existing image is also wrong, since that global site uses only the wordmark (and many other regional sites using oval part without any 3D effect, following their 2020 redesign, in Europe at least, as well as https://toyota.jp, Mexixo, Argentina, Israel, Brazil, Singapore, Bangladesh and Australia)? The ones that are not distributors I could find still using the 3D effect is South Africa, Malaysia, NZ and Egypt. To be fair I have not looked at them all. Inductiveload (talk) 21:23, 26 September 2021 (UTC)

We have quite a few items marked with various invalid determination method or standard (P459) values when the object is very clearly in the public domain due to great age:

My question is: what should the correct modelling for this be? For example:

Inductiveload (talk) 07:57, 27 September 2021 (UTC)

Wikidata weekly summary #487

Here's your quick overview of what has been happening around Wikidata over the last week.
  • Discussions
    • Open request for adminship: BrokenSegue (RfP scheduled to end after 27 September 2021 14:36 UTC)
  • Development
    • Changed the formatting of low year numbers so that they now show as e.g. “5 CE” instead of “5” to reduce ambiugity in dates like “March 5 (CE)” (phab:T104750)
    • Working on fixing an issue where two Properties could have the same label in a given language (phab:T289473)
    • Working on preventing a few more cases where two Items could have the same sitelink (phab:T291377)
    • Mismatch Finder: Continuing to work on showing mismatches on the results page so that they can be reviewed
    • Continuing to work on technical improvements to how changes on Wikidata are propagated to Wikipedia and the other Wikimedia projects

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.

Names with same meaning

I do not like the "said to be same as" thingy and pray for its disappearance. This is something I face a lot in one of my favourite areas of WD work, names (given or family). Let's have a look at: Dieudonné (FR), Diosdado (ES), Tanrıverdi, Allahverdi, Hüdaverdi and Hakverdi (all four are Turkish). Now I have a question. All these names (in this case surnames) have the same literal meaning "God gave" or "Given by God" or -as the EN:WP puts it- "Gift of God". (EN is not my native language, does "gift" come from the verb "to give"?) I do not know if we have a "something" (item, property or any other thing I ignore) to establish a link between these names? This is much better than the "said to be same as" subjectivity. Let me give or repeat an example, the Turkish given name Anıl has nothing to do with the famous Indian actor Anil Kapoor's name Anil (Q19827640) as they have totally different meanings. However, the above surnames (some of which are also given names) all have the same meaning. Do we have an element to create a link between them?

BTW there is a -maybe not so similar but an interesting- relation between the Turkish female given name Ezgi (Q20001279) and the more international (at least used in Hungarian and Turkish) female given name Melodi (Q1175798) which both mean melody in Turkish; naturally ezgi in pure TR and melodi with foreign etymology. Regretfully, when we use "literal translation" statement in name items, we cannot link it to other items...

What could we do about the above cases? I believe "meaning" is much more significant than "sound" or "appearance"... Thanks a lot. --E4024 (talk) 13:45, 24 September 2021 (UTC)

@E4024: Most names (in English that I'm familiar with at least) are not associated with a "meaning". Perhaps the best approach where there is a real meaning like this is to link it to a lexeme with a gloss describing the meaning, and have that lexeme (sense) link to the others through translation (P5972), synonym (P5973) etc. Maybe names generally should move to the lexeme namespace (there's certainly already some duplication there) but that's a separate discussion - I'm not sure whether we already have a property that could work for the relation between a name and the common word that describes its meaning though. ArthurPSmith (talk) 17:03, 24 September 2021 (UTC)
Thanks. I see that some languages have an affinity in this sense. For example, I just made the item of Spanish-language surname Seisdedos (Q108679007); it has the same meaning as the Turkish-language surname Altıparmak (Q104867757): "Six fingers"! --E4024 (talk) 17:54, 24 September 2021 (UTC)
See Wikidata:Property proposal/name shares origin with and Wikidata:Requests_for_deletions/Archive/2018/Properties/1#P3484.--GZWDer (talk) 14:08, 27 September 2021 (UTC)
I find both Ezgi (Q20001279)said to be the same as (P460)Melodi (Q1175798) and Mark (Q13610143)said to be the same as (P460)Marcus (Q4642) to be equally counter-intuitive. How do we distinguish the different cases: Mark (Q13610143)name shares origin withMarcus (Q4642), Ezgi (Q20001279)name shares meaning withMelodi (Q1175798)? If we stick with P460, what qualifiers should be used? ⁓ Pelagic ( messages ) 16:23, 27 September 2021 (UTC)
@E4024: If there is an underlying real-world or abstract concept, I would use named after (P138). Then that concept becomes the connector: Melodi (Q1175798) → melody (Q170412) ← Melody (Q3854288). Would we then need a Q-item for the concept “gift of God / God-given”? Or for “six fingers”? It'd be nice to also make a direct connexion with a suitable property/qualifier, per above. ⁓ Pelagic ( messages ) 17:45, 27 September 2021 (UTC)
Where there's no general concept (names “share same origin” instead of “share same meaning”), I wish we had a Q-item for the concept of the related names, so that we could relate Luke (Q4927045), Lucas (Q12325000), Luc (Q15262570), Łukasz (Q19816594), etc. to some entity ⟨name group Luke/Lucas⟩. But I guess that's a whole other discussion that's been hashed out somewhere before. ⁓ Pelagic ( messages ) 17:45, 27 September 2021 (UTC)
Somewhat related: my proposal at Wikidata:Properties_for_deletion#Property:P460 could involve a "cognate with" relationship. Which could either be a complete graph like "different-from nexuses" are apparently supposed to be, or could be star-shaped with all names linking to a "core" item. Inductiveload (talk) 20:21, 27 September 2021 (UTC)

How would we store the description of a museum object where we do not have a media image

How would we store the description of a museum object where we do not have a media image. Because the museum's image was taken by the museum, and is of a 3D object, it is not public domain, unlike the other objects that are part of this collection. I have an entry for the object, and want a rough translation of the German description. If we had an image displayed, we would use "media legend". See: Hulda Schottländer (1824-1849) lock of hair (Q96657767) for my various attempts which result in error messages. --RAN (talk) 21:24, 26 September 2021 (UTC)

@Richard Arthur Norton (1958- ): Very good question that I'd like to know too. At commons:Commons:Structured_data/Modeling/Illustrations, I settled on title (P1476) for the original image caption (as opposed to media legend (P2096) which is the caption used on-wiki), but this wasn't especially satisfactory to me.
However, perhaps a media legend (P2096) qualified with object of statement has role (P3831) → "original catalog description" (needs an item to be created) would be unambiguous enough? Inductiveload (talk) 08:13, 27 September 2021 (UTC)
"Original catalog description" or just "catalog description" sounds perfect, will you propose it formally? --RAN (talk) 12:11, 27 September 2021 (UTC)
@Richard Arthur Norton (1958- ): Done at Wikidata:Property proposal/original description, but needs 2 more examples. Note that probably you can only copy wholesale text from public-domain catalog entries. I left it a bit more generic, as it gives scope to be used for other descriptions that just in catalogs. Inductiveload (talk) 13:13, 27 September 2021 (UTC)

Using URL-Formatter (P1630) with "only if regex matches" (P8460)

I've been trying to use applies if regular expression matches (P8460) on a formatter URL (P1630) for a complex use case as described in Property:P8460#P2271, but it just ended up highlighting all URLs and ignoring my capture group. My revision (Reverted for now) can be found here. Can anyone tell me what I've done wrong?

Expected behaviour:

Actual behaviour:

Thanks in advance
Unkn0wnCat (talk) 07:02, 27 September 2021 (UTC)

@Unkn0wnCat:: the "end of string" match is a dollar symbol ($), not a section mark (§). The section mark matches a literal "§", which doesn't exist in the given URL., so the match fails.
I use https://regex101.com/ for debugging regexes. Inductiveload (talk) 07:27, 27 September 2021 (UTC)
Ah yes, that is an error, but then it should not match any URIs at all instead of all. I've tried using no start or end markers at all first, as shown in the example values, and that didn't work either. Unkn0wnCat (talk) 08:03, 27 September 2021 (UTC)
Hmm, then I am not sure. It seems what you are doing is right, but I can't make it work either. Sorry! Inductiveload (talk) 08:29, 27 September 2021 (UTC)
@Unkn0wnCat: applies if regular expression matches (P8460) is not supported by the software, see the discussion on the property proposal after it was created. (Unless there’s a gadget set up that I’m not aware of which adds this support.) Lucas Werkmeister (WMDE) (talk) 08:34, 27 September 2021 (UTC)
Ah, bummer, it would be great to have for properties like this one... Thanks for the answer! Unkn0wnCat (talk) 20:47, 27 September 2021 (UTC)

merge (work and edition)

A Modest Proposal (Q78601245) and A Modest Proposal (Q264143) are the same i try to merge them but w3ebsite say no Svenurban (talk) 10:10, 27 September 2021 (UTC)

You deleted the statement that linked the two and explained why they are different: "A Modest Proposal edition or translation of A Modest Proposal". --- Jura 10:35, 27 September 2021 (UTC)
For major works we have an entry for the creative work, which can be the same as the first edition, and then we have an entry for each time it was republished. We do it because the various identifiers for a scanned work are specific to a date of publication. --RAN (talk) 18:18, 27 September 2021 (UTC)

Corporal vs. Korporal

I realize we can have military ranks specific to countries, but at least two of these entries list the same countries. I tried to change the description to match the countries listed, but then I found a third version with some of the same countries listed and thought it best to get help. Can someone with a military history background sort them out better than I can, and write descriptions that better distinguish them. See Korporal (Q157662) vs. corporal (Q17378201) vs. Korporal (Q23058159) vs onbaşı (Q20392348). There may even be more. Should some be merged that do not have their own Wikipedia articles in the same language? --RAN (talk) 18:15, 27 September 2021 (UTC)

Enforce properties for items of certain types

I have the following problem. I have an entity of a certain type, let's say researcher. I would like to put some constrains so that when a new researcher is created then certain properties need to be specified. Like the sex and the domain. Is this possible with the current available constrains? I did not find a way to do this .... DD063520 (talk)

Sounds like a really terrible idea. Who died & made you king? --Tagishsimon (talk) 18:59, 27 September 2021 (UTC)
@DD063520: Constraints apply to properties, not items. However, Entity Schema's in Wikidata do something along the lines you suggest - see the list here: Wikidata:List of schemas. An EntitySchema allows specifying criteria that items should satisfy and checking a list of items against those criteria. Note that even property constraints are not "enforced" here, in the sense that people using them can choose to follow or not follow the constraints. ArthurPSmith (talk) 19:14, 27 September 2021 (UTC)
@DD063520: we have the Wikidata:Recoin gadget for this. You should enable it. Multichill (talk) 20:22, 27 September 2021 (UTC)

Import IEEE Xplore author ID matching existing ORCID?

Many author profiles on IEEE Xplore include their ORCID (such as in this one). Could we have a bot import IEEE Xplore author ID (P6479) when it matches profiles with ORCID iD (P496) that we already have? --Bender235 (talk) 13:25, 17 September 2021 (UTC)

@Bender235 Is there a way to access all IEEE records? Vojtěch Dostál (talk) 11:23, 24 September 2021 (UTC)
You mean other than webscraping? --Bender235 (talk) 14:47, 24 September 2021 (UTC)
@Bender235 Well, ideally, but web scraping would do. Unfortunately, I don't know which features on the web could be used to crawl the author entries. Usually, one does it through lists of entries etc. Any ideas? Vojtěch Dostál (talk) 19:17, 24 September 2021 (UTC)
I don't think there's a directory of all Xplore-listed authors, if that's what you mean. A web-scraping bot would probably have to access https://ieeexplore.ieee.org/author/[Author id] for all possible ranges and check if there's an ORCID iD (P496) reported. --Bender235 (talk) 20:18, 24 September 2021 (UTC)
@Bender235 Yeah, hmm. I was able to automatically assign ORCID ID to about 30 items which already had IEEE Xplore author ID (P6479) but no ORCID ID. That was easy because I only scraped a few hundred IEEE entries which are already in Wikidata but do not have ORCID. Your proposed approach might work and have a big impact, but even if we only crawl IDs 3[7-8][1-9]{9}, it's 774,840,978 combinations which is unfeasible for any bot that would try to go through all the entries one-by-one. Vojtěch Dostál (talk) 15:40, 28 September 2021 (UTC)

Universal Code of Conduct enforcement Draft guideline review, Share your thoughts!

Hello there,

This is your friendly reminder that the Universal Code of Conduct Enforcement draft guidelines review is currently ongoing and will be end on October 17th, 2021. At this time the "Abstract" is available for summarization of the enforcement draft guideline.

Feel free to visit any of On-Wiki discussion that in place on various Wikimedia communities. We also have a feedback page in Wikidata (Wikidata talk:Universal Code of Conduct consultation) to discuss locally.

All of your valuable feedbacks will be passed as the report and will generate into bi-weekly digest which will present to the drafting committee.

Please participate the discussions and spread the words to your fellow Wikidata community members. Thank you! --YKo (WMF) (talk) 11:29, 29 September 2021 (UTC)

constraints to approximate owl:disjointWith

During Data Quality Days @AlePiscopo: was giving an overview of ontology issues. When he described "conceptual ambiguity" I realized I had introduced a few of these myself by trying to satisfy constraints. In one case I made something instance of (P31) database (Q8513) and organization (Q43229).

I think if Wikidata had some property like owl:disjointWith (so we could say database (Q8513) "disjoint with" organization (Q43229) then I could have had a constraint violation which would have caused me to differentiate between the organization and the database that the organization administers.

Thoughts? Justin0x2004 (talk) 13:20, 29 September 2021 (UTC)

Sounds very useful to me.
C.f. a query I literally tried to write today: Wikidata:Request_a_query#Slow_when_in_a_subquery,_but_fast_otherwise(?). The focus of the question is on a technical aspect of the query, but the thrust of the example query is finding taxa entities that are also somehow "concrete" organisms, for example Picea omorika (Q147824) "is a" taxon (Q16521) (correct) and "is a" tree (Q10884) (wrong: it's a kind of tree; Neuhaus Oak (Q114810) "is a" tree).
Lots and lots of schemas are beset by similar confusing conflations, Another one I'm actually trying to deal with: copyright determination method (Q61005213), copyright status (Q50424085) and heuristic for determination of copyright status of a creator (Q108697774). Inductiveload (talk) 13:41, 29 September 2021 (UTC)

A quickstatements gotcha?

There's a change in parliament in Norway following the recent election and so I was running a batch to add end times for the representative's terms. But I had to manually correct when some dates were added to the wrong statement. I was wondering if it was something I did wrong or if this is somehow inevitable using quickstatements. Take Olemic Thommessen (Q6514130) for example. The quickstatements line should have looked like this:

Q6514130 P39 Q9045502 P2937 Q55670426 P582 +2021-09-30T00:00:00Z/11

This added all the qualifiers to the first statement, instead of what I wanted it to do, match all but the last qualifier to a statement then add the last qualifier to it. Is there a way to do this? --Infrastruktur wdt:P31 wd:Q5 (T | C) 14:04, 29 September 2021 (UTC)

i don't understand what you want that QS line to do. it seems to do the right thing for me. BrokenSegue (talk) 14:37, 29 September 2021 (UTC)
(EC) Yes. QS is not the tool to use to add qualifiers to statements where there are multiple statements having the same value. Tool of choice for this would probably be wikibase-cli, having first ascertained the <claim-guid> by using e.g. WDQS to report on the p:P39 value - example. --Tagishsimon (talk) 14:39, 29 September 2021 (UTC)

Oxford Dictionary of National Biography ID (P1415) and recent ODNB entries

I'm having trouble adding an instance of Oxford Dictionary of National Biography ID (P1415) for Derek Parfit (Q962160). The subject does have an entry (see https://doi.org/10.1093/odnb/9780198614128.013.90000380327), but the identifier OUP appears to have assigned to that article—90000380327—doesn't conform to the definition in our property Oxford Dictionary of National Biography ID (P1415). Any ideas? I'm thinking it's related to the fact that the entry I was trying to add was only published on 14 January 2021, so may use a different convention. AleatoryPonderings (talk) 23:13, 29 September 2021 (UTC)

Yes. Property talk:P1415#More URL woes?. --Tagishsimon (talk) 23:16, 29 September 2021 (UTC)

Help needed

Here: Wikidata:Property proposal/TMOK ID. Many thanks in advance. --E4024 (talk) 01:38, 30 September 2021 (UTC)

Category:Higan (emulator) logo image display and output error.

Currently, in WikiData, logo images are well output and displayed, but when viewed in public categories, logo images are not output or displayed.

Symptom: [[File: | 110px]] It comes up like this.

This is a problem in which logo images in the wiki data frame are not output or displayed in the Higan (emulator) category of wikimedia commons. Gameposo (talk) 13:55, 29 September 2021 (UTC)

ListeriaBot at Wikisource

I'm trying to get ListeriaBot working at English Wikisource. Specifically, I think this page should work: s:en:User:Inductiveload/Sandbox/wd_dashboard. However, while the "update this table" link appears to work, it doesn't ever actually edit the page. The query (https://w.wiki/49Fz) is producing plausible data.

I think it should add something like the following: 

{{basic pie chart
 | legend = main subject (P921)
 | labels = no statement with property,item with property
 | values = 7937,2423
}}

The service seems to think all is well: 

Trying to update User:Inductiveload/Sandbox/wd_dashboard...
Done.
Last line: OK: User:Inductiveload/Sandbox/wd_dashboard not edited

I did ask Magnus, but he seems not available, so...does anyone know how I am holding it wrong? Inductiveload (talk) 23:17, 29 September 2021 (UTC)

Could somebody make a peertube address entry like the mastodon one?

mastodon. I have a start amount of data here[9] Greatder (talk) 05:28, 28 September 2021 (UTC)

@Greatder: to do this you need to make a request at Wikidata:Property_proposal. BrokenSegue (talk) 14:22, 28 September 2021 (UTC)
Too much instruction creep, will leave this I guess. --Greatder (talk) 15:49, 28 September 2021 (UTC)
@Greatder: You can store any social/UGC network with website account on (P553) (example). There are people that review the most used values and suggest properties for creation. --Lockal (talk) 07:09, 30 September 2021 (UTC)
@Lockal: The peertube and mastodon addresses are a bit more complicated and would follow more of a "@[email protected]" format. So it will need to be expanded a bit. --Greatder (talk) 09:26, 30 September 2021 (UTC)
@Greatder: feel free, I just followed the examples on en:User:Greatder/sandbox, and there is nothing more than username and domain. --Lockal (talk) 10:07, 30 September 2021 (UTC)

Erroneous dates being added causing errors

See Wikidata:Database_reports/items_with_P569_greater_than_P570 for the list, I am sure there are more that escape this error detection search. The same rogue date being added with Wikitree as the source. The rogue date is "30 November 2 CE". --RAN (talk) 02:16, 30 September 2021 (UTC)

Fixed! --RAN (talk) 23:04, 30 September 2021 (UTC)

SFMOMA artist ID (P4936)

At "SFMOMA artist ID" can I remove the constraints that demand human qualities, the database also has entries for art studios as well as individual artists. --RAN (talk) 02:32, 30 September 2021 (UTC)

i don't see why not though if it's just a very few instances you could add exceptions. BrokenSegue (talk) 21:40, 30 September 2021 (UTC)
Perhaps that is the best way to go. Thanks! --RAN (talk) 23:04, 30 September 2021 (UTC)
Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat/Archive/2021/09&oldid=1510294744"