Wikidata

Wikidata:Project chat/Archive/2018/09

< Wikidata:Project chat‎ | Archive‎ | 2018

Honorable Citizens

Do we have property for en:Honorary citizenship? I mean a property to add all the Honorable Citizens of a municipality to the municipality items. And about the opposite, to add to the item of a person that he/she is a Honorable Citizens of a municipality can we use award received (P166) and how? Xaris333 (talk) 03:08, 1 September 2018 (UTC)

It's done the second way with many instances, like . Ghouston (talk) 03:12, 1 September 2018 (UTC)
So this way is enough? We don't need the first way? Xaris333 (talk) 03:31, 1 September 2018 (UTC)
It seems like enough to me. It's similar to other awards. Ghouston (talk) 11:06, 1 September 2018 (UTC)
Yes, this seems best. Andrew Gray (talk) 14:25, 1 September 2018 (UTC)
By the way, "honorable" and "honorary" are distinct words, and one cannot be substituted for the other. - Jmabel (talk) 16:20, 1 September 2018 (UTC)

Thanks all! Xaris333 (talk) 18:56, 1 September 2018 (UTC)

This section was archived on a request by: Matěj Suchánek (talk) 09:57, 3 September 2018 (UTC)

Dilemma

I simply don't get what the heck is he doing here? He is not even properly explaining what is the purpose for this? And why is undoing the translations in other languages? Why not just edit the description? This is redundant. He is also accusing me of repurposing the matter. I don't know why? I just asked him to elaborate. Harsh Rathod Poke me! 17:41, 2 September 2018 (UTC)

@Harshrathod50: We try not to conflate family name items with given name items if at all possible; you don't see us merging Smith (Q21079662) with Smith (Q1158446), for example. If you must combine the two—which under the current system for modeling names is discouraged—then Jura's last edit summary ('please don't repurpose items. If it's used for both, P31 should be name (Q82799)') is a perfect succinct explanation of what you should do. @Harmonia Amanda: can explain more on this subject. Mahir256 (talk) 18:03, 2 September 2018 (UTC)
Yes, this is the explanation I was asking for. Now I get everything. Thanks. Harsh Rathod Poke me! 19:14, 2 September 2018 (UTC)
This section was archived on a request by: Matěj Suchánek (talk) 09:57, 3 September 2018 (UTC)

Question about mass adding properties into wikidata

So some of my suggested properties for wikidata have recently be approved, how can I add those properties into related wikidata entries relatively quickly? C933103 (talk) 23:18, 29 August 2018 (UTC)

@C933103: it depends what your data source is. If you want to extract them from Wikipedia articles, try Harvest Templates. If you want to import the data from a tabular file, try OpenRefine. For more background, see Wikidata:Data_Import_Guide − Pintoch (talk) 10:35, 1 September 2018 (UTC)
@Pintoch: I am talking about properties of external identifiers. Also, it seems like that Harvest Templates tool cannot be used to harvest wiki not run by WMF?C933103 (talk) 14:51, 1 September 2018 (UTC)

Please delete Q56501558

Unfortunately I created this duplicate to Q4214852.--Carl Ha (talk) 00:11, 7 September 2018 (UTC)

Mahir256 Merged Q56501558 into Q4214852. --- Jura 04:27, 7 September 2018 (UTC)

This section was archived on a request by: --- Jura 04:27, 7 September 2018 (UTC)

Merge instructions - where?

So I tried to add an article to an item and got a warning message saying it was already in another - but if there were really both the same merge them. But the warning did not link to any description of how to merge them. By trial and error, I got two sets of two into one set of four (Q1863530) - with a mostly empty item still hanging around: (Q27664520). How do I get rid of that? Which one should I have chosen as the merge target? Why doesn't the warning message give any guidance? Rmhermen (talk) 16:17, 28 August 2018 (UTC)

Rmhermen, the page Help:Merge explains the different ways to merge items. And, the target item should be the one who is not obsolete. Esteban16 (talk) 18:30, 28 August 2018 (UTC)
Why doesn't the error message link to this explanation, though? Rmhermen (talk) 14:40, 30 August 2018 (UTC)
Doesn't it: MediaWiki:Wikibase-error-sitelink-already-used? Matěj Suchánek (talk) 13:18, 3 September 2018 (UTC)

How to mark or report items which seem to be the same?

A colleague who is currently working on a mapping between STW Thesaurus for Economics (Q26903352) and Wikidata sometimes finds more than one counterpart for a STW descriptor. In obvious cases, he merges the items and goes on. In other cases, items cannot be merged, because they are linked to different Wikipedia pages, or a deeper understandig of the concepts would require more language knowledge - or the items look just too large and complex. One such case is the cluster of fishing (Q14373), fishery (Q180538) and commercial fishing (Q11202642). Please understand that we do not want to discuss this particular example here, but introduce it merely as an illustration of the problem. More generally, it is out of scope of the mapping work he is charged with, to solve such conflicts or invest time into a discussion about a proper solution.

