Shortcut: WD:PC

Wikidata:Project chat

From Wikidata
Jump to: navigation, 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.
Also see status updates to keep up-to-date on important things around Wikidata.
Requests for deletions and merges can be made 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 2015/05.

Chinese question[edit]

Is there an equivalent of Wikipedia:WikiProject China (Q10816953) or Wikipedia:Proposed mergers (Q6596462) in Wikidata ? Visite fortuitement prolongée (talk) 13:26, 19 April 2015 (UTC)

There are some proposed merges: User:Byrial/countrymerge, User:Byrial/numbermerge, User:Ivan A. Krestinin/To merge, User:Pasleim/projectmerge. --Infovarius (talk) 05:39, 22 April 2015 (UTC)

What is the meaning of "内蒙古语言" ? Are w:zh:Category:内蒙古语言 and Category:Languages of Inner Mongolia (Q13328614) related? Visite fortuitement prolongée (talk) 21:25, 21 April 2015 (UTC)

内蒙古语言 literally means "Inner Mongolian Languages". the zh category and fr are related.--KTo288 (talk) 21:07, 22 April 2015 (UTC)
Can somebody change Q9536576 into redirect to Q13328614 ? Visite fortuitement prolongée (talk) 19:49, 22 April 2015 (UTC)
✓ Done Pamputt (talk) 19:54, 22 April 2015 (UTC)
Thank you. Visite fortuitement prolongée (talk) 19:05, 23 April 2015 (UTC)

What is the meaning of "云南语言" ? Are w:zh:Category:云南语言 and Category:Languages of Yunnan (Q13328628) related? Visite fortuitement prolongée (talk) 19:05, 23 April 2015 (UTC)

Yes.--KTo288 (talk) 08:09, 29 April 2015 (UTC)
Then should Q9508494 (Q9508494) and Category:Languages of Yunnan (Q13328628) be merged? Visite fortuitement prolongée (talk) 21:44, 29 April 2015 (UTC)

What is the meaning of "长江水系" ? Are w:zh:Category:长江水系 and Category:Chang Jiang Basin (Q8956112) related? Visite fortuitement prolongée (talk) 19:44, 25 April 2015 (UTC)

What is the meaning of "长江" ? What is the difference between w:zh:Category:长江 and w:zh:Category:长江水系? Visite fortuitement prolongée (talk) 19:43, 26 April 2015 (UTC)

Are Q8115786 (Q8115786) and Yangtze River basin (Q15758768) related? Visite fortuitement prolongée (talk) 19:43, 26 April 2015 (UTC)

Are Category:Chang Jiang Basin (Q8956112) and Category:Yangtze River basin (Q15758937) related? Visite fortuitement prolongée (talk) 19:43, 26 April 2015 (UTC)

"长江" is the Yangtze, strictly translated 长江水系 is the Yangtze drainage system, however at zh wiki it seems to be primarily used for tributaries of the Yangtze with w:zh:Category:长江流域 being used for a mix of the geological, geographical, historical and cultural aspects to the river. I'll have a look at how the cats are actually being used in zh:wiki and elsewhere, rather than just how they named, before getting back to you.--KTo288 (talk) 08:09, 29 April 2015 (UTC)

Same label in many languages[edit]

An examination of the history of GrassBase (Q19816560), which I created recently with the English-language label "Grassbase", shows others adding the same label in French and German. Indeed, I would expect the label, which is a proper noun, to be the same in every language using the western alphabet.

Would it be possible to have an option when setting a label, to do so for every such language? Individual instances could always be changed later, if necessary.

Or perhaps someone might make a tool to do this? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:39, 20 April 2015 (UTC)

Add importScript( 'User:Jitrixis/nameGuzzler.js' ); to your personal JavaScript and copy this page to your own namespace. That would do the job. A link would appear in the tools menu. Sjoerd de Bruin (talk) 09:54, 20 April 2015 (UTC)
Thank you. That looks useful I'm not sure what the "autoselct" option is supposed to do. Also, is there a method to select only languages which are RTL, and/ or use the western alphabet? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:58, 20 April 2015 (UTC)
The autoselect fetches the list from your namespace. I think it contains all western languages. Sjoerd de Bruin (talk) 11:00, 20 April 2015 (UTC)
@Sjoerddebruin: It not working - not doing anything - for me :-( Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:28, 20 April 2015 (UTC)
@Sjoerddebruin: Are you able to advise, please? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 16:26, 23 April 2015 (UTC)
@Pigsonthewing: can you be more specific, please? Sjoerd de Bruin (talk) 17:10, 23 April 2015 (UTC)
@Sjoerddebruin: I click on the "autoselect" link and - literally - nothing happens. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 22:40, 23 April 2015 (UTC)
@Pigsonthewing: you still need to save with the buttons on the bottom. Sjoerd de Bruin (talk) 15:24, 27 April 2015 (UTC)
@Sjoerddebruin: Thank you., but I don't get that far When I click the "autoselect" link, nothing gets selected. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:00, 27 April 2015 (UTC)
@Pigsonthewing: that's weird. You don't seem to have conflicting scripts, don't know what gadgets you use. Or are you double clicking on it? Sjoerd de Bruin (talk) 18:03, 27 April 2015 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── @Sjoerddebruin: Single-clicking (double-clicking doesn't work, either). Oddly, after I click that link, the other link also becomes unresponsive. My enabled gadgets are: Merge; slurpInterwiki; AutoEdit; FindRedirectsForAliases; labelLister; Search; RequestDeletion; CommonsMEdia; Decritions; Reasonator; DraggableSitelinks; Site ID to interwiki; Protection indicators; PopupsFix; Navigation popups; Redirect image links to Commons for files that are hosted there; NewSection. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 19:09, 27 April 2015 (UTC)

