Shortcuts: WD:PC, WD:CHAT, WD:?

Wikidata:Project chat

From Wikidata
Jump to navigation Jump to search

Wikidata project chat
Place used to discuss any and all aspects of Wikidata: the project itself, policy and proposals, individual data items, technical issues, etc.
Please take a look at the frequently asked questions to see if your question has already been answered.
Please use {{Q}} or {{P}}, the first time you mention an item, or property, respectively.
Requests for deletions can be made here. Merging instructions can be found here.
IRC channel: #wikidata connect
On this page, old discussions are archived. An overview of all archives can be found at this page's archive index. The current archive is located at 2018/12.

Project
chat

Lexicographical
data

Administrators'
noticeboard

Development
team

Translators'
noticeboard

Request
a query

Requests
for deletions

Requests
for comment

Bot
requests

Requests
for permissions

Property
proposal

Properties
for deletion

Partnerships
and imports

Interwiki
conflicts

Bureaucrats'
noticeboard

Scholarly articles that are book reviews[edit]

If a scholarly article is a book review, should the “main subject” be the edition of the book, or the subject of the book, or both? - PKM (talk) 02:32, 14 November 2018 (UTC)

@PKM: In the absence of a single value constraint on P921, I see no harm in using both. Mahir256 (talk) 03:10, 14 November 2018 (UTC)
@PKM:Typical problem when mixing different classifications: scholarly article is a text format, book review is about the content of a text. WikiProject Books should once fix the classification by analyzing in detail the characteristics of a book. Snipre (talk) 07:37, 14 November 2018 (UTC)
@Snipre: While a "scholarly article" as used in WD is clearly more like an "edition" than a work (based on its properties), currently, "scholarly article" is <subclass of> "article" is <sublcass of> "work" (while also being a subclass of "publication"). If you have an idea of a way to separate "publications" from "works", please lay it out so we can discuss - I agree this area is fuzzy. But I would say that a "book review" is a type of article either way. In any case, I would not recommend or support making separate "work" and "edition" items for every scholarly article in WD. That way lies madness. - PKM (talk) 20:47, 14 November 2018 (UTC)
@PKM: In relation to your original question, I think "main subject" should point to the book-edition. The item should also be identified somehow (genre?) as a book review. I am dubious about "main subject" also pointing to the book-subject. How much would one learn about the book-subject in the round from the book review? Possibly an case for a weaker subject indicator, perhaps the proposed subject keyword property? Jheald (talk) 22:09, 16 November 2018 (UTC)
@Jheald:, that's my first instinct as well. book review (Q637866) is currently a genre, so that part works. Lots of missing books, alas. Also, we have 2789 items with <instance of> "book review". - PKM (talk) 22:18, 16 November 2018 (UTC)

Just going to throw in that IMO academic journal article (Q18918145) is more accurate than scholarly article (Q13442814) for the instance of (P31) statement of a book review. Circeus (talk) 14:24, 21 November 2018 (UTC)

@Circeus: Agreed! - PKM (talk) 20:51, 24 November 2018 (UTC)

My two cents, @PKM: I created Le nom de peuple Rhedones (Q52160525) some times ago. What do y'all think? Cdlt, VIGNERON (talk) 17:52, 24 November 2018 (UTC)

@VIGNERON: That's very nice! - PKM (talk) 20:51, 24 November 2018 (UTC)
Shouldn't "book review" be a property, rather than an item, as Q637866?
Example: I just created Q59319726 for a book. A published review of that book was previously available as Q58565334. There should be a way to link these two. If "book review" were a property, one could then specify the book as a property of the review. ???
We need some way to link a review with the book it reviewed. Please suggest an alternative or endorse this. Thanks, DavidMCEddy (talk) 03:12, 1 December 2018 (UTC)
Another example: Q58570163 is a review of a book for which a Wikidata seems not yet to exist. I plan to create a Wikidata entry for that book.
Shouldn't the "scholarly article" that is a book review have a property = "review of" being the book? And shouldn't the book have a property "reviewed as", being the review?
I see properties "review score", "review score by", and "reviewed by". None of these sound to me like either "review of" or "reviewed as".
Thanks, DavidMCEddy (talk) 19:56, 3 December 2018 (UTC)
@DavidMCEddy: I have no problem using the existing "main subject" to include the meaning "review of", but I wouldn't object to a separate property "review of" in lieu of both "main subject" and <instance of> "book review" for these items. That would be a very clean solution. - PKM (talk) 20:48, 10 December 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── I've also run into a number of "scholarly articles" that are reviews of museum exhibitions. I've addressed these by creating items for the exhibitions and linking from the review using "main subject". (See ‘Opus Anglicanum: Masterpieces of English Medieval Embroidery’, Victoria and Albert Museum, London, 1 October 2016–5 February 2017 (Q57678571).) Whatever solution we come to should probably handle other types of reviews than book reviews (so if we make a new property "review at" or somesuch, it could accept reviews of plays, films, exhibitions, and books. - PKM (talk) 20:44, 10 December 2018 (UTC)

EOL has changed all its URLs/IDs[edit]

Encyclopedia of Life (Q82486) has changed all its IDs and URL formats, making Encyclopedia of Life ID (P830) wrong where it is used. Example: Prunus prostrata (Q1258395) links to https://eol.org/pages/631658 but should link to https://eol.org/pages/11164788. Abductive (talk) 07:13, 27 November 2018 (UTC)

  • I updated the description. You might want to propose a new property for the new scheme. --- Jura 07:23, 27 November 2018 (UTC)
    • What, keep the old IDs live on Wikidata, and add the new IDs? Abductive (talk) 07:26, 27 November 2018 (UTC)
    • By the way, on how many items is P830 used? Abductive (talk) 07:27, 27 November 2018 (UTC)
  • Yes, for stability's sake, we don't mix the old and the new scheme. Otherwise data users couldn't be sure what they are getting. --- Jura 07:35, 27 November 2018 (UTC)
  • I'm going to leave to pesky details on creating a property and editing 1,375,794 items to you guys. Abductive (talk) 20:11, 27 November 2018 (UTC)