What we could and happily would do is to mark such clusters we come across, in order to hint other users interested a the particular item to other items which seem to be the same. I've experimentally marked the three items mentioned above with said to be the same as (P460) inter each other. I'm not sure, if this is the right way (at that point, the dispute is only in our heads, and we don't want to make it explicit with arguments and counter-arguments). If somebody can point out a better practice of marking the involved items, which does not require much more work, or where to report such items on a maintenance page, we are happy to follow suit. We can also deal with the issues completely on our side of the mapping, but feel that would mean wasting insights we gained along the way. Jneubert (talk) 14:09, 30 August 2018 (UTC)

@Jneubert: "Said to be the same as" is not the correct sollution; a fishery (a venue) is not the same as "fishing" (an activity). In your example, "commercial fishing" is a subclass (or subcategory, if that helps) of "fishing" (which can be commercial or not). It would seem that you and your colleague need to be clearer about what precisely the thesaurus is, in such cases, describing. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:26, 30 August 2018 (UTC)
Does the STW contain a mapping between German and English? – Looking at your example, it is impossible to do a mapping de:STW = en:STW = en:WD = de:WD. Assuming that the STW mapping en:STW = de:STW is correct and that you will be able to do the mapping en:STW = en:WD with reasonable reliability, I would suggest that you focus on mapping en:STW = en:WD and output a maintenance list of all the cases where de:STW != de:WD. – Does that make sense?
I don't like the idea of using said to be the same as (P460) in this case. The problem here lies not so much in the fact that someone would claim that the concepts are the same, but more in fuzzy language links between different Wikipedias, in bad translations on Wikidata, etc.
--Beat Estermann (talk) 14:31, 30 August 2018 (UTC)
Thanks, Andy, Beat. The example was chosen because it is complex (the class and English description for fishing (Q14373) says it is an activity, but the German description says it is an economic sector) - this cannot be solved "en passant" in a straightforward way. The STW is concept-based (according to SKOS and ISO-25964), which means that the English and German labels should denominate exactly the same "unit of thought" (which, in the example, comprises the economic sector and the activities within that sector). It might be broken in some places, but it's the basic principle, and will do our best to fix errors (e.g., misleading labels or scope notes). For Wikidata, in my understanding the basic idea (one concept/item, multiple labels and descriptions in different languages) is the same, but due to historic reasons (Beat mentioned some) there are more places to fix things. In the mapping, we can take into account that Wikidata items may be ambiguous (e.g., by using a close match (Q39893184) mapping relation type (P4390), but we cannot fix more complex issues in Wikidata itself.
We can avoid said to be the same as (P460) - but is there another, more proper way to mark or report such clusters with seemingly overlapping items? Jneubert (talk) 15:28, 30 August 2018 (UTC)
Let me guess: Your dictionary entry refers to fishing industry (Q635139), as in "agriculture, fisheries, and forestry" / "Landwirtschaft, Fischerei und Forstwirtschaft". – You may have missed a WD entry. If this is the case, you should re-think your matching approach (in this case, if you match against "Fischerei" you'll get a false positive because the corresponding Wikipedia articles in German and English are not attached to the same WD item). --Beat Estermann (talk) 14:44, 30 August 2018 (UTC)
Thanks, obviously we indeed missed that one - which just adds to the complexity of the cluster. Jneubert (talk) 15:37, 30 August 2018 (UTC)
I think people are getting hung up here on what turns out to be a bad example, because in this case the answer would be, "Yes, there is a reason for all of these items to be distinct." The original question was how to mark things when there are doubts. - Jmabel (talk) 15:25, 30 August 2018 (UTC)
I don't think it is a bad example, because the various terms and definitions across languages are indeed a big mess in this case (if you were to match against the German version you would need to link to a different Q-number). Maybe you could give us a couple of further examples we can analyse in order to see whether the approach I suggested above would work for all of them. If you don't mind linking against messy data, you could just pretend that English is Wikidata's main language and ignore the other labels, outputting a list of problematic cases for the rest of the community to work on at a later point in time. If you're interested in linking against clean data, I would suggest that you invest some time in cleaning the data up before adding the STW identifiers. Having a list of problematic cases ready may help you mobilize some further helpers from the community. Linking a shitload of external identifiers (you are not the only ones) against messy data does not make much sense after all. By the way, what other data are you adding to the WD items apart from the STW identifiers? And do you have any specific use cases in mind for which your data ingest could be useful? (this could also be a good starting point for any reflections about the importance of having clean data in Wikidata in the first place.) --Beat Estermann (talk) 20:23, 30 August 2018 (UTC)
My colleague came across several such clusters of mostly rather high-level items with multiple language links. I hesitate to introduce them into this discussion, because we're not looking for a solution of the particular issues.
On the gereral level - if I didn't get you wrong - you suggested above to link in respect to language-specific labels/terms, and keep a maintenace list for exceptions. For the latter, we are currently implementing a mechanism. But that still is intended to work on a concept level, across all languages, with the main purpose of being able to provide users with more links to Wikipedia on STW pages (example). We at that point have no resources to get involved into Wikidata clean-up before linking, but would just pragmatically from our side offer links to items and WP pages which seem useful.
Sometimes cleaning up Wikidata would not work, because the mess results from reality. I brought up a - for an economics library quite fundamental - case some time ago: business administration (Q2043282), business economics (Q24208053), and business studies (Q5001951) are closely related and to some extent interchangeable concepts. In that discussion, my concern was about a in my eyes misplaced sitelink to (insofar quite similar to the above example). I was advised to take it to the talk page at the German Wikipedia (what I did), but without any response. What I also did - and what probably is of more lasting value - is interlinking the three according Englisch Wikipedia pages, which up to that point had been completely unrelated, with "See also" links, so readers and maintainers can at least easily discover the related pages.
Perhaps, a "see also" link could serve that purpose on Wikidata, too. There is related property (P1659), but this is restricted to properties. @Srittau: challenged that restriction on Property_talk:P1659, but without much response. So we're still stuck here. Jneubert (talk) 07:31, 31 August 2018 (UTC)
It seems just unlikely that someone on a Wikipedia talk will shed much light on this. At some point, one needs to determine what a Wikidata item is about and then, if some labels or sitelinks don't match that, move them to the appropriate items. Trying to fill up the Wikidata items with all subjects that might also be covered by one of the 256 Wikipedias is just not helpful.
--- Jura 18:28, 31 August 2018 (UTC)

@Pigsonthewing, Beat_Estermann, Jmabel, Jura1: Thank you for your contributions. I've removed the preliminary said to be the same as (P460) entries. Additionally, I did a bit of cleanup (moved de:Fischerei sitelink and adapted the German label of fishing (Q14373)). Since there currently seems to be no common way to mark such clusters of items, we will keep track of those which come up during the STW mapping process on our side. If we stick with the experimental publicly accessible exception list, that at least would allow others to trace dubious cases. Jneubert (talk) 16:28, 3 September 2018 (UTC)

Template:Property proposal content

Where is the boilerplate guidance text for {{Property proposal}} stored? I want to make (or propose) a change. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:35, 1 September 2018 (UTC)

Wikidata:Property proposal/Proposal preload? Template:Property proposal/doc? Matěj Suchánek (talk) 09:56, 3 September 2018 (UTC)

Two different Wikidata items referencing the same Wikipedia article

Prior to 2018-09-01 the Wikipedia article on "w:Historical Statistics of the United States" was a thinly veiled advertisement for the commercial version of this historical project that was introduced in 1949 by the US Census Bureau, then spun off to a commercial version after the 1975 edition. I added that 1975 edition to Wikidata as Q56424104 and then modified that Wikipedia article to also cite Q56424104.

However, I'm not allowed to link from Q56424104 to that Wikipedia article, because:

Could not save due to an error.
The save has failed.
The link enwiki:Historical Statistics of the United States is already used by item Q5773964. You may remove it from Q5773964 if it does not belong there or merge the items if they are about the exact same topic.

What do you suggest be done to resolve this conflict, if anything? I think it's appropriate for both Q56424104 and Q5773964 to reference this same Wikipedia article.

Other questions

  1. Is Wikidata currently inputting standard CC0 data series like the many published by the US government, to eventually make Wikidata a "one-stop shopping bazaar" for standard international data series? If the answer is "partially", what are the obstacles to faster progress?
  2. What might be an appropriate role for Wikidata for inviting the academic community to start publishing things like this within the Wikimedia system?

The US Census Bureau publishes many series monthly, quarterly or annually, as do many other agencies internationally. The US Census Bureau published the first edition of Historical Statistics of the United States in 1949 and updated it in 1954, 1960, 1965 and 1975. The 1975 edition was 2 volumes. The next update appears to have been the 2006 edition, Q5773964, which appeared in five volumes -- and is locked behind a paywall. Rather than pay Cambridge U. Pr. to access it online, I went to a local library that has it in its "reference" department. Thanks, DavidMCEddy (talk) 20:23, 1 September 2018 (UTC)

@DavidMCEddy: I'm not sure on the specifics of this case, but in general if this could be considered a single "work", there should be one Wikidata item for the work as a whole, and then separate items for each edition that is notable. The "work" item should be the one that links to the enwiki article, and the edition items would then link to the work item via edition or translation of (P629). On the other hand, if this should be considered as two (or more) separate "works" or "projects" or some other type of entity, there is at least a succession sequence, so the item for the older project should be linked to the item for the newer project via replaced by (P1366) or followed by (P156); only the item for the current state of the project would be directly linked to the enwiki item. The single-value constraint for wikidata items to wikipedia articles in a given language is strictly enforced (though there is a workaround via redirects). On your other question, if I understand it correctly, there are structural limitations to how many statements can be attached to an item in Wikidata - more than 1000 and the user interface becomes pretty unworkable - but we also allow linking to tabular data in the Wikimedia Commons project, so large statistical datasets would probably be best accommodated that way - as long as they meet the other requirements (like CC0 compatability) for import. ArthurPSmith (talk) 12:30, 4 September 2018 (UTC)

I would like to create a report on new articles: users, wordcount, categories, bytes for a specific wikiproject

I know that I can find out information about wikipedia articles (wikidata items) and their properties on Wikidata. I would like to find information on user contributions per month for a specific Wikiproject. This would help with wikiproject planning and management. I am not a developer. Can you point me in the right direction if Wikidata is not the place to get that info? thx MauraWen (talk) 15:49, 2 September 2018 (UTC)

@MauraWen: Wikidata does not carry metadata about user actions in other wikimedia projects; the data in Wikidata is about the concepts that are described in articles, not about the articles themselves. What you are looking for may be available however from the Wikimedia Statistics pages; please check there. ArthurPSmith (talk) 12:55, 4 September 2018 (UTC)
thx @ArthurPSmith: for answering my question. I eventually figured out that this is a metadata issue, but glad to hear Wikimedia statistics is the best place to get that information. MauraWen (talk) 13:10, 4 September 2018 (UTC)

What is the URL of the RDF representation a property?

Tracked in Phabricator
Task T203400

For example the property P279 (subclass of): https://www.wikidata.org/wiki/Property:P279

According to usage in other entities, it should be http://www.wikidata.org/prop/direct/P279

But there no RDF content obtained at this URL by content negotiation, only HTML is gotten: 

wget --save-headers --header='Accept: text/turtle' http://www.wikidata.org/prop/direct/P279

or 

wget --save-headers --header='Accept: application/rdf+xml' http://www.wikidata.org/prop/direct/P279
wget --save-headers --header='Accept: application/ld+json' http://www.wikidata.org/prop/direct/P279

My use case

I have a web tool that is completely generic about LOD data source , for example here is what I get from a Wikidata URI :

http://semantic-forms.cc:1952/search?q=http%3A%2F%2Fwww.wikidata.org%2Fentity%2FQ40044858

 – The preceding unsigned comment was added by Jmvanel (talk • contribs) at 07:55, 3 September 2018‎ (UTC).

Thanks to Mister Synergy for the Special:EntityData URL's , that are documented at the right place in the doc. https://www.wikidata.org/wiki/Wikidata:Data_access#Linked_Data_interface . This answers to the original question in the title.

However, there is still an issue with respect to Semantic Web good practices. Namely, that an URI should be dereferentiable and subjected to RDF/XML, Turtle, and HTML content negotiation . This indeed is the case for URL's with prefix http://www.wikidata.org/entity/ . But properties, as they are used in triples, are not. For instance, this entity http://www.wikidata.org/entity/Q1656682 uses a property with URL http://www.wikidata.org/prop/direct/P279 . But this latter URL only provides HTML, as demonstrated above. Instead, this well behaved URL should be used in Wikidata RDF data: https://www.wikidata.org/wiki/Special:EntityData/P279 . It is probably the same with every property; prefix should be used https://www.wikidata.org/wiki/Special:EntityData/ . But it would be probably more coherent if http://www.wikidata.org/entity/P279 would be used. It is also a well behaved URL prefix.

—MisterSynergy (talk) 09:04, 3 September 2018 (UTC)
The canonical URI for the property with ID P279 is just like the canonical URI for the item with ID Q42: http://www.wikidata.org/entity/P279, abbreviated wd:P279. wdt:P279 (…/prop/direct/P279) is just one of several predicates related to that property (there’s also /prop/, /prop/statement/, /prop/qualifier/value, etc.) – all of these predicates have different meanings, and we can’t just replace them all with the entity URI because that one happens to resolve better for certain use-cases. However, we can change the other URIs to be more well-behaved – I’ve filed phabricator:T203400 for this. --Lucas Werkmeister (WMDE) (talk) 14:33, 3 September 2018 (UTC)

Thanks for filing an issue, Lucas; since it's not clear to me , shall we continue discussion here or in phabricator:T203400 ?  – The preceding unsigned comment was added by Jmvanel (talk • contribs) at 17:21, 3 September 2018‎ (UTC).

@Jmvanel: I guess it’s easier to do it here, if you have any more comments. --Lucas Werkmeister (WMDE) (talk) 10:34, 4 September 2018 (UTC)

P248 instead of P143

Hi, I noticed that a large number of items use stated in (P248) to cite Wikipedias, instead of using imported from Wikimedia project (P143) just to notice that the information comes from there (unnecessary IMO if there exists a valid source). Wikipedias are not considered valid sources: Help:Sources#Different_types_of_sources. It was noticed in Greek Wikipedia that in relevant articles these wikipedias are cited in the references section through automated infoboxes. I believe that a bot that will change all these stated in (P248)English Wikipedia (Q328) to imported from Wikimedia project (P143)English Wikipedia (Q328) would be of great value. -Geraki (talk) 13:01, 3 September 2018 (UTC)

There are a little more than 14.000 of such references (query1, query2). I can fix them later this day. —MisterSynergy (talk) 13:17, 3 September 2018 (UTC)
All done now. The final ~200 cases where cluttered so much that I had to repair them manually after the bot did most of the work :-/ —MisterSynergy (talk) 22:54, 3 September 2018 (UTC)

It would be nice to make this a constraint violation for stated in (P248) P.a.a (talk) 15:59, 3 September 2018 (UTC)

Good work MisterSynergy! Thanks. -Geraki (talk) 16:36, 4 September 2018 (UTC)

Wikidata weekly summary #328

 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Final polishing on first version of Senses support for Lexemes. (phabricator:T201000, phabricator:T202729, phabricator:T198036, phabricator:T203334)
    • Continued work on merging Lexemes. Merging via the SpecialPage is done and will be rolled out soon. Merging via the API is still being worked on. (phabricator:T189129)
    • Long Lemmas in Lexemes look bad because they are not flowing to the next line and instead break the layout. Working on a fix. (phabricator:T195367)
    • Improving the validity of the HTML of the Lexeme headers. (phabricator:T196228)
    • Worked on showing the Lemma(s) or Representation(s) when Lexemes or Forms are mentioned in constraint reports. (phabricator:T195315)
    • Got a new beta feature ready for deployment that will improve the suggestions for properties like sex/gender by first suggesting the values defined in the one-of constraint. (phabricator:T202712)

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.


Starting Wikidata Query Library

Yes we have Query Examples but it is a very good idea to start a Portal or Libaray that store all kind of queries sorted by subject, Category etc.. and Featured query, Start your first query, New queries, Request for a query etc.. Can we do a query contest? --Ranjithsiji (talk) 10:29, 4 September 2018 (UTC)

There's a parallel discussion on Facebook, where a Query: namespace has been proposed, with one query per page, using Wikipedia- (or Commons-) style categories to aid findability. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:59, 4 September 2018 (UTC)
Not sure if this has been raised elsewhere, but a "Query" namespace has been part of Wikidata for a long time - but it's unused because the original approach to querying was abandoned in favor of the SPARQL service we have now. See this page for some details and links; you can also see a trace of the Query namespace when you do an advanced search, it's one of the options (but there's nothing there). ArthurPSmith (talk) 17:50, 4 September 2018 (UTC)

Do you speak German/French? Help WLM 2018 Switzerland!

Hello guys!

Do you see these giant "de" and "fr" bubbles? If you understand German/French, you can be very useful in helping Wiki Loves Monuments in Switzerland in translating as monuments as possible in English. We want to see the "en" bubble growing!

Even providing an English label to just 2-3 monuments will be very appreciated... but pay attention: it's a drug! :^) Thanks you everybody and have fun! --Valerio Bozzolan (talk) 15:16, 4 September 2018 (UTC)

Implementation of a new Wikidata-to-OSM service for P402

Please, do you support the implementation of a new Wikidata-to-OSM service for OpenStreetMap relation ID (P402)?

Explaining. The new service will solve the cited problem of "only relations": will be possible to link OSM Map Features represented by nodes or ways.

The new server must be hosted at the Openstreetmap-side, but needs the support of the Wikidata community also. The service will redirect Wikidata item "Q" identidiers by http://osm.org/Q$1 (or wikidata.osm.org or other) to the respective geometry. Examples:

  • Relation. The Wikidata item that represents the concept of the country Brazil (Q155), on OSM is a relation,
      http://osm.org/Q155 will redirect to https://www.openstreetmap.org/relation/etc
  • Way. The Wikidata item that represents the concept of the Fraternity Bridge (Q2679759), on OSM is a way,
      http://osm.org/Q2679759 will redirect to https://www.openstreetmap.org/way/etc
  • Node. Wikidata item of the Number zero survey marker of the city of São Paulo, (Q10325364), on OSM is a node,
      http://osm.org/Q10325364 will redirect to https://www.openstreetmap.org/node/etc

See more details at the wiki.openstreetmap.org Proposal-QID. --Krauss (talk) 13:39, 29 August 2018 (UTC)

@Samwilson: You can indeed use toolforge:hub to generate URLs to OSM relations from Wikidata IDs (example: https://tools.wmflabs.org/hub/Q155?property=P402 ) but it doesn't work for ways or nodes as we don't have properties for those (right?). Note that if we had those properties, the link could simply include the different possible properties (example: https://tools.wmflabs.org/hub/Q155?property=P402,PXXXX,PYYYY )-- Maxlath (talk) 11:11, 5 September 2018 (UTC)
  • I don't really understand what this is intended for. What does it have to do with OpenStreetMap relation ID (P402)? What will you do when multiple OSM objects have the same Wikidata ID? Personally I would really like to see OSM support searching by Wikidata IDs, so that we can enter Qxxx or wikidata=Qxxx into the search box, that would give us short copyable URLs as a side effect. - Nikki (talk) 12:47, 30 August 2018 (UTC)


The OSM assumption that Wikidata Q-numbers represent "unique and eternal" identifiers for their objects is blatantly wrong. That's why they need to implement unique IDs for their elements, so we can manage the links to their elements from within Wikidata. This issue concerns for example all the items of museums, archives, libraries, cultural venues and the like which confound the geographical object and the organization. This typically is the case for Wikidata items that were created based on Wikipedia entries and their categories (i.e. tens of thousands of items). On Wikidata, we will end up disentangling these items and their statements, which will "break" the OSM-WD link that they have set on the OSM side with 50% probability. That's why we should be able to assign the OSM-ID explicitly on the WD-side and have an automatized service in place that handles the discrepancies between OSM and WD whenever objects and identifiers get moved around on the WD or the OSM side. --Beat Estermann (talk) 13:53, 30 August 2018 (UTC)
@Beat Estermann: "unique and eternal" is indeed strange but I'm not sure it's « blatantly wrong ». At least a Qid is unique, that's for sure and most of the item it's perennial (but indeed not eternal), especially if you keep in mind that OSM have current objects.
For the GLAMs who are a geographical object and organization, that's why I'm often creating two items, one for each (and I do the same on OSM too). Or splitting when there is only one item and I need to put separate informations (typically for inception (P571) who is the date of construction in the context of a building and the date of creation for an organisation).
For assigning from the WD side it would be ideal, but how to do? As a reminder, when you edit an OSM object, the identifier can change too (which is quite painful... in this sense, it's very understandable than an OSMer thinks that Qid are "eternal").
Cdlt, VIGNERON (talk) 19:23, 30 August 2018 (UTC)
Using Wikidata IDs on OSM objects is the currently best way to guarantee a link between OSM objects and Wikidata concepts. The 'burden' of maintenance is on editing the OSM objects, like it is done for transit relations. OpenStreetMap relation ID (P402) is not the best way to have a permanent correlation because also relations can break and change ids in OSM. The "permanent id" discussion can be solved by a service, yes, but to actually solve it the service would need to be as much automatic as possible, otherwise it's simply a case of moving the problem around. Perhaps the OSM API can be extended to deal with this. --Sabas88 (talk) 09:14, 4 September 2018 (UTC)

Is it possible to add ebird data to Wikidata?

Hello everyone, eBird is a website by Cornell Lab of Ornithology. eBird has a lot of data about birds. If we can able to add them to Wikidata it would be a great achievement for the birders. Because through query service we can find exactly how many number of birds found (from eBird checklist) in this area in so and so the duration of time. I had shared this with Ijon. He suggested me to write here and ping Pigsonthewing. Let me know if it is possible. I can write to contact Cornell Lab also. --Gopala Krishna A (talk) 03:56, 4 September 2018 (UTC)

Note we have eBird taxon ID (P3444) and eBird hotspot ID (P5200) which can link wikidata items to the eBird website (and about 13,000 taxa have already been linked). Pulling in all their data is beyond the scope of Wikidata; it may also not be legally allowable - I couldn't find a rights statement on the eBird site, but Wikidata data is CC-0 so the licensing would need to be compatible. I'm also not sure the data structure of this site is right for this kind of information - you would presumably have to create a statement on each bird item for every observation (with location, date, count)? This might be something that could be done via tabular data in Commons however. ArthurPSmith (talk) 13:10, 4 September 2018 (UTC)
Further to Arthur's very good reply; there's not much point in us trying to replicate what eBird do. In time, it's to be hoped that services like eBird will see the value in making their data available as linked-, open-, data, and providing a SPARQL end-point, so that people can make federated (combined) queries across their database and ours. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:41, 4 September 2018 (UTC)
Thanks everyone for your valuable time and reply. I would also recommend eBird to start a SPRQL based query search on their website. --Gopala Krishna A (talk) 08:03, 5 September 2018 (UTC)

contains administrative territorial entity: value type constraint

Hello. Limassol Municipality (Q28870916) -> contains the administrative territorial entity (P150). It shows value-type constraint (Q21510865). Before some time, there was not such problem. I guess something changed with the value of a property of Quarter of Limassol Municipality (Q29463880). Like third-level administrative division (Q13221722) or third-level administrative division (Q13221722) or about an item which those two are subclass. Because I have created many items for third-level administrative country subdivision for Cyprus, I want to know what to do, so the structure will be correct. Xaris333 (talk) 09:47, 5 September 2018 (UTC)

@Jura1: thanks. But how can I connect Quarter of Limassol Municipality (Q29463880) with Limassol Municipality (Q28870916)? I did it with located in the administrative territorial entity (P131) but I get item-requires-statement constraint (Q21503247). Xaris333 (talk) 11:31, 5 September 2018 (UTC)

  • Maybe the "designation"-P31 should be used there .. Also, I don't think P131 should be used for that. I changed it to "part of". --- Jura 11:35, 5 September 2018 (UTC)

Ok for part of, but I don't think P31 -> administrative territorial entity type (Q15617994) is correct. Xaris333 (talk) 12:34, 5 September 2018 (UTC)

Please Merge

10 minutes in and I'm still at a loss trying to learn how to easily merge two items. This is my first time using or even looking at WikiData and I'm not even sure if I'll return and I hope you'll forgive my laziness. Someone please merge Karlis Johansons (Q56226186) with Kārlis Johansons (Q1387109). I created the English stub using Google Translate from the Latvian stub. Thanks in advance. ~ JasonCarswell (talk)

Already done by Mahir256. --Liuxinyu970226 (talk) 10:44, 11 September 2018 (UTC)
This section was archived on a request by: Liuxinyu970226 (talk) 10:44, 11 September 2018 (UTC)

Sourced invalid statements

I have seen many cases like this: https://www.wikidata.org/wiki/Q384813#P131

Obviously Acropolis of Athens (Q131013) is not an administrative unit. But there is a reference for this statement, although not an authoritative one: https://www.archinform.net/projekte/3921.htm . In fact even the source does not support the claim, it lists the Acropolis as "sonstige Fläche" (to my understanding it means "other"?) Another example would be the statement that an uninhabited islet is a "settlement" just because it is included in census records with 0 population (in fact that would be proof that it is not a settlement). What do you think about the removal of sourced statements that contradict themselves, other sources or common sense? -Geraki (talk) 17:05, 4 September 2018 (UTC)

I guess the statement with P131 should be

. Xaris333 (talk) 09:53, 5 September 2018 (UTC)

Nope, that is still a neighborhood. Administrative units in Greece start at the municipality level. -Geraki (talk) 20:41, 5 September 2018 (UTC)
Then
Xaris333 (talk) 22:02, 5 September 2018 (UTC)

About the 0 population: if an administrative territorial entity has 0 popolulation, is not a problem. The administrative territorial entity is still exist as a legal entity, even thought no one is living there at the moment. Xaris333 (talk) 09:52, 5 September 2018 (UTC)

I am sure I did not use the wording "administrative territorial entity" but "uninhabited islet" and "settlement" (which by definition means an inhabited/populated location). A location with no population presently and in the past, is by definition not a human settlement (Q486972)... -Geraki (talk) 20:41, 5 September 2018 (UTC)
You spoke about settlement that it is included in census records with 0 population. I didn't know that countries use no administrative territorial entities at their census. Usually a municipality is slpited to quarters, parishes, etc... Xaris333 (talk) 22:05, 5 September 2018 (UTC)
The U.S. uses many non-administrative places in their census. See en:Census-designated place. - Jmabel (talk) 04:28, 6 September 2018 (UTC)
I spoke about uninhabited islet that it is included in census records with 0 population, and the conception it is a human settlement (Q486972) (which is not an "administrative territorial entity" per se). There may be some administrative territorial entities called "settlements" in some countries but that would be different items. Do not forget that there are settlements that are not included individually in census records but they are still settlements, and the concept of "administrative entities" is somehow modern and with completely different scope from the common definition of human settlement (Q486972). -Geraki (talk) 08:24, 6 September 2018 (UTC)

Odd identifier, how to do it

There is a proposal for an odd numerical identifier. It is odd because it is used, but it can't be used in an URL in the usual way.

The proposed identifier is Wikidata:Property proposal/Norwegian war refugees register ID. The ids are numbers assigned to war refugees in Sweden during WWII. The best source for them are at Arkivverket Digitalarkivet: Den Kgl. Norske Legasjons Flyktningskontor*, but that is an archive of scanned papers. That is, plain old paper trail. Some pointers; National Archives of Norway (Q6516420), and Digital Archives (Q11154625).

I wonder if this is a kind of identifier that lacks an inherent source, but can be given a source. To make an example; Norwegian war sailor register person ID (P4972) has an inherent source as it can create links by using formatter URL (P1630), that is https://www.krigsseilerregisteret.no/no/sjofolk/$1. The Norwegian war refugees register ID would not be able to use a link like that, but it can use an "URL-source" that points to a source property. That URL-source can then be appended a hash (#) and the identifier, like described for "cool URIs".[1]

For an entry about "Fjellbu, Arne" we would then give a source URL as https://media.digitalarkivet.no/view/43434/194, which would then be used to rewrite the for the identifier like [https://media.digitalarkivet.no/view/43434/194#32915 32915](or simply 32915). We link to the source, but only add the id as a fragment identifier. In the general case we must probably adjust the link somewhat because there might be specific anchors we would like to hit.

I believe this could solve a lot of similar problems, without to much clever hacks, but the problem remains – shall we do it? Perhaps there is already a better way to do it? Jeblad (talk) 19:05, 5 September 2018 (UTC)

Read-only mode for up to an hour on 12 September and 10 October

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

The Wikimedia Foundation will be testing its secondary data centre. 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 to the secondary data center on Wednesday, 12 September 2018. On Wednesday, 10 October 2018, they will switch back to the primary data center.

Unfortunately, because of some limitations in MediaWiki, all editing must stop when we switch. 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 Wednesday, 12 September and Wednesday, 10 October. The test will start at 14:00 UTC (15:00 BST, 16:00 CEST, 10:00 EDT, 07:00 PDT, 23:00 JST, and in New Zealand at 02:00 NZST on Thursday 13 September and Thursday 11 October).
  • 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.
  • There will be code freezes for the weeks of 10 September 2018 and 8 October 2018. Non-essential code deployments will not happen.

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. Please share this information with your community. /User:Johan(WMF) (talk)

13:33, 6 September 2018 (UTC)

Please split and merge

I guess that Q54859371 should be split and some part merge/move with Q54006375 or Q48246688. And maybe deleted, see w:en:Wikipedia:Articles for deletion/MJ Tamondong and w:en:Wikipedia:Sockpuppet investigations/Matrix 2. Visite fortuitement prolongée (talk) 20:37, 10 September 2018 (UTC)

Probably best to delete all three, I think. Andrew Gray (talk) 21:08, 10 September 2018 (UTC)
  Done Mahir256 (talk) 21:30, 10 September 2018 (UTC)
This section was archived on a request by: Visite fortuitement prolongée (talk) 20:40, 12 September 2018 (UTC)

Why does this not work?

The collection list Wikidata:WikiProject sum of all paintings/Collection/Shchusev State Museum of Architecture doesn't work. There are items in the Museum, see Q56596912 or Q56596977.--Carl Ha (talk) 08:19, 12 September 2018 (UTC)


This section was archived on a request by: --- Jura 10:07, 12 September 2018 (UTC)

Revert merge

Can someone revert my item merge? https://www.wikidata.org/w/index.php?title=Q14125305&type=revision&diff=744952190&oldid=653892941 Ilham151096 (talk) 08:20, 12 September 2018 (UTC)

This section was archived on a request by: --- Jura 10:01, 12 September 2018 (UTC)

Hi could you please remind me what is the standard procedure when I need to merge items such as Q2557858 and Q21162042? Shlìuld I remove the link to the category, keep the gallery in the final item.

Please consider that the majority of it-N users are quite practical nowadays, they basically avoid the creation of galleries on commons, they consider them difficult to update and time consuming, if they invest on something are the categories so most of the work of improvement of local items ends up connecting to commons categories.--Alexmar983 (talk) 19:24, 24 August 2018 (UTC)

If there's a Commons gallery, sitelink to it from the main item.
If there's also a Commons category, create a separate item for it with a label starting "Category:", and relate it to the first item by category's main topic (P301)/topic's main category (P910) in each direction.
Also add Commons gallery (P935) statements on both items linking to the Commons gallery, and Commons category (P373) statements pointing to the Commons category. On most Wikipedias, the software will follow these, in preference the sitelinks, so adding the P373 will be enough to make the sidebar link point to the Commons category.
On the Commons category, use c:Template:Wikidata infobox to create an infobox. This should automatically follow the sitelink and then the P301 to draw data from the main item.
A bit of a chore, yes; but it's the system we've come to, and it seems to work reasonably enough.
If there is no Commons gallery, and there is no category item already in existence (eg linked to a Wikipedia category, or to a category on a sister project), then it is acceptable to follow the simpler strategy of linking the Commons category straight to the main item. But this should be done only when the two conditions above are met; otherwise the full rigmarole as previous described is necessary. Jheald (talk) 23:11, 24 August 2018 (UTC)
Creating a new item for the category, with only a Commons sitelink, isn't permitted by Wikidata:Notability. It would be better to keep the category sitelink than replacing it with the gallery, in my opinion. But we've been through all this: I suggested a new policy of giving Commons sitelinks priority over galleries. But people said why not just make a category item for the sitelink, and if the notability policy forbids it, change the policy. So I proposed changing the notability policy, but it got no consensus. Ghouston (talk) 01:22, 25 August 2018 (UTC)
That restriction in WD:N is history. We now have thousands of items with just a wikilink to a Commons category, supporting an infobox there, and nobody is going to delete them. WD:N hasn't been changed yet, but the clause has a footnote noting that its continued application is questionable and pointing to open discussion on the talkpage. In practice the restrictive clause is dead, the message just hasn't reached the brain yet. Jheald (talk) 08:28, 25 August 2018 (UTC)
ok but this is getting confusing. I mean, I need to give newbies very clear tasks. And from this point of view, as long as the information is clear it can always be fixed later by bot. In any case the level of sophistication required by current users is increasing. They expect wikidata infobox and structured data more and more. So just to clear, current consensus is that i put the gallery not the category in the "other projects" section and I don't merge?--Alexmar983 (talk) 19:47, 25 August 2018 (UTC)--Alexmar983 (talk) 19:47, 25 August 2018 (UTC)
The two items you mentioned should be merged, since neither is a category item. Personally, I'd just leave the Commons category sitelink in place and add a Commons gallery (P935) statement for the gallery. Ghouston (talk) 00:11, 26 August 2018 (UTC)
The gallery hadn't been properly updated since 2011 (and only had low-resolution images when more + higher resolution ones were in the category), so I've redirected it to the category and merged the two items. thanks. Mike Peel (talk) 17:38, 26 August 2018 (UTC)
Wikidata infobox has a "qid" attribute which allows to draw in the information from whatever data item you assign it. I have used it on several categories leaving the link open for a gallery if and when they exist. It fixed a problem at source where the template assumes the link is a gallery and also pulls in the category if it is assigned. Since then, a bot has come through and re-assigned the link to the category and it is (as far as I know) simply not needed and ugly at source. It is an old and unnecessary war which I personally will defer to the gallery makers because the good galleries take a lot more work. The galleries with only one little fuzzy image on them are, I think, a response to being told to make the gallery, where the nice galleries are made out of choice and inspiration. Please leave this war with the galleries being the "winner". Also, the Category hack was beautiful, it worked just fine but I am not happy with the additional data entry when software can handle it just fine as it is. Having to choose gallery or category is a terrible thing. I did it a few times and I did not like it.--RaboKarbakian (talk) 20:49, 1 September 2018 (UTC)
There is w:Raising the Flag on Iwo Jima and c:Category:Raising the Flag on Iwo Jima on Q117693. Now I created c:Raising the Flag on Iwo Jima but interwiki doesn't work. If I change the sitelink I'll break the Wikidata infobox I think. @Mike Peel: now what? Alexis Jazz (talk) 16:00, 7 September 2018 (UTC)
@Alexis Jazz: It looks like you created a page that should be in the Commons: namespace, not a gallery. Most of it is about the copyright status, and the part that is a gallery does not look useful to me. So I'd suggest moving it to c:Commons:Raising the Flag on Iwo Jima, and maybe creating a new item here with instance of (P31)=Wikimedia project page (Q14204246). Thanks. Mike Peel (talk) 16:24, 7 September 2018 (UTC)
@Mike Peel: I wasn't sure if it should be in the Commons or gallery namespace. It doesn't really answer the question of what to do with gallery pages. Wikidata infobox needs the sitelink, so a gallery can never be sitelinked? Alexis Jazz (talk) 16:35, 7 September 2018 (UTC)
Personally, I'd first ask whether the gallery is actually useful, or if it should just be deleted/redirected to the category. If it is useful, then create a new item with instance of (P31)=Wikimedia category (Q4167836), set category's main topic (P301) and topic's main category (P910) to link the two items, move the category sitelink to the new category item, and add the gallery sitelink to the item. Thanks. Mike Peel (talk) 16:38, 7 September 2018 (UTC)

Wikidata item popup preview does not work?

I put my mouse on an link to an wikidata item, but in the preview window, what it show is only https://i.imgur.com/UlIw6AJ.png . What's wrong with it?C933103 (talk) 04:32, 1 September 2018 (UTC)

Which gadget does this? Matěj Suchánek (talk) 10:01, 3 September 2018 (UTC)
MediaWiki:Gadget-popups.js ? C933103 (talk) 11:43, 7 September 2018 (UTC)

Biome

Do we have a property to indicate the biome (Q101998) or ecosystem associated with a place (park, nature preserve, or any similar)? I'd like to indicate that the biome found at Konza Prairie (Q6430461) (<instance of> research station) is tallgrass prairie (Q7680132). If not, I'll propose a new property for "biome, ecosystem, or habitat". - PKM (talk) 20:30, 6 September 2018 (UTC)

Javascript hooks are now stable

Hello all,

In order to allow better gadget integration, JavaScript hooks documented in the hooks-js.txt file delivered together with Wikibase source code are considered stable. We just added this information in the stable interface policy.

If you have any question about this, feel free to ping me. Lea Lacroix (WMDE) (talk) 16:22, 7 September 2018 (UTC)

Lua error

I created this property proposal page, but it gives me this Lua error: Lua error in Module:Property_proposal at line 219: bad argument #1 to 'gsub' (string expected, got nil). Why? --Malore (talk) 18:30, 10 September 2018 (UTC)

Fixed.--GZWDer (talk) 19:38, 10 September 2018 (UTC)
This section was archived on a request by: Matěj Suchánek (talk) 08:47, 13 September 2018 (UTC)

Renaming of wikidata element needed

Hi everyone,

I didn't manage to do it myself neither to find where to file a request for renaming. The issue is explained here, the wikidata element Q17269 should be reverted to its original name (Tibet Autonomous Region) to avoid confusion with element Q17252 (Tibet). Thanks for any support. --Dominique Roux (talk) 19:11, 12 September 2018 (UTC)

Sorry, the title seems to have changed automatically after editing the English label, it just needed some time to reflect the change. Now item Q17269 appears as Tibet Autonomous Region, problem solved.--Dominique Roux (talk) 19:17, 12 September 2018 (UTC)
This section was archived on a request by: Mbch331 (talk) 09:03, 13 September 2018 (UTC)

changed name

What can he do? Regards, Conny (talk) 19:57, 7 September 2018 (UTC).

Q7542#P1828 and Property:P1828#P2302 (add all three and a constraint exception) —MisterSynergy (talk) 20:28, 7 September 2018 (UTC)

Q355304 class hierarchy

watercourse (Q355304)

According to @Мастер теней:, a watercourse should be directly a subclass of body of water (Q4114033), omitting the previously used body of water (Q15324) intermediate step. I don't see where is the actual difference between these two concepts anyway, I only noticed it because this change breaks many constraints which rely on Q15324. Can someone who is more fluent in the ontology concept have a look into this? Ahoerstemeier (talk) 23:25, 7 September 2018 (UTC)

How to model a museum label as a reference?

How should I model a museum label (Q6940727) as a reference? Using stated in (P248): museum label (Q6940727) raises a violation of this value type constraint because museum label (Q6940727) isn't an instance but a class and I don't plan to create an item for each museum label. Change the constraint? Any ideas? Thanks a lot in advance! --Marsupium (talk) 08:18, 14 September 2018 (UTC)

Maybe use the item for the museum itself for the value of stated in (P248), and maybe add a quote with the label text. Using museum label (Q6940727) as the value would be like using book (Q571), not very specific. Ghouston (talk) 08:40, 14 September 2018 (UTC)
I suppose a museum may not be an acceptable value either. Ghouston (talk) 08:40, 14 September 2018 (UTC)
@Ghouston: Hm, okay, both does not seem to fit too well. Perhaps one could indicate the location somehow? Or we need a property like "source is instance of"? --Marsupium (talk) 15:27, 14 September 2018 (UTC)
Haha, #Tombstone as information only three sections beneath this gives the solution: type of reference (P3865). Continuing there … --Marsupium (talk) 15:53, 14 September 2018 (UTC)
This section was archived on a request by: Marsupium (talk) 15:53, 14 September 2018 (UTC)

Just a reminder that links to Wiktionary pages in the main namespace are disallowed on Wikidata. Please remove those which you have already added, whether to items about Hangul syllables or to other items, and do not add any more until that restriction is lifted, if that restriction is ever lifted someday. Mahir256 (talk) 19:30, 31 August 2018 (UTC)

@Mahir256: Thanks for the reminder. These statements have been removed. @Okkn: I think an exception should be made for Unicode characters to be linkable to Wiktionary pages. This could be discussed by the administrators. Wiktionary contains descriptive information and users may visit it for more information. KevinUp (talk) 19:48, 31 August 2018 (UTC)
@Mahir256: I understand we usually don't add sitelinks to Wiktionary pages in the main namespace, because they are not concepts, but is it really not allowed to add Wiktionary sitelinks? I think WD:N just says Wiktionary sitelinks are not valid to fulfill the notability criteria, but does not say we must not add Wiktionary pages to already created items, right? When it comes to Unicode characters, including Hangul syllable (Q55809450) and sinogram (Q53764738), they are clearly notable by themselves, and they are concepts rather than representation. Or if we add sitelinks to Wiktionary pages, the function of mw:Extension:Cognate does not work...? --Okkn (talk) 01:30, 1 September 2018 (UTC)
That makes sense. If links to Wiktionary pages are disallowed on Wikidata, then the input box that allows users to add Wiktionary links should be removed from Wikidata. KevinUp (talk) 05:09, 1 September 2018 (UTC)
The restriction only applies to Wiktionary pages in the main namespace, as I stated initially; links to categories/templates/Wiktionary: pages/etc. (except those in the citation, user, and all talk namespaces) are allowed. Mahir256 (talk) 21:15, 1 September 2018 (UTC)
This is a matter for the community at large to decide; not just administrators. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:43, 2 September 2018 (UTC)
Is it possible for us to take a vote regarding this matter? KevinUp (talk) 16:43, 2 September 2018 (UTC)

The discussion above was from my talk page. I wish to gain wider consensus regarding this matter. As mentioned by User:Okkn, Unicode characters such as Hangul syllable (Q55809450) and sinogram (Q53764738) are clearly notable by themselves, and are concepts rather than representation. Does this affect the function of mw:Extension:Cognate? KevinUp (talk) 08:18, 2 September 2018 (UTC)

Also, I have begun to link Unicode characters on Wiktionary to Wikidata. Wikidata is useful for obtaining structural data regarding Unicode characters while Wiktionary is useful for obtaining the meaning and usage of Unicode characters. KevinUp (talk) 08:18, 2 September 2018 (UTC)

WD:N state that the reason why wiktionary pages are excluded because wiktionary interlanguage links are done by Extension:Cognate with the reason on the extension page saying that the use of this extension is because wiktionary links are based on homograph, not concept. However, this assessment does not apply to each individual Unicode characters, since each individual Unicode characters are a concept in themselves, with many different data for each individual unicode code points. Especially for Pan-CJK characters. You can click into any wiktionary page about each individual CJK characters page and see how many values there that can be stored centrally, and there's even a non-WMF wiki known as glyphwiki that store even more info about individual CJK character codepoints. Because of such a number of data that can be centrally managed at wikidata, and because each Unicode code point are representing the same, single concept of a single Unicode code point instead of being merely homonym, I suggest changing the policy to allow the storage of those data within wikidata. C933103 (talk) 14:31, 2 September 2018 (UTC)

Well said indeed. Recently, Wikidata:WikiProject CJKV character has been created to provide structural data for the 88,889 CJKV characters available in Unicode 11.0. Prior to this, only a small number of Unicode items exist. For comparison, please compare 雨 (Q3595028) with wikt:雨. KevinUp (talk) 16:43, 2 September 2018 (UTC)
I believe the restriction was a request from the Wikidata developers, not something that community consensus can address. @Lea Lacroix (WMDE), Lydia Pintscher (WMDE): can you comment? ArthurPSmith (talk) 12:38, 4 September 2018 (UTC)
The reason we asked for this is that we have seen a huge amount of confusion because people didn't understand the difference between concepts and words - in essence the difference between Items and Lexemes here. Often it is not understood how the linking done in Wiktionary's main namespace is different from the one in Wikipedia's main namespace for example. Now there might be rare cases where it still makes sense to add Wiktionary main namespace pages to items as sitelinks. (And the one you mention here looks like it might be one of them.) For those it is totally fine to make an exception from my side. --Lydia Pintscher (WMDE) (talk) 19:28, 5 September 2018 (UTC)

Another type of wikidata concept that I believe should have wiktionary links: chengyu (Q28060424)+yojijukugo (Q7010524)+Sajaseong-eo (Q17017012) (actually why is there at least three different wikidata item for same thing that exists in different language/geographical area), with examples like Q5356314. C933103 (talk) 14:22, 9 September 2018 (UTC)

Item merger

Hi,

I think I spoted two idems which should be merged, but don't know how to do it. I'm basing this on the fact that the Wikipedia pages are about the same topic. I assume that it got fragmated at some point.

If someone could smush these two togeter it would be helpful. Thanks.

--2A00:EE2:204:7500:D461:77CF:8760:7131 19:40, 3 September 2018 (UTC)

Silver tax 1816

What property should be used to indicate that a person contributed to the Silver tax 1816 (Q25429073). I can find participant in (P1344), subject has role (P2868), sponsor (P859) and may be contributor to the creative work or subject (P767). Making this diffcult is that it was a forced tax and I can not see that the Properties mentioned will cover a forcement.

The Silver Tax 1816 was established by the newly created independent Norwegian state (1814). It is a common name for the compulsory deposit, which was issued in 1816, to acquire a foundation fund of 2 million specidaler for the newly created Norges Bank (Q970769). Pmt (talk) 06:05, 8 September 2018 (UTC)

Open Location Codes aka Plus Codes

Is wikidata has a P for Open Location Codes. Any license or compatibility issues with that ? Can we incorporate that ? --Ranjithsiji (talk) 06:51, 8 September 2018 (UTC)

We had a discussion about Plus codes earlier this year but there was no consensus to create a property for it, see Wikidata:Property proposal/Plus codes --Pasleim (talk) 12:13, 8 September 2018 (UTC)
Perhaps a gadget that supplemented the coordinate entry box with a conversion tool from Plus codes back to WGS84 coordinates would be a nice little task for the Code-In? (Similarly for what3words codes or other sorts of coordinate references?) Mahir256 (talk) 22:09, 9 September 2018 (UTC)
I support @Mahir256: it is a necessary one. How we can implement that. --Ranjithsiji (talk) 05:38, 10 September 2018 (UTC)

Puerto Rican nationality

Today, I have removed the country of citizenship property on many Puerto Rican people items, because they wrongly value "Puerto Rican" as the nationality, but it should be "American". AFAIK, Puerto Ricans are citizens of the U.S, althought to get real citizenship (such as voting) they must live in the mainland. When valued "Puerto Rican", the property displays a message error. There must be many more items with this mistake, and I think a bot could easily fix them. Esteban16 (talk) 00:20, 30 August 2018 (UTC)

Ghouston: That is a good idea, too. And yes, they had Spanish citizenship for a while. The Jones–Shafroth Act granted Puerto Ricans American citizenship on 1917. Esteban16 (talk) 02:07, 30 August 2018 (UTC)

@Esteban16: However, according to Wikipedia article w:en:Puerto_Rican_citizenship, "The United States government also continues to recognize a Puerto Rican nationality". @Ghouston: I don't think it is a must for everyone with Puerto Rican nationality to keep living in Puerto Rico? C933103 (talk) 02:25, 30 August 2018 (UTC)

  • It's definitely not "a must". I would think Puerto Rican citizenship should be recorded in Wikidata, although possibly (from 1917 onward) in conjunction with U.S. citizenship. Jmabel (talk) 03:29, 30 August 2018 (UTC)
Then it seems removing the property from some items was wrong, and I think as same as User:Jmabel, the nationality should be recorderd. Esteban16 (talk) 11:04, 30 August 2018 (UTC)
w:en:Puerto_Rican_citizenship is a seriously flawed article, and should be ignored. I don't know what the situation is for Puerto Rico citizenship (if it currently exists), but for US states, the 14th Amendment to the United States Constitution states in part "All persons born or naturalized in the United States, and subject to the jurisdiction thereof, are citizens of the United States and of the State wherein they reside." So if a US citizen resident permanently moved from Puerto Rico to a state, she would become a citizen of that state. If a US citizen resident of a state permanently moved to Puerto Rico, he would cease to be a citizen of the state. Citizenship in a state is not a nationality. Jc3s5h (talk) 13:07, 30 August 2018 (UTC)
@Jc3s5h: You are certainly right about the states here, but I believe you are wrong about Puerto Rico (which is not a state). I believe someone born in Puerto Rico retains Puerto Rican citizenship even if they leave (while also being a citizen of any U.S. state they may reside in), and in particular this is relevant to the Spanish recognition of Puerto Rican citizenship. Do you have any citation to the contrary? - Jmabel (talk) 15:16, 30 August 2018 (UTC)
Jmabel, I do not have sources concerning Puerto Rican citizenship. But of course the burden of producing reliable sources falls upon those who want to state a claim in Wikidata; it is not the responsibility of other editors to disprove claims which lack such sources. Jc3s5h (talk) 15:30, 30 August 2018 (UTC)
https://aldia.microjuris.com/2013/08/30/la-eficacia-y-alcance-del-certificado-de-ciudadania-puertorriquena/ (in Spanish, cited in the English-language Wikipedia article) looks pretty solid to me. There is a specific certificate of Puerto Rican citizenship, and rights to favorable status for gaining Spanish citizenship based on place of birth being Puerto Rico (not needing to renounce prior citizenship) or any other Ibero-American territory. The portion there about "naturales de Puerto Rico estamos incluidos" suggests strongly (though it doesn't state outright) that this would be about place of birth rather than place of residence, so a different criterion than a U.S. citizen becoming a de jure citizen of whatever state they reside in.
I don't have time right now to check out every source of the en-wiki article; do you have specific claims there that you doubt? "...is a seriously flawed article, and should be ignored" is a pretty vague critique, and does not leave me a lot to respond to, short of researching or re-researching an entire article myself. - Jmabel (talk) 20:49, 30 August 2018 (UTC)
Unfortunately I don't speak Spanish. When I read some of the English sources from the article, the sources seemed biased toward a considerable degree of separation between Puerto Rico and the rest of the United States, and didn't seem to clearly support the claims that were just before the footnotes. After I wrote my comment above, I located the current directions (written in Spanish) from the Puerto Rican government to apply for a Puerto Rican certifiate of citizenship. I ran it through Google Translate, and the gist of it sees to be that a US citizen who was born in Puerto Rico, or a US citizen who was born elsewhere but has lived in Puerto Rico for at least one year immediately prior to applying, is eligible for the certificate. Jc3s5h (talk) 00:02, 1 September 2018 (UTC)
And apparently any benefits that Puerto Ricans may obtain in Spain are limited to "natural born" citizens of Puerto Rico, not just any US citizen who spends a year there. Ghouston (talk) 04:41, 1 September 2018 (UTC)
@Ghouston: That is correct. I hadn't realized that you could get the certificate just by being resident, so this may work out differently than I thought: if it provides no information beyond place of birth, it's less relevant. Not stated in the article I had cited, and I hadn't tried following up a ton of sources. Probably should be clarified in the en-wiki article. - Jmabel (talk) 16:14, 1 September 2018 (UTC)
@Jc3s5h: Thank you for now bringing up something substantive, rather than just a claim that the en-wiki article is crap. - Jmabel (talk) 16:14, 1 September 2018 (UTC)
There are also plenty of references in that Wikipedia article supporting what the article describe.C933103 (talk) 22:10, 30 August 2018 (UTC)

Please don't try to standardize for the sake of standardizing. As Puerto Rico doesn't really fit the traditional categorization of sovereign states and nationalities, it is unhelpful to make a blanket rule on whether Puerto Ricans should be recorded as having Puerto Rican citizenship or U.S. citizenship. If in conflict, consult biographical sources about the person. Deryck Chan (talk) 22:26, 30 August 2018 (UTC)

Deryck Chan, people raised in Puerto Rico are commonly referred as "Puerto Rican", regardless if they live there or not (i.e. Ricky Martin), and without providing a nationality in the case they reside in Puerto Rico. Esteban16 (talk) 00:00, 31 August 2018 (UTC)
That's also the case for a lot of places without official citizenships, like Scotland and Tasmania. Ghouston (talk) 04:32, 31 August 2018 (UTC)
Except it's more like sub-sovereign entities like Jersey and Hong Kong, where citizenship of these entities is legally recognised as a different kind of citizenship from citizens of the main country of that sovereign state that holds it. It's a different class of citizenship and it would be against the principle of original research if we refuse to recognise these citizenships categories. Deryck Chan (talk) 09:20, 31 August 2018 (UTC)
This has been discussed enough but no solution has been provided. According to the property, the statements could be a state, a nation or a fictional country. It seems Puerto Rico does not belong to any of them, and I think it should not be considered a nationality, as they are American citizens. If we are not agree about this, then consensus should be made. The property currently has issues in all those items, and it should be fixed ASAP. Esteban16 (talk) 22:33, 31 August 2018 (UTC)
From the article, it seems like one can at the same time be an PR citizen & US citizen & PR national & US national.C933103 (talk) 11:34, 1 September 2018 (UTC)
May I presume that "fictional county" above means to say "fictional country"? - Jmabel (talk) 16:18, 1 September 2018 (UTC)
Yes, Jmabel, it was a mistake. Esteban16 (talk) 16:26, 1 September 2018 (UTC)

Most of us agree with the fact "Puerto Rican" is not a nationality. Then, should I proceed with requesting the bot task to remove the property from the items? Or, should it belong to the property? Esteban16 (talk) 18:36, 2 September 2018 (UTC)

@Ghouston, C933103, Jmabel, Jc3s5h, Deryck Chan: Pinging users who participated in the thread. Esteban16 (talk) 01:06, 3 September 2018 (UTC)
I don't see why it being not a nationality is relevant. If there is a relevant legal status as citizenship of Puerto Rico, shouldn't it be included? We can have multiple citizenships given for a single person, and the constraints can be modified if they don't reflect the concept correctly. --Yair rand (talk) 04:15, 3 September 2018 (UTC)
I can't see how you come up with the conclusion that most of us agreed on that.... C933103 (talk) 06:06, 3 September 2018 (UTC)
I disagree with the summary that 'Most of us agree with the fact "Puerto Rican" is not a nationality.' In fact I am of the view that we should allow Puerto Rico to be listed as a country of citizenship, particularly for people who self-identify as such by reliable sources or by participation in international event as Puerto Rican (rather than USA, or Spanish in the past) representatives. This doesn't exclude them from also being listed as having USA (or Spain, or any other country that the person holds citizenship of) as country of citizenship. If we need to "fix" the constraint then I would broaden P:P27's value type constraint. Deryck Chan (talk) 08:58, 3 September 2018 (UTC)
off-topic a bit, how to treat sub-nation such as Puerto Rico seems a more off-shot discussion. For example, Bermuda had their own en:British passport (Bermuda), as well as the existence of en:British National (Overseas). So, given reliable source to verify, how to properly treat those "sub-class" of nationality of an empire or "federation of state"? British National (Overseas) were either de facto stateless (some ethnic non-Chinese minority thus they can exchange the status from BNO to BC) or ethnic Chinese. The Chinese, after 1997 had de jure automatically qualified (or became) as China PR citizen. But it seem wise to list them under value "British Hong Kong" as depreciated value. Also, for all other former colony, at that time there is no separation of nationality in the law of the empire, thus how to treat them, filling en:Gold Coast (British colony)? or British subject for those obtained British nationality before independent ? Matthew hk (talk) 06:42, 3 September 2018 (UTC)
@Deryck Chan, C933103: I thought most of us were agree because of the provided arguments. Anyways, I still consider the value should be fixed, regardless if it is accepted as a nationality or if it is changed/removed. Esteban16 (talk) 00:56, 9 September 2018 (UTC)
@Esteban16: Fixed it for you [2]. I've added value-type constraint (Q21510865):class (P2308):dependent territory (Q161243), which captures Puerto Rico, British Hong Kong, and the other citizenships of sub-sovereign countries we've discussed here. Deryck Chan (talk) 09:07, 10 September 2018 (UTC)

Google has introduced a beta Google Dataset Search available at https://toolbox.google.com/datasetsearch/ which may be of interest here. It was reported in Nature yesterday. There is no Q item for it yet. Abductive (talk) 18:20, 6 September 2018 (UTC)

Google Dataset Search (Q56524784) Blue Rasberry (talk) 15:24, 10 September 2018 (UTC)

Dataset search tools

Hi all

Google have recently released Dataset Search, which looks really interesting. What other data search tools are available to find data that might be suitable for Wikidata?

Thanks

John Cummings (talk) 17:53, 7 September 2018 (UTC)

Wikidata weekly summary #329

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

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.


Excessively long names

When the Pawn... (Q2003805) has the alternate name When the Pawn Hits the Conflicts He Thinks Like a King What He Knows Throws the Blows When He Goes to the Fight and He'll Win the Whole Thing 'fore He Enters the Ring There's No Body to Batter When Your Mind Is Your Might so When You Go Solo, You Hold Your Own Hand and Remember That Depth Is the Greatest of Heights and If You Know Where You Stand, Then You Know Where to Land and If You Fall It Won't Matter, Cuz You'll Know That You're Right. How can I add this? —Justin (koavf)❤T☮C☺M☯ 04:27, 8 September 2018 (UTC)

This is not possible due to length limit by the software. There is a phabricator ticket for it phab:T154660. --Pasleim (talk) 12:18, 8 September 2018 (UTC)
I@Koavf: You could cheat if you wish for any part of the string to show in the search results, and just complete the title in the next line. The artist might object, however. - Bossanoven (talk) 21:54, 10 September 2018 (UTC)

Recursive application of continent (P30)

I asked a user to remove "continent: Asia" from items about Indian villages on the basis that there would be no ambiguity about which continent they're on, since India is entirely in Asia and the villages would be noted, via located in the administrative territorial entity (P131) and country (P17), as being part of India and the continent could be inferred from there. Yet I have seen the recursive application of located in time zone (P421) to places at the village level for many countries (thanks @Nikosguard:!)—which I contend is rather inefficient—and am concerned that performing such a recursive application for other properties is just extra work whose benefit, when compared to the vast majority of other ways by which to improve items for geographical entities—such as adding some demographic info, adding specific coordinate locations, or adding authority control of any sort—is quite low.

The questions I wish to ask are this: Is it necessarily appropriate to recursively add continent (P30) to subnational entities of countries that are entirely in a single continent†? Where should we draw the hard line between the explicitly enumerable and the implicitly inferrable? Mahir256 (talk) 21:58, 9 September 2018 (UTC)

† or to entities located in federal subjects of Russia/provinces of Turkey/etc., where the federal subjects/provinces are entirely in a single continent, or other situations like this at a lower administrative level in the appropriate countries

Three questions.
  • Question1. Is Wikidata following waterfall model? Is property of parent data not needed for child data. And same problem with the located in time zone (P421)timezone thing. For example, India follows single timezone. If it is in waterfall no need to add the timezone to all geographical entities in countries where single timezone is present.
  • Question2. thinking from a single Q item. Property of the geographical entity includes the continent, planet, solar system, galaxy, galaxy cluster, universe. So adding these properties is very much valid (We don't know what is outside universe. If something there then that must be included in Wikidata).
  • Question3. We dont have a list of confirmed Properties for a Q(At least I cannot find one. If there please pardon me and redirect me to that. I am new to the scenario).
So I am open for more instructions. Please help me. --Ranjithsiji (talk) 05:34, 10 September 2018 (UTC)
If the inheritance not work then the data point is not existing in X. So If the continent is not on X then it is not on X. No inheritance. So can we add? Is the data incomplete without it? Basically it is a property of every geographical location in wikidata. So what is the decision? --Ranjithsiji (talk) 09:37, 10 September 2018 (UTC)
The existing consensus from previous discussions, as I understand it, is to limit it to countries or country subdivisions, except for Antarctica and places where it's not obvious and I think that makes sense. While we don't have any automatic inheritance of statements, we've always considered items to inherit information from other items, e.g. we generally only link to the most specific values for instance of (P31) and located in the administrative territorial entity (P131). Sometimes we intentionally duplicate things because it's very useful (e.g. country (P17)) but I don't see why we should do it for continents (or timezones). - Nikki (talk) 11:30, 10 September 2018 (UTC)

This isn't limited to the continent - for countries which have just one timezone, villages might have that statement as well even though it should be possible to be retrieved. Or the postal code, or even the country can also be retrieved from the items higher in the administrative subdivision tree. But there is no such automatic inference, which would require be a totally new software feature of "calculated statements". Especially as for countries like Turkey or Russia, the continent is not trivially inferred from the country. Ahoerstemeier (talk) 10:35, 10 September 2018 (UTC)

We need automatic inheritance for statements. Because that is the better way of keeping data more accurate and problem free. It is a high priority required feature. -- Ranjithsiji (talk) 14:39, 10 September 2018 (UTC)

If you're interested in this problem, you may want to look at Wikidata:Property_proposal/Generic#value is inherited from. - PKM (talk) 22:09, 10 September 2018 (UTC)

Ιnception of a municipality

Deryneia (Q777760) -> inception (P571) -> 1994

Hello. An item is about a human settlement. That settelement is also a municipality. By using P571 as a property, it means that the municipality was create at 1994 or the human settlement was created at 1994? The first is correct, the second not.

Of cource I have the option

but I just wanted to know about the first question. Xaris333 (talk) 08:27, 10 September 2018 (UTC)

Settlements and municipalities should be seperate items for this reason. Sjoerd de Bruin (talk) 09:53, 10 September 2018 (UTC)
From a data point of view, that's the way it should be, and that's the reason why geonames did duplicate them all - and thus via ceb-Wikipedia we already have lots of these in here. However, almost no Wikipedia ever does this duplication, so to be pedantic we'd even need a third item here which indicates that the linked Wikipedia articles cover both aspects. But even if we keep both aspects together in one item for simplicity, the inception can be clarified by using the qualifier applies to part (P518) -> municipalities of Cyprus Republic (Q16739079). Ahoerstemeier (talk) 10:26, 10 September 2018 (UTC)

It's a problem that we have only one article to most of Wikipedias... I think is better to decide what to do in Wikidata, and maybe wikipedias follow us later, if we decide to have two articles... Xaris333 (talk) 10:29, 10 September 2018 (UTC)

  • No, it's not a problem that Wikipedias are aimed at how humans think, rather than at some kind of pure epistemology. By the nature of Wikidata, we need to always be "splitters", distinguishing closely related concepts because they may have different attributes. But, in general, that is not how people want an encyclopedia to work. If you look up Seattle in an encyclopedia, you don't want separate articles to cover its pre-incorporation period, its brief period as an incorporated town, the brief period after that township was dissolved but before it incorporated as a city, and its period as an incorporated city. If you are managing it in a project like Wikidata, then these distinctions matter. - Jmabel (talk) 18:06, 10 September 2018 (UTC)

I mean it is a problem because one of the item will not have sitelink for a wikipedia, but the other will have. Morevore, it will be problem beacuse, for example, some wikipedia articles fetch data from wikidata. Is easiest to have all the information to a wikidata item than in two. I don't know if we can made template of wikipedia to take some informations for one templae and some from the other. Xaris333 (talk) 18:13, 10 September 2018 (UTC)

songs on albums - published in or part of?

It seems like published in is the wiser choice. - Bossanoven (talk) 21:46, 10 September 2018 (UTC)

@Bossanoven: We have tracklist (P658) and "on the tracklist of" as an alias for published in (P1433) (@Moebeus: regarding that alias); do either of those properties help? Mahir256 (talk) 21:57, 10 September 2018 (UTC)

Ideally we would have a property for specifically linking music tracks to tracklists, but in the absence of that P1433 is a lifesaver, and matches with Property:P577 publication date, helpful for when a track is present on several releases. "part of" is too broad in my opinon. Moebeus (talk) 22:04, 10 September 2018 (UTC)

Seattle Landmarks

How should we indicate buildings (and possibly districts) that have Seattle Landmark status? I see the one case

but that seems wrong to me: we should be recording that it is present in an actual government list of landmarks, not a Wikipedia list article, especially because there is a possibility that the latter might eventually exist in multiple languages and be better maintained in one than in another. - Jmabel (talk) 19:31, 10 September 2018 (UTC)

heritage designation (P1435)? --Pasleim (talk) 20:15, 10 September 2018 (UTC)
@Pasleim: Clearly heritage designation (P1435), but what would the value be? Is it simply that we need to create a new item for the concept of a designated Seattle Landmark? - Jmabel (talk) 22:19, 10 September 2018 (UTC)
I've created Seattle Landmark (Q56572098) --Pasleim (talk) 09:37, 11 September 2018 (UTC)

How to represent label changing over time?

Entities such as places or organisations (and sometimes even people) often change names over time. The time span during which a given name has been used could be represented by qualifiers attached to the label statement, but there is currently no way to attach qualifiers to the label statements. What is the alternative? I've not found any property such as "former name" to which time qualifiers could be attached. -- Bvatant (talk) 23:47, 10 September 2018 (UTC)

Game Publishers with No Information

For the past few months I have been adding instance of (P31) video game publisher (Q1137109) and industry (P452) video game industry (Q941594) to all companies/labels listed as a publisher for a video game in prominent game databases like MobyGames and Gamebase64. Yesterday I realized that this is probably not right to do for companies that aren't primarily focused on video games, like the retail companies Sears (Q6499202) (published some arcade games) and Zellers (Q845330) (published some bootleg console games). I am in the process of going through my history to remove these inappropriate claims, but now I don't know what to do when I can't find any information about the publisher for a game besides that it apparently published some or several video games. Often times the only evidence I find of its existence is in video game databases, which cite either images of old disks and cartridges games displaying an apparent publisher name, or a brief mention in the title screen of the game itself. Should I put/leave instance of (P31) video game publisher (Q1137109) and industry (P452) video game industry (Q941594) because they are related to the only verifiable information I have? Or should I leave those blank because I can't verify the company focused primarily on video games? And in that case, what should I put in the description of the item? Rampagingcarrot (talk) 19:16, 7 September 2018 (UTC)

@Rampagingcarrot: Well, industry (P452) would be correct in any case, wouldn't it? A company can be in more than one industry, and producing a video game makes the statement correct, I would think. (Not sure about this.) Regarding descriptions, I would recommend leaving them blank until an actual general source about the publisher is available. --Yair rand (talk) 18:37, 12 September 2018 (UTC)

Prayer

We're currently not distinguishing between prayer (Q40953) as an act and as a work (e.g. as in Lord's Prayer (Q23393)). I believe we should have a prayer with

⟨ subject ⟩ subclass of (P279)   ⟨ work (Q386724)      ⟩

and start moving some statements over. Then we can start correctly modeling translated prayers, etc. I'm asking first since it's bound to affect a large number of items. What do you think? --Azertus (talk) 10:30, 11 September 2018 (UTC)

Why doesn't Wikidata allow two qualifiers for a statement?

Hi all

Can someone explain why Wikidata doesn't allow two qualifiers for a statement? Is this a restriction used in the model of how Wikidata should be structured, or is it a techncial limitation or something else?

As an example, Shrek (Q483815) has a list of voice actors, with the qualifers describing which character they voiced, however this isn't accurate, these actors only voiced the characters in English. It seems like the model doesn't allow you to record which character the voice actor played and the language version they played it in. Maybe this isn't the most important example I could have come up with but it feels like a clear example. Maybe I'm missing something?

Thanks

--John Cummings (talk) 09:50, 12 September 2018 (UTC)

  • Jura is correct - you can do this but only by creating a new statement to hang the new qualifiers off. The key thing here is that while a statement can have many different qualifiers, they all apply to the whole statement. To do otherwise we'd need to have qualifiers applying to other qualifiers, which doesn't work with the existing data model. Andrew Gray (talk) 11:54, 12 September 2018 (UTC)
Ah it seems link someone worked it out, you have two qualifiers for the the same statement, I assume that you could add a third if they were the same character in other languages (I think Antonio Banderas may have been Puss in Boots in the Spanish version also).
  • Voice actor
    • Mike Myers
      • character role: Shrek
      • language of work or name: English
Thanks
John Cummings (talk) 18:37, 12 September 2018 (UTC)

Generating a list of references for a set of literature works

Hello, after reading Wikidata:How to use data on Wikimedia projects I'm still clueless about how to get a query trying to fetch all literature works about epistomology that Wikidata includes. The query itself surely should be improved, but my main helplessness pertains to how to make a wiki bullet list or even a table. I'm open with a solution that requires writing Lua modules, just show me the relevant documentation if what I'm aiming at is currently possible and documented. :) Cheers, Psychoslave (talk) 15:30, 12 September 2018 (UTC)

Wikidata:WikiProject Women/Wiki monitor/frwiki has an example of generated table using template:Wikidata list

Creating best practice example items for different subjects

Hi all

Nav Evans, the good people of Wikimedia Deutschland UX team and myself have been working on ways to try to make modelling items on Wikidata easier to understand, easier to learn and for items to be modelled more consistently.

As I'm sure many of you have experienced each of these issues causes quite a few problems, e.g trying to query a subject and the data is modelled in two/five/ten different ways....

Our first approach is to make it easier to find an example of well a modelled item for a subject e.g Douglas Adams as a well modelled item for an author. We're doing this through two properties, one to label the example item on the item for the topic, and one to label the example item as a good example for a topic e.g

  • Author has model item = Douglas Adams
  • Douglas Adams = model item for Author

We've started two property proposals to make this happen (not exactly inverse properties), I hope you will support them

Thanks

--John Cummings (talk) 18:44, 12 September 2018 (UTC)

Splitting country of citizenship (P27)

I just realized that the English description for P27 is "country of citizenship: the object is a country that recognizes the subject as its citizen.". And then, in some other languages, the word "nationality" also appeared in description. Such description would cause numerous problems:

  • For instance when someone is a citizen of a non-widely recognized country, and then when that non-widely recognized country appear as a value for the property, someone who are against the existence of that country might dispute it and replace the value with countries that claims to control the area
  • Or if the subject is a citizen of a dependent territory or other area that are not a country in itself, the property cannot be used to reflect such situation
  • And see w:WP:Citizenship and nationality for one of the attempted explanation for difference between "nationality" and "citizenship"

As such, in order to properly describe those subjects, please separate the property for "nationality" and the property of "citizenship" into multiple properties. C933103 (talk) 09:49, 30 August 2018 (UTC)

  • "Nationality" seems suspiciously like a way of associating people with countries based on somebody's arbitrary judgement that they belong with that country. If it's just country of birth, we already have a separate property for it. If it's not country of birth, how is it defined exactly? Ghouston (talk) 10:55, 30 August 2018 (UTC)
  • I don't think the "country of birth" part in that proposal make a lot of sense since there are countries that do not determine nationality according to country of birth. There seems to be multiple definition for what the term "nationality" could mean. In some cases it is a legally defined term that comes with rights and duties, while in other cases it might also be the case, and in some cases it could even be arbitrarily decided by individuals. For instance, For British person, they are UK citizens but they are English/Scottish/Welsh/N.Irish/etc. nationals according to my understanding although they are not legally defined if I didn't miss anything. It is obviously helpful to include such information in wikidata but then "how" would be the problem. Another example is that, for a citizen in Hong Kong, as Hong Kong is not a country so it cannot be a value in P27, the P27 value for those subject can only be China/UK/India/nil/etc., with an additional property saying the subject is a "permanent resident" of Hong Kong which might not sufficiently explain the status of it being equivalent to citizenship of Hong Kong in most cases.C933103 (talk) 11:37, 30 August 2018 (UTC)
Ad 1 and 2: Since when are contradicting statements a problem on Wikidata? – If a fact is disputed and there are valid sources for either view, just enter the contradictory statements. I don't think we'll be able to resolve the type of cases you are mentioning by refining the definitions.
Ad 3, I don't see the problem with country of citizenship (P27); the labels and descriptions look ok. There are a few (pseudo-)nation states that confound the concepts of citizenship and nationality/ethnic group, and this is reflected in their language (thus the primary label of "country of citizenship" in French is "pays de nationalité").
There also is ethnic group (P172), which in my understanding largely covers the concept of "nationality" stripped of its meaning of "belonging to a country".
Cheers, Beat Estermann (talk) 13:20, 30 August 2018 (UTC) If anybody wonders what I mean by pseudo-nation state, here you go: Willensnation (Q694366)
  • How about when the value is clearly not a country like, let say, French Polynesian? The French translation have been adjusted according to what you said, however in English it would still say "Country of citizenship: French Polynesia" when French Polynesia isn't a country.
  • P172 is ethnicity. It is still a very political term and sometimes there are even special legal definition that restrict it in some rather strange ways. Like if someone from Taiwan try to claim his ethnicity is Taiwanese, then he could be considered as a radical separatist by China, and if the situation occurs within China then the person could face severe administrative punishment. C933103 (talk) 13:57, 30 August 2018 (UTC)
Ad 1: country of citizenship = France; nationality / ethnicity = Polynesian.
Ad 2: why do you think the term "nationality" is less prone to that type of problem?
--Beat Estermann (talk) 14:13, 30 August 2018 (UTC)
  • So, a French Polynesian if supposed to fill France in P27 as country of citizenship, then how about when someone immigrated to French Polynesia? I am pretty sure ethnicity won't change due to immigration, but what sort of property would describe the subject's status as part of French Polynesia? Like if the subject is an Indian immigrating to French Polynesia, his ethnicity will still be Indian regardless of his status, and wouldn't be an ethnically Polynesia according to my understanding.
  • Using Taiwan as example, in 1992 cross strait talk a consensus have been reached that would enable both sides to express themselves as being part of China and by extension to that the P27 of Taiwanese subject can be described as "Republic of China" in Chinese label to show its different from People's Republic of China. As long as individuals continue to claims the scope of "Republic of China" is not an entity separated from mainland China then it would be slightly more politically acceptable. (Although still not strictly acceptable)
    • Note:The situation described above was only to illustrate how ethnicity can also be politically sensitivity, the proposed nationality-citizen split will most probably not be used on subject of Taiwan.
      • Edit: Actually I should have used myself as an example. Given that myself is a
        1. People's of Republic China national, which mean People's Republic of China citizen
        2. "British National Overseas", which is NOT British Citizen and would not be treated as UK National by numerous authorities including EU
        3. Permanent Resident of Hong Kong, which also represent most of the citizen right in the territory
        4. Ethnically Han Chinese, belong to the sub-ethnic group of Canton
      • In the current wikidata structure, if I somehow become notable enough to get a wikidata entry about myself, that entry will only feature P27: PRCHina, Ethnicity: Han Chinese, Permanent Resident: Hong Kong, which is not very descriptive about the actual situation of such a subject like myself. People who are familiar with the situation of the territory can easily infer what these value mean however that would require such background knowledge to fully understand these wikidata values.
C933103 (talk) 22:09, 30 August 2018 (UTC)
The only thing you would seem to be lacking is a way to represent "British National Overseas". Maybe just use British National (Overseas) (Q5613380) in country of citizenship (P27)? No, I guess that wouldn't work because of the way the value of country of citizenship (P27) is formulated to be a country. Ghouston (talk) 00:04, 1 September 2018 (UTC)
@Ghouston: And how do you think the Taiwanese problems here? Really they are Republic of China nationalities, NOT Taiwan nationalities! --125.36.185.148 03:13, 14 September 2018 (UTC)
I guess having a separate item for the citizenship/nationality would help clarify what it means. Ghouston (talk) 04:18, 14 September 2018 (UTC)
See prior discussions Wikidata:Property proposal/Nationality, Wikidata:Project_chat/Archive/2017/08#How_to_look_up_persons_nationality.3F. "Nationality" is not a workable property. --Yair rand (talk) 19:56, 30 August 2018 (UTC)
What about only allow the use of such property when they are legally defined?C933103 (talk) 22:09, 30 August 2018 (UTC)
If the property is created, people will use it any way they like. It's quite possible that people not familiar with Wikidata will pick it instead of citizenship. Ghouston (talk) 04:28, 31 August 2018 (UTC)
Naming it something like legal nationality could help? C933103 (talk) 10:17, 31 August 2018 (UTC)

Pointing out that the "country of birth" is irrelevant to citizenship in many, many cases. E.g. millions of Palestinians have been born refugees in Jordan and Lebanon for decades but are stateless persons. They still have an ethnic group to which they belong (the Palestinian people) but no citizenship rights and certainly none in their countries of birth. —Justin (koavf)❤T☮C☺M☯ 00:08, 1 September 2018 (UTC)

I've seen somewhere recently the suggestion of using citizenships instead of countries in P27. So instead of P27 = United States of America, you'd have P27 = United States citizen. That would allow creating items for arbitrary citizenships and nationalities that aren't states, e.g., citizen of Puerto Rico or British National (Overseas) (Q5613380). That would be better than having separate properties for "country of citizenship" and "nationality". It would also allow describing citizenships better in their own right. E.g., Australian citizenship has an inception date of 26 January 1949. However, this still leaves the problem that people were commonly described as "Australian", even in the 19th century, and many are marked up that way in Wikidata. Ghouston (talk) 00:38, 1 September 2018 (UTC)

Additionally, American citizens are also citizens of states (for those who live in states--i.e. not D. C., Guam, CNMI, Puerto Rico, or USVI). —Justin (koavf)❤T☮C☺M☯ 01:10, 1 September 2018 (UTC)
It seems like a good idea. C933103 (talk) 04:34, 1 September 2018 (UTC)

I have always used both country of citizenship (P27) and ethnic group (P172) for people. That serves for all purposes. Let's take as examples revolutionaries for national independence:

and

(he died before the creation of a nation-state called Greece). In many cases the most important property would be ethnic group (P172) (when someone looks for "German philosophers" usually looks for a list containing Immanuel Kant (Q9312) rather than ommiting most of those that would be included in such a list. -Geraki (talk) 18:28, 4 September 2018 (UTC)

We already have country of citizenship (P27) (legal) vs ethnic group (P172) (ethno-cultural). Creating an extra "nationality" property will make it even more confusing, as "nationality" (as the English language uses it) is a combination of "citizenship" and "ethnicity" with a little bit of self-identification. Deryck Chan (talk) 09:05, 10 September 2018 (UTC)

I'm not sure which which properties I can add to Fundação Alexandre de Gusmão (Q56604803)

Hello! I'm creating Fundação Alexandre de Gusmão (Q56604803)) and I'm not sure which instance of (P31) I could add to this item. To explain, this is a foundation under Brazil's Ministry of Foreign Affairs of Brazil (Q1193807). I can't think of similar institutions in Brazil to copy and paste.

Also, there are two institutions "below" (I'm not sure the correct term for it), one is a library, and the other is a research institute. I'm going to create both eventually, but I'm wondering what property I could use for them.

Thanks for all the help! Tetizeraz (talk) 13:32, 13 September 2018 (UTC)

  • It depends what it does. I added some statements. It seems to act as a publisher, but "publishing house" seems suboptimal. You could add library and research institute. --- Jura 14:41, 13 September 2018 (UTC)
Hi Jura1, thanks for the help! Tetizeraz (talk) 00:05, 14 September 2018 (UTC)
For the "institutions below" you could maybe use empresa matriz (P749) <=> subsidiária(s) (P355)? The English label for "empresa matriz" is "parent organization" with various aliases that allow for more than just conventional "empresas". Moebeus (talk) 00:30, 14 September 2018 (UTC)

SPARQL Query

Hi, I was wondering about this for a long time and I didn't find the answer, so hopefully someone will help me. I'm adding Slovak descriptions, and sometimes I use Descriptioner tool to add repetitive descriptions and I'm using SPARQL Query. I need to know 2 things: is there a possibility to specify, that I want only one item to one property? For example when I want to add description Belgian tennis player, it will mostly return Belgian players, when I will specify country of citizenship: Belgium. But there will be also e. g. French-Belgian players, which have Belgium in this property, but they also have another country there. So if I can specify just e.g. Belgium. Second thing: Is there a possibility to return only items with some specified description? For example I will choose description Belgian tennis player and I will add Slovak description, so I don't need to worry about inaccurate descriptions, because English ones are nearly always accurate and correct. Thanks for the answers. --Luky001 (talk) 21:23, 13 September 2018 (UTC)

Maybe you could avoid the issue and just add the translation of "tennis player" as the description. It would only be a problem if there are multiple tennis players with the same name. Ghouston (talk) 00:59, 14 September 2018 (UTC)
It's standard practice here to include the country. - Nikki (talk) 08:41, 14 September 2018 (UTC)
If year of birth and perhaps place of birth are known, they may work better as disambiguators than citizenship(s). Ghouston (talk) 01:15, 14 September 2018 (UTC)
You can use ?item schema:description "Belgian tennis player"@en . to select items with the English description "Belgian tennis player". If you want to include multiple descriptions (e.g. when there's more than one way to write something or if you want to use multiple languages), you can do something like values ?desc { "Belgian tennis player"@en "belgian tennis player"@en "belgische Tennisspielerin"@de } ?item schema:description ?desc . (which would find items with any of those three descriptions) - Nikki (talk) 08:41, 14 September 2018 (UTC)
Thank so much Nikki, pity I didn't ask sooner. It solves (at least I think) all problems, which I experienced during adding descriptions for many items at once. --Luky001 (talk) 13:30, 14 September 2018 (UTC)

http://data.bnf.fr as reference for human

Seemingly http://data.bnf.fr is in a lot of cases reference for the statement 'human'. But http://data.bnf.fr mentions only "gender", but does not mention, whether a living being is human or an animal.

Though - normally - the statement 'human' is correct, http://data.bnf.fr is not the correct reference for the assertion at issue.

Of course, normally we can deduce from other information, that a certain item is (1.) a living being and (2.) human. But such deduction is something different than a reference. -

However GND ID (property:P227) consist of the information 'Typ[:] Person (piz)' - e.g. http://d-nb.info/gnd/119545373 -: German 'Person' = English 'person' ≈ English '(a certain) human (i.e.: an individual)' ≈ German '(ein bestimmter) Menschen (ein Indiviuum)'.

So, if references for the statement 'human' are need, http://data.bnf.fr could be substitute by GND ID.

--Villa loga-WB (talk) 09:48, 14 September 2018 (UTC)

  • Maybe the bot operator can explain how it's inferred. Please don't replace valid statements with some resource you consider "more valid". --- Jura 14:08, 14 September 2018 (UTC)

Autmatically Adding Images (P18) to Resources

Hi @all, I'm currently using DBpedia and Wikidata as query endpoints and one thing that would be very helpful for me is having a describing image for each resource in Wikidata. When going through data obtained from DBpedia i noticed, that many concepts in dbpedia have a "dbo:thumbnail" property, that is not reflected by a P:18 (Image) property on wikidat.

For example, The dbpedia entity: http://dbpedia.org/page/Graphical_user_interface has a dbo:thumbnail and a owl:sameAs "http://www.wikidata.org/entity/Q782543".

The entity Q782543 has no image.

My approach now would be to automatically go through the DBpedia concepts I use, and for each concept with a dbo:thumbnail check the corresponding Wikidata item (with owl:sameAs) and set the P31 value to the dbo:thumbnail value, if the Wikidata item has no image so far. I think, from a technical standpoint I am able to do this, but my question is: Is this a valid approach? Or am I missing something that could have negative consequences? --Mackeprm (talk) 11:57, 14 September 2018 (UTC)

Thanks, that answers my question! And thank you for the reference to wdfist! --Mackeprm (talk)

Tombstone as information

Since we have to have a reference for religion, I added tombstone (Q203443) as an instance of information since a Star of David or a Latin cross will differ between Judaism and Christianity. Yet when I use tombstone as a reference for religion here, I still get an error flag: Max S. Freudenberg (Q20726682). Can someone see how to fix it, or come up with a more elegant way to be able to use a tombstone as a reference without getting an error flag? --RAN (talk) 14:38, 14 September 2018 (UTC)

Someone asked on IRC the same about interviews yesterday, we have type of reference (P3865) for this. Sjoerd de Bruin (talk) 15:01, 14 September 2018 (UTC)
Thanks a lot, Sjoerddebruin, I've also asked only some hours before in #How to model a museum label as a reference? above. :-)
A following question: It would probably now be good to indicate the location and the date of survey/consultation of the tombstone (Q203443) or museum label (Q6940727).
  1. My use of location (P276) has been moved to a qualifier by DeltaBot.
  2. retrieved (P813) does not seem to be made to indicate a date of a physical survey. Should we broaden the scope? Or use point in time (P585)?
Thanks in advance, --Marsupium (talk) 16:10, 14 September 2018 (UTC)
Maybe Help:Sources#Headstones_at_Commons or Q706363#P569 can help. --- Jura 16:39, 14 September 2018 (UTC)

proto-language (Q206577) reconstructed/unattested?

There's currently this item, which is for a common ancestral language. Some of the labels say that it's reconstructed, but at the same time Proto-Norse (Q1671294) is a proto-language but is not entirely reconstructed; there are inscriptions in Proto-Norse. w:Proto-language also says usually unattested, but not always. So what is the case here? Is the label wrong and proto-languages can have written attestations, or is the claim that Proto-Norse is a proto-language wrong? In other words, is proto-language (Q206577) the same as "unattested language" or "reconstructed language" (neither of which have items) and thus redundant to them, or do these items need creating? Rua (talk) 14:54, 14 September 2018 (UTC)

Invitation to Wikidata QuickSheets online training

Hello Wikidata project chat. Over the past half year I have been working on a tool that semi-automates the improvement and citation of Wikidata items. You can read more on this Rapid Grant proposal. I wanted to let you know I will be holding an online training for this tool. This training will take place Tuesday September 18th, from 4:00-5:30PM, Eastern Standard Time. More info on the Dashboard page.--Theredproject (talk) 01:46, 15 September 2018 (UTC)

This section was archived on a request by: Matěj Suchánek (talk) 09:34, 20 September 2018 (UTC)

Wikidata property for enwiki

Does Wikidata have a property number or similar for Wikipedia pages, in the same way that Encyclopædia Britannica Online ID (P1417) gives me the relevant Encyclopædia Britannica page or subreddit (P3984) shows me the subreddit? Wikidata's user interface presents Wikipedia pages separately at the bottom, but I'm trying to get the title of a Wikipedia page in a SPARQL query where a property id is required. This query throws up nothing, and it seems odd that Wikipedia is the only major encyclopedia not represented. I'm aware of Sitelinks and Special:GoToLinkedPage/enwiki/Q… but I don't see how to use either in this context. Thanks, Certes (talk) 16:13, 16 September 2018 (UTC)

@Certes: Here's a simple query that returns the names of 300 random enwiki articles:
SELECT DISTINCT ?item ?page_titleEN WHERE {
  ?article schema:about ?item ; schema:isPartOf <https://en.wikipedia.org/> ;  schema:name ?page_titleEN .
}
LIMIT 300
Try it!
Hope that helps. Mahir256 (talk) 16:26, 16 September 2018 (UTC)
Thank you! That's exactly what I was looking for. Certes (talk) 16:38, 16 September 2018 (UTC)
This section was archived on a request by: Matěj Suchánek (talk) 09:34, 20 September 2018 (UTC)

What am I doing wrong?

Hey there,

on Pentax X-5 (Q7165092), I added Commons:Category:Taken with Pentax X-5 as category for pictures taken with equipment (P2033) – worked like a charm. So I wanted to do the same with Pentax XG-1 (Q18387564) and Commons:Category:Taken with Pentax XG-1, but I only get "no match was found". I thought it might have to do with Commons:Taken with Pentax XG-1 being marked as a hidden category, so I turned it into a normal category for testing purposes, but Wikidata still does not recognize the category's existence. Am I doing something wrong? Cheers, --El Grafo (talk) 09:08, 18 September 2018 (UTC)

Same problem for Commons:Category:Taken with Pentax X70 and Pentax X70 (Q56651080) … --El Grafo (talk) 09:18, 18 September 2018 (UTC)
  solved Nevermind, I just didn't notice that on that first edit I actually entered an item on Wikidata for the category on Commons rather than just the name of the Category as it is done with Commons category (P373). Problem solved never actually existed. --El Grafo (talk) 09:39, 18 September 2018 (UTC)
This section was archived on a request by: Matěj Suchánek (talk) 09:34, 20 September 2018 (UTC)

CollabPad (but it is a special page)

Tracked in Phabricator
Task T204873
Resolved

In case you're wondering why your watchlist and other special cases have such a funny header: phab:T204873. Multichill (talk) 19:55, 19 September 2018 (UTC)

This section was archived on a request by: Matěj Suchánek (talk) 09:34, 20 September 2018 (UTC)

Hello, The wiki markup [[Q2]] creates a link to Q2. But is there a markup to create a link with the label of the item ? For instance [[Q2||label]] for Earth. Thanks,  – The preceding unsigned comment was added by Hopala! (talk • contribs).

There is the Q template which displays the label in the user's preferred language, e.g. {{Q|2}} produces Earth (Q2) - Nikki (talk) 09:25, 20 September 2018 (UTC)
Thank you very much ! - Hopala! (talk) 09:32, 20 September 2018 (UTC)
This section was archived on a request by: Bencemac (talk) 12:33, 20 September 2018 (UTC)

Q741775 - "Enemy of the people" and "class enemy"

After a discussion concerning the term enemy of the people (as used by Donald Trump) I have seen that the Wikidata item Q741775 confounds two different concepts: the enemy of the people (stemming from Roman hostis publicus, used time and again, most notably in Nazi terminology as de:Volksfeind and in the Soviet Union mainly in the 1930s, Russian: ru:Враг народа. There is also the more specific term class enemy (German: de:Klassenfeind, Russian ru:Классовый враг which redirects to ru:Классовая борьба = class conflict/de:Klassenkampf) which was more widely used in the 1920s after the Revolution. There are some articles that deal with the class enemy such as da:Klassefjenden, hr:Klasni neprijatelj, nl:Klassenvijand, no:Klassefienden, and some that deal with the enemy of the people such als en:Enemy of the people, de:Volksfeind, ca:Enemic del poble, pl:Wróg ludu etc. I would like to separate the two (which means that the English language Wikipedia would have a redirect for en:Class enemy only). Any thoughts on this? --Andropov (talk) 08:47, 9 September 2018 (UTC)

  • As a native English speaker, I would definitely agree that these are two distinct concepts, and should be separated, even if they have sometimes been used in a similar manner as political epithets. - Jmabel (talk) 04:17, 10 September 2018 (UTC)
@Jmabel: Thank you for your input! Could you, speaking of muddled concepts, tell me what the difference between en:enemy of the people and en:public enemy is? Kind regards, --Andropov (talk) 10:14, 15 September 2018 (UTC)
In the U.S., at least, "public enemy" has a connotation of actual criminality. The FBI used to put out a list of the "Ten Most Wanted" criminals, and the person at the head of the list was referred to "Public Enemy Number One." "Enemy of the people" is less specific; the phrase echoes the Ibsen play of that name, where it is used more or less ironically, in that the person who is accused of being an "enemy of the people" is the doctor who correctly diagnoses that the waters of the town's famous baths are contaminated, and his publicizing this hurts the local economy. That irony may or may not be there in any particular usage. - Jmabel (talk) 16:25, 15 September 2018 (UTC)

How to propose renaming a property?

Is there a way to propose renaming a property, or propose replacing one with another? If so, how? Rua (talk) 17:53, 15 September 2018 (UTC)

If the name of the property is incorrect, you can just change the label. If the you want to change the purpose of the label, start with a discussion on the talk page of the property. It might result in a PFD procedure and new property request. Mbch331 (talk) 18:25, 15 September 2018 (UTC)

Q25056785 and Q56537023 refer to the same real life object

  • Q25056785 ("F.A. Brockhaus AG" – without blank between "F." and "A.") consists only of three statements and two interwikis links. This item belongs to w:en:F.A. Brockhaus AG. There is said:
"Friedrich Arnold Brockhaus founded his publishing house in 1805 in Amsterdam, [...]."

and

  • Q56537023 ["F. A. Brockhaus (Verlag; ab 1817: Leipzig)" with blank between "F." and "A."] consists of few more information and belongs to GND 65191-6. There is said:
"1805 in Amsterdam unter Rohloff & Compagnie gegründet; 1811 Umsiedlung nach Altenburg in Thüringen; 1817 nach Leipzig".

Therefore I guess: This two item should be fused. - However, Q464633 (Bibliographisches Institut & F. A. Brockhaus) belongs to a different real object, because it came in existence not before 1984 - due to an fusion of two distinct companies. The latter item belongs to w:de:Bibliographisches Institut & F. A. Brockhaus. There we can read:

"Als Beginn des Verlages F. A. Brockhaus wird die Gründung des Verlages 'Rohloff & Co.' am 15. Oktober 1805 in Amsterdam durch den Kaufmann Friedrich Arnold Brockhaus angesehen, der zuvor mit einem Handel für Wollstoffe gescheitert war. Da Brockhaus kein Mitglied der örtlichen Buchhändlergilde war, erfolgte die Gründung über einen Strohmann, den Buchdrucker J. G. Rohloff."

--Villa loga-WB (talk) 18:08, 15 September 2018 (UTC)

P values to use for gene structure

 

Hello all. I'd like to try to encode the hierarchical organisation of gene components as summarised in the diagram (right). What are the most logical P properties to use? Is there something more specific than "is part of" / "is instance of", e.g. for the relationship between promotor and regulatory sequence? Evolution and evolvability (talk) 02:53, 15 September 2018 (UTC)

@Evolution and evolvability: The relationship between a regulatory sequence and a promoter in it can be described using part of (P361) and has part(s) (P527). But I think there is currently no way to link between a gene (which has genomic start (P644) and genomic end (P645)) and its regulatory sequences. In addition, genomic start (P644) and genomic end (P645) of genes are currently not only including open reading frames, but also including untranslated regions. So we may have to create some new properties. --Okkn (talk) 06:08, 16 September 2018 (UTC)

Cirques

Can anyone clarify what the difference between cirque (Q184368) and glacial cirque (Q388227) is supposed to be? One is supposedly a subclass of the other, but they have the same English label, they're both described as valleys caused by glaciers, they have the same Commons category and essentially the same GeoNames code (one is singular the other is plural), so I have no idea which one to use. - Nikki (talk) 09:54, 15 September 2018 (UTC)

Sorry, I do not remember. Chaoborus (talk) 12:14, 15 September 2018 (UTC)
Both have dewiki sitelinks, and the dewiki sitelink for glacial cirque (Q388227) seems to describe it as a general geological shape, possibly but not necessarily caused by glaciers, with cirque (Q184368) being a special form of it (i. e. the reverse of the subclass of (P279) situation on Wikidata). --Galaktos (talk) 23:14, 15 September 2018 (UTC)

Gee fizz

Can someone protect Rick and Morty (Q15659308). It's currently my entire en.wiki watchlist. GMGtalk 00:20, 16 September 2018 (UTC)

@GreenMeansGo: it has been protected, but requests that need sysop actions are placed on the administrators' noticeboard. Esteban16 (talk) 02:35, 16 September 2018 (UTC)

Make Wikidata P and Q templates universal in Wikimedia projects

I am writing to propose making P and Q templates in Wikimedia projects outside Wikidata, in every language, to redirect to Wikidata. Any comment here in support or criticism of this idea will help future planning.

Is anyone aware of this being discussed before? Can anyone say where they saw this, even if it was another language or project?

Consider {{P}} and {{Q}}. In Wikidata these templates are fundamental to quick discussion of Wikidata items and properties because they convert Wikidata identifiers to human readable text for conversations. Outside of Wikidata in other Wikimedia projects there are often P and Q templates which link to Wikidata. For example, see Commons:Template:P and Commons:Template:Q. Having these templates in place means that irrespective of language or project, editors can use P and Q templates to make connections to Wikidata.

Check out Template:Wikidata property link (Q19694638) and Template:Wikidata entity link (Q17280715), which are Wikidata's own records of which Wikimedia projects have equivalent templates by any name. Each of these are currently in about 40 Wikimedia projects. In about 20 cases the name is P or Q. In other cases perhaps there is another name, but P and Q are redirects. For some of the cases P and Q go to non-Wikidata uses. I think there are about 800 Wikimedia projects total. If it would be useful to make P and Q templates universal then we should make some plan to set that up or reserve it.

In English Wikipedia en:Template:P currently goes to en:Template:Smiley to make an emoji. In German it goes to en:Template:P for "priority" or the number 1. In French fr:template:P goes to the portal system. It causes big social problems to change templates which get established in Wikimedia community projects. Wherever possible we should propagate templates out now so that in the future we do not have to negotiate for this in every language and every project. Currently I am talking about this on English Wikipedia at en:Template talk:P where there is resistance to the idea.

Sorry - I have a major deficiency in this, in that I do not know the best way to migrate templates across languages and projects. If anyone can point to documentation on how to do this or outline the workflow of how this should go down then speak up. Also, if anyone has an objection to making P and Q templates universal then please say why. Blue Rasberry (talk) 14:04, 5 September 2018 (UTC)

The simplest solution is to do this as parser functions. I already wrote those parser functions when I was at WMDE, but it was turned down as it would interfere with community work on templates. In my opinion parser functions are the right way to do this. Jeblad (talk) 18:42, 5 September 2018 (UTC)
@Jeblad: Thanks, I would not have known to talk about that. What do you mean you wrote those parser functions? You mean for migrating arbitrary templates, or for this case specifically? Blue Rasberry (talk) 01:29, 6 September 2018 (UTC)
@Bluerasberry: As I recall they were parser functions for label and description, but in effect nearly the same. Jeblad (talk) 02:25, 6 September 2018 (UTC)
Most projects have little or no need for such a template, and occupying two of the single-letter template names is really a bad idea, probably disrupting dozens of local workflows and making everyone there memorize new names. I would advise against trying to make these universal. --Yair rand (talk) 00:20, 6 September 2018 (UTC)
@Yair rand: How would you feel about doing this for languages which do not have a P or Q and instead use non-Latin characters? What about for languages which have these letters, but where P and Q templates do not exist? Blue Rasberry (talk) 01:29, 6 September 2018 (UTC)

This is not something that Wikidata can decide - it is exclusively a matter for the community on each individual project. I guess that it is unlikely to be a significant issue to create them on wikis that do not currently have templates by this name (unless it conflicts with any local policies, e.g. I have a very hazy recollection that one of the Indic language wikis doesn't (or didn't) like templates other than in that language's script). On wikis where templates by these names do already exist you need to discuss any proposals to change with the community on that project. Thryduulf (talk) 16:30, 6 September 2018 (UTC)

Any project that want to use Wikidata, or really that enable the client part of the Wikibase extension, will at some point need tools to point to items, properties, and a number of other entities. Now those projects has to implement those tools themselves. In fact, when any project must implement a module to make a template work it is a clear indication that some basic tool are missing. To not implement a tool just because it could be implemented as a Lua module is not very wise, and it blocks smaller projects from progressing.
There are several other modules that are reimplemented again and again, and those should also be replaced by generalized tools and libraries. Now many modules are copied between projects, and more often than not they should not be used at all because they fail even quite basic quality measures (not to say tests, they have none).
Please do request the devs to implement basic tools for accessing entities, it is the best way to help smaller communities to access and use Wikidata. Jeblad (talk) 18:17, 6 September 2018 (UTC)
Whether the tools are or are not needed or wanted is irrelevant to this discussion. This is about only the name for templates that refer to Wikidata properties and items (i.e. the equivalent of {{P}} and {{Q}}). This is something that can only be decided by the individual wikis. It is not possible for a discussion here to determine this for any project other than Wikidata. Thryduulf (talk) 20:50, 6 September 2018 (UTC)
Quite frankly, this does not make sense. Jeblad (talk) 11:52, 10 September 2018 (UTC)
@Jeblad: What doesn't make sense to you? Why do you think it doesn't make sense? Thryduulf (talk) 01:30, 17 September 2018 (UTC)

Battles

Is there a property to use to mark a battle in a war, and in relation to fronts and other battles? The part of (P361) piles everything together, and does not structure the information very well. Or can conflict (P607) be used for battles in war? –Susanna Ånäs (Susannaanas) (talk) 11:22, 16 September 2018 (UTC)

What about significant event (P793) per significant or notable events associated with the subject. Pmt (talk) 11:51, 16 September 2018 (UTC)
Thanks, I think it's much better. I realise that this may be the smallest of problems, it seems that most everything about wars is hard to model to the level of Wikipedia infoboxes: Who were the fighting parties, who lead them, how many casualties and prisoners were there on each side in each battle etc. – Susanna Ånäs (Susannaanas) (talk) 11:59, 16 September 2018 (UTC)

Geographical coordinates from image metadata

If we add geographical coordinates to a listing based on the metadata of an image pertaining to that listing, would we add a source for this statement, and, if so, what kind? I originally asked in Help talk: Sources. ARR8 (talk) 14:39, 16 September 2018 (UTC)

  • Not an answer to your question, but from my experience at Commons, a lot of images have inaccurate geocoord metadata in their EXIFs. Before trusting that, always look at a map and see if it is at least highly plausible. This should never be done by a bot and simply trusted. - Jmabel (talk) 17:17, 16 September 2018 (UTC)
Thanks for the reminder. In this specific instance, I have done so. The specific use case here is landmark listings on Wikivoyage which are missing coordinates but have pictures in Commons, so this will be a manual and infrequent process. ARR8 (talk) 02:29, 17 September 2018 (UTC)

deactiveing article preview

How can I hide article preview pop-up permanently?Yamaha5 (talk) 02:44, 17 September 2018 (UTC)

@Yamaha5: disable the “Preview” gadget? or do you still want to have the gadget, but without the preview opening by default? --Lucas Werkmeister (talk) 10:43, 17 September 2018 (UTC)
@Lucas Werkmeister: This preview artcile window should be optional or should be disabled by gadget or prefrencess.
 
This Window
Yamaha5 (talk) 13:38, 17 September 2018 (UTC)
As Lucas wrote, you need to disable the "Preview" gadget. You can do this at Special:Preferences#mw-prefsection-gadgets --Pasleim (talk) 14:41, 17 September 2018 (UTC)

Wikidata weekly summary #330

 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Events
    • Continuing through September and early October: Andy Mabbett is touring Australia for a series of open-science and GLAM Wiki-focused talks, workshops, and meetups.
    • New events added for the sixth birthday of Wikidata: Berlin, Oslo, Tehran, Beijing
  • Development
    • Fix a problem with the language of the lemma (phab:T194347)
    • Improving the diffs for Lexemes (phab:T185481)
    • Exclude es-formal and hu-formal from monolingual text codes (phab:T203311, thanks to MarcoAurelio)
    • Implement the contemporary constraint (phab:T141859, thanks to Abiàn)

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.

TV anime described as film

Why are there many TV anime entry on wikidata being mistakenly described as other things like film or TV drama or whatever other things? C933103 (talk) 13:31, 13 September 2018 (UTC)

Hi C933103. In general, this is because Wikipedia articles cover all media of a given franchise together, and this was used to seed Wikidata initially. For example, Black Lagoon covers 5 media (manga, both anime seasons, a light novel and an OAV) or City Hunter 12 (!) media.
I tend to think the correct way to do that is to have the "main item" about the media franchise, and separate item for each different medium. Some examples: Dragon Ball (Q2020) Naruto (Q642), Ghost in the Shell (Q92580), Cardcaptor Sakura (Q49182)
That’s a lot of work though :)
Jean-Fred (talk) 14:48, 13 September 2018 (UTC)
That would be hard to do interwiki link if wikidata entries are broken down this small...C933103 (talk) 08:03, 14 September 2018 (UTC)
Why so? Most of the interwiki links would be on the franchise item. If Wikipedia articles happen to exist dedicated to a movie or an OAV, then they can be linked to the Wikidata item. This is exactly what happens for Ghost in the Shell (Q92580):
That way, we have a 'proper' data model and reasonable interlinking, no? Jean-Fred (talk) 10:10, 14 September 2018 (UTC)
It would be good to fix these at some point. I tend to avoid them. In general, statements about any of the elements end up combined on some item. Maybe the situation has gotten better recently. --- Jura 10:20, 14 September 2018 (UTC)
If Wikipedia language version A create only an article for a novel version of a series, then Wikipedia language version B create only an article for comic version of a series, and then Wikipedia language version C create both articles then user would not be able to jump between language version A and language version C article on the same series directly. Unlike the current situation that all of them would be linked to same wikidata entry for the series and then only link to individual works when such wikipedia article exists.C933103 (talk) 03:06, 15 September 2018 (UTC)
@C933103: If there are article groups which have this problem, then for each item new placeholder pages should be created on each wiki, added as sitelinks to the items, and then turned into redirects. The alternative is that the concepts are conflated into one item, which is convenient from the WP perspective but incorrect from the WD perspective. Jc86035 (talk) 14:21, 15 September 2018 (UTC)
@C933103: That’s a valid concern, but I think in practice the pattern of linking together the main Franchise item will probably work in many cases, in particular the most complex ones. No Wikipedia links to Naruto (Q26971382) or Naruto (Q26971391), because it is likely that no Wikipedia will ever want to create a separate article for manga and anime.
Where I agree with you and am a bit worried about are cases where « what is the "main" medium » is debatable. For example, the manga Miss Hokusai (Q29940472) vs. its movie adaptation Sarusuberi (Q11580762). French Wikipedia is the only one having an article for both ; and for some language versions is is unclear which one they 'mainly' or 'primarily' talk about. A third item about a franchise would feel like overkill to me.
Jean-Fred (talk) 10:16, 18 September 2018 (UTC)

wikibase and authentication methods

Hello, I'm new with wikidata and I don't know if it's the right place to ask about technical question about wikibase. I wonder if it's possible to have several authentication methods (ex: LDAP, oAuth, SAML, OpenID ...) when installing and configuring a standalone wikibase instance?  – The preceding unsigned comment was added by 2a01:cb1d:89d9:d000:886:6d0f:7907:f52c (talk • contribs).

You probably want to talk to the developers - Wikibase Installation has some info, also the project page outside of wikimedia. I can't find anything directly about authentication, but I expect it's something that could be configured as you like. ArthurPSmith (talk) 18:27, 18 September 2018 (UTC)

Distinction of title of authority (Q7810129) and position (Q4164871)

Despite those items are said to be distinct, I don't see when to use which. There are also some Item that claim to be Instance of both (list). Can someone help me out? -- Dr.üsenfieber (talk) 13:07, 18 September 2018 (UTC)

@Dr.üsenfieber: title of authority (Q7810129) refers to how a person would be addressed - for example "Professor X", "Dr. Y", "President Z" etc.. position (Q4164871) is the label for the job they are in, whether or not they would be addressed that way, and it is usually much more specific, for example "President of Singapore", etc. ArthurPSmith (talk) 18:35, 18 September 2018 (UTC)

How to enter this property?

SO I'm working with herbaria (because of the newly approved Index Herbariorum code (P5858)) and at Oakes Ames Orchid Herbarium (Q55828891) I am trying to enter the collection or exhibition size (P1436).

Entering a number? It's a no go. The property pretends the "units" subproperty/qualifier is optional, but clearly it is not. In fact, it won't save on older entries that have no unit if you attempt editing the property (e.g. Maksim Bahdanovič Literary Museum, Minsk (Q12337378)). Alright, so I try to enter biological specimen (Q2075980) (I mean, what else am I supposed to use?!)... but it still won't save.

What am I doing wrong? Can I adjust the property so this nonsense will stop without manually adding exceptions for every collection in the world? Circeus (talk) 13:02, 18 September 2018 (UTC)

@Circeus: This should work with or without a unit, see the examples on collection or exhibition size (P1436). What exactly is the error message you are seeing? "won't save" suggests maybe there's something else wrong - if it's a constraint violation it will still let you save but then show a warning flag. ArthurPSmith (talk) 18:30, 18 September 2018 (UTC)
GAH. Turns out it was far more stupid than I thought: I pasted the number as found on IH with the space and all, and what goes on is that numbers (unlike dates) don't have any wiggle room whatsoever when you enter them. Circeus (talk) 19:40, 18 September 2018 (UTC)

What do you think is the main benefit of Mix'n'match?

Hi, I'm preparing for a presentation on Mix'n'match at Wikiconference North America. I have a little experience with Mix'n'match, but I know that I don't know very much compared to what everyone else knows. If you are going to Wikiconference North America and would like to collaborate on the presentation, please e-mail me or leave a talk page message. If you're not going to the conference but have knowledge about it, you can tell me here and I'll incorporate it into my presentation.

On Mix'n'match, I've imported a database there and I've done some matching. As I see it, right now links to external identifiers like those found in library databases are nice to have, but I don't think other sites use them (I'm aware that SNAC pulls from Wikidata, but I don't think it picks up non-authority file links). I think of it like investing in Wikidata without knowing what the payoff will be. Are there sites that currently use links from Wikidata like those matched through Mix'n'match?

I know Magnus created Mix'n'match as a way to create redlink lists--is the Creation candidates part of the site currently used for making new Wikidata items? I haven't heard of many people using it, but what do you think? From Wikidata, the Listeriabot can make redlink lists, like those for the Women in Red project--are there other projects using Wikidata to make redlink lists?

Are there other things about Mix'n'match that you think other Wikipedians and library people should know?

Thanks, Rachel Helps (BYU) (talk) 16:00, 18 September 2018 (UTC)

The biggest benefit is to find external id's for people, but more recently I have been using it for paintings. It's great to match up Qids for datasets that connect to some external database already (like any of the catalogs in there already, you can easily upload your own dataset, but sometimes you just want the Qids). Jane023 (talk) 18:48, 18 September 2018 (UTC)
Hmm, when would you just want the Qids? Rachel Helps (BYU) (talk) 19:45, 18 September 2018 (UTC)
I always explain it like this to Wikimedians: In Wikipedia you get the basic information about a topic and links to further literature. In Wikidata it's the same thing. You can basic data about a topic and then humans and machines get links to other databases/catalogs/etc to find out more. One of the things Wikidata is good at is being this identifier hub that brings all these different identifiers together. When you have one identifier you can easily find all the others be it as a human in the website or as a machine via the API. --Lydia Pintscher (WMDE) (talk) 18:52, 18 September 2018 (UTC)
okay, so mix'n'match links are useful because the page they link to could provide more information about a subject, which can then be used to improve Wikidata/Wikipedia? Rachel Helps (BYU) (talk) 19:13, 18 September 2018 (UTC)
Yes that is one really important aspect. The other part is what Jane was referring to I believe: When you are building a third party app or are matching catalogs then Wikidata can be very helpful by being the glue between many catalogs. If you have a list of IDs from the German National Library and want say the equivalent IDs in the French National Library. The German National Library might not have the link but you can go to Wikidata to find it because they are all collected in the same item here. (Made up example! They probably link to each other but there are enough combinations where this connection is useful but doesn't exist.) --Lydia Pintscher (WMDE) (talk) 19:21, 18 September 2018 (UTC)
Oh, I can see how that would be useful. Do you know of third party apps or websites that are currently using Wikidata for this kind of thing? Rachel Helps (BYU) (talk) 19:45, 18 September 2018 (UTC)
  • More specifically about "Mix'n'Match": it's mainly a tool to avoid creating duplicates. Let's say you have some identifier about 100 martians that are notable and should be added to Wikidata, you can create the items directly as you know nobody else created them yet. However, if you want add some identifier about 100 British PMs, you should avoid creating new items as they mostly likely already have items. The identifier should be added to the existing item. Many datasets are somewhere between these two.
    There are few other tools to achieve the same. --- Jura 19:24, 18 September 2018 (UTC)
oh, definitely! It's such a basic convenience of Mix'n'match that I didn't even think of it. Rachel Helps (BYU) (talk) 19:45, 18 September 2018 (UTC)

Prefix wdtn: not working for quantities?

The following query should retrieve the normalized elevation of mountains, right? 

select * where {
  ?mountain wdt:P31 wd:Q8502 .
  ?mountain wdtn:P2044 ?elevation .
} limit 3
Try it!

However, there are no results. Changing wdtn:P2044 to wdt:P2044 gives results, but then ?elevation is not guaranteed to be in meters.

The list of prefixes lists wdtn: (and further above explains normalization of quantities) but I can't find any example of this prefix being used. Toni 001 (talk) 14:07, 19 September 2018 (UTC)

Seems so indeed, but no idea why (I never used this prefix). Here is a workaround: 
SELECT * WHERE {
  BIND(wd:Q59805 AS ?mountain) .
  ?mountain p:P2044 ?statement .
  ?statement psv:P2044/wikibase:quantityAmount ?elevation .
  ?statement psn:P2044/wikibase:quantityAmount ?elevationNormalized .
}
Try it!
—MisterSynergy (talk) 14:18, 19 September 2018 (UTC)
@Toni 001, MisterSynergy: The wdtn: prefix is (currently) only used for normalized external identifiers (linking to the full URI according to formatter URI for RDF resource (P1921) – see the announcement), not for normalized quantities. --Lucas Werkmeister (talk) 15:00, 19 September 2018 (UTC)

Can properties contain a pair of values?

I don't mean a property that has more than one value, but one where the value itself is a pair. I'm dealing with URLs in an external database like:

I want to turn the link to these into a property, like the many other ID properties that already exist, but as you can see the URL has two parts, both of which are needed to identify a given entry. The first identifies the dictionary, the second the entry within that dictionary. Is there a way to capture this in a single value, in a way that the software can still piece together the link? Since the number of dictionaries is limited, these could also in theory all become separate properties; then the wdb= part of the URL is hardcoded into the property and only the id= is needed. What do others think? —Rua (mew) 16:03, 19 September 2018 (UTC)

There can only be one value, so you would need separate properties. I think separate properties would make sense anyway if they're separate dictionaries. - Nikki (talk) 16:56, 19 September 2018 (UTC)
They're separate, but they are stored in a common database with a common URL format. So kind of a grey area? —Rua (mew) 17:32, 19 September 2018 (UTC)
So you could just store the id in the form 'wdb=ONW&id=ID1000' and use the single property and URL, that works though it doesn't look pretty. If there's a standard form format for the pair it might be possible also to use that, for example ONW:ID1000 or ONW/ID1000 (if it is displayed in that way on the site for example, that might be a good standard to follow to really call it an id). We do have some properties like that where we go through a third-party reformatter (on the wmflabs tools server) to fix the url's. So it's possible to do this as a single property, it depends on what people agree looks right here. ArthurPSmith (talk) 18:03, 19 September 2018 (UTC)
I just went with multiple properties. See Wikidata:Property proposal/GTB database IDs. —Rua (mew) 18:16, 19 September 2018 (UTC)
But conceptually they're different, even if they're part of a single website. There are a few cases where we still have a single property for multiple types of identifiers (IMDb being the main one), but experience showed that it's generally a bad idea (e.g. it often leads to problems with constraints or formatter URLs, it makes using the data more complicated), so now we tend to avoid doing that and have split most of the old combined ones. - Nikki (talk) 09:55, 20 September 2018 (UTC)

Trying to edit two entries

I've been trying, unsuccessfully to edit two items:

Isabel's husband does not have an article or item. His name was Martín López de Henestrosa y Córdoba, not Martín López de Córdoba (Q5407465) Martín (Q5407465) married 2x: First wife was Sancha Alfonso Carrillo and his seconds wife was Teresa Álvarez de Haro. I tried to fix both Isabel and Martín but was unable to do so. I could add references when both have been fixed.--Maragm (talk) 13:42, 20 September 2018 (UTC)

@Maragm: unsourced and contested statements removed. strakhov (talk) 14:23, 20 September 2018 (UTC)
@Strakhov:, thanks. Will edit articles when I have time.--Maragm (talk) 14:46, 20 September 2018 (UTC)

P17 country and disputed claims

Just a heads up that there is a discussion currently taking place on Commons about how best to handle country (P17) claims on places located in places that have disputed country claims, specifically as applied to Judea and Samaria Area (Q513200), which may or may not be part of Israel (Q801). This affects the display of infoboxes on that project. Bovlb (talk) 00:13, 14 September 2018 (UTC)

In the case of Crimea (Q7835), it has been added to both Russia and Ukraine. Can the same be done for Judea and Samaria Area (Q513200)? The additional country would be State of Palestine (Q219060) or via Palestinian territories (Q407199). Ghouston (talk) 00:49, 14 September 2018 (UTC)
Ghouston Thanks for the suggestion. That is a reasonable way to handle multiple claims of ownership over a region. This specific discussion was about how to handle P17 claims on places (e.g. cities) within disputed areas. There are two obvious options:
  1. Add the seven dispute qualifiers onto the P17 claim for every city. If the qualification ever changes, we must maintain the information in hundreds of places.
  2. Remove the P17 claims on cities within disputed regions.
In addition, we need to consider whether project infoboxes can and should check for these and other qualifications (e.g. end time) whenever they try to indicate the country of an item. Cheers, Bovlb (talk) 15:50, 14 September 2018 (UTC)
No, it cannot be treated like the Crimea situation (In Crimea, 2 countries actually both claim the same land), as Israel has never formally claimed the West Bank as Israeli territory (except for a part of the Jerusalem municipality). Take a look at what started this, namely Category:Shim'a, then see how that is handled on en.wp: for region there it is stated "West Bank" (and not "Israel"). --Huldra (talk) 21:33, 14 September 2018 (UTC)
In that case, the country (P17) can just be set to State of Palestine (Q219060) or whatever, with optional dispute qualifiers. It's similar to Guantanamo Bay Naval Base (Q762570) having country (P17) of Cuba (Q241). Locations within the region should have the same country (P17) as the region itself. Ghouston (talk) 21:43, 14 September 2018 (UTC)
It's not that simple. Israel does administer the territory, various cities and settlements within are treated (for most intents and purposes) as Israeli. The State of Palestine's claim to the land (as well as the recognition of this entity) is in dispute. While Israel hasn't annexed the land, it hasn't said it does not belong to Israel - as this is former Mandate territory the legalities are rather murky, and Israel has been pursuing an agenda of ambiguity (as it does in other areas of policy).Icewhiz (talk) 21:51, 14 September 2018 (UTC)
I don't see the problem. If Israel doesn't claim it, then country (P17) shouldn't be set to Israel. If the State of Palestine does claim it, but it's in dispute, just add a disputed qualifier. Ghouston (talk) 23:48, 14 September 2018 (UTC)
Israel does not claim that it is part of Israel *now*, but it (along with most of the world) does claim that the status of the territories is to be determined by negotiations. It is assumed by many that most (or all) of the territories will end up being part of SoP, but this is not a fact. WarKosign (talk) 05:41, 15 September 2018 (UTC)
Not correct. All of the world, except Israel, consider these territories as occupied. Israel, and only Israel, consider them to be "disputed".--Huldra (talk) 20:03, 15 September 2018 (UTC)
I did not say anything about occupation. Whatever the status is now, the final status of the territories is yet to be determined. The world calls these "Palestinian Territories", not "State of Palestine", because even SoP says that it is prepared to negotiate and thus would probably end up with some subset of the territories (and maybe some extras as a result of territory exchange). WarKosign (talk) 21:22, 15 September 2018 (UTC)
Well, I think the infobox should reflect todays status, and not what some people dream about becoming the status tomorrow. --Huldra (talk) 22:24, 15 September 2018 (UTC)
It comes down to the details of its current status and also how country (P17) is used. We have non-administering countries in country (P17) on Guantanamo Bay Naval Base (Q762570) and Crimea (Q7835). According to en:State of Palestine, it's recognized by 136 UN member states, so it has a lot of recognition. On the other hand, we also have a lot of items with country (P17) set to Taiwan (Q865), without bothering to mention that Taiwan (Q865) has much less recognition, and People's Republic of China (Q148) also claims the entire area. Ghouston (talk) 23:59, 15 September 2018 (UTC)
Recognition of SoP and of SoP's claim on the land are two separate issues. SoP is somewhat recognized, it owning the land is merely "what some people dream about". In fact while Israel doesn't make an official claim for the territories (except East Jerusalem), it has de-facto control of all of them (allowing civilian Palestinian control at some places), and has de-facto claim on the territory of the settlements. WarKosign (talk) 07:28, 16 September 2018 (UTC)
Again, this cannot be compared with the Crimea, or the Taiwan cases. In both of those case you have two countries officially claiming a piece of land belonging to them. This is not the case with the West Bank: Israel has never claimed the West Bank as part of Israel (except for a part of the Jerusalem municipality.) There is a good reason for this: if they did so, they either have to give the local Palestinians equal rights, (which will never happen, IMO,) or they would be officially instituting an apartheid system (unlike now, where they have unofficially instituted such a system), (There is a third way, of course, which is to make life as unliveable as possible for the Palestinians; forcing them to emigrate...but that is a long term strategy, and one which doesn't seem to be working very well,) --Huldra (talk) 20:37, 16 September 2018 (UTC)
The questions seem to be, for Judea and Samaria Area (Q513200), a) whether it makes any sense to set country (P17) to Israel, as User:WarKosign seems to want, when Isreal hasn't annexed the area but is occupying it and is the de facto government, and b) whether it makes any sense to set country (P17) to State of Palestine, when that state has never controlled that area and it's still unknown if they ever will. If neither makes sense, then I suppose country (P17) would be set to <no value>. Ghouston (talk) 21:56, 16 September 2018 (UTC)
Setting it to <no value> is definitely an improvement of present situation (..which is setting it to Israel, which is clearly wrong), --Huldra (talk) 22:28, 16 September 2018 (UTC)
Both Israel and SoP are associated with the territory. I'm not familiar with the technical side, if country (P17) attribute is exclusive it would be equally incorrect to set it to either. Both Israel and SoP claim and control the area to some degree; Israel claims less and controls more than SoP. If country (P17) indicates "belongs to" that neither would be correct. If it means "controlled by" then Israel would be correct (except areas A and maybe B); if it means "claimed by" then SoP would be correct (except East Jerusalem). If this tag has no intrinsic meaning and is used to indicate that there is some kind of association between land and a state (or a state-like entity), then it would be most correct to apply both and add some note explaining the complex situation. WarKosign (talk) 09:50, 17 September 2018 (UTC)
We have statement disputed by (P1310) for such a note, see Q39760#P17 --Pasleim (talk) 10:00, 17 September 2018 (UTC)
I think territory claimed by (P1336) describes SoP's relations to the territory accurately. For Israel, maybe located in the administrative territorial entity (P131) ? country (P17) seems wrong for either, because neither is "sovereign state of" Judea and Samaria Area (Q513200). WarKosign (talk) 10:11, 17 September 2018 (UTC)
No it doesn't...as Israel does NOT oficially claim the West Bank, --Huldra (talk) 20:39, 17 September 2018 (UTC)
I'm not sure which part of the above you're disputing. Please clarify? --Yair rand (talk) 20:45, 17 September 2018 (UTC)
The "claimed by" statement. In the above statement one have Senkaku Islands as an example. Now, that is clearcut: AFAIK both Japan and China claim them. Alas, Israel does not claim (officially) the West Bank, it administer certain parts, where they have criminally, according to international law, transferred some of their own population. --Huldra (talk) 22:45, 17 September 2018 (UTC)
So are you saing that SoP *does not* claim the territory because Israel doesn't claim it ? WarKosign (talk) 08:33, 18 September 2018 (UTC)
Huh?? How on earth do you come to that conclusion? --Huldra (talk) 20:27, 18 September 2018 (UTC)
I suggested to write that the area is claimed by SoP and apparently you argue against that. WarKosign (talk) 21:20, 18 September 2018 (UTC)
Plenty of countries have administrative territorial entities for areas they don't actually administer, so individual cities and whatnot can be simultaneously within administrative districts of different countries, only one of which is of the administration. However, a district that structurally only exists within one country's system (regardless of the geographic area it represents) clearly has more association to one country than the other. I think it would go in its P131 tree and probably also P17. I think we'd agree that even Taiwan's old districts for mainland areas it hasn't controlled for a long time would still have P17: RoC. --Yair rand (talk) 20:54, 17 September 2018 (UTC)
A relevant point here is that Republic of Crimea (Q15966495) only has country: Russia and Autonomous Republic of Crimea (Q756294) only has country: Ukraine.
There are a lot of issues to unpack here, and the decisions for each of them will affect dozens of items in similar situations. We need to figure these out systematically, and not try to just figure out an outcome for a single item. --Yair rand (talk) 21:02, 17 September 2018 (UTC)
Related: Wikidata:Project_chat/Archive/2017/07#What_country_are_Israeli_Jewish_settlements_in?. Anyone know how occupations (without territorial claims) are handled in other situations? The Occupied Enemy Territory Administration (Q7075820) seems to be considered as though it were a country in its own right, as is Allied-occupied Germany (Q2415901) (and not as, say, territories of the respective occupying powers), historical American unannexed territories I think are considered American, Guam (Q16635) has country (P17) United States of America (Q30) despite being officially specifically not part of the US. What do we do with United States Civil Administration of the Ryukyu Islands (Q55526)? We don't seem to be completely consistent about these things. Is the deciding factor which power administers the area? Which claims it? Which is recognized to have it? It's complicated, but I think we should try for as much consistency as possible. --Yair rand (talk) 22:54, 16 September 2018 (UTC)

I would think the correct data handling of Israel's relation to the West Bank involves using occupied territory (Q2577883) as a qualifier on something, though I don't know what. Thoughts? - Jmabel (talk) 23:50, 17 September 2018 (UTC)

Yes, good idea, I think that could cover it. --Huldra (talk) 20:27, 18 September 2018 (UTC)

I'm not sure that we have solved every aspect of this issue, but I believe the originally-reported problem is now resolved. Bovlb (talk) 02:20, 21 September 2018 (UTC)

new items in one window are not available in another

At this time the responsiveness of the system is so bad that you cannot work on lists where you have to create items that are to be used in the next. This is highly demotivating. The same is true with adding publications to authors.. The new tool by Magnus does not get enough space so that single researchers can be added within the timeframe of multiple days.

This is in my opinion a major handicap to keep people involved. Thanks, GerardM (talk) 17:46, 20 September 2018 (UTC)

Currently investigating this with others. Sjoerd de Bruin (talk) 18:56, 20 September 2018 (UTC)

The Dog

Thanks for merging that thing yesterday. I still don't understand Wikidata but I'll learn more as I get exposed to it. Poking around I discovered that a couple years ago I started the Wikipedia article about a documentary The_Dog_(2013_film) and here on Wikidata I changed The Dog (film) into The Dog (1992 film) which is now The Dog (Q7730510), a 1992 short film by Todd Field. I don't know if they are connected in any way. They shouldn't be if they are. Feel free to fix my links and the articles above as you see fit. Thanks for your attention. ~ JasonCarswell (talk)

All seems ok. There is The Dog (Q28136699) for 2013 film. --Infovarius (talk) 16:45, 21 September 2018 (UTC)

Hoe verdwenen straten in Haarlem op te voeren

The Haarlem Erfgoed & Data WikiProject does not exist. Please correct the name.

Hoe kun je een verdwenen straat in Haarlem opvoeren? De huidige link werkt via een bot en verwijdert handmatige toevoegingen.

Zo heb ik de Achterstraat in de Burgwalbuurt gevonden. In Kurtz/Temminck 1999 via lemma's achterhaald. Per 14 juni 1876 verdeeld: hernoemd tot Spaarnwouderstraat (van Hagestraat tot Korte Brug) en Antoniestraat (van Hagestraat tot Antoniebrug)  – The preceding unsigned comment was added by Arjan Vink (talk • contribs).

I'm not sure what you are saying about bots and links, does this query belong on the Dutch Wikipedia? It's possible to make a separate item on Wikidata for an old street if it was subdivided into two new streets. In this case, Achterstraat divided into (Spaarnwouderstraat (Q17286899) and Antoniestraat (Q17286360) on 14 June 1876. In that case, the inception date of the last two streets would be 14 June 1876, and Achterstraat would be disestablished on the same date. Ghouston (talk) 11:54, 20 September 2018 (UTC)
Some context: Members of Historische Vereniging Haerlem (Q3238760) are active on Wikidata working on current and historic streets. See https://haerlem.nl/index.php/uw-interesse/erfgoed-data for some background information (in Dutch).
@Arjan Vink, Hannolans, Ghouston: the suggestion is also how I would probably do it. Multichill (talk) 15:42, 21 September 2018 (UTC)

Country and city attribution of geolocated item

I am trying to make use of GeoData API to perform aforementioned task.

I found GeoData API very clean, simple and user friendly in retrieving various data according to geo location of the item. But there are difficulties with retrieving country/city affiliation of the item. While country can theoretically be get in a single request (also not always but only if being specified and not in name format but rather by its alphabetic designation), the city is possible to be get only for items which are cities by themselves. Let's imagine I want to determine in one request providing the coordinates of the Sagrada Familia temple the name of the item and that it is located in Barcelona, Spain. As far as I understood there is no way to do that. From the second hand this information does exist for every geo tagged item and is available for example through WikiData SPARQL query service. But then I'll need to perform a second request to WikiData which I would have liked to avoid by all means.

Looking on advice on the optimal strategy to perform the desired. If not is it possible to add the country/city attributes to GeoData list=geosearch attributes? -  – The preceding unsigned comment was added by Chainastole (talk • contribs).

@Chainastole: I think you will have to use the Wikidata API. Cities and towns might not even have designated boundaries, and AFAIK the GeoData extension only allows for the entry of ISO 3166 subdivision codes (which most cities don't have). Jc86035 (talk) 12:00, 22 September 2018 (UTC)

Two new principles introduced by Andy Mabbett

At Q27652812 there is another instance of the by now customary edit war by Andy Mabbett, in which he reverts time after time, without providing any kind of argument for the "content" he added, or answering any argument about content. In this instance there is an additional twist; he introduces two new principles into Wikidata:

  • As an excuse for editing he postulated that if a concept can possibly be regarded as a lexeme this overrides the basic Wikidata model of having an item when there is a sitelink.
  • He wants to have an item devoted to the state of being new. That is, a separate item, for an already existing item, devoted to the moment when the concept was new. This is a revolution within Wikidata. Anything man-made is "new" at some point, any book, movie, car, plane or what have you. By Andy Mabbett's reasoning there should be items "new book", "new movie", " new car", "new plane", etc (for most existing items). Presumably to be followed by items "one-year-old book", "one-year-old movie", "one-year-old car", "one-year-old plane", etc. In turn to be followed by "two-year-old book", "two-year-old movie", "two-year-old car", "two-year-old plane", etc.

Brya (talk) 04:20, 15 September 2018 (UTC)

First, please Brya, notify the relevant user. It is rude to attack somebody in public without letting them know.
Second, if the scope of an item is unclear, it helps to look how the item is used on the project. species nova (Q27652812) seems mainly be used as a value of main subject (P921) on scholarly articles. Is the main subject of these articles a latin phrase or a species? --Pasleim (talk) 08:30, 15 September 2018 (UTC)
As to the first, he is all over the place anyway.
        As to how it is used on Wikidata, this is not saying much as these links were made by a bot, a bot, QuickStatementsBot, which is notorious for the many errors it makes. Putting a bot to work will run up numbers quickly, no matter the "value" of the content. These links are weird: if there is a paper on "The new model Volkswagen Tiguan", the main subject is not "new model car" but the Volkswagen Tiguan. Not to mention those minerals that supposedly are "new species of organisms". - Brya (talk) 09:44, 15 September 2018 (UTC)
Hey Daniel: I think most of the additions are made by you.
Hey User:Chris.urs-o: I think most of the (misplaced) mineralogical usages of species nova (Q27652812) as main subject (P921) are done by you.
--Succu (talk) 19:19, 15 September 2018 (UTC)
I agree that species nova (Q27652812) should not be about the newness/ novelty (which is ephemeral) but about the taxonomic term that has a specific meaning in biological nomenclature. My reasoning behind using it in main subject (P921) statements is that this basically flags the existence of at least one taxonomic treatment (Q32945461) in and/or at least one nomenclatural act (Q56027914) associated with the publication in a more consistent manner than the various variants of "new species"/ "sp. nov." / "spp. nov." etc. On that basis, it is then simpler, for example, to create lists of works which do not have ZooBank ID for name or act (P1746) or Plazi ID (P1992) statements but probably should have some. As for "new species" of minerals, I think that should be a separate item. --Daniel Mietchen (talk) 22:14, 15 September 2018 (UTC)
I need help. I need a list of haswbstatement:P921=Q83353 AND haswbstatement:P921=Q27652812. "New species" of minerals: type description (Q56241591).
Type specimen, type locality and type description are valid concepts. --Chris.urs-o (talk) 03:15, 16 September 2018 (UTC)
@Chris.urs-o: Something like this query? --Succu (talk) 15:17, 16 September 2018 (UTC)
Thank you. --Chris.urs-o (talk) 15:45, 16 September 2018 (UTC)
As to papers that introduce a new species of organism, these should be linked to the new species they describe (for example Cherax snowden). Then, preferably the item of the species should be linked to the paper. I guess this might be done by bot, but probably not easily. - Brya (talk) 05:55, 16 September 2018 (UTC)
Or it could be a statement instead of a qualifier. - Brya (talk) 07:38, 16 September 2018 (UTC)

Looks like that Mr. Mabbett is avoiding this place. No reason givin in this and other matters.--Succu (talk) 05:39, 19 September 2018 (UTC)

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

I'm not "avoiding" this place at all. The fact that I am travelling (and will be for a further two weeks) - to speak about Wikidata at conferences and seminars - is widely known and has been previously (and at the time of writing is still) reported on this very page. Note also Brya's refusal to ping me when discussing me (a failure about which I have complained previously) and refuses deliberately to do so even when reminded to do so by other editors. Brya's opening post in this section contains a number of falsehoods in which - like your "avoiding" and "no reason given" allegations - he ascribes to me actions and beliefs which are not mine. I do not intend to dignify such abuse with a response, but I do note that Pasleim eloquently addressed the core issue. Absent a cogent rebuttal of that point, there is no need for further comment, and your tag-team edit warring to try to make the item about something which it is not (just as table (Q14748) is not about "a term used to describe an item of furniture with a flat top and one or more legs") is increasingly disruptive. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 07:38, 20 September 2018 (UTC)
I hope you do not encourage new users to use as before or as previously as an edit comment, Mr. Mabbett. --Succu (talk) 21:45, 20 September 2018 (UTC)
Species novum is an attribute of literature. It is where a species is introduced for the first time. It is definitely not an item in its own right. Where Andy is right is that it needs its own place however having it in a separate item is wrong. In the same way, species, subspecies, genus et al change over time. They change in literature. Almost by definition, what is meant is different with the new documentation. For this reason it is not realistic to have our current taxons exactly identify the described species novum and what follows. This is particularly clear because the full name of a taxon includes not only the author but also the publication.
As for the continuous bickering, I have largely stopped being involved by the bullying behaviour that is oh so easy to observe. Thanks, GerardM (talk) 05:34, 21 September 2018 (UTC)
GerardM - 1) The item is there because there are two sitelinks, as would have been apparent upon even the most superficial look (if you want to complain about there being Wikipedia pages at all, address Andy Mabbett who made the enwiki page). 2) By definition (ICZN Article 51.1, ICNafp Art. 23.1, 46.1, etc) the full name of a taxon does not include the author nor the publication. - Brya (talk) 14:14, 22 September 2018 (UTC)

Is there a simple description of lexemes and how they might be used?

Hi all

I'm writing a proposal for a project that includes a Wikidata element, I'm aware that lexemes are going to be available soon. Is there a description of what lexemes are somewhere that could be understood by a non technical person, and also some information on how they might be used or any future additions to them?

Thanks

--John Cummings (talk) 08:13, 18 September 2018 (UTC)

What little I understand of it is that basically Wikidata is a general structured ontology (i.e. it's about concepts), whereas lexeme are structured lexicographical data (i.e. it's about words). It may or may not be accurate (as I said, I'm not very knowledgeable about lexemes) to say that lexemes structure Wiktionary data instead of Wikipedia data. Circeus (talk) 14:04, 18 September 2018 (UTC)
Hello John,
Lexemes are available since May 2018. Did you already browse Wikidata:Lexicographical data and its subpages? If something is missing in the existing documentation, let us know. Lea Lacroix (WMDE) (talk) 14:44, 18 September 2018 (UTC)
Naively, a lexeme is a word; it's just that some things longer than one word function as lexemes (e.g. phrases that have a meanings little related to their components, as in Cockney rhyming slang; legal phrases like "sub judice" or "ipso facto"). - Jmabel (talk) 15:54, 18 September 2018 (UTC)

@John Cummings: Lexeme is label (lemma) + set of forms (inflexion) + meaning (senses). For example for "run" you have label "run" which represents set of forms ("run, runs, running" ) and meaning ("To move forward quickly upon two feet by alternately making a short jump off either foot" source en.wikt). If you have more lexemes oriented questions you can find more discussions about it at Wikidata talk:Lexicographical data. KaMan (talk) 09:35, 19 September 2018 (UTC)

@Circeus:, @KaMan:, @Jmabel:, @Lea Lacroix (WMDE):, thanks very much :) --John Cummings (talk) 13:51, 22 September 2018 (UTC)

Predecessor and successor state

For Germany (Q183) is there a field for predecessor state names and successor state names? I get an error message now for citizenship unless I have the proper name of the country for the years a person was living in that country. --RAN (talk) 01:19, 22 September 2018 (UTC)

@Richard Arthur Norton (1958- ): Each state should have its own item. Snipre (talk) 13:48, 22 September 2018 (UTC)

category contains vs category combines topics

What is the difference between category contains (P4224) and category combines topics (P971) , if any ? Thanks! Nat965 (talk) 09:39, 22 September 2018 (UTC)

@Nat965: you might want to read Wikidata:Property proposal/category contains. It discusses the difference between the two. Multichill (talk) 13:10, 22 September 2018 (UTC)

Transferring the Dictionary of African Biography to Wikidata

Hi there,
as part of my Masters in African Studies I need to write a term paper about digital resources. My idea was to compare the amount of entries of female biographies in Wikipedia vs in one of the most notable biographical dictionary, the Dictionary of African Biography. To do so, my plan was the following.

That was my plan. Especially the first part, transcribing all 2220 biographies into a spreadsheet will take a bit of time. But in general, does this make sense? I'm afraid there's no shortcut for this, right? Let me know what you think. Best regards, --Jcornelius (talk) 14:49, 22 September 2018 (UTC)

Hi @Jcornelius: and @Jmabel:, I will do my best to help, I think I know a way to speed some of this transcription up, will write a proper reply on Monday. Best, --John Cummings (talk) 17:20, 22 September 2018 (UTC)

Commons category

Just wondering (sorry if all these have already answered):

1) Why we need Commons category (P373) since we have commonswiki?

2) Why Commons category (P373) is not a link like commonswiki?

3) Is there a bot that checks:

  • a) if P373 value is different from commonswiki link?
  • b) if there is a value for P373 but not for commonswiki and add it?
  • c) if there is a value for commonswiki but not for P373 and it?

Xaris333 (talk) 12:08, 21 September 2018 (UTC)

@Xaris333: multiple items (category item, list item, article item) often link to the same category. Downstream users are using it. Mike is running some bots to keep things sane and we have several reports. Mike can probably tell a bit more about it. Multichill (talk) 15:45, 21 September 2018 (UTC)
@Xaris333: I'll let others answer (1) and (2), as I mostly work with the commonswiki links. With (3), Pi bot does (a) and (b), and DeltaBot does (c), as much as they can. There are quite a few cases where the bot can't resolve the differences / add the links, though, that need human checking. If you're interested in helping clean these up, then Wikidata:Database reports/Constraint violations/P373 is a good place to start (and if you spot any patterns that a bot could sort through, let me know and I can see if I can code something up). Thanks. Mike Peel (talk) 16:51, 21 September 2018 (UTC)
Why Commons category (P373) is not a link like commonswiki? is a question I have been asking since my first week here. What is the holdup? I think it had to do with whether the field should hold the category or the page. --RAN (talk) 01:24, 22 September 2018 (UTC)
The arguments over whether to use the Category or the Gallery (main-space) page were entirely about the interwiki link. Commons category (P373) is the Commons category, regardless of whether the interwiki link points to the Category or the Gallery. - Jmabel (talk) 02:31, 22 September 2018 (UTC)
@Xaris333: I don't know what you mean by 2nd point as P373 values look like links to me. May be you have the gadget "AuthorityControl" switched off? --Infovarius (talk) 20:21, 22 September 2018 (UTC)
Yes. Thanks for that information. Xaris333 (talk) 20:24, 22 September 2018 (UTC)

Commons category (2)

I made a question to User:Mike Peel, but I want to be sure.

I believe that Category:Mesa_Geitonia is for Mesa Geitonia (Q649368) and not for Category:Mesa Geitonia (Q55510271).

User:Mike Peel said that "If there is a category item, then the current convention there is for the commons category sitelink to be there rather than in the topic item. For more background, see Wikidata:Requests for permissions/Bot/Pi bot 6. "

Is that what we should do? I mean that:

a) Mesa Geitonia (Q649368) --> Commons category (P373) --> Mesa Geitonia

b) Category:Mesa Geitonia (Q55510271) --> commonswiki: Category:Mesa Geitonia

That we should have? Xaris333 (talk) 18:09, 22 September 2018 (UTC)

Mike is right, you're wrong. I restored the link on the right item. Multichill (talk) 18:48, 22 September 2018 (UTC)

Ok. But why is that the correct structure? Xaris333 (talk) 18:49, 22 September 2018 (UTC)

Proposition to extend a property

Hi ! train depot (P834) is for the moment for rail yard (Q19563580) and motive power depot (Q10283556) only. I would like to extend it for bus depot (Q1191753). Where should I ask for this ? Wikidata:Property proposal seems only for creations. Thanks ! Léna (talk) 20:59, 22 September 2018 (UTC)

You can bring it up at the Propertys discussion page Property talk:P834 Pmt (talk) 23:34, 22 September 2018 (UTC)

Statements - Order

Dear administrators,

I've just edited this item (P1971): https://www.wikidata.org/wiki/Q98034

Nevertheless, I'm not sure if the order of the statements is correct: reference URL - stated in - title - publication date - publisher - retrieved.

Regards.

83.43.127.190 17:41, 22 September 2018 (UTC)

The order of statements and qualifiers doesn't have any meaning. Even if statements are supposed to be ordered, they are ordered by adding qualifiers like series ordinal (P1545) and not by rearranging them within the data. Jc86035 (talk) 07:07, 23 September 2018 (UTC)

I have observed that the link to the Spanish version of many articles is intentionally excluded and instead a link to Catalan is existing, a much less important regional dialect.  – The preceding unsigned comment was added by 163.117.204.88 (talk • contribs).

Could you please be more specific and provide some examples? --abián 18:21, 22 September 2018 (UTC)
Trolling of a student of the Universidad Carlos III de Madrid (Q1247135)? Multichill (talk) 18:56, 22 September 2018 (UTC)
  1. Certainly there is no deliberate exclusion of Spanish. It is possible that there are items where a Catalan-language article exists and no Spanish-language article exists. Obviously, links to Spanish-language articles are always welcome, if such an article exists.
  2. Do you have any tangible examples of what you are complaining about?
  3. Perhaps people working on the Spanish-language Wikipedia have been less diligent about adding backlinks from Wikidata to connect their articles to those in other languages than is the case for those working on the Catalan-language Wikipedia.
  4. Or perhaps this is just trolling: Catalan is certainly a language, not a "regional dialect". It has its own Academy (two of them, actually, because there is one in Valencia besides the one in Catalonia), a rather large literature, and it is different enough from Spanish that it is common for work to be professionally translated from one to the other. - Jmabel (talk) 02:11, 23 September 2018 (UTC)

I think somebody is trolling. I work with many Q that have articles in Spanish and/or Catalan and I can't remember the last time I found one of either links missing (when available). I do recall that hapening sometime, but I guess chances are very low. B25es (talk) 05:54, 23 September 2018 (UTC)

I'd like to adjust Wikidata:Met Open Access Artworks Challenge/ES so it queries only items that have sitelinks at other Wikipedias, but ignores Commons sitelinks.--Pharos (talk) 22:14, 22 September 2018 (UTC)

@Pharos: [3]. In general Wikidata:Request a query is the best place to ask these kind of query related questions. You can just post the half done, not fully working query and enough people who like a good puzzle keep an eye on that page. Multichill (talk) 17:08, 23 September 2018 (UTC)

Official sites

Two things about official sites:

  • I have found some strange urls added with QuickStatements [4]. The person name doesn't match the domain, and the url doesn't show a lot info. Are they correct? @Oliviervd:
  • When a domain expires and it is registered by other organization, how should we state this? I think we should keep the original domain, set a qualifier with a link to Archive.org, and set a date when the domain was correct.[5] It seems @Bencemac: thinks different [6]

Opinions? Regards. Emijrp (talk) 09:14, 23 September 2018 (UTC)

@Emijrp: Templates (e.g. many infobox) most of the time load just the URL, not the archived version (stored in archive URL (P1065)), which could cause that they would use the unoriginal page. Bencemac (talk) 09:24, 23 September 2018 (UTC)
I think sometimes Wikidata gets mistaken for a webdirectory. Furthermore, there is no exclusivity for web.archive.org.
Adding an end date is the correct approach. History doesn't change when people die. --- Jura 09:33, 23 September 2018 (UTC)

Denisova 11

Is Denisova 11 (Q56233289) to be treated as humanoid (Q502931)? --Succu (talk) 21:30, 22 August 2018 (UTC)

As you know, I just created that, Yet you have not pinged me here. Why is that? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:33, 22 August 2018 (UTC)
Oh, I pinged you. So why? --Succu (talk) 21:38, 22 August 2018 (UTC)
„Here we present the genome of ‘Denisova 11’, a bone fragment” --Succu (talk) 21:59, 22 August 2018 (UTC)
Are not those folks simply archaic human (Q284851)?Bvatant (talk) 21:55, 22 August 2018 (UTC)
So how this item could be remodeled, Bvatant? --Succu (talk) 22:08, 22 August 2018 (UTC)
archaic human (Q284851): A subclass of human evolution (Q83944)?!? Has part Homo heidelbergensis (Q105784)?!? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:27, 22 August 2018 (UTC)
Succu Andy Mabbett Indeed I don't know, because we stumble here on the fact that archaic human (Q284851) is a subclass of human evolution (Q83944), has part(s)(?) elements such as Neanderthal (Q40171), itself instance of taxon (Q16521). I can't make sense for the moment of such a mess. The way taxons conflate with classes in WD is just a mystery for me, I'm currently trying to make sense of it and clarify constraints on parenthood relations mother (P25) father (P22) child (P40), in order to enable race horses, giant pandas and other pets to have proper genealogy, along with deities, dragons etc. I'm pretty sure that if Denisova 11 (Q56233289) is declared as type archaic human (Q284851), she will not be allowed by the current constraints to have a father and mother like you and me, more than she is with her current types: neither humanoid (Q502931) nor hybrid (Q42621) are allowed to bear mother (P25) or father (P22) in the current state of affairs. Will think about it, but a quick and dirty way to shunt the taxonomic jungle would be to declare those folks as instance of person (Q215627), which would be more respectful to them than humanoid (Q502931) or hybrid (Q42621). But just my 0.02€ :-) Bvatant (talk) 22:51, 22 August 2018 (UTC)
I think archaic human (Q284851) are all the members of Homo (Q171283) (Human) which aren't anatomically modern human (Q5891007). Taxons vs subclasses are a bit of a mystery. I thought Wikidata items needed to be a subclass of something if they could have instances. E.g., requires that wolf (Q18498) be a subclass of something, presumably Canis (Q149892). But I only get reverted if I do that, most recently with "it's already a subclass". Ghouston (talk) 03:27, 23 August 2018 (UTC)
We could use instance of Q171283; notwithstanding that that is but an instance-of-an-instance-of second-order class (Q24017414). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:42, 23 August 2018 (UTC)
Any comments to this solution? --Succu (talk) 18:41, 24 August 2018 (UTC)
@Succu: Now I'm a bit lost, sorry. Which problem does this change solve? We have two different problems here, #1 consensus on the type(s) of Denisova 11 (Q56233289) and #2 allow at least one of those types to bear mother (P25) and father (P22). Do you mean your proposal solve both, supposing the type archaic human (Q284851) is added to Denisova 11 (Q56233289)? I don't want to nitpick, again, but those things are really tricky. In any case, seems to me your solution conflates the person/organism who was alive here and there, and its fossil remnant. A fossil does not have mother and father, for example. See my other comment below.Bvatant (talk) 20:50, 24 August 2018 (UTC)
I responded to this remark. --Succu (talk) 21:02, 24 August 2018 (UTC)
I'd like to discuss Denisova 11 (Q56233289) nothing else. I don't think the current English description (girl with a Neanderthal mother and a Denisovan father) is correct. „Denisova 11“ is the name of a bone fragment. I created minimalistic items for earlier findings: Denisova 3 (Q56240560), Denisova 4 (Q56240584), Denisova 5 (Q56240616) and Denisova 8 (Q56240592). I doubt the usage of place of burial (P119) and related properties is correct. All fragments were found at Denisova Cave (Q1029322). I can not find any evidence that the girl - which the bone fragment was part of - was buried there. I don't think the usage of hybrid (Q42621) for a human is correct. --Succu (talk) 19:56, 23 August 2018 (UTC)
Succu +1 ! I pretty much like your minimalist descriptions, as they elegantly kick off the taxonomic issue. And indeed, those entities are fragmentary fossils, not persons (whatever their classification).Bvatant (talk) 20:45, 23 August 2018 (UTC)
You appear to be labouring under a misapprehension. The item is about the humanoid, not the bone. If you wish to create an item about the bone, no-one is stopping you. Readers will also note that P119 has many aliases, not all of which imply burial per se; and that "Hybrid" is exactly the term used by one of the cited sources - in its title no less. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:20, 23 August 2018 (UTC)
Further: "The tiny arm or leg fragment belonged to Denisova 11, a 13-year-old hybrid hominin" - [7]. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:33, 23 August 2018 (UTC)
Your latest argument, Andy Mabbett, led me to read through en:Denisovan#Fossils and indeed "Denisova 2 and Denisova 3 are prepubescent or adolescent females, while Denisova 4 and Denisova 8 are adult males". If I get correctly the meaning of are in this sentence, the names "Denisova n" denote individual persons, and not their fossil remains. So much for your interpretation, Succu, even if I was tempted to buy it yesterday. I would be tempted to extend parenthood properties used on human (Q5) to the whole genus Homo (Q171283). But what is the best way to do that?  – The preceding unsigned comment was added by Bvatant (talk • contribs) at 16:47, 24 August 2018‎ (UTC).
„Denisova n“ refers to the label given to the specimen. See e.g. „Scientists exploring Denisova Cave in the Altai Mountains discovered the worn baby tooth in 1984 and labeled it ‘Denisova 2.’“. --Succu (talk) 18:32, 24 August 2018 (UTC)
@Succu:Sorry for nitpicking :-) ... the source you quote is not convincing at all. First it's not a primary research paper, but an article in general press, less precise on vocabulary in general, and the referent of "it" in "labeled it" can be either the tooth or the baby. Regarding Denisova 11, this article at Smithsonian's is clearly using the name several times as the name of the girl, not of her bone, e.g., Denisova 11’s mother was more closely related to Neanderthals dwelling in western Europe than those residing in the Siberian cave some 120,000 years ago. Denisova’s paternal relatives, on the other hand, stuck to the region surrounding the cave—Denisova 3, the hominin whose pinky toe first led scientists to the species, lived in the area a few thousand years after Denisova 11.Bvatant (talk) 19:29, 24 August 2018 (UTC)
Why are people assuming there is no ambiguity here and that those who use it one way or the other are simply wrong? - Jmabel (talk) 19:33, 24 August 2018 (UTC)
Please see above, where I wrote "The item is about the humanoid, not the bone. If you wish to create an item about the bone, no-one is stopping you.". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:16, 24 August 2018 (UTC)
So this is item not about a member of Hominidae (Q635162), but only the reseamblace (humanoid) with a „human“ (=Q5?) --Succu (talk)
I presume Andy meant to write "hominid" rather than "humanoid". And I suspect you are trying to pick a fight rather than to reach consensus. - Jmabel (talk) 02:58, 25 August 2018 (UTC)
Did he? He referenced humanoid (Q502931) [8], [9]. --Succu (talk) 20:57, 25 August 2018 (UTC)
From the original publication (first sentence of the abstract): „Neanderthals and Denisovans are extinct groups of hominins that separated from each other more than 390,000 years ago.“. What consensus do you have in mind, Jmabel? --Succu (talk) 20:23, 27 August 2018 (UTC)
The one most of the people here seem to be trying to work toward, rather than see how close to their own original view we can end up. - Jmabel (talk) 22:28, 27 August 2018 (UTC)
From en:Hominid (disambiguation): „A hominid is any primate in the family Hominidae“. From en:Humanoid: „is something that has an appearance resembling a human without actually being one“. From your point of view: are these references well done? --Succu (talk) 20:47, 28 August 2018 (UTC)
To cite from a publication I referenced today multiple times Genera of the human lineage (Q28177674): „What Is a Hominid?“ They are not wondering about to be humanoid (Q502931), Mr. Pigsonthewing. --Succu (talk) 20:00, 1 September 2018 (UTC)
Try Nuclear and mitochondrial DNA sequences from two Denisovan individuals (Q29013840). Of course these fragments belog to a particular individual, but they are not same as these individuals. --Succu (talk) 20:35, 24 August 2018 (UTC)
@Jmabel:. Yes there is ambiguity, that's why we are discussing :-). For the sake of Wikidata consistency (at least local consistency) we must come to a consensus, or agree the name is ambiguous and create two elements, one for the person, and one for the fossil.Bvatant (talk) 20:52, 24 August 2018 (UTC)
Only the secondary sources (you added) use the term „hybrid“ not the primary source: The genome of the offspring of a Neanderthal mother and a Denisovan father (Q56234568). --Succu (talk) 20:09, 27 August 2018 (UTC)
Neanderthal (Q40171) == Extinct species of the genus Homo"; Denisova hominin (Q151055) == "Paleolithic-era species of the genus Homo"; ;hybrid (Q42621) == "offspring of cross-species reproduction". Though why the former two items are not marked up as having, for instance, parent taxa, is left as an exercise for the reader. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:58, 28 August 2018 (UTC)
Could you please explain this cryptic answer. Thanks in advance. --Succu (talk) 21:00, 28 August 2018 (UTC)
wikt:exercise for the reader. But never mind, I found out why Q151055 has no parent taxon Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:13, 28 August 2018 (UTC)
Oh, it would be very interesting to have scientific reference for the treatment of Denisova hominin (Q151055) as a species (Q7432). --Succu (talk) 21:06, 28 August 2018 (UTC)
Perhaps you could ask an editor who labelled it as such. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:13, 28 August 2018 (UTC)
That's the way you argue: Version vom 11. März 2014, an early Bot expierence?
BTW The evolution of Homo sapiens denisova and Homo sapiens neanderthalensis miRNA targeting genes in the prenatal and postnatal brain (Q28603765) is a source which treated Denisova hominin (Q151055) as subspecies (Q68947)... --Succu (talk) 21:29, 28 August 2018 (UTC)
If this item is about the girl then why this item is not an instance of human (Q5)? --Succu (talk) 21:14, 24 August 2018 (UTC)
The description of Q5 is "common name of Homo sapiens (Q15978631), unique extant species of the genus Homo" (though I shall now remove the QID from that)). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:18, 24 August 2018 (UTC)
I think the usage of female (Q6581072) implies human (Q5). You added the references. --Succu (talk) 21:26, 24 August 2018 (UTC)
I would gladly extend the definition of Q5 to include the whole genus Homo.Bvatant (talk) 21:36, 24 August 2018 (UTC)
I don't think that's OK. Please see population (Q15840798). --Succu (talk) 21:29, 25 August 2018 (UTC)
That is a subclass of population (Q2625603) (which you added on 25 August) and of Homo (Q171283) (which you added on 26 August). Aside from that issue; what is its relevance here? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:20, 1 September 2018 (UTC)
I'm aware of what I added to population (Q15840798), and I think you are aware about what I meant above. --Succu (talk) 20:08, 1 September 2018 (UTC)
My question - which you have not answered - was "what is its relevance here?". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:25, 1 September 2018 (UTC)
„relevance“ of what. Please don't be vague. Thx. --Succu (talk) 21:13, 1 September 2018 (UTC)