I already have this, will that do? --Magnus Manske (talk) 10:03, 20 April 2015 (UTC)
@Magnus Manske: Thank you. Is there any documentation? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 10:58, 20 April 2015 (UTC)
@Magnus Manske: that seems very interesting, but how do you use it to edit, please ? --Hsarrazin (talk) 19:46, 24 April 2015 (UTC)

Combining Q112865 & Q15149663 (Mexican States)[edit]

Can these items (Q112865 and Q15149663) combine in some way? Maybe they are totally different items but there is something wrong. Both are marked in Finnish with the same item "Meksikon osavaltiot" (in English States of Mexico). Q112865: en:Administrative_divisions_of_Mexico is pretty much the same as Q15149663: fi:Meksikon_osavaltiot. I am sorry fragmentation of discussion in many places: Talk:Q112865 and Requests for comment/Adopt Help:Classification as an official help page (Deleted comment). --Raid5 (talk) 11:48, 20 April 2015 (UTC) edit. --Raid5 (talk) 14:35, 20 April 2015 (UTC)

@Raid5: Depending on how much an individual article at administrative territorial entity of Mexico (Q112865) covers not only estados but also municipios as second-order subdivisions it could or could not be moved over to state of Mexico (Q15149663). Looking at the associated "main categories" Category:States of Mexico (Q7146004) and Category:Subdivisions of Mexico (Q6418549) shows a clear overlap, i.e. many wikipedia instances have both categories. I think in the sense of "first-level-subdivisions only" vs. "any subdivision" holds and the items should not be merged. -- Gymel (talk) 05:48, 21 April 2015 (UTC)
I think the current Finnish article has now fewer things. It would be difficult to understand if it would be made an another article and then the Finnish Wikipedia article would be equal to current English article. The result would be two new almost the same kind of articles. But you may be right, because you know better structure of Wikidata. Thank you. --Raid5 (talk) 13:16, 21 April 2015 (UTC)
@Raid5: Perhaps I did not correctly understand your question, but I let me rephrase my answer:
  1. There is no wikipedia which has two articles (one belonging to administrative territorial entity of Mexico (Q112865) and the other to state of Mexico (Q15149663)), so technically the items could be merged
  2. however the different (and definitively non mergeable) "main categories" for the two items stress the fact, that "primary subdivisions" (i.e. states) and "any subdivision" (i.e. states and municipalities) are distinct topics and therefore the wikidata items should not be merged.
  3. current assignment of individual wikipedia articles to the two items seems to be in alignment with the article titles: "states" here, "subdivisions" there. Deep inspection of each single wikipedia article might yield a better assignment (e.g. an article named "subdivisions" which in fact only deals with the primary subdivisions should be transferred to the "states" item. Or the other way round, an article named "states" which also explains in length how the states are subdivided should move to the "subdivisions" item).
  4. Please feel free to move fi:Meksikon osavaltiot to that item where it fits best based on its content (Hm. I gather that it is not an article at all but just a list or table...). It would be nice then if you also could set the finnish labels for the two items in such a way, that confusion is reduced (thus the acutal article title "Meksikon osavaltiot" should be kept in mind). -- Gymel (talk) 15:17, 21 April 2015 (UTC)
@Gymel: Hi, we're having a word in the RfC about administrative division classification (For example, an item type of administrative division in Mexico, with
< Mexican state > instance of (P31) miga < type of administrative division in Mexico >
is beein discussed, consistently with the framework I propose in Help:Classification. This could help sorting this kind of items out correctly, so if we could read and leave a comment on Wikidata:Requests for comment/Adopt Help:Classification as an official help page I would be pleased :) TomT0m (talk) 15:24, 21 April 2015 (UTC)
@Gymel: Yes I know there is no two articles about that. I meant if, then they would be almost the same. I will not argue the matter (because I don't know much about structure of Wikidata). I am trying to study the things of which you wrote and perhaps then I understand better. --Raid5 (talk) 17:24, 21 April 2015 (UTC)
Raid5 No. 17:25, 25 April 2015 (UTC)

How to add "A has exactly one B, which is C[edit]

How can I tell Wikidata that astronomical year numbering (Q751976) has a 0 (Q23104), which is 1 BC (Q25299)?
And when I remove three improper properties from 0 (Q23104) (1, 2, 3), how can I add edit summaries, so other users won't fix it back? Watchduck (quack) 20:05, 24 April 2015 (UTC)

Dunno, the wikidata editor is a hopeless piece of junk from script hell. Otherwise you could try see also (P1659) 1 BC (Q25299) on 0 (Q23104) and vice versa as a clue. But as is this cannot be saved without any clue what's wrong or missing. Unbreak now: Be..anyone (talk) 22:19, 25 April 2015 (UTC)
Perhaps that would work? It's the best that I could come up with. I admit to not be clear about anything about this, though. Neither the items nor the properties involved are seem clearly defined to me. Am I understanding correctly that 0 (Q23104) is a year-numbering concept, while 1 BC (Q25299) (existing aliases: 1 BCE, 753 AUC, 0) refers to a fixed period of time, independent of year-numbering system? Dancter (talk) 00:44, 26 April 2015 (UTC)
Yes, "year zero" is a concept used in some year numbering systems (like a.y.n.), and 1 BC is a specific year in history: "1 BC is the year zero of astronomical year numbering."
Actually this isn't more complex than "Olympus Mons is the highest point of Mars." or "Bloemfontein is a capital of South Africa.".
Probably the correct way is to create the property "has year zero". Unfortunately there seems to be no semantic way to make clear that this is a one-to-one relationship. Watchduck (quack) 20:13, 26 April 2015 (UTC)


I want really want to start integrating the Wiktionary into Wikidata. With whom do I have to get in contact and what pages do I have to know for this? --Impériale (talk) 08:20, 25 April 2015 (UTC)

See Wikidata:Development plan#Wiktionary support and Wikidata:Wiktionary. -- Bene* talk 12:33, 25 April 2015 (UTC)
Thank you :) --Impériale (talk) 09:22, 26 April 2015 (UTC)