@Abductive: Your claim „EOL has changed all its IDs and URL formats” is wrong.
@Jura: formatter URL (P1630) has to be changed from http://eol.org/pages/$1/overview to https://eol.org/pages/$1. That solved the general problem.
@Abductive: EOL ids refer to taxon concepts and are a subject to change. In the past we had EOL ids that refered to internally used ids and caused similar errors. Maybe references to The Plant List 1.1 (Q15628808) got new ids. Not sure at the moment.
--Succu (talk) 20:15, 27 November 2018 (UTC)
In my example the ID is different. That may not always be the case? Anyways, I have already stated that this is not my forte. It's up to you guys to fix or ignore link rot (Q1193907) as you see fit. Abductive (talk) 20:19, 27 November 2018 (UTC)
Sorry, but rechecking the known 2,237,550 EOL ids against our taxa has a low priority on my todo list. --Succu (talk) 20:37, 27 November 2018 (UTC)
Presumably this can be automated? Perhaps by another with the requisite skill set? Abductive (talk) 05:40, 28 November 2018 (UTC)
Regarding your example: Added by User:BotNinja (= User:Termininja). --Succu (talk) 20:56, 27 November 2018 (UTC)
Okay, so you don't want to fix it either. I completely understand; this is a volunteer project and nobody knows how to write a program to fix these things. Abductive (talk) 02:25, 4 December 2018 (UTC)
You are wrong and as I told you above this has a low priority on my todo list. --Succu (talk) 22:15, 10 December 2018 (UTC)
So, you are the only person here capable of doing it? Abductive (talk) 18:40, 12 December 2018 (UTC)
Out of around 200,000 items having both PlantList-ID (P1070) and Encyclopedia of Life ID (P830) around 10,000 EOL ids are wrong now. I will correct them within the next days. --Succu (talk) 19:35, 12 December 2018 (UTC)

GlobalFactSyncRE/DBpedia project proposal[edit]

DBpedia, which frequently crawls and analyses over 120 Wikipedia language editions, has near complete information about (1) which facts are in infoboxes across all Wikipedias, and (2) where Wikidata is already used in those infoboxes. GlobalFactSyncRE will extract all infobox facts and their references to produce a tool for Wikipedia editors that detects and displays differences across infobox facts in an intelligent way to help sync infoboxes between languages and/or Wikidata. The extracted references will also be used to enhance Wikidata. For more see meta:Grants talk:Project/DBpedia/GlobalFactSyncRE

Please let us know what you think, your opinion is important to us! Thank you!  – The preceding unsigned comment was added by 212.27.205.232 (talk • contribs) at 13:38, 30 November 2018‎ (UTC).

Storing all sports results in Wikidata?[edit]

Hey, does anyone know if there has ever been any discussion about expanding Wikidata's sport data to include scores and other data from all matches of professional sports teams? On Wikipedia, it's pretty common to have this data in the articles for each team's season (e.g. en:2017–18 Manchester United F.C. season). This data ends up being duplicated a lot – every result needs to be recorded in both teams' season articles and the league's season article, in every language's Wikipedia. If this data were on Wikidata, it would be less work for editors to update when matches conclude, and it would automatically sync to every page in every language. It would also be incredibly valuable to anyone wishing to reuse Wikidata data for other projects. But, this would mean every sports match would have its own item, and we'd definitely need major buy-in from one of the larger Wikipedias for the data to be kept up to date. I'm curious what others think of implementing something like this. Thanks, IagoQnsi (talk) 17:51, 3 December 2018 (UTC)

The field of sports results is not well developed indeed. Some thoughts:
  • A major concern is about licencing of typically commercial sports results databases. Unlike in the cultural sector where lots of institutions move to open licences, most sports results databases are incompatibly licenced (with proprietary licences), as companies earn quite some money with their data. I am not sure based on which legal basis Wikipedias copy that much data from various proprietary databases, but doing so in Wikidata where we add an explicit CC0 licence tag to the sports results would clearly create some serious headache. At least for me.
  • If we ignore the legal concerns, some further thoughts: you can aim for in depth sports results that cover each and every aspect of a match/game/competition/tournament; this requires a lot of items likely on a per-match/race/fight/etc. basis, which need to be properly connected to each other and properly identified against external resources with identifiers; that is technically possible already now, but the amount of items would clearly make this a demanding task that requires a lot of automation. Alternatively, a simple approach would be to add consolidated results (winner, second, third, …, last place; with some relevant extra data like final scores, race time, etc) to existing items, but ignore all in-depth details that happened before the final round of matches; this way, one wouldn’t need to create lots of extra items and could immediately use such data in infoboxes etc, but one could not replace excessive data in pages such as en:2017–18 Manchester United F.C. season.
  • Another problem of in-depth results is that one also needs a lot of extra items about players, clubs, competitions, etc. that are not yet available. In Wikipedia, you can just add a red link if something is missing, but we cannot do so here. Formally, we are probably able to create many of these missing items as well (as long as they can be matched against an external resource), but this is a significant task by its own which should not be ignored.
  • When presenting sports results, all kinds of obscure special situations have to be considered and properly modeled. This is much easier to get done with unstructured, explanatory wikitext in Wikipedia than with structured data here at Wikidata.
  • There is also a desire to make “sports results in Wikidata” available according to a somewhat generic model that fits “all” types of sports, while still being able to consider sports-specific details. That would allow to gain lots of really interesting insight that is not even remotely available anywhere else. The excessive data collections in Wikipedia have not been designed with that aim; in Wikidata, the general model would be much more complicated to elaborate.