I removed two wrong references to The genome of the offspring of a Neanderthal mother and a Denisovan father (Q56234568). --Succu (talk) 20:14, 1 September 2018 (UTC)

Promptly reverted of course... --Succu (talk) 20:20, 1 September 2018 (UTC)
[ec] I've restored the source. I note that Succu gives no indication of why they believe it to be "wrong". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:25, 1 September 2018 (UTC)
What about a full text search? --Succu (talk) 20:30, 1 September 2018 (UTC)
Maybe you find this change more „entertaining“. --Succu (talk) 20:52, 1 September 2018 (UTC)
entertaining. Not for me! --Succu (talk) 21:01, 1 September 2018 (UTC)

Is there any reason why this girl should not be treated as an instance of Denisova hominin (Q151055)? --Succu (talk) 05:48, 2 September 2018 (UTC)

Yes: The subject is "...a hybrid between Neanderthals and Denisovans.", as quoted from one of the cited sources; had a "Neanderthal mother" according to a second cited, and quoted, source; and was "...the offspring of a Neanderthal mother and a Denisovan father" according to the quoted title of a further cited source, which you yourself created as an item - which is why the reason I gave in the edit summary for the diff you provide was "per cited & quoted sources". Conversely, your claim that she was a straightforward "instance of Denisova hominin" was uncited. Your repeated, and unexplained, attempts to make this item about anything other than what it actually is about are becoming tendentious. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:15, 2 September 2018 (UTC)
So if you insist on the exact wording of your secondary sources: I can not find the word humanoid (Q502931) in your reference Remains of hybrid human girl with Neanderthal mother discovered in Siberian cave. What I'm missing? --Succu (talk) 15:07, 4 September 2018 (UTC)
What are you missing? My post with the time stamp of "22:42, 23 August 2018", it seems. "if you insist on the exact wording of your secondary sources" I do not. HTH. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:57, 4 September 2018 (UTC)
I deleted the wrongly sourced statement. --Succu (talk) 20:00, 4 September 2018 (UTC)
And I reverted you, because it is a sourced statement. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 05:47, 5 September 2018 (UTC)
It's not the first time you reverted claiming „it is a sourced statement“ (aka as before). Could you please explain how your sourced statement supports the claim you made? Thx. --Succu (talk) 21:17, 5 September 2018 (UTC)
BTW: Most of your claims raise a „type constraint“. As father of Denisova 11 (Q56464945) and mother of Denisova 11 (Q56464406), created by User:Yair rand (thx) do. --Succu (talk) 20:41, 4 September 2018 (UTC)
As I have said previously, bad constraints can and should be fixed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 05:47, 5 September 2018 (UTC)
For hybrids we have hybrid of (P1531), so I've made an adjustment. --Succu (talk) 20:48, 11 September 2018 (UTC)
Reverted three times one, two, three with the edit comment as before by Mr. Mabbett. What exactly is wrong with this addition? --Succu (talk) 19:13, 17 September 2018 (UTC)