wd-condensed.css: Condensed Wikidata UI CSS[edit]

I've been working on some CSS to make Wikidata's UI more condensed and it is now stable enough for other people to try.

Add @import url('//'); to your common.css file (Special:Preferences#mw-prefsection-rendering, and click "Shared CSS/JavaScript for all skins: Custom CSS").

Here are some screenshots:

Notable improvements:

  • Responsive layout; layout changes depending on the window width to make viewing/editing easier
  • Columned view: statements in a statementgroup are now inlined to take less space
  • edit/add buttons are invisible until you hover over a statementgroup/statement

Known issues:

  • Columned view has holes when statements have inconsistent heights
  • Width of references list is sometimes small

I've used it for the last few weeks or so, and I believe I've found/fixed all the critical bugs. Only tested on the latest browsers (~ Chrome 40+, Firefox 36+, IE11).

Hope this is useful. –Hardwigg (talk) 08:46, 25 April 2015 (UTC)

wow, nice, will certainly try it :)
the way you manage inline display of statements, while keeping them in column for edition is exactly what I would like for language management ;) - now, it's very difficult to add a long label to an item, even worse for descriptions and aliases :( --Hsarrazin (talk) 09:26, 25 April 2015 (UTC)
@Hardwigg: could one have subClassOf and instanceOf always at the top? In many cases both act similar to the description. FreightXPress (talk) 23:35, 25 April 2015 (UTC)
@FreightXPress: Not with plain CSS. If you want that, add the following to your common.js page:
if ( mw.config.get('wgNamespaceNumber') === 0 ) { // On an entity page
        $('.wikibase-statementgrouplistview > .wikibase-listview')
                .prepend($('#P31, #P279'));
Hardwigg (talk) 02:59, 26 April 2015 (UTC)
Thanks for sharing this. :) It's great to see people trying to reduce the amount of unnecessary whitespace. That's one of the things which bothers me most about the current layout. I won't be using this as it is though. :( My comments:
  • The hover effect is actually a big hindrance to me, not an improvement. It means I can't see where I'm aiming for on my main computer until I'm already close. It also seems to make it completely impossible to edit statements on touch screen devices like my tablet, since they don't really do hovering.
  • I don't really like the position of the edit link. It feels a bit lost amongst all the qualifiers and references and I keep wanting to interpret it as a link for editing the references, not for editing the statement.
  • The "add qualifier" link when adding a statement appears on the very right of my screen, a long way from the input field and save links.
  • The font sizes for the edit/save links and reference toggle are too small for me and it also makes them harder to click because they're even smaller than they were and I have to be even more accurate with my aiming. It's also problematic on touch screen devices where accurate clicking is difficult.
  • The headings for the "In more languages" section don't have enough padding and the letters are touching or even hanging out of the grey bar.
  • The responsive design doesn't seem to kick in on my mobile or tablet, not sure if it's possible to make that work.
  • This also seems to move the sitelinks (which are currently on the right for me on my main computer) back to the bottom. I'm not sure if that was intended or not, but most of the time there is only one statement for a particular property, so it means the right side of my screen is mostly wasted again, like it used to be before the sitelinks moved there.
Thanks for the piece of JS above! The statements having no consistent ordering is the other thing which bothers me but I hadn't managed to figure out how to reorder them using JS. - Nikki (talk) 09:21, 26 April 2015 (UTC)
@Nikki: Thanks for the great feedback, Nikki! I'm working on these issues, and will post an update sometime in the next few days. -Hardwigg (talk) 03:27, 28 April 2015 (UTC)

Hardwigg - thanks for the JS. I extended it, see below #wd-sorted-statements.js. I agree with Nikki that hiding edit links and requiring hover is a hinderance. FreightXPress (talk) 17:13, 26 April 2015 (UTC)

Slow creation of properties[edit]

Hello, there are many property proposals, which have had some supporting and no opposing votes since months ago, like the input set. Why haven't they been created yet? Petr Matas 12:38, 25 April 2015 (UTC)

I've been working through the backlog, and have now created input set (P1851). Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:27, 25 April 2015 (UTC)
@Pigsonthewing: Thank you, Andy! I would like to bring Similar item and its qualifiers into focus as well. In December you wrote that the proposal is unclear, but the details are described in the linked RfC. Have you seen that? Petr Matas 14:50, 25 April 2015 (UTC)
@Petr Matas: I've replied there. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:56, 25 April 2015 (UTC)

Strange invisible change by KrBot[edit]


KrBot has very recently (a few minutes ago) modified all scan file (Commons) (P996) claims that I recently did, like

I really cannot see what is the modification. Could someone pleaseexplain it to me, so that when I add thousands of other such claims (for all articles of the same origin in wikisource), I do not make an error that would need such a bot-correction ?

Thank you very much --Hsarrazin (talk) 07:35, 26 April 2015 (UTC)

Your file name had underscores instead of spaces. --Pasleim (talk) 07:42, 26 April 2015 (UTC)
oh, thank you Pasleim, sorry for the accidental copy/paste - the links were working, so I did not know it mattered :) --Hsarrazin (talk) 07:46, 26 April 2015 (UTC)

e-mail (P968) data type[edit]

The datatype of this is String according to the template, but URL according to statements in the entity. It should be string with a formatter url specifying "mailto:". Currently it is only used on one item (with mailto: in the value), so it can be fixed manually. -Hardwigg (talk) 08:14, 26 April 2015 (UTC)

