Wikidata:Project chat
Wikidata project chat
A place to discuss any and all aspects of Wikidata: the project itself, policy and proposals, individual data items, technical issues, etc.
Please use

the first time you mention an item or property, respectively.
Other places to find help
Start a new discussion
Afrikaans العربية беларускаябеларуская (тарашкевіца) български Banjarবাংলা brezhoneg bosanski català کوردی češtinaсловѣньскъ / ⰔⰎⰑⰂⰡⰐⰠⰔⰍⰟ dansk DeutschZazaki dolnoserbski Ελληνικά EnglishEsperanto español eesti فارسی suomi føroysktfrançais Nordfriisk galego Alemannisch ગુજરાતીעברית हिन्दी hrvatski hornjoserbsce magyarհայերեն Bahasa Indonesia interlingua Ilokanoíslenska italiano 日本語 Jawa ქართულიқазақша ಕನ್ನಡ 한국어 kurdî Latina lietuviųlatviešu Malagasy Minangkabau македонскиമലയാളം मराठी Bahasa Melayu Mirandés مازِرونیNedersaksies नेपाली Nederlands norsk bokmålnorsk nynorsk occitan ଓଡ଼ିଆ polski portuguêsRuna Simi română русский Scotsdavvisámegiella srpskohrvatski / српскохрватскиසිංහල Simple English slovenčina slovenščinashqip српски / srpski svenska ślůnski தமிழ்తెలుగు ไทย Tagalog Türkçe українська اردوoʻzbekcha/ўзбекча Tiếng Việt Yorùbá 中文
On this page, old discussions are archived after 7 days. An overview of all archives can be found at this page's archive index. The current archive is located at 2021/09.
a query
for permissions
for deletions
Report a
technical problem
for comment
for deletion
for checkuser
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)
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
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 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 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 using http and https protocolsSELECT ?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 "" . 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 "*" . bd:serviceParam mwapi:geulimit "max" . ?item wikibase​:​apiOutputItem mwapi:title . } } UNION { # Find items with http URLs SERVICE wikibase:mwapi { bd:serviceParam wikibase:endpoint "" . 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 "*" . bd:serviceParam mwapi:geulimit "max" . ?item wikibase​:​apiOutputItem mwapi:title . } } }} AS %get_itemsWHERE{ 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​), "") 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)
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​. 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).
Item fix request
Is there someone that can kindly change official website (P856) from to on Mexico 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)
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​[Author id]
for all possible ranges and check if there's an ORCID iD (P496) reported. --Bender235 (talk) 20:18, 24 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:
--- 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)
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)
Please use Wikidata:Café for Spanish language posts. --- Jura 13:52, 19 September 2021 (UTC)
User:Esp1986, do you understand Spanish? :) --E4024 (talk) 14:23, 19 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)
I think that this discussion is resolved and can be archived. If you disagree, don't hesitate to replace this template with your comment. E4024
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​,​,​, and​.
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)
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)
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 (P8032) are both used:
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
victim cause of death (P509) value, with qualifier statement is subject of (P805)instance of airplane crash
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!
victim significant event (P793) instance of airplane crash
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 while
- Syzygie (Q2377241) refers to
The correct Deutsch translation is Syzygie. 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. 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)
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)
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)
copyright status (P6216)
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
copyright status (P6216)public domain (Q19652), qualified 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)
Wikidata weekly summary #486
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Upcoming:
    • Next Linked Data for Libraries LD4 Wikidata Affinity Group call: Bionomia and maintaining Wikidata synchrony with David Shorthouse (Agriculture and Agri-Food Canada). [1], Sep 21st.
    • Lightning Talk: Wikidata in your Civic Tech project | Summit 2021 - YouTube
  • Ongoing:
    The Creative Commons Global Summit and Hack4OpenGLAM hackathon take place from September 20 until 24 (fully online). Several sessions and projects are related to Wikidata and/or Wikibase (see schedule search).
  • Past:
    • Periodic editathons as a way to improve data quality on Wikidata: an experiment in Italy - YouTube
    • Bringing Czech authority files into 21st century: Integration with Wikidata - YouTube
Press, articles, blog posts, 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
Tool of the week
User:Inductiveload/scripts/ShowQsAndPs shows the Q and P IDs on Items.
Other Noteworthy Stuff
OpenRefine has started development of features for Structured Data on Wikimedia Commons. Sign up here if you want to receive occasional updates on a Wikimedia talk page of your choice.
Did you know?

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.
Monthly Tasks
Read the full report · Unsubscribe · Mohammed Sadat (WMDE) 15:13, 20 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):
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)
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 [2]. 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)

Is there a good reason such edits are technically even possible?
[3]. This whether the page is protected or not. --- Jura 20:14, 22 September 2021 (UTC)
@Jura1: No she is not. If I see correctly in the side protection log, the last protection ended on February 21, 2020. --Gymnicus (talk) 20:43, 22 September 2021 (UTC)
Would it be possible to prevent edits like this with abuse filters? --Marsupium (talk) 09:24, 23 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:
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)
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)
26 million articles to go...
I created a new tool for improving our scientific articles with main subjects 2 weeks ago. Since then, over a million articles have now got their first main subject!
We only got ~26 mil. left (out of a total of 73 mil. articles).
The tool uses some bandwidth, so recently I improved it, so it can run in the WMF Cloud Services Kubernetes platform also.
Feel free to help out :)--So9q (talk) 11:29, 23 September 2021 (UTC)
Don't many papers submitted come with "tags" e.g. this paper is tagged as "randomized algorithms", "rejection method" and "Random number generation". I wonder if we could import those in a sensible way. BrokenSegue (talk) 13:57, 23 September 2021 (UTC)
I did not find the "rejection method" there, but yes, that particular page lists tags. There are thousands of publishers so making a tool that reliable scrapes these tags is IMO not feasible (for big repos like PubMed it might be worth it).
I recently created a NER capable tool, but it needs more input data than WDQS can give today (cirrussearch limits to 10000).
The very best would be open science with high quality linked metadata including categorization (a little like PubMed has MeSH, although it does not have to be a controlled vocabulary), but anything machine readable is better than nothing. I asked in the telegram groups if anyone sits on a reliable source for the abstracts, that does not need scraping, but none has come forward. I'm thinking about downloading the libgen archive and do NER matching on cleaned PDF data, but that is unfortunately a terribly messy approach (and possibly illegal too). It could be fun though :)--So9q (talk) 20:07, 23 September 2021 (UTC)
I don't find edits like these especially helpful. If you don't know the difference between CRISPR (Q412563) and CRISPR screen (Q106472333) then please avoid biomedical literature. I know the topic is complicated. Please have respect and note that proper terms may consist of multiple words that may not be adjacent. --SCIdude (talk) 06:59, 24 September 2021 (UTC)
@SCIdude: Thanks a lot for your feedback. I was not aware of CRISPR screen (Q106472333). I added it here to keep track of it. If you find other similar cases, please feel free to add it there in a comment.--So9q (talk) 08:39, 24 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 (P459) is also given.
The following query shows items where relevant date for copyright (P9905) is used, but at least one of determination method (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 methodSELECT 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)
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)
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)
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)
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)
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)
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 cholorphyll (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)
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)
Last edited on 25 September 2021, at 03:03
All structured data from the main, Property, Lexeme, and EntitySchema namespaces is available under the Creative Commons CC0 License; text in the other namespaces is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy.
Privacy policy
Terms of Use
 Home Random  Nearby  Log in  Settings  Donate  About Wikidata  Disclaimers