Maybe archaic human admixture with modern Homo sapiens (Q4785541) helps for a more general understanding... --Succu (talk) 21:41, 4 September 2018 (UTC)

Subclass of gene flow (Q143089)? Involving H. sapiens? How does that help? Oh, and since you are concerned with „type constraints“, that has one. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 05:48, 5 September 2018 (UTC)
Done. --Succu (talk) 21:17, 5 September 2018 (UTC)

Two Wikipedias have now an article. Maybe this helps to get this settled. --Succu (talk) 18:26, 16 September 2018 (UTC)

The Silence may be with you. --Succu (talk) 21:49, 23 September 2018 (UTC)

Wikidata:Requests for comment/2018 administrator policy update

A RFC has been proposed on changes to various administrator and user conduct policies including edit warring, page protection, involved administrators, and interface administrators. --MediaWiki message delivery (talk) 23:25, 23 September 2018 (UTC) (for Rschen7754)

Converting references to point to items

I added the same reference to dozens of statements on multiple items. How could I (automatically?) convert those references to point to a new item which describes the source being cited, while deleting the duplicate data except for retrieved (P813)? Is it better generally to do so, even if the reference would not satisfy the notability policy if not for being used as a reference? Jc86035 (talk) 14:22, 23 September 2018 (UTC)