@Hardwigg: mailto will disallow addresses without @. See --GZWDer (talk) 13:03, 26 April 2015 (UTC)
@GZWDer: (Assuming you mean the mailto in the value of an e-mail (P968) statement; let me know if I misunderstood) That's true, but the user doesn't have to enter "mailto:", and could use another protocol altogether. The format can at least be specified (although not enforced) using regex on the property. There are 3 reasons why I think it should be string:
  • an email address, by itself, doesn't have "mailto:"; adding the mailto protocol creates a link to an email address
  • I'm afraid that this is causing confusion. I've abandoned adding this property myself a number of times, because I didn't realize "mailto:" was necessary, and was confused by the "invalid URL" error I received when I'd entered a very valid email address. I'm afraid this might be why it's only used on 1 item ~1.5 years after this property was created.
  • We would still be able to link the email address using formatter URL (P1630).
-Hardwigg (talk) 21:56, 27 April 2015 (UTC)

Wikidata weekly summary #155[edit]


Thanks a lot to User:Hardwigg for posting

if ( mw.config.get('wgNamespaceNumber') === 0 ) { // On an entity page
        $('.wikibase-statementgrouplistview > .wikibase-listview')
                .prepend($('#P31, #P279'));

I extended this to User:FreightXPress/wd-sorted-statements.js.

Nikki - you said you are interested in consistent ordering too. I would be happy to hear, whether you think this is an improvement. FreightXPress (talk) 17:08, 26 April 2015 (UTC)

To get sorted statements, you might be interested in this user script: User:Soulkeeper/statementSort.js --Pasleim (talk) 19:37, 26 April 2015 (UTC)
@Pasleim: thanks a lot. The function toBottom is what I needed. FreightXPress (talk) 21:01, 26 April 2015 (UTC)

@Pasleim, Hardwigg, Soulkeeper, Nikki: Pasleim uses colors for the different data-types in the page Wikidata:Database reports/List of properties/all. I would like to have these colors on item pages too. Is that possible with JS or CSS? FreightXPress (talk) 21:08, 26 April 2015 (UTC)

@FreightXPress: Nice! I think a combination of the two would work best. First add a class to each datatype. The easiest way would probably be like this:
And then style each different type with CSS. Here's a material design styling, just for fun. To use it, add to your your common.js:
mw.loader.load( '//', 'text/javascript' );
mw.loader.load( '//', 'text/css' );
-Hardwigg (talk) 03:13, 28 April 2015 (UTC)
@Hardwigg: I will try your design later. Maybe you like to test mine: . I used "_" instead of "-", that could potentially allow the code to be even smaller, if one could provide "'datatype_monolingualtext'" as a string and then within the function it is converted to a variable name. Also, I failed to have all the data in one (2-dimensional) array with named fields, or a json object, but that should be possible. Then via providing a string to the function one could access the array in the array. For the CSS: I used only border coloring. I had background, but it was too much deviation from the normal interface. But I didn't tried your's yet! Thanks a lot! FreightXPress (talk) 12:05, 28 April 2015 (UTC)
@Hardwigg: I adjusted the class names in my JS to match yours. Then I tried your CSS - looks good. I then also changed my colors to be closer to yours, but kept 3-digit notation with multiple of 3 (0, 3, 6, 9, c ,f). FreightXPress (talk) 13:59, 29 April 2015 (UTC)
@FreightXPress: Hyphenated CSS names are part of the MedaWiki Coding Conventions. (Not that my CSS is that good about following conventions ;)). I tried out your bordered-style, and it looks good; it's less jarring than the material one. -Hardwigg (talk) 04:34, 2 May 2015 (UTC)

I managed to store all datatype-property-relationships in one object and name the fields by the CSS names:

FreightXPress (talk) 19:40, 29 April 2015 (UTC)

Datatype comparison table[edit]

Name from Special:ListDatatypes Commons media Globe coordinate Quantity String Time URL Item Property Monolingual text
Qunatity from Wikidata:Database reports/List of properties/all 31 8 102 ~700 29 23 590 6 17
Name from Wikidata:Database reports/List of properties/all commonsMedia globe-coordinate quantity string time url wikibase-item wikibase-property monolingualtext
Name in CSS classes, lowercase of the DB report names commonsmedia globe-coordinate quantity string time url wikibase-item wikibase-property monolingualtext
Color from Wikidata:Database reports/List of properties/all antiquewhite lavender oldlace lavenderblush lightyellow honeydraw wikibase-item / no specific color wikibase-property / no specific color mintcream
Color from User:FreightXPress/commons.css 3 digit web-safe color (Q19842015) #f90 #3c9 #3cf #fc0 #0cc #009 #3c3 #933 #ff0
Color 3 digit / bright #fda #afd #aef #feb #9ff #ccf #cfc #fcc #ffc
Color from User:Hardwigg/wd-material-typed.css 1 #FF9800 #4CAF50 #FFC107 string / no coloring #FFEB3B #03A9F4 #3F51B5 string / no coloring #00BCD4
Color from User:Hardwigg/wd-material-typed.css 2 #FFE0B2 #C8E6C9 #FFECB3 string / no coloring #FFF9C4 #B3E5FC #C5CAE9 string / no coloring #B2EBF2

@Hardwigg, Pasleim: I made a comparison table. I adjusted my border-colors to better match the dark colors used by Hardwigg, but rounded them, so that in 3-digit notation only multiple of 3 would be used (0, 3, 6, 9, c, f). I used a value close to link-blue for URL. Item statements and string statements will occur very often, so something aggressive is ruled out, I chose green for item. Hardwigg - where do your dark values come from? E.g. FF9800 is very close to my f90, but maybe there is a reason to have FF9800? In your color sets two datatypes have no coloring. FreightXPress (talk) 13:50, 29 April 2015 (UTC)