I would really like to see some progress regarding sports results in Wikidata. So, editors, please add more input here. —MisterSynergy (talk) 18:30, 3 December 2018 (UTC)
@MisterSynergy: Thanks for your thorough response. To respond to some of your concerns...
  • Licensing: You can't own the facts. If we went really in-depth (like detailed stats on each player), licensing might be an issue, but I don't think we need to go that far. Just the basics (e.g. teams, league, final score, date, time, referees, venue, line-ups, who/when for goals/discipline/substitutions, etc) would be enough. Our schema is entirely original, so there'd be no realistic basis for a copyright dispute.
  • Missing items: This will definitely happen sometimes, but I don't think it'd be entirely that often. On English Wikipedia, the notability standard for sports is a very low bar: for most major sports, if an athlete has appeared in even one fully professional match, they are considered notable. Thus, we have Wikipedia articles (and thus, Wikidata items) for even obscure players.
  • Lack of structure: This is true to an extent, and making a full data model won't be easy, but I think it's definitely doable. A lot of Wikipedia articles already use highly-structured templates such as en:Template:Football box collapsible (example: en:2017 Atlanta United FC season#Results). There will surely be some edge cases, but I think 99.9% of matches will be represented without major issues.
  • Need for automation: Automation will definitely be needed to initially add the data, but if we can get buy-in from a big Wikipedia, I think we might have a reduced need for ongoing automation. If, say, English Wikipedia started replacing manually-edited templates with Wikidata templates, then the hordes of people who typically update the articles would hopefully learn how to make the update on Wikidata instead (liberal use of "edit on Wikidata" links and explanatory source code comments will likely be necessary). For the initial import, we can hopefully automate importing a lot of data from articles that already use templates (as I mentioned in the "Lack of structure" bullet point). There are also some public domain sports data sources such as sport.db and football.db.
IagoQnsi (talk) 19:01, 3 December 2018 (UTC)
@IagoQnsi: "You can't own the facts": you are right ... if you extract the data from the newspapers, TV sport program or other different sources. But if you extract all data from the same source, then you are wrong. One fact id not copyrighted, but a set of structured facts in one data model is.
Then import from WP is not welcome as this is copyrighted under CC BY SA and WD is licenced under CC0. And I don't speak about the rejection by WP of massive and uncontrolled data from all WPs in WD. Snipre (talk) 20:42, 3 December 2018 (UTC)
@Snipre: In the U.S. (where Wikimedia's servers are located), a database is only copyrightable if there is something original/creative about the way the data was gathered/organized. Facts such as the date, the location, who won, who scored at what time, etc require no creativity to compile, and thus are not protected by copyright. These facts are comparable to phone book information, which the Supreme Court has ruled are not copyrightable, or to data in Wikipedia infoboxes, which we import to Wikidata all the time. It's possible that the visual layout of templates such as en:Template:Football box collapsible could be copyrightable, but we wouldn't be replicating the visual presentation on Wikidata -- we'd just be grabbing the raw data. In the European Union, there is the Database Directive which provides database rights as you described, but as long as we avoid importing data from European sources, we should be fine. More info: meta:Wikilegal/Database Rights, en:Sui generis database right. –IagoQnsi (talk) 21:05, 3 December 2018 (UTC)
Additional note: For importing data from the Wikipedia templates, we would definitely have to omit the 'notes' field, and we can't import the match report URLs unless we're very careful about it (sometimes people will add multiple URLs and/or link to the team's report instead of the league's, which could be argued as a creative decision). But for everything else, I don't think there's any realistic argument that any originality went into compiling that data. –IagoQnsi (talk) 21:22, 3 December 2018 (UTC)
@IagoQnsi: I am aware of meta:Wikilegal/Database Rights so I can only rcommend you to read it carefully, especially that comment about copyright protection in the US: "The level of creativity required is low, so it doesn’t have to be very creative — as long as the author had some discretion and made some choices in what to include or how to organize it, the database is likely to be protected." So if a website is copyrighting its database, better be careful before judging that Supreme Court reference can overule that copyright.
And your choice of using WP instead of original databases to import data into WD is clearly a way to bypass the copyright question, if it is really so clear that no copyright can be applied why don't extract data directly from the original databases ? Why use a dataset which is probably corrupted due to manual entry ? And finally you don't provide any argument to oppose the fact that WPs don't want to use WD data because WD is unreliable due to use of data from sources considered as no reliable reference. WP itself considers that WP data can't be used to source other WP statements but only external sources can be used as reference. You just reinforce their criticism about WD, so thank you to work so hard to transform WD as completely useless for WP. Snipre (talk) 20:10, 4 December 2018 (UTC)
@Snipre: I definitely agree that trying to import from premium sports databases that claim copyright is risky and not ideal. This is why I favor importing data from Wikipedia, since there's little risk that anyone would challenge our public domain rationale. I also like using that data because it's what Wikipedia is already using. It will be easier to convince the Wikipedia community to keep using the same data they already have (just migrated to a new place), rather than switching to a completely new data source that they don't know anything about. It doesn't really matter that it's unreliable when they're already using it anyway.
Additionally, my expectation is that we'd only really be importing data to start this project—moving forward, the data would be maintained by Wikipedia users. The existing data on Wikipedia doesn't come from a database – after every match, someone manually updates each article based on match reports. If we started replacing the old manually-edited templates on Wikipedia with new Wikidata-powered templates, then those people who used to update the templates would hopefully learn to update Wikidata instead. We've already got an army of volunteers doing the work of maintaining this data—we just need to redirect them to Wikidata. Of course, this will require major buy-in from the Wikipedia community, but I'm optimistic that we could get consensus—after all, this would be reducing their workload in the long-term. –IagoQnsi (talk) 20:55, 4 December 2018 (UTC)
If you import data from Wikipedia then the resulting data on Wikidata won't be accepted in any of the major Wikipedias. If your goal is to have data that gets used by multiple Wikipedias it's no available strategy. ChristianKl❫ 09:49, 5 December 2018 (UTC)
I've started working on a document outlining precisely what properties a sporting event can/should/must have: User:IagoQnsi/sports. Any feedback would be appreciated. –IagoQnsi (talk) 19:45, 3 December 2018 (UTC)
It seems to me like a collaboration with sport.db and football.db would be ideal as those projects already value putting data into the public domain. Given that they have a forum, how about asking there what they think about collaboration? ChristianKl❫ 10:58, 5 December 2018 (UTC)
@ChristianKl: I'm okay with the idea of using an external data source like football.db. However, if we're choosing to work with them over importing from Wikipedia because we don't think people will trust Wikipedia data, I don't think they're any better – just like Wikipedia's data, theirs is manually maintained by editors. Wikipedia data is probably more trustworthy because it usually includes a link to the official match report as a reference (which we could import to Wikidata). There are other issues with football.db's data as well. It's very incomplete and barebones – except for their World Cup, they only have the team names and the final score, even for the biggest leagues (e.g. English Premier League, Bundesliga, La Liga). For less-popular leagues like Major League Soccer, the data can be years out of date. Wikipedia data is much more detailed and is very up-to-date.
I know accuracy/reliability is a major problem with imported Wikipedia data, but I think it's a solvable problem. After importing the data, we can manually check it against official match reports, and then link those match reports in the reference field. This would be probably have to be done rather slowly, one league at a time, but I think it's the only way we can get data that is detailed, accurate, and not-legally-risky. –IagoQnsi (talk) 19:52, 6 December 2018 (UTC)

Wikidata in bussiness[edit]

I'm giving a talk/workshop about Wikidata in few days and wanted to include some info on examples of Wikidata use in bussiness world. Maybe we know something? --Edgars2007 (talk) 18:42, 4 December 2018 (UTC)

Apparently Apple use it, see for example [1]. Ghouston (talk) 02:12, 5 December 2018 (UTC)
Linked Geodata: OpenStreetMap (based commercial and community maps) using this. ( for example: Mapbox ) ; OpenStreetmap has a new name/brand sugestion index for contributors - with banks, shops - with wikidatid ( see : [2] ) ; osm_wiki"brand:wikidata" ; Current tags:osm_taginfo"brand:wikidata" ; Google/Facebook likes Wikidata + OSM : good for SEO ! --ImreSamu (talk) 12:57, 6 December 2018 (UTC)
Google uses it in Knowledge Graph, DuckDuckGo uses it for some of the external identifiers. Jc86035 (talk) 11:22, 7 December 2018 (UTC)

Purpose of Q19803442 and the like[edit]

How should Q19803442, Q19803497 and the like be used? Are they supposed to be for names where the person is known just by the initial (I'm looking at Q4647657) and if we find the full name, should that be there too? Or should it only be the letter name? Was this correct or should both have been kept? I can see why it would be helpful to keep track of B.B. King under Ben and Riley for given names but then should he also be under "B." as if that's an actual name? -- Ricky81682 (talk) 01:39, 5 December 2018 (UTC)

For convenience in reading: A. (Q19803442), B. (Q19803497), A. Craig Copetas (Q4647657). - Jmabel (talk) 04:44, 5 December 2018 (UTC)
  • given name (P735) can hold multiple values. Depending on the use, one or the other can be the one people are most interested in. --- Jura 05:45, 7 December 2018 (UTC)

Heads-up: Upcoming GeneDB item creation[edit]

The good folks at GeneDB (Q5531047) are the authoritative source for gene annotation data for about 50 species. They are preparing a new web presence, and they would like to base some of it on Wikidata! As part of this, I have test-imported two of their species genes, and accompanying proteins, as items into Wikidata a while ago, and made a prototype browser for that information. Now that proof-of-concept is established, they would like me to go ahead and import their entire database as Wikidata items. That's about 770K genes, and about as many proteins, so we are talking about ~1.5M new items for this, over the next 1-3 months. All items will have a GeneDB ID (P3382) statement, and various referenced statements about genomic location, taxon, orthologs/paralogs, and function (example items: PPPK-DHPS (Q18970312) and hydroxymethyldihydropterin pyrophosphokinase-dihydropteroate synthase (Q56565045)).

We already have complete genes and proteins for several species (human, mouse, various bacteria), and I believe this will be a real boost, both in network effects (think main subject (P921) for publications), and in establishing Wikidata as a serious, reliable cornerstone of modern science and research. --Magnus Manske (talk) 09:56, 5 December 2018 (UTC)

  • Symbol support vote.svg Support This is great. ChristianKl❫ 11:39, 5 December 2018 (UTC)
  • Symbol support vote.svg Support Sounds good to me. Have you talked to the User:ProteinBoxBot people to make sure you're not both importing the same things? Are these items that GeneDB (Q5531047) already assert are not yet in Wikidata? ArthurPSmith (talk) 15:51, 5 December 2018 (UTC)
  • Symbol support vote.svg Support pretty please can someone write a case study for this project? I think it would be super useful to help other organisations understand how Wikidata would be useful for them. I'm very happy to help with a write up John Cummings (talk) 16:15, 5 December 2018 (UTC)
  • Pictogram voting question.svg Question Why don't they set up their own wikibase instance and federate it with Wikidata (when that is possible)?--Micru (talk) 16:30, 5 December 2018 (UTC)
    • I don't have a strong enough concept of the standards for inclusion here to have a strong opinion, but I share Micru's question. Not as an objection, but out of curiosity, to know how more involved Wikidatans tend to view such decisions. -Pete F (talk) 23:07, 5 December 2018 (UTC)
      • They are looking into that possibility, but despite the Docker containers available, this is still early stage technology, and "federation" doesn't really work on wikibase level yet (SPARQL, perhaps). If they set up their own wikibase, they would likely do so to track additional, detailed data that would be unsuitable here. --Magnus Manske (talk) 15:02, 6 December 2018 (UTC)
  • Symbol support vote.svg Support Yay! Thanks! --Denny (talk) 22:20, 5 December 2018 (UTC)
  • How would updates happen? --- Jura 08:27, 8 December 2018 (UTC)

How do I model an item for a series of reports[edit]

Hi all

I'm trying to model an item for a series of reports produced by UNESCO Reshaping Cultural Policies (Q59456378), there is a Wikipedia article for the reports but I don't know how to model it in Wikidata since it refers to more than one publication. What should Instance of be?

Thanks

--John Cummings (talk) 11:38, 5 December 2018 (UTC)

  • Presumably, each report should get its own Wikidata item. Then there are several different ways you can effectively relate them to the item for the article. If the article corresponds to some recognized grouping, has part (P527) probably is best, along with part of (P361). Also, if the reports have a clear sequence you might consider relating them to one another with follows (P155) / followed by (P156); if each is an update of the one before there is replaces (P1365) / replaced by (P1366). - Jmabel (talk) 18:05, 5 December 2018 (UTC)
    • Should be ideally identical to how TV series for example are modelled. @Jura1: I think worked on this, where can documentation or informations be found on current practices on concensus on modelling series ? author  TomT0m / talk page 11:37, 6 December 2018 (UTC)
  • @John Cummings: You should provide a better description of the case: is it a serie of reports or one report composed of several documents ?
In the first case, each report has to have an item and an additional item is required for the serie. The report items have to follow the model described by Help:Sources#Reports, policy, legislation and technical documentation. In the second case, we need to provide a clear model to handle that case. Snipre (talk) 12:41, 6 December 2018 (UTC)
@John Cummings: I think it would be useful to make a new item "report series" modeled on existing book series (Q277759). In fact, I am rather surprised we don't have this already. There are a number of items that are defined as a "series of law reports" but are <instance of> "law report", and that seems wrong to me; those should "report series" (or even a subclass "law report series") with parts of the class "law report". - PKM (talk) 20:59, 6 December 2018 (UTC)

tool for importing information from Commons templates to Wikidata?[edit]

Hi, is there a tool that takes information from a Commons image's template and uploads it to Wikidata? Rachel Helps (BYU) (talk) 19:05, 5 December 2018 (UTC)

For some Commons templates QuickStatements is used, see commons:Category:Pages with QuickStatements links.--Jklamo (talk) 23:59, 5 December 2018 (UTC)
thank you! Rachel Helps (BYU) (talk) 21:46, 6 December 2018 (UTC)

Watchlist notices: let users dismiss these notifications[edit]

A while ago Tagishsimon noted that there is no simple way for users to hide the notices that are displayed above the watchlist (see the discussion). This is a real issue on small screens, as the list takes a lot of space above the watchlist itself (see this screenshot in 1280x800). I therefore propose that we switch to the solution adopted by the English Wikipedia, where watchlist notices consist of short sentences which can be dismissed with the help of a Javascript gadget (see en:Wikipedia:Watchlist_notices). Please add your support here if you think this would be a good move so that we can get the gadget enabled on Wikidata. @Multichill, Nikki, Galaktos: pinging editors involved in the previous discussion. − Pintoch (talk) 04:05, 6 December 2018 (UTC)

  • Yeah, support. --Tagishsimon (talk) 12:52, 6 December 2018 (UTC)
  • Sounds good, be bold :-) I think some wiki's have the option to only show it to certain user groups (like only admins). Might be useful for us too. Multichill (talk) 12:58, 6 December 2018 (UTC)
  • The gadget is suitible for seperate lines of notices. We use static sections with dynamic content, not sure how that will work. Sjoerd de Bruin (talk) 13:20, 6 December 2018 (UTC)
    • @Sjoerddebruin: yes, so we should switch to using separate lines of notices. − Pintoch (talk) 23:13, 6 December 2018 (UTC)

WikidataCon, the conference for open data enthusiasts, will take place in Berlin in October 2019[edit]

WikidataCon 2017.svg

Hello dear Wikidata community,

After the success of the first WikidataCon in 2017 and many conversations regarding the future of this conference, we are now ready to announce that the WikidataCon 2019 will take place on October 25th-26th 2019 in Berlin.

Apart from this first piece of information (save the date in your calendars!), there are some important changes regarding the goal of the conference that we would like to share with you.

After its first iteration, the goals of the conference will evolve. The event will be more focused on networking and strategic discussions. The target group will of course include the Wikidata community in its broad sense, especially people and organizations who are already involved in editing, structuring and reusing the data, but will also reach further the organizations who may be interested in using Wikidata and Wikibase, or contributing in various ways to the evolution of Wikidata.

The program will be adapted to this new goal, and organized around different levels of involvement for the participants: from being inspired (with keynotes, success stories, vision of Wikidata’s future) to diving deeper into the hot topics, but also action: the participants will have the opportunity to work on projects during the conference.

Besides many possible topics that will be submitted by the participants, we plan to have a dedicated track about lexicographical data, discussing the perspectives for further reusing data about words within and beyond Wikidata.

A lot of space will be left for discussions, networking, building connections between the different stakeholders and members of the broad Wikidata community.

The conference will be hosting at least 250 participants. In order to make sure that the access to the conference is fair and to not reproduce the issues of last year (rush to get a ticket and long waiting list), we will set up a more streamlined registration process, where a committee made up of both staff and volunteers will make sure that the applicants will contribute in one way or another to the goal of the conference. I will keep you updated for the next steps of this process.

You can already see Wikidata:WikidataCon 2019 which will be improved step by step over the next months, and you can already use the discussion page. If you have any question, you can also contact me on my talk page or by email: lea.lacroix@wikimedia.de.

We're looking forward to a great WikidataCon 2019, together with you!

Thanks for your attention, Lea Lacroix (WMDE) (talk) 08:24, 6 December 2018 (UTC)

Label when adding a wikipedia page[edit]

Can someone explain me why the title of a wiki page is not automatically used for the label of the item when a wikipedia page is added in that language from the wikipedia? It is this way by default if you create an item, but not if you only add a link to a wikipedia page. Why is that behaviour of the Wikipedia tool? Thanks in advance, Paucabot (talk) 10:53, 6 December 2018 (UTC)

As I recall (and it has been a while), this is because of the Wikipedia problem with disambiguation of names, so for people and places (the bulk of early Wikidata items) you would have "Saint Mary's Church, (XXX)" where the XXX is for location, which is generally placed in the description, not the label. That is just one example, but there are many more. Nowadays it might be worth reinvestiging this decision. Jane023 (talk) 11:57, 6 December 2018 (UTC)
Is it a technical problem? Because I think it is worse to have no label than to have misplaced parentheses ... Paucabot (talk) 12:33, 6 December 2018 (UTC)
It's not a technical problem. It's just that the code to enforce/undertake addition of a label based on the sitelink is not in place, because no-one has thought it a good idea to make it so, largely for the reasons set out by Jane023. I have some sympathy for your view, but equally sympathy for the notion that labels are important enough that we don't fudge them. Next, your idea /might/ sort out a single or a small set of language label values, albeit at the cost of the addition of suboptimal labels, but it's not applicable across the board: the Thai label taken from a Thai article is not much use for the English langauge label. Given there are ~200 languages wanting labels, the solution doesn't go very far. --Tagishsimon (talk) 13:01, 6 December 2018 (UTC)
@Tagishsimon: I'm not asking for the label to be automatically set in every language, only for one language: if I'm adding a catalan sitelink, then this text would be automatically used for the label in catalan only. Paucabot (talk) 19:30, 6 December 2018 (UTC)

I created a ticket for a similar idea at phab:T148762 a couple of years ago, where the label would not be set automatically, but where the user is given the choice to set the label for the connected Wikidata item.

Unfortunately, nothing has come out of it yet, but if more people show their interest in features like this, maybe we could finally get something implemented. --Njardarlogar (talk) 16:40, 6 December 2018 (UTC)

Thanks, @Njardarlogar:. I'll ask it there. Paucabot (talk) 19:35, 6 December 2018 (UTC)

I have seen that there is a bot (@MatSuBot:) that does this kind of work: Special:diff/800581443. If it's done with a bot I don't see any reason why not do it automatically from the beginning. Paucabot (talk) 08:48, 7 December 2018 (UTC)

@Paucabot: I don't agree that a strictly automatic solution is good, because then a lot of labels would get wrong capitalization, and the user would have to go over to Wikidata to correct the labels, anyway, if they want the labels to be correct. Automatic labels should be better than the current state, where no labels are added at all (with the exception of the work of bots); but you should be able to adjust the label in the dialogue where you connect the page to item, such that you can ensure that the capitalization is correct and that no disambiguation is present in the label. --Njardarlogar (talk) 11:16, 8 December 2018 (UTC)
@Njardarlogar: If, anyway, I have to go to Wikidata to get things done, I prefer only having to change capitalization or removing disambiguations than having to add everything from scratch. Maybe even we could get rid of the parentheses automatically ...
Have you seen T58410? They have discarded offering to change the label as an option. Having done so, I think that a strictly automatic solution is better than the current situation. Paucabot (talk) 11:26, 8 December 2018 (UTC)
Having corrected lots of item labels (for various reasons different from Wikipedia titles) I think it's not a good idea to do this automatically, unless it is offered as a yes/no pop-up option when the sitelink is created. Then it is up to the user to have the whole title copied into the label or not. Even this may be a bad idea, I am not too sure how often "Wikipedians with zero Wikidata experience" actually add sitelinks by hand. Jane023 (talk) 11:56, 8 December 2018 (UTC)
@Jane023: Maybe you're right, but this behaviour is not very coherent with the actual behaviour of the tool if the item does not exist (it copies the sitelink to the label) or with the existence of bots that do exactly this work. Paucabot (talk) 12:19, 8 December 2018 (UTC)
@Paucabot: In the ticket I created (which is still open), I actually address the concern about casual users mentioned by hoo (see my reply to Edgars2007): the option for adjusting the label could be under an "advanced" section, or even completely hidden unless the user opts in on the feature in the user settings. I'd also add that connecting Wikipedia pages in different languages is already some distance into advanced users territory, so the addition of an "advanced" section should not be very problematic. If you are really sceptical about such a section and think it will confuse inexperienced users, you could even have it appear only after the user has connected 10 pages.
Regarding the concern about making the linkItem code more complicated, I don't know how important that is; but I doubt it would/should be that much more complicated to e.g. make it launch a new dialogue with its own code that allows the user to set the label after the page has been connected to the item. Again,such a dialogue could not show at all by default, or the user could choose to have the dialogue never appear again.
In short: if there is a will to implement such a feature, there is almost certainly a way. :-) --Njardarlogar (talk) 12:11, 8 December 2018 (UTC)
Thanks for your thoughts, @Njardarlogar:. Paucabot (talk) 12:15, 8 December 2018 (UTC)
How about having a popup in case a new Wikilink gets entered in a language that doesn't already have a label that suggests adding the title as a label but leaving the user the option to adapt it as well? ChristianKl❫ 13:05, 10 December 2018 (UTC)
That would be fine for me, @ChristianKl:. Paucabot (talk) 19:54, 10 December 2018 (UTC)

Urlencode for external identifier[edit]

Is it possible to urlencode the value in external identifier property? isomeric SMILES (P2017) usually has symbols like '/' etc. which cannot be properly used in an URL without encoding it first, so in many situations link in the property is faulty, e.g. http://www.simolecule.com/cdkdepict/depict/bow/svg?smi=CC[C@H]1[C@H]([C@@H](C/C(=C/C=C/[C@@H]([C@H](OC(=O)/C(=C\C(=C\[C@H]([C@H]1O)C)\C)/OC)[C@@H](C)[C@H]([C@H](C)[C@]2(C[C@H]([C@@H]([C@H](O2)/C=C/C)C)O)O)O)OC)/C)C)O&zoom=2.0&annotate=cip should be encoded to something like [3] to work properly. Wostr (talk) 13:08, 6 December 2018 (UTC)

@Wostr: The ID in Wikidata should be the real string form of the ID, whatever it is. URL-encoded strings don't get interpreted properly by the Wikidata client UI anyway. There may be a fix we could work out with the wikidata-exteranlid-url service, you can experiment with it here: https://tools.wmflabs.org/wikidata-externalid-url/ or let me know if it doesn't seem to be handling the string properly. ArthurPSmith (talk) 19:13, 6 December 2018 (UTC)
@ArthurPSmith: that does not seem to work for isomeric SMILES (P2017); it returns valid URL (prefix+id+suffix), but it does not encode the identifier: http://tools.wmflabs.org/wikidata-externalid-url/?p=2017&url_prefix=http://www.simolecule.com/cdkdepict/depict/bow/svg%3Fsmi=&url_suffix=%26zoom%3D2.0%26annotate%3Dcip&id=CC[C@H]1[C@H]([C@@H](C/C(=C/C=C/[C@@H]([C@H](OC(=O)/C(=C\C(=C\[C@H]([C@H]1O)C)\C)/OC)[C@@H](C)[C@H]([C@H](C)[C@]2(C[C@H]([C@@H]([C@H](O2)/C=C/C)C)O)O)O)OC)/C)C)O or maybe I'm doing something wrong? Wostr (talk) 20:51, 6 December 2018 (UTC)
I'm sure there's a way to do it, I'll take a look... ArthurPSmith (talk) 01:53, 7 December 2018 (UTC)

Genus and/or species for Bismarckia[edit]

The two items Bismarckia (Q13055333) and Bismarckia nobilis (Q664462) seems to be mixed and intertwined. One of them is supposed to regard the plant genus Bismarckia and the other of them the species Bismarckia nobilis within that genus, but right now it's all a bit confusing. Looking through the different Wikipedia links on Bismarckia nobilis (Q664462) one can see that they sometimes point to a species page, and sometimes to a genus page. I guess one of the problems is that several of the Wikipedias redirect Bismarckia to Bismarckia nobilis since the genus is monotypic and a separate page for the genus therefore seems redundant. This is of course not the case here at Wikidata, where we always keep specific WD items for specific taxa. How can we fix this without mixing up all the identifier links (IPNI, the PlantList, Tropicos, etc.) on each of the item pages? –Tommy Kronkvist (talk), 14:42, 6 December 2018 (UTC).

Pragmatic policy is to keep all the sitelinks together in one item (to make it easier for users to find other pages), in the item of the species in most cases (but in the item for the genus for fossils). When there is a Wikipedia that has pages for both the genus and the species, the sitelinks are split: those for the genus in the genus item, those for the species in the species item. - Brya (talk) 03:52, 8 December 2018 (UTC)

Admin pages Q3907246 and Q4580256[edit]

User:Infovarius reverted me. IMHO, that wasn't an improvement.

I suggest we lump "page used to make different requests to administrators" (which Q3907246 was reverted to) together with "page used for communication which requires administrators attention" (Q4580256 (this tends to be the same thing) and move link portals to Q9004001. Perhaps create a new item for admin-specific link portals. On w:Wikipedia:Requests for administrator attention, w:pt:Wikipédia:Pedidos and w:nl:Wikipedia:Verzoekpagina voor moderatoren, you can't make any request. (please ping me if you reply) Alexis Jazz (talk) 18:27, 6 December 2018 (UTC)

Highest current QID / LID / PID[edit]

Is there an API call to figure out the highest Q ID, L ID, or P ID right now? --Denny (talk) 19:48, 6 December 2018 (UTC)

@Denny: https://www.wikidata.org/w/api.php?action=query&list=recentchanges&rctype=new&rcnamespace=0&rclimit=1 (Sort of cheating, but...) --Yair rand (talk) 20:42, 6 December 2018 (UTC)
Thank you, perfect! :) --Denny (talk) 21:24, 6 December 2018 (UTC)
Highest L is izioki (L171081) --- Jura 04:36, 7 December 2018 (UTC)
:D perfect, thanks, Jura. I was looking for Yair's answer, but you are correct! (for now) --Denny (talk) 16:48, 7 December 2018 (UTC)

New Wikimedia password policy and requirements[edit]

CKoerner (WMF) (talk) 20:03, 6 December 2018 (UTC)

male / female only parenting[edit]

I'd like to suggest a new property in order to distinguish between single, male only or female only, and child rearing by both parents. There are many animal species where the male is the only parent (seahorses, cassowary, ...). Then there is the female does the parenting (tigers, elephants, ...). It would be great if we could add female/male, male/male, and female/female offspring care as well. Thoughts? --Hedwig in Washington (talk) 18:24, 7 December 2018 (UTC)

@Hedwig in Washington: This has to be discussed on Wikidata:Property proposal. Esteban16 (talk) 21:32, 7 December 2018 (UTC)
Yes, it would be possible and useful to have such a property. - Brya (talk) 03:57, 8 December 2018 (UTC)

References not to displayed unfolded[edit]

Is there a way the references not to displayed unfolded when there is a constraint violation within the reference? It really makes my constributions difficult. Xaris333 (talk) 10:34, 9 December 2018 (UTC)

Hello,
Displaying the reference unfolded when there is a constraint violation is done on purpose: this way, we encourage the community to fix either the content or the constraint. However, if many people complain about it and wish for a way to fold the references, we're ready to think about it further. I hope this answer helps you. Lea Lacroix (WMDE) (talk) 11:48, 10 December 2018 (UTC)
@Lea Lacroix (WMDE): I understand why that was applied. But for me it is very difficult. Because of that problem Wikidata:Project chat/Archive/2018/11#single-value constraint with title property, in many items that I am adding properties, the references are display unfolded. Xaris333 (talk) 16:10, 10 December 2018 (UTC)
I think we really need to clean up the constraint then. I know this sucks but it's better to fix the underlying issue than glossing over it :/ --Lydia Pintscher (WMDE) (talk) 09:45, 11 December 2018 (UTC)
@Lea Lacroix (WMDE): How to clean up? The references are correct. The constraint is correct. @Jura1: Xaris333 (talk) 19:35, 11 December 2018 (UTC)
It seems a bit of an overkill to add the title twice at Q6377735#P1082, but not at all the item about the source itself Cyprus census 1976 (Q29639032). If you use "stated in", I don't think the reference should even include title. Maybe Help:Sources needs to clarify this. --- Jura 19:49, 11 December 2018 (UTC)
Some references have titles in more than one language. Is not a solution just not to add them. Xaris333 (talk) 20:30, 11 December 2018 (UTC)
Can you give a couple of samples? --- Jura 09:27, 12 December 2018 (UTC)
Wikidata:Project chat/Archive/2018/04#Title Xaris333 (talk) 20:56, 12 December 2018 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Thanks. Looks like a non-issue then. I found three samples there:

  1. Q6377735 with 262 in population. It was discussed above. The titles were incorrectly added in references instead of the item about the source (Q29639013). If you move them there it should take care of it.
  2. Q25991162 and Q25991163 which don't have the problem as the title (P1476) is used as main value.

That said, maybe non-mandatory constraint violations don't need to have the references displayed unfolded. --- Jura 08:39, 13 December 2018 (UTC)

And how that can be done? How the non-mandatory constraint violations don't need to have the references displayed unfolded? (I disaggreei that the titles were incorreclty added). Xaris333 (talk) 15:02, 13 December 2018 (UTC)

Q11263220 and Dumbing down (Q5313720) - are they the same and should they be merged?[edit]

Q11263220 refers to policies like Fado, Football, and Fatima (Q3539497) or 3S Policy (Q10854388) or Bread and circuses (Q845658) that make people either unable to or doesn't want to care about politics, usually for the purpose of maintaining or strengthening the control of the ruling government on a country/society. Can it be said as equal to dumbing down and thus can the two wikidata items be merged? C933103 (talk) 16:30, 9 December 2018 (UTC)

Miniature map for coordinate properties[edit]

Hello all,

After we deployed the Commons miniature pictures for the image properties, some editors suggested to do something similar with maps. From Wednesday, December 12th, we will also have a miniature map displayed for the properties containing coordinates, like coordinate location (P625). This feature uses mw:Extension:Kartographer and OpenStreetMap.

Viewing the map directly in the item will help the editors to check quickly if the coordinates seem correct, and therefore improve the data quality.

Some useful features:

  • Double-click on the miniature map: display it in full screen
  • On full screen view: click on “external maps” to display different map services and links to many external maps
  • In edit mode: when adding or editing coordinates in the field, the maps is automatically updated to fit the coordinates you entered
  • The coordinates are still displayed under the map and link to Geohack if you have the gadget AuthorityControl enabled

If you have any questions or issues with this feature, let me know. You can also see the related ticket. Lea Lacroix (WMDE) (talk) 15:22, 10 December 2018 (UTC)

@Lea Lacroix (WMDE): Very nice! Will this display for all coordinates, or only for coordinates with globe=Earth (Q2) (the latter is better)? Thanks. Mike Peel (talk) 16:41, 12 December 2018 (UTC)
Ah, looks like it displays for all coordinates. I'll ask about this on phabricator. Thanks. Mike Peel (talk) 16:43, 12 December 2018 (UTC)
@Mike Peel: No this is just for coordinates on earth, others are exempted (see for example Q499158#P625). Cheers, Hoo man (talk) 16:48, 12 December 2018 (UTC)
Aah, I was confusing it with User:Aude/mapview.js in those cases, thanks for the clarification. I've made a couple of other suggestions on the phabricator ticket anyway. Thanks. Mike Peel (talk) 16:50, 12 December 2018 (UTC)

Linking musical settings with source texts[edit]

What are the correct properties to use when linking a source text with a musical setting of that source text? and when linking an original melody with a set of alternate lyrics written to that tune at a later date? In these cases the melody and the lyrics will be separate items. Sorry if this has been asked before. Beleg Tâl (talk) 15:27, 10 December 2018 (UTC)

I've found has melody (P1625) which looks like it addresses some of what I was looking for... is there a reverse property for back-linking? Is it appropriate to use has melody (P1625) if the musical setting comprises more than only melody? Beleg Tâl (talk) 13:58, 13 December 2018 (UTC)

Wikidata weekly summary #342[edit]

Request for filling out a questionnaire on Wikidata[edit]

Dear Wikidata enthusiasts, I have a huge favor to ask of everyone reading this --

TLDR: Please fill out the questionnaire linked here!

And now in more details: As some of you may know, I'm PhD candidate at the School of Education, Tel Aviv University, and my research focuses on Wikidata as a learning platform. To succeed in my research, I need lots of data about how users (such as yourselves) interact with Wikidata, so it would be of great help if you could take the time to fill out the questionnaire linked above. It's estimated that it should take between 15-30 minutes, depending on how detailed your answers would be. I'm striving for at least 100 replies, but this is one of those cases of "the more, the merrier", so really, every single person filling it out is of huge help.

If you have any questions, or are willing to participate in a follow up interview, please feel free to ping me via my talk page, privately or by email (shani.even at gmail.com). Thanks in advance for considering filling it out. I will be forever grateful to anyone who can help and promise to update you on my progress. :) Shani Evenstein (talk) 22:46, 10 December 2018 (UTC)

Property:P443[edit]

How about to move all instances of this property from items to appropriate Lexemes? (Only a word can have pronunciation, not a notion) --Infovarius (talk) 14:41, 11 December 2018 (UTC)

Yes, that sounds like a worthy project. ChristianKl❫ 15:12, 11 December 2018 (UTC)
Some items are about words. For example: Donau­dampf­schiffahrts­elektrizitäten­haupt­betriebs­werkbau­unter­beamten­gesellschaft (Q20167), fuck (Q31928). (And if the items have sitelinks, we can’t delete them.) --Lucas Werkmeister (talk) 17:18, 11 December 2018 (UTC)

How do I describe population of a species[edit]

Hi all

I'd like to add the population of African elephants to African bush elephant (Q36557), the only thing I can find is population (P1082) which is specific to humans, are we missing a property or am I just missing the magic words?

Thanks

--John Cummings (talk) 17:26, 11 December 2018 (UTC)

@John Cummings: I think its uncommon to see items about species with their amount of individuals. I've searched on Special:ListProperties and I found nothing. Esteban16 (talk) 20:12, 11 December 2018 (UTC)
This was asked recently at Wikidata:Project_chat/Archive/2018/10#Number_of_peoples_or_animals_among_a_nationality_/_population_/_breed. How to model this appears to be unresolved. (A solution to this would also need a way to indicate species populations within a particular area at particular times.) --Yair rand (talk) 20:16, 11 December 2018 (UTC)
@John Cummings: quantity (P1114) View with SQID. Taxons are classes of individuals and number is supposed to give the number of instances, hence individuals, of that class. author  TomT0m / talk page 20:30, 11 December 2018 (UTC)
@TomT0m:, thanks, could you give an example item where this has been used? Quantity seems like a strangely worded way of saying it. --John Cummings (talk) 23:52, 11 December 2018 (UTC)
@John Cummings: Maybe the english label is just wrong because if I remember correctly the proposal time, it’s the exact purpose of the proposal. author  TomT0m / talk page 07:48, 12 December 2018 (UTC)
Thanks @TomT0m:, I tried to find the conversation about the property proposal which describes how the property can be used but I can't find it, any ideas? --John Cummings (talk) 08:24, 13 December 2018 (UTC)
Indeed, it’s a weird situation, the link provided in the property statements is https://www.wikidata.org/wiki/Wikidata:Property_proposal/Archive/19#P1114 . The creation is acknoledged but it seems the discussion is lost. @Zolo: Any idea what happenned ?
Thanks to wikiblame we can find the initial proposal : https://www.wikidata.org/w/index.php?title=Wikidata:Property_proposal/Generic&diff=prev&oldid=76584375&diffmode=source
(I was pinged for the creation it seems but I can’t find any trace of the interventions I had in this. I’m pretty sure I participated though, weird. Old times.) author  TomT0m / talk page 12:16, 13 December 2018 (UTC)

Are Amazonia (Q2841453) and Amazon rainforest (Q177567) the same thing[edit]

Hi all

I think that Amazonia (Q2841453) and Amazon rainforest (Q177567) are possibly the same thing? Could someone have a look?

Thanks

--John Cummings (talk) 17:34, 11 December 2018 (UTC)

In french, one is about a (geographical region), the other about the forest that is located on that region. If the second disappears, the first will still be there, so I think they are different entities. author  TomT0m / talk page 17:55, 11 December 2018 (UTC)
Thanks @TomT0m:, --John Cummings (talk) 18:09, 11 December 2018 (UTC)

Using qualifier on identifiers for type of record[edit]

In the US National Archives catalog, the same identifier set is used for all types of records, including both authority records and descriptions of archival holdings. This is nice, because the number is the only thing a resource you need to know to refer to it. However, I'd like to be able to distinguish the record types on Wikidata, so that we can perform queries on only a single type of record—e.g., see all items with NARA authority IDs. Does anyone have opinions on the best way to do this? The only idea I have is to add it as a qualifier of the identifier, like the example I have done at Q59296199#identifiers. However, I have not seen qualifiers used for external identifier statements before, and I am not sure if object has role (P3831) is the best choice for it, so I was wanted to see what others thought of that before applying it to thousands of items. Thanks for any help! Dominic (talk) 22:00, 11 December 2018 (UTC)

Could we use type of reference (P3865) for this, with a constraint change to allow it to be used as a qualifier for an identifier? - PKM (talk) 20:15, 12 December 2018 (UTC)

Bug fix - references are now accessible for non-logged in users on protected items[edit]

Hello all,

Usually I don't announce every small bug fixes that we make, but I thought this one could be interesting for you to know - if you hear someone complaining about this bug, you can tell them it's fixed now :)