@Jc86035: If the same reference is being used on multiple items then it should meet the Wikidata notability guidelines under the "structural need" criteria, and I would recommend creating an item for it and referencing it via stated in (P248). Wikidata:WikiProject Source MetaData and the Wikicite project might also be relevant. ArthurPSmith (talk) 12:18, 24 September 2018 (UTC)

songs on albums - published in or part of?

It seems like published in is the wiser choice. - Bossanoven (talk) 21:46, 10 September 2018 (UTC)

@Bossanoven: We have tracklist (P658) and "on the tracklist of" as an alias for published in (P1433) (@Moebeus: regarding that alias); do either of those properties help? Mahir256 (talk) 21:57, 10 September 2018 (UTC)

Ideally we would have a property for specifically linking music tracks to tracklists, but in the absence of that P1433 is a lifesaver, and matches with Property:P577 publication date, helpful for when a track is present on several releases. "part of" is too broad in my opinon. Moebeus (talk) 22:04, 10 September 2018 (UTC)

No resolution… perhaps @Simon Villeneuve: cares to comment? - Bossanoven (talk) 19:56, 23 September 2018 (UTC)
I don't know enough about this field to have a relevant opinion on that. If a consensus is found, it will be easy to transfer the info from one property to another. --Simon Villeneuve (talk) 00:01, 24 September 2018 (UTC)
@Bossanoven: I agree with Moebeus that it is somewhat unusual to say that a song or track is part of (P361) multiple unrelated releases. However, published in (P1433) might not be technically correct in all cases (unreleased albums for which the track listing is known, for example), so I would retain part of (P361) unless an inverse to tracklist (P658) is created. Jc86035 (talk) 02:20, 24 September 2018 (UTC)
If we're going to have inverse statements anyway, I think it would make sense to have a dedicated inverse property, so that we can have better constraints. It would also have the advantage of being able to change whether the property is a subproperty of part of (P361), published in (P1433), both or neither in the future without having to update lots of items every time we change our mind. - Nikki (talk) 16:50, 24 September 2018 (UTC)