@FreightXPress: My palette's taken from Google's Material Design specification (using I have no special attachment to the specific colors :) I mostly tried to use colors of similar hue to those of Wikidata:Database reports/List of properties/all. The uncolored datatypes are just the result of negligence on my part. When I have some time, I'll work on the material design, place some more thought into the color choices, and fill in the missing types. -Hardwigg (talk) 04:34, 2 May 2015 (UTC)

@Pasleim: You use Honeydraw, do you mean Honeydew? FreightXPress (talk) 19:50, 29 April 2015 (UTC)

Redirect after (trivial) manual merge[edit]

Hi. I just emptied this page after moving the only link to Q10927834. I don't know if this counts as a merge, and if so, how to make a redirect. --Rinaku (t · c) 19:07, 26 April 2015 (UTC)

You can read about merging at Help:Merge. Moving a link is okay, but you could also move the label for Russian. Redirecting is possible by API or the gadget (see the help). Matěj Suchánek (talk) 19:27, 26 April 2015 (UTC)
There was no label. I was unsure about merging the page after emptying it. Anyway, done. --Rinaku (t · c) 19:31, 26 April 2015 (UTC)

Two posts for vietnamese-american author Nha Ca[edit]

Q112180187 and Q10800987 refers to the same person. I do not know how to correct this. Boberger (talk) 12:22, 27 April 2015 (UTC)

Could you please correct the first link.--Ymblanter (talk) 13:07, 27 April 2015 (UTC)
Did you mean Q19629357? I have merged these. --Yair rand (talk) 14:06, 27 April 2015 (UTC)

"list of" episode[edit]

The class of all episode of Doctor Who (Q34316) (View with Reasonator) just has been linked to the item about the serie. So we now got an item that is both

< Doctor Who episode (Q387513) (View with Reasonator) > subclass of (P279) miga < episode (Q1983062) (View with Reasonator) >

and a list of episode. Is this really correct ? I don't know, do we have guidelines somewhere ? at some point we must have a rule for this otherwise this is a mess.

About episode (Q1983062) (View with Reasonator) : we can subclass this item with tv series and radiophonic episode. I think I did in the past, does anyone knows why they have been merged ?)

TomT0m (talk) 14:56, 27 April 2015 (UTC)

If you ask me it is wrong. There may be a category or a list article where the "list of" makes sense. Having a subclass of "Dr Who episode" is plain silly. Thanks, GerardM (talk) 06:45, 28 April 2015 (UTC)
you mean having a subclass of episode ? It's not silly, it's pretty convenient to be able to make specific subclasses (that's the whole point of subclassing). Imho the episode concept barely make sense if it is not subclassed. It's always an episode of some series. (and tv series episode is even more senseful, not having it would make a query in the set of all series who are television series more complicated). TomT0m (talk) 07:06, 28 April 2015 (UTC)
I agree that "Doctor Who episode" should not be a subclass of "episodes"; it should only be a list of episode (and probably renamed to something like "Doctor Who episode list"). Having "Doctor Who episode" implies "episode" should be subclassed into "Big Bang Theory episode", "Friends episode", "Modern Family episode", etc, which is silly. However I support subclassing "episode" into television/radio/etc. episode. -Hardwigg (talk) 03:28, 29 April 2015 (UTC)
@Hardwigg: First, no, it does not imply that. If you really want to list every episode instances, you can use Wikidata Query, which will work whether or not it is subclassed, but there is no problem with this. Considering a serie is by definition a list of episode, there is no need for a list of episode item, essentially. If we generate a query by episode in the future, this modelling is fine too: the article about the episode will list all the instances of some series' epidode class, ordered by their season/sequence number. Second, What's the problem with creating those items ? TomT0m (talk) 15:17, 29 April 2015 (UTC)
@TomT0m: I agree that subclassing with "Doctor Who episode" does not limit queries in any way. You can still search all episodes (CLAIM[instanceOf:TREE[episode][][subclassOf]]).
However not subclassing with "Doctor Who episode" also does not limit queries. You can still search for Doctor Who episodes (CLAIM[instanceOf:TREE[episode][][subclassOf]] AND CLAIM[series:Doctor Who]). I personally find this cleaner than CLAIM[instanceOf:Doctor Who episode], because it is more generic. It will work for any series; just replace the value of the series claim.
I also agree that having that "list of episode" item is not very useful, but we need a way to represent list pages in Wikipedia. (Actually, should Doctor Who episode (Q387513) and List of Doctor Who serials (Q19838686) be merged? Their corresponding Wikipedia pages both look to be lists of Doctor Who episodes).
I also agree that there is nothing technically incorrect with subclassing in this way (the universe of Doctor Who episodes is a subset of the "episode" universe). The reason I am against it is because I think it is too specific a subclass to be useful, and I don't see why it should be created. The relationship between a Doctor Who episode and the series "Doctor Who" is already well represented by the "series" property. I see subclassing "episode" into "Doctor Who episode", etc., the same as subclassing "novel" into "Harry Potter novel", "Sword of Truth novel", etc. Actually, you could probably replace every statement on an item with a subclass: "Hemingway novel", "1923 novel", "originally English language novel", "novel with Harry Potter character". I don't think "Doctor who episode" is any different from these. What does having a "Doctor Who episode" item add?
Also, you are correct that it does not imply that those items need to be created. It does support their creation, though, with which I have the above problem.
-Hardwigg (talk) 20:21, 1 May 2015 (UTC)
@Hardwigg: I do not agree. I think those item are useful, and if the model offers the flexibility to make this work, I see no reason why we should not do that.
details on how I see things:
  • There is an item for list of doctor who episode. In the original plan of Wikidata, this corresponds to a query. This query will very much look like CLAIM[] (plus an ordering for the sequence, maybe). Let's call this item Doctor Who episode.
  • This query defines a class by intensional definition (Q1026899) (View with Reasonator).
  • We should (that's where the uncertainty lies) be able to assert the membership of an item to a class, so potentially a query, if we want. This would mean this item should be in the query result
    < the episode > instance of (P31) miga < Doctor Who episode >
    should be something a user should be able to state (one edit at a time) :) So if the query does not returns the item, the item should be in a constraint report, and maybe someone would know the user did not put the series: Doctor Who claim. A semantic reasoner would not even need this, he would just deduce the claim himself.
Everything says that this makes sense and that it is possible. So this will be done by users. If we have the flexibility to do this, and this is consistent, I say we do this. If there is no real issue, no necessity to make some.
And last this is a flexibility I think we will need in a lot of cases when we do not really have enough information to build a meaningful query, and in which classes will exists and will be reals, but the properties we have won't be able to build a precise enough query. I think this ability to mix extensional definitions (when we explicitely says these items are members of this class and intensional one (a query will compute the instances) is a powerful thing that we should keep in mind.
So my position: if we can, this will be done, and there is no reason to fight this. This is (if nothing more) a conflict avoidance strategy :) TomT0m (talk) 08:23, 2 May 2015 (UTC)