Before the fix, on protected or semi-protected items, non-logged in users could not display the references. The references section was folded, the link "X references" was grey and non-clickable, meaning that readers without an account couldn't display or access the references.

This bug is now fixed, non-logged in users can access the references on all items. You can test it quickly by opening Douglas Adams (Q42) in a private session of your browser. If you encounter any issue, feel free to add a comment in the ticket or ping me.

Cheers, Lea Lacroix (WMDE) (talk) 13:47, 13 December 2018 (UTC)


Model item (Property:P5869)[edit]

Just wondering, which type of entities should this property be on?

It was originally proposed for items (see samples on Wikidata:Property_proposal/Model_item), but can now also be found on a property (Property:P747#P5869).

On properties, to some extent it duplicates:

Supposedly, the still proposed inverse property for model item (P5869) couldn't work when using it on properties (Wikidata:Property proposal/Model item for).

Also, if selection is mainly done by the number of statements on an item, the query links on the property talk page are better than a static link to one item. --- Jura 14:12, 13 December 2018 (UTC)

The recent court judgement for Q48928408[edit]

The High Court of Hong Kong has made a judgement on 13 December 2018. According to paragraph 64 of the Judgement, Judge Anderson Chow said:

It is not in dispute that the West Kowloon Station Mainland Port Area (Q48928408) falls with the territory of Hong Kong under the “Order of the State Council of the People’s Republic of China No 221” dated 1 July 1997, which was promulgated in accordance with the “Decision of the National People’s Congress on the Establishment of the Hong Kong Special Administrative Region” adopted at the Third Session of the Seventh National People’s Congress on 4 April 1990.

That means the correct statement is West Kowloon Station Mainland Port Area (Q48928408)located in the administrative territorial entity (P131)  Hong Kong (Q8646)!!!! 223.17.64.233 14:31, 13 December 2018 (UTC)