Prog Archives ?

Prog Archives [10] is a huge and accurate database on-line dedicated to progressive rock, and I think it must be a valid identifier for prog bands and works, as Encyclopaedia Metallum is for metal bands and works.

What's your opinion about ?

 astio  talk  22:20, 23 September 2018 (UTC)

@Astio k: I think you could submit properties for this website at Wikidata:Property proposal (probably in the section for external identifiers – follow the instructions there). Virtually any external public database with standard URLs and without serious quality issues can have properties created for it. Jc86035 (talk) 02:28, 24 September 2018 (UTC)
@Jc86035: : thank U a lot. Today, I wanna get a look. Have a nice day.  astio  talk  07:54, 24 September 2018 (UTC)

Requesting a merge

Hi all, I have only ever used the Merge Tool, which isn't happy merging these two items which are duplicates of each other: Q28152644 and Q55045359. If someone could merge them for me (for use in WLM), it would be hugely appreciated. Thanks very much! Smirkybec (talk) 12:10, 24 September 2018 (UTC)

  Done --Pasleim (talk) 17:07, 24 September 2018 (UTC)

Property creation for structured data on Commons

Hello all,

As you may now, the project to connect Commons and Wikidata in order to provide structured data for Commons is moving forward. While some heavy technical changes are made, both communities are discussing about the best way to organize the data in the future. You can follow the state of the project and discussions here. The team expects the first deployments of statements on Commons (e.g. “depicts”) in the first months of 2019.