Merge problems (2)[edit]

Can someone merge englisch en:Category:Biotechnologists (Q7626947) with German de:Kategorie:Biotechnologe (Q8908992) ? 17:33, 27 April 2015 (UTC)

→ ← Merged --Pasleim (talk) 17:41, 27 April 2015 (UTC)

Can someone merge english en:Category:Bion satellites (Q7021297) with German de:Kategorie:Forschungssatellit (Biologie und Medizin) (Q8957715) ? 17:40, 27 April 2015 (UTC)

Can someone merge en:Category:Hunting legislation with German de:Kategorie:Jagdrecht (Q8978391) ? 17:50, 27 April 2015 (UTC)

Can someone merge en:Category:Biotechnology law (Q7487449) with German de:Kategorie:Gentechnikrecht ((Q16863875)) ? 17:54, 27 April 2015 (UTC)

Done. --Marek Koudelka (talk) 18:00, 27 April 2015 (UTC)

Can someone merge en:Category:Cell culture (Q7305817) with German de:Kategorie:Zellkultur ((Q19617161)) ? 18:14, 27 April 2015 (UTC)

Can someone merge en:Category:Marine reserves (Q7145269) with German de:Kategorie:Meeresschutzgebiet (Q9017452) ? 18:25, 27 April 2015 (UTC)

→ ← Merged, I think it's better if you register here and activate the merge gadget. These requests will become annoying after some times. Sjoerd de Bruin (talk) 18:26, 27 April 2015 (UTC)
Even without an user account it's possible to merge items with Special:MergeItems --Pasleim (talk) 18:40, 27 April 2015 (UTC)

Match available Wikipedia data with empty Wikidata data (From infoboxes)[edit]

Hello Wikidatorians,

After discovering this project today I noticed a potential improvement on the current system of Wikidata but i'm not sure if this is possible or not, so it will be great if someone can review this comment and let me know how we can do this. After viewing Anzac Day which was a public holiday recently observed in Australia and New Zealand I noticed that the date observed (which is reoccurring annually on the same day) is April 25th, this data was not entered into Wikidata until the 15th Sept 2013 however the data was showing on Wikipedia in the infobox ever since 25th Nov 2006 is it possible to programmatically connect data available in Wikipedia from infobox's, to data available in Wikidata that has not been entered? is this even a good idea?

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

First of all: Wikidata didn't exist in November 2006. Wikidata was started on October 29, 2012, statements weren't enabled until February 2013, and data for what day of the year holidays occur could not be added to Wikidata until September 3, 2013.
Lots of data from Wikipedia is frequently mass-imported to Wikidata, and of course many Wikipedias are using data from Wikidata in their infoboxes. Importing data can be problematic as the infoboxes are sometimes unsourced, or sometimes importing the sources automatically can be difficult. --Yair rand (talk) 08:38, 28 April 2015 (UTC)
Thank you for clarifying the details around timings. Since Wikipedia infobox data is problematic do you then think it is a better solution for someone like me or anyone else to manually update data in Wikidata and find sources on government websites for things like public holiday dates if they reoccur on the same day each year. --Deepheater (talk) 03:23, 29 April 2015 (UTC)
Yes, that would be exactly right. --Denny (talk) 16:21, 30 April 2015 (UTC)
Is there a commonly used method to enter the date of a Wikidata event such as a Public holiday that is not a specific date of the year like April 25th every year. How would someone enter the date of an event if that date was a unique date to this year like on the 26th of April this year but on the 27th of April next year for example. Also is there a method to enter data such as this event occurs on the First monday before a specific date every year. --Deepheater (talk) 22:19, 30 April 2015 (UTC)

ISSNs for web and print[edit]

John Vandenberg (talk) 09:30, 2 December 2013 (UTC)
Aubrey (talk) 12:15, 11 December 2013 (UTC)
Daniel Mietchen (talk) 12:47, 11 December 2013 (UTC)
Micru (talk) 13:09, 11 December 2013 (UTC)
DarTar (talk) 01:37, 15 January 2014 (UTC)
Randykitty (talk) 14:57, 15 January 2014 (UTC)
Maximilianklein (talk) 00:23, 28 March 2014 (UTC)
Mvolz (talk) 08:10, 20 July 2014 (UTC)
Andy Mabbett (Pigsonthewing); Talk to Andy 22:17, 27 July 2014 (UTC)
Mattsenate (talk) 17:26, 14 August 2014 (UTC)
Pictogram voting comment.svg Notified participants of Wikiproject Periodicals @Andrew Gray, Hsarrazin: Last month I asked: "Faraday Discussions (Q385884) (for example) has two values for ISSN (P236), one for print the other for the online version. Should we use qualifiers, or separate properties to distinguish them. In either case, what should these be, or be called?" Several people said we should use qualifiers, but no-one suggested what these should be. Any suggestions?

I was also told, off-wiki: "There is now also the ISSN-L which is used to link together the various incarnations of the journal in different media (print/electronic/other). The ISSN-L has the same value as one of the existing ISSNs for the journal - so the ISSN-L for Faraday Discussions is 1359-6640 (i.e. same as p-ISSN)". Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 09:54, 28 April 2015 (UTC)

Well, you equally could have consulted, on-wiki, en:International Standard Serial Number... Thus the problem has two dimensions: While in theory the wikidata item for the "periodical-as-work" could be related to additional items for the web and print versions (different dates of first issue / launch, different dates of cessation, or maybe the content is not an 1:1 copy, the print version having different ads, the web version having multimedia annexes to articles...), I agree, that the use of suitable qualifiers (for all these properties) could help avoiding such splits. I'm not sure whether the property for this qualifiers really does exist, applies to part (P518) sound so "phyiscal"... Or - the value of that qualifier could best be exactly the respective ISSN for identification purposes, thus for ISSN (P236) we would need a different set of qualifying values, representing "online" and "print" (usually - there were times where some publications may have been distributed on CD-ROM also - maybe someone finds an example for a serial with a third ISSN for that kind of carrier / distribution media).
The L-ISSN on the other hand is non-unique in princple, and it is always one of the "ordinary" ones. Since I expect that we extremly seldomly will have more than item representing the different forms of a periodical I propobse that instances of ISSN (P236) could be qualified with three cases: "novalue" (this is not the L-ISSN), "this is the L-ISSN and also a valid ISSN for this item" (which one is indicated by a different qualifier, cf. the preceding paragraph), "this is the L-ISSN but not a valid ISSN for this item" (this last case being extremely seldom and it should be kept out of uniqueness constraint reports...).
The situation is similar to books and editions, but much worse over there (items for 19th century works haunted by an arbitrary selection of ISBNs of modern editions in any language whatever, or, three-volume publications having four ISBNs: one for each volume and one for the "set". Or - for authority control: different pseudonyms plus the real identity all have different VIAF identifiers, but the real identity somehow is "distinguished"), perhaps one can learn from the ISSN: "L" stands for "Leader", i.e. it is permissible to view something as distinct entities (each of them with their own distinct ISSN) 'or' to combine the items to something (a group of publications regarded the same content-wise) and in the latter case the combined item should be identified by the distinguished "leader"-identifier. Thus a general property for identifier strings could take the values "leader, valid for this item", "leader, not valid for this item". -- Gymel (talk) 10:38, 28 April 2015 (UTC)
I would suggest the way to express all of the above in wikidata properties is that ISSN (P236) has two values and we use "applies to part" as the qualifier for each value to link to "on-line edition" or "print edition" where these are generic items rather than items representing the specific online and print editions of this publication. If one of the ISSN is identified as the leader then make it "preferred" rank.
For books we will usually have separate items for translations but often we will have one item for all the English language editions, even though their will likely be different ISBNs for the UK and USA editions. We may need to create items for the UK edition and for the USA edition, separate from the main item for the book, with the ISBNs listed in the item for the edition it applies to. This can mean the main item for the book doesn't have any ISBN. OK? Filceolaire (talk) 04:13, 30 April 2015 (UTC)
Very much agreed. However we may think for a moment whether we should now introduce a generic property "applies to version" (or more technically, "applies to expression or manifestation") and use that instead of applies to part (P518): As stated above I have trouble to dissect "the serial" (in several aspects an abstraction quite far away from the world of physical "things") into two parts, namely the "physical exemplars?" and the "electronic" (or online or CD-ROM-based) ones. And furthermore a dedicated (well, general enough to be extensible to "books") property would allow specific constraints checking. -- Gymel (talk) 09:16, 30 April 2015 (UTC)

Merge Problems[edit]

Can someone merge en:Category:Fishing museums (Q16780536) with German de:Kategorie:Fischereimuseum (Q8954440) ? 18:45, 28 April 2015 (UTC)

✓ Done see Q8954440. Delsion23 (talk) 23:58, 28 April 2015 (UTC)

Generating items from Wikipedia categories[edit]

In the category cy:Categori:Eisteddfodau yn ôl blwyddyn on, the articles for eisteddfodau (plural of eisteddfod) up to 1881 have Wikidata items, but not the ones for 1882 to the present day. Can the remaining items be generated automatically from the Wikipedia category? Ham II (talk) 05:17, 29 April 2015 (UTC)

With you can create them directly. --- Jura 06:34, 29 April 2015 (UTC)
@Jura1: Face-wink.svg Thank you!—starting to get the hang of it now! Ham II (talk) 06:52, 30 April 2015 (UTC)
To add English labels you can edit the result from [1] and add it with [2]. Adding "point in time" is a bit more complicated. --- Jura 08:23, 30 April 2015 (UTC)

How to Create company database in Wikidata[edit]

Hi there,

It would be great if you help me about how to save company database into wiki data. As we know Freebase is a medium to get fetched data as a knowledge graph into google searches. Since Freebase stopped providing services and its entire data is migrating to So how we will come to know or able to get database as knowledge graph for google search engine. Please suggest the steps to create company page as simply we had to create in freebase. --VarunNegiUr (talk) 08:38, 29 April 2015 (UTC)

Please read this first. Also, your company needs to meet our notability policy. Sjoerd de Bruin (talk) 08:47, 29 April 2015 (UTC)

extract items ordered by value on a certain property[edit]