I wanted to share with you a few suggestions in order to move forward on the Wikidata side and be ready to welcome these changes.

  • For now, most of the discussions take place on Commons, which make senses, since the changes will have a big impact on them, but what about having also a place to discuss on Wikidata? Should we use the existing Wikidata:WikiProject Commons, create a dedicated one, or just keep discussing on the Project Chat?
  • In the next months, some new property proposals will be made by editors working on this project. In order to make them more visible, what do you think about creating a special section, just like it was done for Lexemes?
  • In general, do you have any questions about the project, any concern you would like to raise? The team working on SDoC, and especially the Community Liaison Keegan (WMF) will be happy to help.

Thanks, Lea Lacroix (WMDE) (talk) 07:22, 20 September 2018 (UTC)

  • Maybe the following points should be born in mind:
  1. Commons will introduce a new entity type (M-entities for media)
  2. the plan seems to be that properties are only created on Wikidata even if they are used mainly on Commons
  3. items used as values would be created on Wikidata (an exception might be some individual media creators such as photographers)
  4. Commons may have different usage rules and constraints for properties compared to Wikidata
  5. Commons might end up with a complicated use of "depicts"-statements
  6. Commons might generate some statements directly from image metadata
  7. it's possible to limit use of properties to Commons only (just as some properties only apply to L-entities or P-entities).
Hope I got that right. Personally I think mainly #4 could lead to confusion. --- Jura 08:01, 20 September 2018 (UTC)
@Lea Lacroix (WMDE): Will this have any impact on existing Wikidata properties that have Commons media files as values (for example image (P18) which is "Commons media file" data type)? ArthurPSmith (talk) 14:39, 20 September 2018 (UTC)
No, as far as I know. Lea Lacroix (WMDE) (talk) 07:55, 25 September 2018 (UTC)

Requests for Interface administrators

Should we have a dedicated page for requests for Interface administrators (linked from Wikidata:Interface administrators)?--Ymblanter (talk) 20:09, 24 September 2018 (UTC)

Wikidata:Requests for permissions/Interface administrator. Sjoerd de Bruin (talk) 20:11, 24 September 2018 (UTC)
My apologies for not being exactly clear. What I mean is a page users can leave requests to edit pages which only interface administrators can edit.--Ymblanter (talk) 20:30, 24 September 2018 (UTC)
Other Wiki's have two different systems:
  1. A request page to change something, for example nl:Wikipedia:Verzoeken voor wijziging menu's en dialoogteksten
  2. Some template asking an administrator to edit a protected page, see {{Edit request}}
For this, the first system is probably best. People can just put it on their watchlist and I don't expect a high volume of requests. I guess the name would be Wikidata:Interface administrators' noticeboard in line with the other similar noticeboards we have? Multichill (talk) 15:15, 25 September 2018 (UTC)