I would like to (continually) be given a list of all items that have a certain property, ordered by the value of that property. Specifically, I would like all the items that have the Perry Index (P1852) property, ordered numerically by their value. So, say, a table the first column listed the P1852, the second column listed the (possibly more than one) items that have that specific value.

What is, at the moment, the easiest way to that? I know of Wikidata:Database reports/Constraint violations, but I don't mean to limit the above query to values that are erroneous. Gabbe (talk) 09:48, 29 April 2015 (UTC)

I also know how to construct this, but not how to sort the table by its rightmost column. Gabbe (talk) 10:26, 29 April 2015 (UTC)
I would try downloading it. Spreadsheet software should be able to sort it. Popcorndude (talk) 11:38, 29 April 2015 (UTC)
You might want to try TAB --- Jura 11:46, 29 April 2015 (UTC)

Commons category cannot be linked anymore[edit]

commons category can no longer be linked at Other Sites, e.g. Otto Modersohn (Q71425) c:Category:Otto Modersohn --Oursana (talk) 12:28, 29 April 2015 (UTC)

Seems working here. Sjoerd de Bruin (talk) 12:30, 29 April 2015 (UTC)
Thanks for your help, today it finally works again--Oursana (talk) 13:45, 30 April 2015 (UTC)

Should usage instructions be included in descriptions?[edit]

Please join the discussion at Help talk:Description#Putting usage instructions in descriptions. Cheers! Kaldari (talk) 21:35, 29 April 2015 (UTC)

Why not use appropriate properties to describe? And reduce "description" to comment for rare cases. FreightXPress (talk) 14:21, 30 April 2015 (UTC)

Merge problems: Eyal[edit]

Can someone merge German article de:Eyal (Q1385639) with english article en:Eyal (disambiguation) (Q5422549) ? 23:26, 29 April 2015 (UTC)

→ ← Merged -- LaddΩ chat ;) 02:29, 30 April 2015 (UTC)

If it's written with a different alphabet is it a different language?[edit]

There are a number of languages which can be written in multiple alphabets. When we use the "monolingual text" datatype we are asked to indicate which language the text is in but it should also be possible to indicate which alphabet is used. Can this be done with monolingual text? Filceolaire (talk) 16:15, 30 April 2015 (UTC)

Script (per ISO), via "ISO 15924 alpha-4 or numeric code" (Property:P506) and/or an orthography? FreightXPress (talk) 16:32, 30 April 2015 (UTC)
This should be done with IETF language tag (Q1059900). I tried "en-latn" with Sandbox Monolingual text (P1450) in Wikidata Sandbox (Q4115189), but my edit was blocked. IETF language code seem to be forbidden in "monolingual text". Ask developpers. Visite fortuitement prolongée (talk) 19:36, 30 April 2015 (UTC)
The answer is no. When something is written in a different script, it is still in the same language. Serbian may be sr-Latn or sr-Cyrl. Wikipedia uses technology to convert on the fly from one script to another. As far as I know we do not use that technolcogy for Wikidata. That is an issue and it is not solved by pretending that it is a different language. On a practical level, would we link sr.wp to the Cyrillic or to the Latin version... Same is true for Chinese. Consequently, it needs some REAL attention to do justice to this issue. It is not as simple as using monolingual type. Thanks, GerardM (talk) 05:50, 2 May 2015 (UTC)

Level of granularity of properties[edit]

We have simultaneous discussions about deleting properties in favour of (i.e. effectively merging them into) more general properties (Wikidata:Properties for deletion#Slovene Cultural Heritage designation (P1597); Wikidata:Properties for deletion#MTR station code (P1377)); and, conversely, splitting specific properties off from the more general (Wikidata:Property proposal/Authority control#Web Gallery of Art id).

On the one hand, more specific properties allow easy use of formatter URL (P1630); on the other, they may make it harder to keep track of what's what.

We need, I think, to agree a policy on this. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 20:00, 30 April 2015 (UTC)

Wikidata:Database reports/List of properties/datatype/string lists 712 properties. Many are identifiers. It would be nice if a table could show
for all of them. Maybe User:Magnus Manske could create a tool or it exists already? List selected properties of all properties of a specific datatype. FreightXPress (talk) 00:05, 1 May 2015 (UTC)

Add a link to the creation discussion to property talk pages[edit]

Most property talk pages have very little information on how the property is to be used. They have the constraints but these in some cases contradict what was agreed in the discussion when the property was created.

Can we add a link to the archived property creation discussion? Let's put this at the top of the page, above the constraints? These discussions usually include useful guidance on how the property is to be used which is not available elsewhere and which is not easy to find. Filceolaire (talk) 01:19, 2 May 2015 (UTC)

I agree that we probably can do much better (I did propositions some time ago but nobody understood /o\). But things also evolves for good reasons beetween the creation and the current usage on the property. So I do not agree to just put a link. We should (and either the wikidatian who proposed the property, the creator ...) care to put a good documentation and a little text explanation on how to use the property on the property page. And when things evolves and new usecase are found, keep this up to date
If that's too big of a burden, we should index the usecases themselves, as often properties are used together, or said differently, for a given usecase, there is a set of properties involved. We should document the usecases, and for each property, give links in the property documenation on this pages.
That's why I proposed to also document classes, as a class is often associated to a set of related properties (for example, an event and its subclasses all have a date or an interval of date, usually a topic ..., that's also true for the subclasses). TomT0m (talk) 07:59, 2 May 2015 (UTC)

Don't change old values of publication?[edit]

The instruction for publication (P577) currently says "don't replace old values", but it doesn't say why. If, for example, an art-house film was released during a film festival, what would be wrong about increasing the precision of P577 from "2014" to "2014-09-03"? Is there any reason for retaining the less precise value (unlike in the publication values for Lucy (Q15624215))? Gabbe (talk) 08:47, 2 May 2015 (UTC)