Wikidata weekly summary #331

 
Here's your quick overview of what has been happening around Wikidata over the last week.
  • Development
    • Work on editing Form statements using the API (phab:T194732)
    • Show the Lemma(s) or Representation(s) when Lexemes or Forms are mentioned in constraint reports (phab:T195315)
    • Add hyphenation for long Lexeme lemmas and representations (phab:T195367)
    • Normalize SPARQL queries (phab:T204122, thanks to Abiàn)
    • Fix a bug on the Query Service about exported query results being different from the displayed result (phab:T195258)
    • Fix a bug on the Query Service about empty map results returning error (phab:T178786)

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.


+ contemporary constraint (Q25796498) --- Jura 14:17, 25 September 2018 (UTC)

One or two items for one bridge in two locations ?

Hi all,

With @Jura1: we have a discussion on the french Project chat about should we have one or two items about a bridge that has been moved but it's going in circle and other point of view could help (@Fralambert, El Caro: also take part in the discussion.).

So, there is a bridge who was in London, UK and which is now in Arizona, USA. At the end of the discussion, we are midstream (pun intended) and we have two items: London Bridge (Q1868889) and New London Bridge (Q56739652). The second one is specific about the bridge when it was in London (not sure if it's really needed, I would tend to ask for its deletion) and the first is unclear; I see it as the bridge globally (qualifiers could easily deal with multiple locations) but Jura seems to see it as the new bridge in Arizona only.

What do you think? Did anyone had to deal with a similar situation?

Cheers, VIGNERON (talk) 14:54, 25 September 2018 (UTC)

  • I think the bridge is the same thing when it moves, just like a particular cast of a bronze statue is still the same item if it is moved from one museum to another. - Jmabel (talk) 17:02, 25 September 2018 (UTC)
  • I favor in this case two items because the Arizona bridge is not really the same thing as the London bridge. Both bridges look the same but while the London bridge was a stone bridge, the Arizona bridge is a reinforced concrete structure. The stones of the London bridge were only used to clad the concrete structure of the Arizona bridge. --Pasleim (talk) 19:38, 25 September 2018 (UTC)
  • I'd go by the commons categories here - that they should be separate entries. It looks like London Bridge (Q1868889) and New London Bridge (Q56739652) are the wrong way around with their commons links, though (and they generally need cleanup to make the distinction between the bridge in London and the bridge in Arizona). And then there's London Bridge (Q130206) for the present-day structure. Thanks. Mike Peel (talk) 00:11, 26 September 2018 (UTC)

Commons Louvre

The last few weeks I have noticed that for Louvre Museum (Q19675) and other items the radioBox Other sites now have been given a button Commons With link to the page https://commons.wikimedia.org/wiki/Louvre on Commons. The three values Commons category (P373), Commons gallery (P935) and Commons Institution page (P1612) are also used. What is purpose with the buttons in addition to the Three propoerties mentioned? Pmt (talk) 19:43, 25 September 2018 (UTC)

item name for a radio station?

I want to make an item for a local radio station (Salt Lake City's X96), but I'm not sure what to call it. Are there naming conventions for radio stations? Thanks Rachel Helps (BYU) (talk) 20:28, 25 September 2018 (UTC)

American radio stations are named after their call signs, just like on the English Wikipedia. X96 already has an item (Q6341519) with the label KXRK. Väsk (talk) 20:45, 25 September 2018 (UTC)
thanks Rachel Helps (BYU) (talk) 21:00, 25 September 2018 (UTC)

HURDAT P502 as external identifier

The property HURDAT HURDAT ID (P502) is described as an identifier per HURDAT (North Atlantic hurricane database) The property has datatype String. But is is described With Wikidata property for authority control (Q18614948). Should the Property therefore have datatype External identifier? Pmt (talk) 21:47, 25 September 2018 (UTC)

Q1754965

A user (user:Bossanoven) and I are in disagreement about the title/label of Chicago metropolitan area (Q1754965). His claim is it that should be called "Chicagoland", which is not the name of the English Wikipedia article, "Chicago metropolitan area". There are a number of reasons why the Wikipedia article has this title, chief among them is that Chicagoland is poorly defined. The term is also used largely by automobile sales advertisers, marketers, weatherpeople and traffic reporters, not so much by residents of the city of Chicago. "Chicago metropolitan area", by contrast, is defined by the US Office of Management and Budget (Q284392). In any case, this user keeps reverting me, and since I have no wish to get into an edit war with a user who has more edits here than I do, I am asking for input. Speciate (talk) 17:01, 25 September 2018 (UTC)

Reinheitsgebot creates wrong P570 claims

Hi all, I am tired in reverting all wrong P570 claims of Reinheitsgebot. It was working 10 minutes on it and I can not revert them over 2 hours. I gave up at Philippe Herreweghe (Q168039). Please help someone. Thank you. ato (talk) 07:14, 27 September 2018 (UTC)

  Resolved Thank you all. ato (talk) 09:47, 27 September 2018 (UTC)

British/Canadian English

Is there a database report of labels and descriptions which differ between en, en-gb (British) and en-ca (Canadian), possibly excluding normal spelling differences like color/colour? This isn't usually an issue but it gets quite annoying when property labels are changed in en and not updated for en-gb and en-ca (I use en-gb). It would also help to fix these for items (I think in general if a page move for a sitelinked page occurs then the label should be kept on a report until it's updated or checked). Jc86035 (talk) 12:03, 18 September 2018 (UTC) 

#SELECT DISTINCT ?property ?en_label ?engb_label ?enca_label ?en_desc ?engb_desc ?enca_desc
WHERE
{
    ?property rdf:type wikibase:Property .
    optional { ?property rdfs:label ?en_label. FILTER(LANG(?en_label) = "en") }
    optional { ?property rdfs:label ?engb_label. FILTER(LANG(?engb_label) = "en-gb") }
    optional { ?property rdfs:label ?enca_label. FILTER(LANG(?enca_label) = "en-ca") }  
    optional { ?property schema:description ?en_desc . FILTER(LANG(?en_desc) = "en") }
    optional { ?property schema:description ?engb_desc . FILTER(LANG(?engb_desc) = "en-gb") }
    optional { ?property schema:description ?enca_desc . FILTER(LANG(?enca_desc) = "en-ca") }
}
Try it!
As you can see, the majority of properties have no engb or enca label (which at least stops them from getting out of sync). There are only 120 where all labels/descriptions line up:
SELECT DISTINCT ?property ?en_label ?engb_label ?enca_label ?en_desc ?engb_desc ?enca_desc
WHERE
{
    ?property rdf:type wikibase:Property .
    optional { ?property rdfs:label ?en_label. FILTER(LANG(?en_label) = "en") }
    optional { ?property rdfs:label ?engb_label. FILTER(LANG(?engb_label) = "en-gb") }
    optional { ?property rdfs:label ?enca_label. FILTER(LANG(?enca_label) = "en-ca") }  
    optional { ?property schema:description ?en_desc . FILTER(LANG(?en_desc) = "en") }
    optional { ?property schema:description ?engb_desc . FILTER(LANG(?engb_desc) = "en-gb") }
    optional { ?property schema:description ?enca_desc . FILTER(LANG(?enca_desc) = "en-ca") }
    filter(str(?en_label) = str(?engb_label)). filter(str(?en_label) = str(?enca_label)).
    filter(str(?en_desc) = str(?engb_desc)). filter(str(?en_desc) = str(?enca_desc)).
}
Try it!
Personally I feel we should just deprecate en-gb and en-ca - the incredibly small number of cases where they're useful don't seem to make up for the hassle of chasing discrepancies and synchronising labels, and it is also a little weird that it's implicitly defining "en" to be en-us. But that's another issue, and probably something we should have thought about more five years ago. Andrew Gray (talk) 19:49, 18 September 2018 (UTC)
I'd assume plain "en" can use any widely-used variant spelling, and that en-gb would only be set in cases where there's a specific variant to be used. If there's no en-us, that's surprising. Ghouston (talk) 00:55, 19 September 2018 (UTC)
Yeah, it's not an ideal situation. In general the en versions mostly (but not universally) use en-us spellings for cases where the two differ. Thankfully Wikidata seems to be mostly free of edit wars about the correct English labels for items - we've avoided that traditional enwiki pastime! Maybe it's because we can't make snippy comments in the edit summaries :-)
We retained en-gb and en-ca after a fairly short discussion in May 2013 (Wikidata:Requests for comment/Labels and descriptions in language variants). The UI issues I mentioned then have improved a lot over the past five years; back then it was a real mess because you'd just get Q-numbers and P-numbers in links everwhere rather than falling back to en. So it's no longer as much of a problem as it used to be, just a bit of a maintenance hassle.
Going back to the original question, for items rather than properties, see User:Pasleim/Language statistics for items, which identifies about 75% of items as having an en label, but only ~2.5% with en-ca or en-gb. Numbers are a bit better for descriptions where a little over 30% of en-ca or en-gb have them, but I wonder how many of those are bot-filled boilerplate like "disambiguation page", "journal article", etc. Aliases for items are rare in both (10-20k items with aliases as against a few million for en)
By comparison, simple has been aggressively cleaned of localised terms, with virtually no items having labels, descriptions, or aliases. I guess the idea here is that the names of things are unlikely to be simplified so we won't need to have diferent labels? Andrew Gray (talk) 17:11, 19 September 2018 (UTC)
It seems silly to set the en_gb and en_ca labels and description to the same values as en: better to just leave them blank. Why should bots do that? If I change the en values, I typically won't notice if en_gb and en_ca differ, because they aren't shown by default, just the two languages I've set in a babel box. Ghouston (talk) 21:59, 19 September 2018 (UTC)
I definitely agree with this part. Copying en labels/descriptions to en_gb and en_ca seems like a sure-fire way to get outdated labels/descriptions there in the future. Just let the language fallback system do its job, IMHO. —Galaktos (talk) 10:18, 20 September 2018 (UTC)
@Galaktos, Ghouston, Andrew Gray: Thanks for the info. I would favour a new RFC proposing to (1) allow for the official designation of en as American English, zh as either Traditional Chinese (Taiwan) or Simplified Chinese (China),* and so on; (2) actually designate official variants for specific languages like en and zh; (3) [automatically] remove labels and descriptions for language variants (including Hokkien, Old English, etc.) where the variant text is identical to the fallback text. Jc86035 (talk) 12:13, 22 September 2018 (UTC)
* There are phrases and transliterations which differ between the regional variants, so this is an important distinction. Unfortunately, mandating a default for all languages and not just English would probably instigate at least one geopolitically-tinged fight. I guess for languages like Chinese which don't implicitly have a default variant (whereas there isn't actually an en-us in the software), the status quo of using the primary language variant used in the sitelinked Wikipedia article could be made official instead (if it isn't already). Jc86035 (talk) 12:44, 22 September 2018 (UTC)
@ Jc86035: I don't think your suggested (1) is a good idea at all, I'm afraid. en is not American English and that should not be adopted as our official standard. Making that definition will a) cause endless confusion in future, and b) has some unpleasant overtones ("American is the correct English and everything else is dialects of it") - I'm sure you don't mean that, but it's what people will interpret it as! It's worth remembering that one of enwiki's undeniably more successful moves has been to explicitly discourage splitting national variants, and after seventeen years I think we can reasonably say it's practical for people to coexist reasonably well on a single language code.
My personal preference would be to abandon both en-gb and en-ca (and arguably even simple) and settle on just en, with some compromises around primary labels and aliases as needed, but failing that, we should add en-us rather than redefine "common" English as being en-us.
The recommendation in (3) for fallbacks and removing unnecessary labels etc makes sense, and it seems to have been done for simple already without any problems (although I don't think many people would ever use that as an interface language). Andrew Gray (talk) 16:49, 22 September 2018 (UTC)
@Andrew Gray: The American English issue is mostly the same as phab:T33874 (issue open since 2011), and Wikidata seems to have inherited this lack of en-US. The comments on the bug make it clear that "en" was always implicitly intended to be American English in MediaWiki, even though "American" is, of course, not always the same as "international" (e.g. metre/meter, railway/railroad, football/soccer). Since there has been virtually no progress made since the bug was created, I think it would be prudent to either (a) obtain at least local community consensus for creating some or all of the locales en-US, en-AU, en-ZA, en-IE, en-NZ, en-IN, en-SG, en-NG, en-PK and pt-PT in Wikidata and in MediaWiki, since this would give developers some impetus for actually implementing the necessary software changes; or (b) obtain community consensus for deprecating en-ca and en-gb within Wikidata or even technically preventing users from adding en-gb and en-ca labels and descriptions. Jc86035 (talk) 07:01, 23 September 2018 (UTC)
The problem is that Wikidata treats language variants as completely independent languages, when they're not. I would like to see a way of grouping certain codes together with the option to expand and collapse the group. When the labels don't differ, the group would be collapsed by default and it would update all variants simultaneously when editing. When they do differ, the group would be expanded by default and the variants would be editable separately. - Nikki (talk) 08:54, 28 September 2018 (UTC)

Nationality

There was a discussion about a proposed property Nationality. This discussion is closed as "not done", which is no so strange given the discussion. Unfortunately most of the discussion is simply wrong, and I wonder if it is a carry over from American English.

There are three closely related concepts; the citizenship of a state, the ethnicity, and the nationality of a person. The citizenship is given by country of citizenship (P27), and the ethnicity is given by ethnic group (P172), but there are no way to express nationality.

A state exist within some timespan. It comes to existence because of births of rulers, deaths of rulers, wars, etc. Whatever state exists when a person is born often defines his or hers citizenship. A person can't be a citizen of a state that does not exist within his or hers lifetime. Erik the Red (Q172345) wasn't citizen of Norway (Q20), and it does not help adding sources![11] The state of Norway had its inception in 1905. About 1000 years after Eirik Raude was born. (Now I'll be spanked with a frozen Q2258881 by someone from Q189)

A nation exist without any clear timespan. It comes to existence through time and it dissolves. Norway has a previous history as "the North Way" (Heide, Eldar, 2017: "Noregr tyder nok vegen mot nord, likevel".Namn og nemne, 2016. Vol 33, 13-37.) and people belong to this strange nation long before the state, even before unions with Sweden and Denmark, and even before all the small kingdoms.

A nation is not ethnic group (P172), it consists of people from one or more ethnic groups. The nation Norway has several ethnic groups, like the Sámi people (Q48199), the Kven people (Q610315), and then the Norwegians (Q188779). The nation has ethnic groups.

And then, at some point in time, the state is the nation, in part or the whole.

Willy Brandt (Q2514) was a German all his life, even if he had a Norwegian citizenship for a few years.[12] He was both an ethnic German and part of the German nation, even if he did not posses a German citizenship for ten years.

Right now we can add country of citizenship (P27) without sources, which is strange because it is very hard to prove anybody's citizenship without accessing protected state-owned databases. It is although rather easy to define someone's nationality. It is like "quacks like a duck – is a duck".

We need some kind of property for nationality, and that property is not country of citizenship (P27) and it is neither ethnic group (P172). Jeblad (talk) 19:48, 23 September 2018 (UTC)

Agreed. - PKM (talk) 20:52, 23 September 2018 (UTC)
No more than one? This is a property that is previously denied? Jeblad (talk) 09:20, 27 September 2018 (UTC)
@Jeblad: the nationality issue is something we haven't properly tackled yet. I think the most recent iteration of conversation was at Property_talk:P27#Multiple_UK_values_-_reality_check_pls. I think to solve this problem, someone should take the time to gather what is discussed and create a page (Wikidata:Nationality problem?) describing the problem (not a proposed solution). That page can be improved until we reach consensus about the problem is exactly (it's actually multiple overlapping problems, but that should be clear by then). Based on this agreed on description of the problem, we can work towards a solution to fix it. Yes, this is a lot of work and will take quite some time, but probably the only way to actually solve this. Multichill (talk) 19:58, 27 September 2018 (UTC)
I agree completely with Multichill. I tried making some notes towards this earlier in the year but it rapidly became a really large task and I've struggled to get anywhere with it - if anyone would like to take up the task let me know and I'll dig them out. I think I could identify at least five or six connected problems here and none of them are easy. Andrew Gray (talk) 20:02, 27 September 2018 (UTC)

Property for creation

Wikidata:Property proposal/Australia and New Zealand Standard Research Classification 2008 has unanimous support and has been open for the requisite seven days; I should be grateful if someone can expedite its creation as it ties in with my current tour of Australia, speaking about Wikidata. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:19, 28 September 2018 (UTC)

Bad coordinate data from Russian Wikipedia upload.

Could we have a do-over for all the coordinates uploaded from the Russian Wikipedia? They are nearly all over-rounded and now the bad coordinates are contaminating the English Wikipedia. Basically any coordinates that don't report non-zero arcseconds are incorrect. Abductive (talk) 20:35, 29 September 2018 (UTC)

This is also my experience.--Ymblanter (talk) 19:59, 30 September 2018 (UTC)
Abductive, could you explain, or provide a link to, your belief about how coordinates should be rounded. My opinion is that if the coordinates fall within the feature being located, they are adequate, although it's better if the coordinates appear to be visually near the center when viewed on a map. Jc3s5h (talk) 15:59, 1 October 2018 (UTC)
My belief? Sounds dismissive. If you don't mind incorrect data on WikiData, there's nothing I can say to convince you. And I have already complained here about the Russian Wikipedia being many km off in some instances. Abductive (talk) 04:20, 2 October 2018 (UTC)
You have just been asked for the evidence. Why such a tone? Matěj Suchánek (talk) 14:04, 2 October 2018 (UTC)
There are multiple possible ways to decide on precision. My preferred approach would be to use a precision commensurate with the size of the feature, but sufficiently precise to make the point fall within the feature (so the point for a 1000 km river might need a precision of 10 m to make sure it falls within the river). Another approach, which I loath, is to have many digits of precision so it is clear the value was typed using arcseconds rather than decimal degrees. Another approach would be to reproduce the precision of the instrument that made the measurement, so if the coordinates of a 10 km by 10 km town were measured with a survey-grade GPS, the precision would be 0.001 arcsecond (another approach that I woudldn't favor). Jc3s5h (talk) 14:29, 2 October 2018 (UTC)
There are problems with the 'size of the feature' metric. One is that it introduces an additional layer of work for people who are trying to do a good job, and simultaneously encourages the lazy "it's close enough" squad. Two is that lower precision has traditionally been used to indicate both uncertainty (Q13649246) and measurement uncertainty (Q1403517), as might be the case for battles fought long ago. Three is that even very large entities such as countries have geographic centers that have been worked out by reputable secondary sources to a higher degree of precision than would be specified by their size. This means deliberately ignoring the sources to reduce accuracy for no real reason. And four, most large features such as national parks have a main parking lot or main headquarters whose location is far more useful than the rounded geographic center, which, by the way, is not easy to work out. Five, this is also true of many irregularly shaped geographic features: Do we look at their area? Their widest dimension? What about an object like a lake whose center works out to be on dry land? Abductive (talk) 19:37, 2 October 2018 (UTC)
This section was archived on a request by: I think we already had this: Wikidata:Project_chat/Archive/2018/07#Coordinates_"Imported_from_Russian_Wikipedia". --- Jura 12:16, 4 October 2018 (UTC)

Photographing trip: Mark items that can not be uploaded to Commons anyway?

I often go out of my way to photograph an item that has no image yet (using the Commons Android app or WikiShootMe).

So I arrive there, take a picture, and... realize I can not upload it to Commons due to copyright problems.

This problem could be avoided if the item was somehow marked as "No need to go there because pictures of that item can not be uploaded to Commons anyway". The app and WikiShootMe could filter out such items, thus allowing people like me to go to more useful places. Is there anything like this?

Thanks! Syced (talk) 07:51, 28 September 2018 (UTC)

One option could be to add a statement "image: no value" and then potentially some qualifier to explain it more similar to "reason for deprecation". --LydiaPintscher (talk) 16:50, 28 September 2018 (UTC)
Great idea! Would nobody be against that? If not I will start doing like this. Syced (talk) 03:50, 29 September 2018 (UTC)
Prototype: Monument to Osip Mandelstam in Vladivostok (Q25394721) Does that look acceptable? Syced (talk) 03:58, 29 September 2018 (UTC)
Looks reasonable to me. - Jmabel (talk) 18:32, 29 September 2018 (UTC)

Hi!

I'm trying to parse Wikipedia articles to get a distant-supervision training set for relationship between literary characters, and I'm running into an issue:

Many book/movie characters in EN locale do not have their own standalone page; instead, they are organized into a List_Of page with anchored links that redirects to the corresponding section of the page. For example:

"Marge Dursley" redirects to "List_of_supporting_Harry_Potter_characters#Marge_Dursley"

I would like to associate the Wikipedia link "List_of_supporting_Harry_Potter_characters#Marge_Dursley" with the "Marge Dursley" Wikidata entity: https://www.wikidata.org/wiki/Q2567947

However, I cannot think of any easy/smart solutions. Here is a dumb one:

  1. Search the List_Of page's article name in rdcheck
  2. Find an exact matching of "Marge Dursley", get all of the titles that redirects to "Marge Dursley", e.g. "Aunt Marge"
  3. Search via Wikidata's SPARQL endpoint with the names (there could be multiple results, but I can filter them by checking for attributes pertaining to literary characters)

Has anyone tried to solve this before?

Thanks!

James 54.240.198.33 08:52, 28 September 2018 (UTC)

We don't support linking to section headers or redirects (at the moment). How do we track changes on them for example? Related discussion can be found here: Wikidata:Requests for comment/Allow the creation of links to redirects in Wikidata. Sjoerd de Bruin (talk) 13:48, 28 September 2018 (UTC)
Use described at URL (P973) such in crank magnetism (Q43195941). Visite fortuitement prolongée (talk) 09:07, 29 September 2018 (UTC)

Data Donation from OpenBenches.org - howto?

As per the Data Donation page, I'm interested in seeing how I can properly donate a dataset.

OpenBenches.org is a crowd-sourced database of memorial benches. It includes geolocation, images, and text of inscription.

New data is added every few days, and is available as GeoJSON (or CSV, MySQL, etc - whatever's easier).

Is this sort of data useful to this site? If so, what's the best way to collaborate?  – The preceding unsigned comment was added by Edent (talk • contribs).

  • I'm not sure all (or even most) of this reaches Wikidata's level of notability; I think we should work that out before focusing too much on technical solutions. But things can be done pretty easily with CSV, if there is a reason to do them at all. - Jmabel (talk) 18:35, 29 September 2018 (UTC)

New item

I have created Q56809534 but I don’t know why the languages in the each wikipedia do not appear... --151.49.81.242 13:43, 29 September 2018 (UTC)

I have deleted it, because "Does not meet the notability policy". You can see the policy in Wikidata:Notability, point n° 1. --ValterVB (talk) 13:49, 29 September 2018 (UTC)

Noobie Questions

Now I'm curious about this WikiData thing. I found something needing merging, then came back about "The Dog" ( https://www.wikidata.org/wiki/Q28136699 ). Seeing that no one had touched it I looked into it. The information does not overlap. Then I wondering about why I'm unable to add more details to that article.

For example, The Dog has two co-directors and I can't even add one, much less worry about duality.

I find it strange that I can add "terrorism" as one of the main subject qualifiers but I can't add "theft" "robbery" "bank" etc. (I pulled up Iron Man (2008 film) to use as a template/reference for adding details.)

Turns out I can still add a lot in "depicts" and "main subject". Is there a difference? I added much of the same to both.

I stumbled upon a glitch: Adding the film premiere info (URL, title, date, retrieved date, author), all was fine until I tried to add unknown authors, then it would freeze and no longer "publish" - even when I removed the 'author' part. The first time I'd filled out all the things without publish-saving. The second time I'd filled out each item and published one at a time - until I had to refresh Firefox. Similarly, I discovered you have to add the co-directors names and some details before you can even reference them. Empty non-links are not allowed yet people stubs are. Weird.

I also wanted to add the link to my original article https://infogalactic.com/info/The_Dog_(2013_film) (almost identical because I wrote them at the same time - but IG has an image that was removed on WP (who censor everything)).

I have no dog in maintaining "The Dog" or it's unimportant article, but I thought it'd be a good enough place to learn about WikiData.

I kinda see the potential but there's sooooooo far to go - and then there's the faaaaaaar bigger problem of the corporatocracy censorship, distortion of events, evasive truth, and intolerance of anti-establishment ideas and authentic freedom. Any A.I. that may use this is already crippled by all the corrupted systems, including legacy media the limited and limiting so-called source of "facts" allowed on Wikipedia, etc.

Suggestions for good tutorial videos or a short overview would be greatly appreciated. ~ JasonCarswell (talk) 06:54, 15 September 2018‎ (UTC)

Retrieved from "https://www.wikidata.org/w/index.php?title=Wikidata:Project_chat/Archive/2018/09&oldid=2030239688"