Wikidata:Project chat

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 2019/03.

SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day.

Please block User:UU[edit]

He vandalised many interwikis about Planet X or Planet Beyond Neptune.  – The preceding unsigned comment was added by 2001:2d8:e290:9990::ba48:af02 (talk • contribs) at 16 February 2019‎ (UTC).

How to distinguish against events?[edit]

I'm trying to find items near a given geographical point that are not events -- eg not 'happenings'.

It used to be that I could exclude (or de-prioritise) items that were in the subclass tree of occurrence (Q1190554) to achieve this.

But now I am finding chains like the following are breaking this assumption

• occurrence (Q1190554)
• phenomenon (Q483247)
• state (Q3505845)
• order (Q16513015)
• organization (Q43229)
• institution (Q178706)
• cultural institution (Q5193377)
• GLAM (Q1030034)
• museum (Q33506)
• national museum (Q17431399)

and similarly for eg monastery (Q44613) --> organization (Q43229) etc

So: (i) do we think these are valid subclass of (P279) chains ?

And (ii) how best now to distinguish/exclude true "events" -- ie things happening over a finite (short) duration -- from general items ? Jheald (talk) 22:54, 24 February 2019 (UTC)

The most recent link in the chain above I think was organization (Q43229) --> order (Q16513015), by User:-xfi- on 27 January diff. This is what I think has joined up the chain, that has broken my query. It may have been based on reading a different sense of the word "organization". On the other hand, maybe it has a certain validity. Are there other links that should be questioned? Jheald (talk) 23:06, 24 February 2019 (UTC)

That certainly strikes me as the weakest link in the chain. - Jmabel (talk) 00:31, 25 February 2019 (UTC)

That link is certainly questionable, but I also question the chain which leads us from state (Q3505845), which seems to me to be associated with a certain stability and duration, to occurrence (Q1190554), which is specified to have has quality (P1552) = point in time (Q186408). The distinction would be useful to be able to draw, in our class tree, I think. Jheald (talk) 12:27, 25 February 2019 (UTC)

It’s very possible state (Q3505845) is actually a metaclass, so should be left out of this class tree. Let « combat state » be the state of a military ship prepared for a fight (Real example in Wikidata if I recall). This « combat state » has instances in the real world, obviously, and can be characterized - weapons armed, crew ready … But imho it’s not a subclass of states, but an instance of state. A state is then not a subclass of events, but a class of events. This fits with the definition of a state : « denotes the presence of stable values of a set of variables of an object ». Combat state IS the set of variables of the ship. The « state » concept itself is a kind of events-class, it is instantiated by giving the characteristics of the instances of that event class - just like the « ship » concept is instantiated by giving an object that fits the characteristics of a ship. author  TomT0m / talk page 12:54, 25 February 2019 (UTC)

--Micru (talk) 21:46, 24 August 2014 (UTC) Tobias1984 (talk) TomT0m ^(talk) Genewiki123 ^(talk) Emw (talk) 03:09, 9 September 2014 (UTC) —Ruud 16:15, 9 December 2014 (UTC) Emitraka (talk) 14:32, 14 October 2015 (UTC) Bovlb (talk) 19:10, 21 October 2015 (UTC) Peter F. Patel-Schneider (talk) 22:21, 23 October 2015 (UTC) ArthurPSmith (talk) 15:51, 5 November 2015 (UTC) --Daniel Mietchen (talk) 20:53, 3 January 2016 (UTC) --Harmonia Amanda (talk) 22:00, 27 February 2016 (UTC) --Lechatpito (talk) --Andrawaag (talk) 14:42, 13 April 2016 (UTC) --ChristianKl (talk) 16:22, 6 July 2016 (UTC) --Cmungall Cmungall (talk) 13:49, 8 July 2016 (UTC) Cord Wiljes (talk) 16:53, 28 September 2016 (UTC) DavRosen (talk) 23:07, 15 February 2017 (UTC) Vladimir Alexiev (talk) 07:01, 24 February 2017 (UTC) Pintoch (talk) 22:42, 5 March 2017 (UTC) Fuzheado (talk) 14:43, 15 May 2017 (UTC) YULdigitalpreservation (talk) 14:37, 14 June 2017 (UTC) PKM (talk) 00:24, 17 June 2017 (UTC) Fractaler (talk) 14:42, 17 June 2017 (UTC) Andreasmperu Diana de la Iglesia Jsamwrites (talk) Finn Årup Nielsen (fnielsen) (talk) 12:39, 24 August 2017 (UTC) Alessandro Piscopo (talk) 17:02, 4 September 2017 (UTC) Ptolusque (.-- .. -.- ..) 01:47, 14 September 2017 (UTC) Gamaliel (talk) --Horcrux92 (talk) 11:19, 12 November 2017 (UTC) MartinPoulter (talk) Bamyers99 (talk) 16:47, 18 March 2018 (UTC) Malore (talk) Wurstbruch (talk) 22:59, 4 April 2018 (UTC) Dcflyer (talk) 07:50, 9 September 2018 (UTC) Ettorerizza (talk) 11:00, 26 September 2018 (UTC) Ninokeys (talk) 00:05, 5 October 2018 (UTC) Buccalon (talk) 14:08, 10 October 2018 (UTC) Jneubert (talk) 06:02, 21 October 2018 (UTC) Yair rand (talk) 00:16, 24 October 2018 (UTC) Tris T7 (talk) ElanHR (talk) 22:05, 26 December 2018 (UTC) linuxo

Notified participants of WikiProject Ontology for input -- Jheald (talk) 12:29, 25 February 2019 (UTC)

Why should phenomenon (Q483247) be a subclass of occurrence (Q1190554)? A phenomenon (Q483247) is not necessarily associated with any time. — Finn Årup Nielsen (fnielsen) (talk) 12:56, 25 February 2019 (UTC)

The definition in english is « observable occurence », by this definition this is an event. On the frwiki article however we get a different definition « Un phénomène est la manière dont une chose, un fait du monde physique (objet, action…), psychique (émotion, pensée…) ou social (produit d'interactions sociales) se manifeste à la sensibilité d'un être vivant. » (a phonomenom is the way a thing or a physical (or social) fact manifests itself to a beeing sensitivity) which is definitely not the same. I’d say that then that it’s the same as for « state », « phenomenom » may be a metaclass. Watch a tree out of the window, you’ll feel twice the same tree, experimenting something similar if not identical. It seems reading a little more reading the frwiki article a little more that a « phenomenom » could be more precisely defined as a process in which a living entity feels the outside world. If instances of a process (say « jumping ») are events, « jumping » is a subclass of events. But not « process », which is a kind of events, a metaclass. So I’d best see « phenomenom » as a metaclass, but philosophical notions are always a challenge. author  TomT0m / talk page 13:30, 25 February 2019 (UTC)

It's not just this chain. I keep noticing subclass relationships on general classes that I do not agree with. I've learned to just live with them, to the point that I don't even record or remember them. If someone is interested in attempting to clean up the subclass hierarchy in Wikidata I'm motivated to participate. My first suggestion would be to require that general classes have a much better description, with examples and counter-examples, so that at least there is some guidance as to what correct and incorrect subclass relationships are. With the current level of documentation for general classes, it can be impossible to determine whether a subclass relationship on one of them is valid. Peter F. Patel-Schneider (talk) 12:54, 25 February 2019 (UTC)

I removed "order" as a superclass for "organization", and added it separately under "has quality". I see a lot of people using the class hierarchy for abstract relationships like this when we have much more suitable properties. There's no reason to defer to something that doesn't make sense. ArthurPSmith (talk) 13:35, 25 February 2019 (UTC)

I’m curious to know the rationale behind that statement. Is the « order » term used as a kind of synonym of the structure of an organization ? I can’t read the articles in which the term is defined. author  TomT0m / talk page 13:49, 25 February 2019 (UTC)

It seemed like a better relation - but perhaps there should be no such relation? I don't mind if somebody else removes it completely. The subclass of (P279) relation was certainly wrong anyway. I suspect the editor who added that was thinking of the meaning of the word "organization" as a state or condition, not the actual meaning of that entity as a class of groups of people etc. ArthurPSmith (talk) 17:02, 25 February 2019 (UTC)

I agree with Peter F. Patel-Schneider. The problem seems to be that subclass relationships are added on an adhoc basis whenever somebody thinks it's a good idea. This is the Wiki way after all. But unfortunately they don't always verify that every instance of the subclass is also an instance of the parent class. I'd suggest that an improvement would be to discuss the reasoning for the relationships in detail in the Talk page for each item, and then watch the item to revert changes that aren't consistent with the reasoning, at least without further reasoning. Ghouston (talk) 22:17, 25 February 2019 (UTC)

We probably also need regression tests. These would be particular queries that are expected to return certain results. Ghouston (talk) 22:41, 25 February 2019 (UTC)

Perhaps it would be useful if we had a central {{Wikidata list}} (or equivalent) for the upper ontology, which users could add to their watchlists to monitor changes to the items (and use the history to find the order of changes), and other lists for specialized ontologies for each Wikiproject which could be monitored there. --Yair rand (talk) 22:53, 25 February 2019 (UTC)

{{Wikidata list}} could also be used to construct regression tests: you'd just have to add the output page to your watchlist. Ghouston (talk) 23:10, 25 February 2019 (UTC)

I created the page Wikidata:WikiProject Ontology/Top-level ontology list to show the top two levels of the ontology, the theoretical fundamentals as stored on Wikidata. It's ... pretty bad. :( --Yair rand (talk) 02:26, 28 February 2019 (UTC)

Yeah, and improving it would involve a multitude of struggles, on a case-by-case basis. Ghouston (talk) 21:36, 28 February 2019 (UTC)

A lot of the entries are colours, I think I can do something with those. Ghouston (talk) 21:45, 28 February 2019 (UTC)

@Ghouston: Be sure to discuss with User:ArthurPSmith before wading in too quickly re colours. It's been quite a contentious area in the past. Jheald (talk) 21:48, 28 February 2019 (UTC)

Still, they can be subclasses of color (Q1075) instead of subclasses of entity (Q35120) ... it seems to me. Ghouston (talk) 21:53, 28 February 2019 (UTC)

Well, nothing is easy. What does the item color (Q1075) represent? Enwiki says "colour (Commonwealth English), is the characteristic of human visual perception described through color categories, with names such as red, orange, yellow, green, blue, or purple." So it's a "characteristic of human visual perception", but maybe we'd need another item to represent the colours themselves. Or perhaps color (Q1075) should represent the colours and there are other items like color vision (Q374259) to represent the mechanism. Ghouston (talk) 22:04, 28 February 2019 (UTC)

@Ghouston: User_talk:ArthurPSmith#Colors_as_subclass_of_entity?. --Yair rand (talk) 22:33, 28 February 2019 (UTC)

I see you've already been over the exact subject, and it shows how obscure these discussions can get. I'd imagine having a particular item representing the range of possible colours (at least such colours as we'd want to describe with items), with a colour like "red", actually a range of colours, being a subclass, and a "pure" colour, an item representing a "single colour" that can't be divided, being an instance. Ghouston (talk) 22:54, 28 February 2019 (UTC)

@Ghouston: Relevant: Wikidata:Requests_for_comment/Are_colors_instance-of_or_subclass-of_color. I'm not even sure if distinct "single colors" are things that can exist. Or maybe all the colors are pure/indivisible colors, but just somewhat ambiguous which one it is? Interestingly, the Suggested Upper Merged Ontology has Red instance of PrimaryColor subclass ColorAttribute subclass VisualAttribute, but Emw mentioned that BFO uses subclass all the way. Maybe splitting the colors into range items and pure-color items makes sense. (Notifying @ArthurPSmith: of this discussion.) --Yair rand (talk) 23:49, 28 February 2019 (UTC)

Uh, yes, it gets complicated. I think starting at the top level is the wrong approach - it's much easier to think about relationships at a more concrete level, and even with something seemingly as simple as color is actually quite tricky. As I just noted on my talk page, I think treating colors as classes may have been wrongheaded, and we should handle them more like the way we handle locations. Locations have natural hierarchies which we capture in wikidata with various properties like located in the administrative territorial entity (P131). Perhaps we need a special property for color space that works similarly - or maybe a generic property like facet of (P1269)? Using subclass of (P279) to represent this hierarchy seems to be definitely quite confusing. ArthurPSmith (talk) 16:00, 1 March 2019 (UTC)

It's hard to work out whether or not colours should have a subclass hierarchy, and how to construct a hierarchy. However, it doesn't seem to me that individual colours deserve to be near the top-level item in the ontology. Maybe the best thing for now would be to make each colour item an instance of color (Q1075), as many already are, and remove any subclass statements. At least they will be grouped together and can be enumerated with a simple query. Ghouston (talk) 08:00, 3 March 2019 (UTC)

Alternatively perhaps make the top level of colours a subclass of qualia (Q282250) ? Jheald (talk) 10:08, 3 March 2019 (UTC)

That would be color (Q1075) itself. Colours are subjective, but in response to particular a physical phenomenon, so colours can be standardised and measured and so forth. Ghouston (talk) 10:15, 3 March 2019 (UTC)

Don't think so. Every case of a colour in the class "red" is a case of a qualia. So that looks more like a subclass relationship. It may also be a case of a physical phenomenon. Items can combine more than one class heritage. Jheald (talk) 10:29, 3 March 2019 (UTC)

I don't think that the idea of colour subclasses is wrong, although building a good hierarchy of colours would be difficult because there are different schemes for defining and naming colours. You can start with a statement like "red is a colour", which gives an idea of what the "colour" item is going to be: the class of all possible colours. So red (Q3142) is an instance of color (Q1075). But then if you read the Wikipedia article about red, it confirms that red is a colour, but it turns out there's a whole range of reds, each of which can also be described as colours. Some are defined from the colours of chemical compounds, some from colour standards, some may be pretty vague. So it also makes sense to say that red (Q3142) is a subclasss of color (Q1075). Ghouston (talk) 10:57, 3 March 2019 (UTC)

If you declare that A is an instance of B and also a subclass of B you must be either conflating two different meanings in the item "A" or in the item "B"; in this case I think the conflation is between "red as a color" and "colors perceived as reddish" as a class of colors. As to the "top of the class hierarchy" issue - I think this is a pretty meaningless criterion. If you look at computer programs (java say) in practical use, huge numbers of classes are at the "top of the class hierarchy" because it's not useful to define them as subclasses of anything else. It's not wrong or a problem, just the way the world is. At least that's my view. But I wouldn't be opposed to a more general color class representing "all of colorspace" or something like that if it made sense. ArthurPSmith (talk) 14:27, 4 March 2019 (UTC)

Maybe perception (Q160402)   is a better item, less close to the philosophical definition problem. Both can be done, a specific colour seems to be a qualia-class to me.

< visual perception > subclass of (P279) < perception >

-

< human visual perception > subclass of (P279) < visual perception >

-

< (human) color perception > subclass of (P279) < Human visual perception >

(because of course bees do not perceive the colours the same way humans do-

< Red > subclass of (P279) < (human) color perception >

. The « colour » property associated to this hierarchy could then be labelled « perceived by human as colour».

If we want to then have a « colour » class, it should be a perception meta-class. This item would be described as « a class of visual sensation that humans gives names to, by which they can characterize objects or lights. »

Anyway there is a lot of aspects of colours (blue-light for example is different from blue-light qualia, a blue object is also something different), so a « one size fits all » approach may be doomed to fail. Also it would be a shame to avoid the hierarchy issue when it seems there is a natural colour hierarchy. A classification of light rays according to their wavelenght (X-ray, visible light, infrared …) is definitely something doable. Of course then « red light » is naturally a subclass of « visible light ». Of course it’s a little bit more complicated if there is a combination of different wavelenghts like in the light emitted by a star of in « white light » (enwiki: « White light, a combination of lights of different wavelengths in the electromagnetic spectrum »).

Another item funny item I found HTTPS://WWW.WIKIDATA.ORG/WIKI/Q375479

To sort this mess, I think I important question is « what do we want to achieve, what are our use cases ? » Do we want to describe paintings with colours ? Describe star lights ? Both ? Why should we have only one colour property ? author  TomT0m / talk page 10:59, 3 March 2019 (UTC)

This is why we have abstract concepts like "colour", so that we can talk about colours as a general concept and not have to deal with each colour individually. So whatever a colour is declared to be, we can declare it on color (Q1075), and then declare individual colours to be instances or subclasses of that. Ghouston (talk) 19:39, 3 March 2019 (UTC)

@Ghouston: There is a definition of color (Q1075) : « visual perception of light wavelengths … » (english description) and it’s no more no less abstract than any other concept. I don’t think we can use this as a catch all item for anything related to the colour domains as we like. So I don’t think your suggestion, if I understand it correctly, is of any help to sort anything out. author  TomT0m / talk page 12:38, 4 March 2019 (UTC)

"Visual perception of light wavelengths" is really the definition of color vision (Q374259). How do you define "a colour"? It will involve some subset of visible light. It's true some statements about particular colours may not apply to all colours, so can't be put directly on color (Q1075). In some cases the statement may be unique to that colour, in other cases there may be a subclass of colours, such as colours of a single hue, monochromatic color (Q6901438). Ghouston (talk) 20:18, 4 March 2019 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ A useful reference here might be the Getty AAT color hierarchy, which distinguishes "colors (hues or tints)" and "color (perceived attribute)". [They also have color (pigment)" as a material, one or more pigments collectovely in suspension, but that's different.] - PKM (talk) 23:08, 4 March 2019 (UTC)

color (Q1075) is currently linked to the first two, using AAT ID (P1014). I think 300080438 colors (hues or tints) is the right match for this item. I'm not sure if there's an existing item corresponding to 300056130 color (perceived attribute), or how it could be used. Ghouston (talk) 04:29, 5 March 2019 (UTC)

Shouldn't proper names be considered lexemes?[edit]

Ash Crow
Dereckson
Harmonia Amanda
Hsarrazin
Jura
Чаховіч Уладзіслаў
Sascha
Joxemai
Place Clichy
Branthecan
Azertus
ToJack
Jon Harald Søby
PKM
Pmt
Sight Contamination
Tris T7 ^{TT me}
MaksOttoVonStirlitz
BeatrixBelibaste
Moebeus
Dcflyer
Looniverse
Aya Reyad
Orr Deanna LeiAnn HeaveLEI
Infovarius
 Klaas `Z4␟` V:  Notified participants of WikiProject Names

Wiktionary contains proper names. Why here on Wikidata they are considered items and not lexemes?--Malore (talk) 00:11, 27 February 2019 (UTC)

• We certainly need them when they coincide with categories, which many (potentially most) do. - Jmabel (talk) 02:25, 27 February 2019 (UTC)

The name properties family name (P734) and given name (P735) were created as item properties without sufficient consensus for this data type. (When summoned, they have been kept with the reasoning, consensus for deletion hasn't been reached either…) Lexeme or multilingual text, or even monolingual text would be definitely much better choice, but I'm afraid, too many users and too many robots have made their career on Wikidata on propelling the established misconception and it's practically impossible to change it now. However, if you're willing to try, you can count on my support.--Shlomo (talk) 10:19, 27 February 2019 (UTC)

• A lexeme exists in a certain language. On the other hand names in the item namespace are independent of a given language. ChristianKl ❪✉❫ 11:42, 1 March 2019 (UTC)

• Yes, we can link the L-entities from these items. --- Jura 12:00, 3 March 2019 (UTC)

• @Malore: You can create lexemes for names (given names or family names). What do you think currently prevents you from doing so? --- Jura 12:00, 3 March 2019 (UTC)

• @Jura1:Nothing, simply I couldn't find any example of such uses and I didn't know why.--Malore (talk) 13:49, 4 March 2019 (UTC)

What about limiting the domain of named after (P138) and named by (P3938) to lexemes?[edit]

Currently, there are over 180000 uses of named after (P138), but only three of them are in lexemes.

named by (P3938) is used only one time for lexemes.

I think they should be used only for lexemes and for proper names. Why not including proper names in lexemes and limit the domain of these properties to lexemes?--Malore (talk) 00:21, 27 February 2019 (UTC)

Are you saying that we should not have, for example

< W.E.B. DuBois Clubs of America (Q7945187)   > named after (P138) < W.E.B. Du Bois (Q158060)   >

? Or that something with lexemes would somehow replace this? - Jmabel (talk) 02:29, 27 February 2019 (UTC)

@Malore: Lexemes are for language-dependent concepts. named after (P138) is generally independent of language and should be at the concept level (items), not lexemes. Otherwise you would have the same relationship repeated for 300 lexemes (each language a proper name might be used in). ArthurPSmith (talk) 13:53, 27 February 2019 (UTC)

@Jmabel: I'm saying we should:

• remove named after (P138)  W.E.B. Du Bois (Q158060) from W.E.B. DuBois Clubs of America (Q7945187) because it doesn't talk about the organization but it talks about (one of) its name;

• create a lexeme for each name of the organization. In particular, one entitled "W.E.B. DuBois Clubs of America" with a sense that talks only about the name of the organization, and therefore containing named after (P138)  W.E.B. Du Bois (Q158060) and WikiCFP conference series ID (P5127)  W.E.B. Du Bois (Q158060).

In general, I think an item shouldn't contain statements about its name, which can be more than one or differ from language to language. Instead, each of these names should be represented by a lexeme.--Malore (talk) 14:01, 27 February 2019 (UTC)

@ArthurPSmith: named after (P138) is not always language-indipendent. For example, Pascal's triangle (Q177051) can be named "Pascal's triangle" or "Khayyam's triangle" or "Yang Hui's triangle" or "Tartaglia's triangle", each of which is named after a different person. It's not so uncommon that the same thing is named after different people in different countries. Sometimes it's named after different persons even within the same country. --Malore (talk) 14:09, 27 February 2019 (UTC)

That's not a matter of language, that's conceptual attribution (you yourself mentioned it's a regional, not lingual, issue), and it should still be at the concept level, just have the concept named after several different people. Such problems are quite rare. Otherwise we're replacing 180,000+ items with 54 million+ (?) lexemes! ArthurPSmith (talk) 14:17, 27 February 2019 (UTC)

Because what you want for lexemes is derived from (P5191) anyway? Circeus (talk) 16:45, 27 February 2019 (UTC)

@ArthurPSmith: What I propose won't "replace" any item and, although it requires to create lexemes, these lexemes should be created anyway: "Pascal's triangle", "Tartaglia's triangle", etc. have every right to be lexemes. What I propose is to move the statements involving named after (P138) from the item to the lexemes' senses. It obviously requires more work but it will allow to better understand which word is named after which entity.

As for the regional vs lingual issue, it's not always true because January (Q108) is named after Janus (Q167685) in English, but it's named after ice (Q23392) in Czech.--Malore (talk) 21:00, 1 March 2019 (UTC)

You can qualify the statement on the item to express this. If you develop some model for these, maybe there is use for L-entities for "W.E.B. DuBois Clubs of America", but if it's only to link to "W.E.B. DuBois" indirectly, I don't see an advantage. --- Jura 12:06, 3 March 2019 (UTC)

Yes, we could use applies to name (P5168), but I think it's conceptually wrong. I think this issue can be solved through a bot, without requiring to manually create a lot of lexemes--Malore (talk) 17:20, 4 March 2019 (UTC)

Harry Potter is a fictional human[edit]

Can anybody help me to revert this edit but I only want to revert what was removed, I don't want to touch anything else. Or should I just manually enter the information again? I want to be effective... cause what if this happens many times, I'll lose so much time on this and I want to save my time. Thank you. Btqfshfst (talk) 17:14, 27 February 2019 (UTC)

@Btqfshfst, Fuzheado: That Harry Potter is a fictional human is already implied by the statement instance of (P31): wizard in the Harry Potter universe (Q15298259) (as wizard in the Harry Potter universe (Q15298259) is a subclass of fictional human (Q15632617)). So there is no need to add additionally instance of (P31): fictional human (Q15632617). I suppose that this was the reason for the removal. If there is no reason to keep this statement nonetheless, I would remove it again. - Valentina.Anitnelav (talk) 19:58, 27 February 2019 (UTC)

Thanks, I don't feel strongly one way or another - just make sure we are consistent. -- Fuzheado (talk) 20:08, 27 February 2019 (UTC)

So are there no non-human wizards in the Harry Potter universe? (I don't know the books well enough to know the answer.) - Jmabel (talk) 02:58, 28 February 2019 (UTC)

@Jmabel: Correct, other species can't be wizards in the series. --Yair rand (talk) 03:09, 28 February 2019 (UTC)

Si if I understand correctly Yair rand (do you have a reference, I easily remember non-human doing magic but not that their called "wizard/witch"), then, we should revert this removal Special:Diff/867421525 and this adding Special:Diff/211825515 (both by Infovarius who strangely hasn't been pinged yet). Cheers, VIGNERON (talk) 08:21, 1 March 2019 (UTC)

So it looks like in the Harry Potter universe non-humans are not allowed to have wands but it looks like half-humans can be wizards? I don't know how people want to model this in relationship to fictional human (Q15632617) vs fictional character (Q95074) *shrug*[1] -- ElanHR (talk) 05:38, 3 March 2019 (UTC)

Hm, I forgot about the case of half-humans. Assuming we don't count half-human as a subclass of human, then each human-wizard item should also have instance of (P31) fictional human (Q15632617). If we do count them as humans, then the additional statement is unnecessary, and wizard in the Harry Potter universe (Q15298259) should have subclass of (P279) fictional human (Q15632617). --Yair rand (talk) 04:48, 4 March 2019 (UTC)

Thank you. I'm happy I was patient enough to wait and not take further erroneous actions Btqfshfst (talk) 20:31, 6 March 2019 (UTC)

P4224 and redundancy[edit]

Epìdosis
Jura
PKM
ValterVB
Jheald
Ghuron
Infovarius
Sannita
Avatar6
Pasleim
John Samuel
ElanHR
Tris T7 ^{TT me}

Notified participants of WikiProject Categories

99of9
Achim Raschka (talk)
Brya (talk)
Dan Koehl (talk)
Daniel Mietchen (talk)
Faendalimas
FelixReimann (talk)
Infovarius (talk)
Jean-Marc Vanel
Joel Sachs
Josve05a (talk)
Klortho (talk)
Lymantria (talk)
MargaretRDonald
Mellis (talk)
Michael Goodyear
MPF
Mr. Fulano (talk)
Nis Jørgensen
Peter Coxhead
PhiLiP
Andy Mabbett (talk)
Plantdrew
Prot D
pvmoutside
Rod Page
Strobilomyces (talk)
Tinm
Tom.Reding
Tommy Kronkvist (talk)
TomT0m
Tubezlob
RaboKarbakian
Circeus
Enwebb
Manojk
Tris T7 ^{TT me}
PEAK99
Notified participants of WikiProject Taxonomy

We have certain disagreement with @Brya: regarding possibility to add statements like Category:Boidae (Q7149834)category contains (P4224)  taxon (Q16521). As far as I understand, he believes it is redundant because Category:Boidae (Q7149834)category's main topic (P301)  Boidae (Q45556) + Boidae (Q45556)instance of (P31)  taxon (Q16521) and such statements clutter view for human being, who might decide to edit such items manually. I think that having P4224 statements on as many category items as possible reflects current community consensus and simplifies both writing SPARQL queries and manual editing. We don't have to rigorously follow database normalisation (Q339072) here, some verbosity is good. @Infovarius: believes that category contains (P4224)  taxon (Q16521) +parent taxon (P171) as qualifier are useful and supported by reasonator. Other members of Taxonomy project were not particularly interested in this discussion, so I am trying to get opinions of wider audience here. --Ghuron (talk) 08:49, 1 March 2019 (UTC)

I must admit that I did intentionally not participate in the discussion, but I have read it. As far as I am concerned, I agree with Brya that we should be reluctant in adding data that can be constructed from existing data-chains. So I have serious doubts as to if category contains (P4224) improves our structured data. I can understand the SPARQL-argument, but IMHO we don't build our database for SPARQL. Having said that, you can conclude that I am not really into the community consensus on category contains (P4224). Lymantria (talk) 11:34, 1 March 2019 (UTC)

@Lymantria: can you please elaborate more on what kind of doubts you have regarding P4224? --Ghuron (talk) 16:19, 1 March 2019 (UTC)

Well, let me try the obvious example: the claim of

< Category:Insects (Q5608148)   > category contains (P4224) < taxon (Q16521)   >

is about the elements of that catogory being taxa. But nl:Categorie:Insect for instance contains Sterile insect technique (Q1462045) and insect hotel (Q1664398), both not being taxa. Lymantria (talk) 17:06, 1 March 2019 (UTC)

@Lymantria: I do not see how does this relates to redundancy. You are right that Category:Insects (Q5608148) should not have P4224 statement (thus I reverted my edit). I certainly can verify if there are any non-taxon items, that belongs to the category, and, if so, do not add P4224 --Ghuron (talk) 13:38, 4 March 2019 (UTC)

As per Lymantria, a big issue is how categories are used on different language Wikipedias. Even for plants on the English Wikipedia, where we try hard to separate "taxonomic" categories from more general ones, it's not possible to persuade all editors that this is correct, and there are many "mixed" categories like the nl one above. Only yesterday I altered en:Category:Fagopyrum and en:Category:Buckwheat so that they were distinct, but this may not have consensus, and will probably get changed back. So I do rather support Brya's point. Peter coxhead (talk) 20:55, 1 March 2019 (UTC)

@Peter coxhead: I agree that different wikis has somewhat different ideas about criteria for inclusion articles in the categories mentioned above (and many others). But the issue for >4M items will not disappear once we declare it. We might want to capture and express this criteria in wikidata and allows local wikis to display it. P301 is certainly step in the right direction and Template:Cat main (Q6383110) can use it. I've also seen some categories in uk-wiki (couldn't find it now), that were using P971 statements to describe criteria, but I strongly believe that P4224 is more appropriate way to express it. For instance, when I (incorrectly) add Category:Insects (Q5608148)category contains (P4224)  taxon (Q16521) and if en:Category:Insects would be displaying header like The main article for this category is Insect. The category should contains instances of taxon, exceptions are possible as rare values may exist, people would notice this and revert my edit. Alternatively, if they see that majority of categories are dedicated to taxons, they will extract other categories to separate element. --Ghuron (talk) 13:38, 4 March 2019 (UTC)

I sympathize with @Brya:'s desire to simplify things and not needlessly duplicate information however category contains (P4224) and category's main topic (P301) serve different semantic purposes and should not be considered redundant. category contains (P4224) typically defines a Wikimedia set category (Q59542487) whereas category's main topic (P301) is typically used to provide context and applies to all category types even those serving administrative functions (e.g. Category:Wikipedia administration (Q2944611)). Additionally even in cases where category's main topic (P301) can be used to infer a set category (as it appears to be in the case for taxon (Q16521)) the conversion to category contains (P4224) statement is often context dependent and requires information not captured in category's main topic (P301). For example:

• Category:Marie Curie (Q6898030)category's main topic (P301)  Marie Curie (Q7186) however this does not imply Category:Marie Curie (Q6898030)category contains (P4224)  human (Q5) as would be implied if we use the same rule as in the taxon (Q16521) example.
• Category:Astronauts (Q6990046)category's main topic (P301)  astronaut (Q11631) however this statement does not imply Category:Astronauts (Q6990046)category contains (P4224)  profession (Q28640) but rather Category:Astronauts (Q6990046)category contains (P4224)  human (Q5) / occupation (P106)astronaut (Q11631).
• Category:Germans (Q3919754)category's main topic (P301)  Germans (Q42884) becomes Category:Germans (Q3919754)category contains (P4224)  human (Q5) / country of citizenship (P27)Germany (Q183). (Edit: fixed a typo saying the country was Germans (Q42884) rather than Germany (Q183))

While the approach using category's main topic (P301) may work with the current structure of taxonomic categories, it does not scale well to other domains. category contains (P4224) provides a way to specify the necessary information needed to define most category memberships while not requiring an editor to know SPARQL. -- ElanHR (talk) 00:07, 3 March 2019 (UTC)

As arguments go, this is not very convincing:

• Category:Astronauts (Q6990046)category's main topic (P301)  astronaut (Q11631) does imply "category contains instances of human with profession astronaut", since "profession" is a property limited to cases of "human". A matter of writing one's software properly.
• Category:Germans (Q3919754)category contains (P4224)  human (Q5) / country of citizenship (P27)Germans (Q42884) is even worse as an example because it differs from the item in accepting only one kind of Germans, while the item accepts two kinds of Germans. Category:Germans (Q3919754)category's main topic (P301)  Germans (Q42884), if queried properly, would be more accurate.

Brya (talk) 15:14, 3 March 2019 (UTC)

@Brya: Wikidata UI displays a single item "as is" and does not have to do it differently depending on whenever it is human, taxon or wikimedia category. Major wikidata consumers such as infobox modules, google knowledge strip (graph), siri/alexa/cortana, etc do some preprocessing such as filtering/joining/aggregation/etc. They also do not want to have different processing for items depending on their P31. They value uniformity over redundancy and it is not a "matter of writing one's software properly". It is cost of access to data, and if its too high, the data will not be used. --Ghuron (talk) 13:38, 4 March 2019 (UTC)

In my experience there are different kinds of infoboxes for different topics. In that case it is no hardship to make sure that the infoboxes read the information correctly. Commercial sources such as siri/alexa/cortana can afford to write their software properly, although they would prefer to slide by without making an effort. - Brya (talk) 17:46, 4 March 2019 (UTC)

@Brya: Whoops - definitely had a typo in my 3rd example (meant Germany (Q183) instead of a Germans (Q42884)) thank you for pointing that out - I've fixed in the original.

I totally agree that in some cases 'main topic' can be used (with appropriate domain knowledge) to infer the set definition reasonably well. That said I still believe category contains (P4224) provides a much more natural and scalable way of doing so. Perhaps an argument that would sit with you better would be cases where constructing an appropriately descriptive 'main topic item' would itself be unnatural. For example:

• Category:Hindu poets (Q8514421) (could be easily modeled as Category:Hindu poets (Q8514421)category contains (P4224)  human (Q5) / religion (P140)Hinduism (Q9089) + Category:Hindu poets (Q8514421)category contains (P4224)  human (Q5) / occupation (P106)poet (Q49757) )
• Category:1963 disestablishments in Kenya (Q24990592)
• Category:1810 songs (Q7937783)

Note: As part of my Wikipedia:Conflict of interest (Q4663309) I will mention that I have a relationship with Google (Q95). That said, data normalization helps everyone! As you pointed out, larger institutions have the resources to deal with these issue but properly structuring data allows hobby developers like @Ghuron: (and myself) to create consistency checks as well as import information that has been already human-curated in the form of structured categories. Cheers, ElanHR (talk) 05:21, 5 March 2019 (UTC)

If nothing else, your third example shows that adding an extra, redundant shell brings extra risks of introducing error.

        Your "Category:Hindu poets (Q8514421) (could be easily modeled as Category:Hindu poets (Q8514421)category contains (P4224)  human (Q5) / religion (P140)Hinduism (Q9089))" is a case where there isn't a "category's main topic" so seems to be out of scope for this discussion.

        As with everything, data normalization can be overdone. It depends entirely on one's perspective if a further degree of normalization is helpful; in practice data normalization often enough loses information and introduces error. - Brya (talk) 12:14, 5 March 2019 (UTC)

Mass revert?[edit]

My bot made some unfortunate edits (unexpected statements removed, code is now fixed so it won't happen again). Can someone easily revert ~2800 revisions with these revision IDs please? They should all be the latest edit on the respective item, at this moment. Is there a tool for that? --Magnus Manske (talk) 14:59, 1 March 2019 (UTC)

@Magnus Manske: I am not aware of a tool for that, but have you considered enabling your bot for EditGroups? This way it will not be a problem if (when?) that happens again. − Pintoch (talk) 16:29, 1 March 2019 (UTC)

Doing, but it will take an hour or so… —MisterSynergy (talk) 19:51, 1 March 2019 (UTC)

Now done. —MisterSynergy (talk) 21:19, 1 March 2019 (UTC)

Thanks! --Magnus Manske (talk) 08:32, 5 March 2019 (UTC)

how to add more languages in a page[edit]

[2] sagt "choose your language in the menu that appears at the top of the screen, and then happy editing !". bei mir erscheint aber kein "menu at the top of the screen". (um ping wird gebeten) W!B: (talk) 18:12, 1 March 2019 (UTC)

PS: übrigens schaff ich es auch nicht, ein zweites alias einzugeben. beim erstellen steht "Aliasse, mit „|“ getrennt", aber wir geht das beim datenobjekt? (Q1776351) W!B: (talk) 20:01, 1 March 2019 (UTC)

Ich nehme an, es geht um das Änderung von Bezeichnungen, Beschreibungen, und Aliasse (hier zusammengefasst als "Begriffe"). Es gibt da im Grunde zwei Möglichkeiten:

1. Du hast Javascript aktiviert, und wartest bis die Objekt-Seite vollständig geladen ist. Dann kannst Du mit dem "bearbeiten"-Link direkt über der Box mit den Begriffen den Bearbeitungsmodus direkt auf der Objektseite aktivieren. Dabei kannst Du alle Sprachen bearbeiten, für die bereits eines der Felder ausgefüllt ist (ggf. "In weiteren Sprachen" klicken), oder die Du standardmäßig angezeigt bekommst (siehe hierzu auch weiter unten in diesem Kommentar). Bei dieser Methode brauchst Du keine "|"-Separatoren für Aliasse, da immer hinreichend viele Felder angezeigt werden.
2. Ohne Javascript wirst Du zum Bearbeiten auf die Seite Special:SetLabelDescriptionAliases/Q1776351 geleitet, um Begriffe zu bearbeiten. Da steht auf der Seite dabei, in welcher Sprache Du bearbeitest, und das ist meines Wissens dieselbe Sprache, die Du für die Benutzeroberfläche ausgewählt hast. Typischerweise wird das mit dem "Universial Language Selector" ausgewählt, der im Vector-Skin rechts oben neben dem Link zu Deiner Benutzerseite zu finden ist. Das dürfte das "menu at the top of the screen" sein. Alternativ kannst Du mit bspw. Special:SetLabelDescriptionAliases/Q1776351/fr zum Beispiel die französischen Begriffe mit deutscher Benutzeroberfläche verändern, oder neu setzen falls sie noch überhaupt nicht existieren. Bei dieser Methode gibt es nur ein Feld für Aliasse, die entsprechend mit dem Separator "|" getrennt werden müssen – siehe auch Special:SetLabelDescriptionAliases/Q1776351/de im aktuellen Zustand.

Letztlich noch ein Kommentar zu den standardmäßig für Dich angezeigten Sprachen: das wird aus irgendeinem Grund so ausgewählt, wie Du babel-Boxen auf Deiner Benutzerseite hast. Ich nehme also an, dass Du zurzeit deutsche und englische Begriffe angezeigt bekommst, und alles andere versteckt wird. Korrekt? Viele Grüße, —MisterSynergy (talk) 20:24, 1 March 2019 (UTC)

danke dir, das hilt. ja. mit Special:SetLabelDescriptionAliases/Q1776351/la (das wollte ich) hats geklappt. ich hab Javascript natürlich an. und ja ich kann alle sprachen bearbeiten, für die bereits eines der felder ausgefüllt ist. nur, wie leg ich eine neue sprache an? oder geht das sowieso nur mit Special:SetLabelDescriptionAliases? und wenn dem so ist, wärs doch nett, den link dort zu deponieren. jedesmal Javascript ein/aus, sprache umstellen oder den link händisch eintippen ist ja auch nicht lustig.

(PS: bei "alias hinzufügen" hab ich mich übrigens nur patschert angestellt. W!B: (talk) 20:57, 1 March 2019 (UTC)

Es gibt unter Special:Preferences#mw-prefsection-gadgets ein Gadget "labelLister". Wenn Du das aktivierst, bekommst Du zwischen den Tabs "Lesen" und "Versionsgeschichte" (im Vector-Skin) einen weiteren Tab mit einem separaten Begriffe-Tool. Das braucht auch Javascript, aber da kannst Du dann auch einen Sprachcode ohne bereits definierte Begriffe angeben und dann entsprechend etwas ergänzen. Etwas anderes fällt mir gerade nicht ein… —MisterSynergy (talk) 21:09, 1 March 2019 (UTC)

tut mir leid, aber das zeigt auch nur die schon eingegebenen sprachen (und das "NEW ! : Change several language in one fell swoop (go to beta version)." schickt mich nur wieder zum eingabefeld)

ich würde dich jedenfalls herzlichst bitten, das irgendwo auf der passenden hilfeseite zu vermerken (ich kann ja nicht der erste sein, der damit kämpft), und einen bugreport zu machen: es würde auch reichen, wenn ich irgendwie standardmässig "alle sprachen" bekomme: ich kann ja auch den italienischen namen einzugeben fähig sein, ohne italienisch zu können (googlen reicht). da hält uns wer für zu dumm ;) W!B: (talk) 23:22, 1 March 2019 (UTC)

Hier klappt das mit der älteren Version von labelLister durchaus. Wenn ich auf den Tab klicke kommt ein Dialog eingeblendet, dort auf "edit" bzw. "Bearbeiten" klicken. Dann ist da ein Eingabefeld, wo ich einen Sprachcode eingeben kann (zum Beispiel "hu" für Ungarisch), auch solche die noch keine Begriffe haben. Klappt das auch nicht?
Mir ist leider keine vollständige Liste der Sprachcodes bekannt, allerdings sollte Help:Wikimedia language codes/lists/all für die allermeisten Anwendungsfälle reichen. —MisterSynergy (talk) 07:14, 2 March 2019 (UTC)

MisterSynergy: ah, jetzt geht der labelLister: steht als "Liste der Bezeichnungen" ganz oben zwischen "Lesen" und "Versionsgeschichte". ich hab wohl nicht genug neu geladen nach dem freischalten, sollte ich eigentlich wissen ;). danke dir für mühe. W!B: (talk) 12:08, 5 March 2019 (UTC)

Candidate for elected office[edit]

Is there a standard way we show someone was a candidate for an elected office without creating, say, 50 "candidate for Governor of state X" entries? If we created the categories would it also list the winner of the election or just the losers? --RAN (talk) 20:54, 1 March 2019 (UTC)

The usual way seems to be to create one item per election (often created anyway for Wikipedia), then each person can be listed with candidate (P726). E.g., South Korean presidential election, 2012 (Q82241) Ghouston (talk) 04:15, 2 March 2019 (UTC)

There's also the inverse approach, using candidacy in election (P3602) on the person, pointing at the election item. --Oravrattas (talk) 08:26, 2 March 2019 (UTC)

• Just what I was looking for ... thanks! --RAN (talk) 21:51, 5 March 2019 (UTC)

Reducing people to an identifier with an ORCID identifier[edit]

Hoi, I strongly object to the practice where researchers are reduced in their descriptions to a researcher with an ORCID identifier. I fully understand the reason why but it is an awful practice. It is bad enough to only say "researcher" when it is a psychologist, a microbiologist or whatever.

The objective is disambiguation. As automated descriptions are superior anyway, it follows that disambiguation is done best by adding statements that distinguish one person/item from another. Thanks, GerardM (talk) 07:44, 2 March 2019 (UTC)

Wikidata is a WIP project, isn't it. I believe these items are going to be better and better. I am currently working on items of young Polish scientists who quite often are only an item with ORCID ID. There probably should be a list of these items (or a Wikidata project) to work on. Kpjas (talk) 08:03, 2 March 2019 (UTC)

195k items with an ORCID iD (P496) statement have three or even fewer statements (which are 42% of all items with an ORCID iD (P496)). There is quite a lot to do, I guess. —MisterSynergy (talk) 08:14, 2 March 2019 (UTC)

@MisterSynergy: The task looks overwhelming but... please compare [3] and Mateusz Adamiak (Q61101679). I am busy on items like this. Kpjas (talk) 08:48, 2 March 2019 (UTC)

I am working hard to bring authors and papers together like I just did for Mateusz Adamiak. I follow this up with work on co-authors that are evident in the Scholia for an author.

This is however beside the point. The point is that descriptions identifying people with a number is not acceptable. Thanks, GerardM (talk) 10:07, 2 March 2019 (UTC)

I don't think these items are of much use. For most cases, the easiest is probably to just ignore them. The query suggested by MisterSynergy can be used to filter them. --- Jura 12:20, 3 March 2019 (UTC)

Many of these items have dozens, some even hundreds of links to scholarly papers. So there is a use for them it will evolve over time. There has been for a month or so adding employment info for scholars. Thanks, GerardM (talk) 13:59, 4 March 2019 (UTC)

I've adjusted dozens of these descriptions to be more natural; however I don't see any problem with them as interim descriptions for people. ArthurPSmith (talk) 14:33, 4 March 2019 (UTC)

So you are perfectly happy for me to ask what people find about this outside of Wikidata? Really? Thanks, GerardM (talk) 14:35, 4 March 2019 (UTC)

A survey would be a great idea, if that's what you're suggesting? ArthurPSmith (talk) 19:39, 4 March 2019 (UTC)

As an "outside" user of Wikidata information, I prefer the description to be a plain, natural-language phrase that can be shown to an end user without provoking bafflement and confusion. Hence, while I sympathize with the problems this is trying to solve, I don't think we should be subverting the description to include identifiers in this way. Cheers, Bovlb (talk) 05:39, 5 March 2019 (UTC)

@Bovlb: Hmm, I'm not sure what you mean by "subverting the description". These are newly created items, so there was no description for them before. What would you suggest as "the description" that should be used to help disambiguate them? ArthurPSmith (talk) 19:08, 5 March 2019 (UTC)

@ArthurPSmith: I used the word "subvert", not because some prior value is being displaced, but because it seems to change the purpose of the description in a way which interferes with the established use case I described above. As to what I would suggest, I have looked at several cases and I agree that coming up with a good description is not easy, especially when all we have is an ORC_ID. The uniqueness constraint ("no two items can have both the same label and the same description") is going to make it harder and harder to generate useful descriptions automatically as Wikidata grows. The current work to import publications is putting pressure on person entities in this regard. We also see it when trying to add descriptions to geo-locations. Cheers Bovlb (talk) 19:27, 5 March 2019 (UTC)

The purpose of the description is to disambiguate the item label; that much is clear from sentence 1 of help:description, so it is a stretch to describe such disambigation as subvertion. The purpose of the description is not to describe the subject of the item; that's what item property statements are for. Expecting or relying on the description to decribe the item subject is a category error, easily made but nontheless wrong. --Tagishsimon (talk) 23:43, 5 March 2019 (UTC)

Way to model a gift (Q707482)[edit]

In this example: Domestic Scene (Q18510574), the subject of the item has been given to the museum that still owns it. This is currently modelled with significant event (P793) and the givers are qualified with participant (P710). I would like to explicitly mention the receiver(s) for such statements. How should this be done? Are there gift examples anywhere? Thanks in advance. Jane023 (talk) 11:05, 2 March 2019 (UTC)

We have donated by (P1028), currently 3370 times as a main statement and 2963 as a qualifier. Does this fit the need? Jheald (talk) 15:51, 2 March 2019 (UTC)

Interesting thanks! I didn't know about that, but it works for the giver. I am still looking for the receiver. See e.g. Dutch Gift (Q1165096). Jane023 (talk) 09:28, 4 March 2019 (UTC)

Reception will often be implicit in the start date of a collection (P195) statement, which would implicitly identify the receiver. But I can see things may get more challenging if there is a lengthy chain on provenance that we are seeking to record, more than just the final gift to the current collection. Although, on the other hand, an item can have many collection (P195) or owned by (P127) statements, each with a start date and end date. Jheald (talk) 10:58, 4 March 2019 (UTC)

Well I was thinking more generically, not just for collections, but to pinpoint a gift in time and place with giver(s) and receiver(s). Donated by works, but received by is needed. Jane023 (talk) 17:34, 5 March 2019 (UTC)

Different names in different roles[edit]

Nancy Bradfield (Q59529891) used her maiden name "Nancy Bradfield" in her work on dress history and her married name "Nancy Sayer" in her work as an illustrator. Is there an elegant way to record these facts in WD? - PKM (talk) 20:40, 2 March 2019 (UTC)

Presumably name (P2561) is the main property we're looking for here. Perhaps field of work (P101) for an appropriate distinguishing qualifier? Jheald (talk) 21:20, 2 March 2019 (UTC)

Interesting! It seems maiden name is typically represented with birth name (P1477) but pseudonym (P742) is usually used for a names used in a specific context (e.g. Hermann Hesse (Q25973) Mark Twain (Q7245)). Maybe use both and mark with field of work (P101) as @Jheald: suggests for pseudonym (P742)? That way it would be accessible to queries for people interested in either. -- ElanHR (talk) 20:12, 3 March 2019 (UTC)

It's not really a pseudonym if it was her actual birth name / married name. So that's why name (P2561) seems to me more appropriate than pseudonym (P742). It would also be appropriate to have statements for birth name (P1477) and married name (P2562), but I would suggest also have the two P2561 statements. Jheald (talk) 01:18, 4 March 2019 (UTC)

What seems right to me is new property “Professional name” = version of name used in a business or academic context, which will often be the version of the name used as the label (example J.R.R. Tolkien). - PKM (talk) 05:21, 4 March 2019 (UTC)

I would support that. Jheald (talk) 10:52, 4 March 2019 (UTC)

P53 (family)[edit]

Property:P53 is set to contain only a single value, but isn't every noble woman that marries into a noble family a member of two noble families? She would be a member of her parental family and after marriage a member of her husband's noble family. How should this be handled? Looking at various examples they tend to be a mix of the parental family and the family they marry into. Is it meant to only be genetic (parental family)? --RAN (talk) 05:16, 4 March 2019 (UTC)

Like Isabella Teotochi Albrizzi (Q5454), for example. That one could be fixed by marking start/end time qualifiers as separators in the constraint. But the setup on that item assumes that somebody ceases to be a member of a family when they marry into another family, which seems doubtful. Ghouston (talk) 05:59, 4 March 2019 (UTC)

No, it doesn't make that claim, only the first married family has an end time. I added start/end time as permitted qualifiers on family (P53), and as separators on the single-value constraint, that should be enough to handle it? Ghouston (talk) 06:35, 4 March 2019 (UTC)

Should we remove the restraint that it contain a single value? Half the entries will give an error if we assume half of the noble family entries are female. --RAN (talk) 06:49, 4 March 2019 (UTC)

Just give a start date for the second family and the constraint should be satisfied, even if it's <unknown value>. Ghouston (talk) 07:09, 4 March 2019 (UTC)

@Ghouston: How do I add in a null value, does it have a Q code? --RAN (talk) 18:04, 5 March 2019 (UTC)

See Help:Statements#Unknown or no values. Matěj Suchánek (talk) 19:10, 5 March 2019 (UTC)

• Isabella Teotochi Albrizzi (Q5454) has a tricky name: her surname is being written "Teotochi Albrizzi", which is her birth name Teotochi, which is Greek and normally written in English as Theotokis, but in this case with the Italian spelling, along with the surname of her 2nd Italian husband Albrizzi. I'm not sure how to set this up in Wikidata such that it will sort properly in Commons. Ghouston (talk) 07:15, 4 March 2019 (UTC)

I suppose you create a special family name item just for her. Ghouston (talk) 07:28, 4 March 2019 (UTC)

Linking to commons[edit]

Hi. I often try to link Commons cats to wikidata items but when I try do the add wikidata can't find the category, even though the category has existed for some time. For example, I am trying to link Matthew Quashie Q16150053 to commons but get this error A page "Matthew Quashie" could not be found on "commonswiki". Any idea why this happens? Gbawden (talk) 08:52, 4 March 2019 (UTC)

@Gbawden: Because c:Matthew Quashie does not exist but c:Category:Matthew Quashie does. The best thing to do is to add the property for Commons category and create a gallery page on Commons to link here. —Justin (koavf)❤T☮C☺M☯ 09:14, 4 March 2019 (UTC)

I'm pretty sure that creating galleries on Commons just to link with Wikidata is a bad idea. Ghouston (talk) 09:17, 4 March 2019 (UTC)

? —Justin (koavf)❤T☮C☺M☯ 09:18, 4 March 2019 (UTC)

Koavf Ok thanks that makes sense. Ghouston that wasn't my intention - I misunderstood what that linking was meant for Gbawden (talk) 09:21, 4 March 2019 (UTC)

Speaking as a Commons admin: please don't create a gallery as a redirect just for Wikidata's convenience. You can (and should) sitelink the Commons Category page directly. - Jmabel (talk) 17:13, 4 March 2019 (UTC)

If I add an image to a wikidata item the file name resolves quickly. However if I add a commons category the category name doesn't resolve, although if I hit publish it accepts and saves. Is this normal? Thanks Gbawden (talk) 09:32, 4 March 2019 (UTC)

@Gbawden: It should do that if you add it as a sitelink ('Other sites' -> 'commons' -> add 'Category:X', and you'll get a pop-down list of matches), but it won't if you add it as Commons category (P373). Despite what @Koavf: said above, the best thing to do now is to add it as a sitelink, not as P373 unless the sitelink is already used by a gallery. That way the information from Wikidata can be used on Commons through the infobox there. Please don't create a new gallery unless it's actually needed and going to be maintained. Thanks. Mike Peel (talk) 10:28, 4 March 2019 (UTC)

Protect Q60458248[edit]

Hello,

This item should be protected as it is the victim of troll attacks. Cheers, FR (talk) 12:34, 4 March 2019 (UTC)

I protected it. ChristianKl ❪✉❫ 12:55, 4 March 2019 (UTC)

What's going on with National Library of Ireland authority ID (P1946)?[edit]

When this was originally proposed (and accepted with only two votes), there was no formatter URL. The one that has been added since is completely improper, as it has nothing to do with actual author records, but only book records. In fact, the numbers found in VIAF systematically correspond to individual works in that url, and not even works by those authors.

Example 1: In the original property proposal, Philip Henry Wicksteed (Q2306330) is given as having the id vtls000036581, this is the record for the Irish version of a Children's book about Ancient China (the author of which has become entangled on Wikidata with Lustmord (Q913245), I have fixed the VIAF link, but it will take some work to properly disentangle them).

Example 2: To Marianna O'Gallagher (Q3291272) was added the purported id vtls000086697. this correspond, again, not to O'Gallagher, but one of her books It is not, in fact a valid author record at all. The correct id as reported in VIAF is vtls000022718, and that corresponds to an edition of a play by Marina Carr (Q467609).

Example 3: Even the property example on the property page itself is incorrect, because the correct id in VIAF is vtls000044446.

I have deleted the formatter url from the property, as not only is it incredibly misleading, but the author records are not accessible online. I suspect many more authors that O'Gallagher are in the same situation of having a given record number that is incorrect. Circeus (talk) 15:43, 4 March 2019 (UTC)

Wikidata weekly summary #354[edit]

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

• Discussions
  • Open request for adminship: Esteban16
  • Closed request for comments: 2018 administrator policy update

• Events
  • Upcoming: WikiConNL in Utrecht (Netherlands), on March 8-9th (in Dutch and English)
  • Upcoming: Wikidata meetup in Berlin, on March 12th
  • Upcoming: Wikidata meetup in Paris, on March 15th
  • Upcoming: Wikidata & Wikipedia workshop in Aberdeen, Scotland, on March 19th
  • Upcoming: GLAM and Wikidata in National Library, Bern (Switzerland), on March 28th (in German and French).
  • Upcoming: Wikidata Workshop for GLAM in Lausanne (Switzerland), on March 29th (in French).

• Press, articles, blog posts
  • Matching BnF and Wikidata video games using Dataiku DSS (in English) by Envel Le Hir

• Other Noteworthy Stuff
  • Congratulations to Siobhan Leachman (d:User:Ambrosia10), awarded the "Companion of the Auckland War Memorial Museum" medal for her volunteer work, including contributions to Wikidata: [4].
  • You can now try Shape Expressions on a test system
  • Creative Commons has a proposal for tool development with Wikidata's copyright metadata for the 2019 edition of Google Summer of Code. Interested student developers are invited to apply.
  • Tpt's Wikidata history query service stores and allows querying metadata about Wikidata's edit history
  • A new beta version of the Daty Wikidata Editor has been released, check out the changelog. You can also show your endorsement to the project over here.
  • Scholarship application phase for Wikimania 2019 is now open until March 15th. The call for track leaders is also open.
  • OpenRefine 3.2 beta was released, with a collection of new features and bug fixes, many of which improve the Wikidata integration.

• Did you know?
  • Newest properties:
    • General datatypes: multi-channel network, Stack Exchange site, total shots in career, total points in career, total assists in career, penalty minutes in career, career plus-minus rating, preferred pronoun
    • External identifiers: BHL part ID, Gateway to Research Project ID, Yandex.Music genre ID, Yandex.Music label ID, Catálogo de Patrimonio Cultural de Castilla-La Mancha ID, Inventário dos Monumentos RJ ID, NZ On Screen person ID, NZ On Screen work ID, Pacific Coast Architecture Database firm ID, Physics History Network ID, Twitter user ID, identifier of games on Queerly Represent Me, Brazilian Electoral Unit ID, SICRIS researcher ID
  • New property proposals to review:
    • General datatypes: Location specifics, Mountain chain, temperature record, stroke order, Höchstes Break, Dutch Instrument Makers ID, Lucerna person ID, Endowment, Guggenheim fellows ID, Downloads page, is a synonym of taxon name
    • External identifiers: Académie de Rouen member ID, Sistem Registrasi Nasional Cagar Budaya ID, Musenor ID, ProQuest document ID, Florida Historical Marker List ID, Klexikon-Article-ID, Federal-State Cooperative System ID, identifikátor v Adresáři knihoven a informačních institucí v ČR, Cour des comptes report ID, Directorio Legislativo ID, Deportation Database transport-ID, Art Fund ID, Scripts.com script, National Book Foundation author ID, National Book Foundation book ID, DFD-ID, Mutual Art artist ID, a-tremasov.ru biography ID, Project Drawdown solution ID, Paintings by Salvador Dalí ID, HCA Red List of Endangered Crafts ID, flgr-results.ru athlete ID, Resident Advisor artist ID, Resident Advisor record label ID, ACA ID
  • Query examples:
    • Average distance between a French museum and its hosted artists' place of birth (source)
    • Persons with a surname that matches the past participle form of a Danish verb (source)
    • Town halls of communes bordering Paris (source)
    • Literary awards with 0–2 recipients (source)
    • Female Howard medical grads before 1900 (source)
    • items including the property "preferred pronoun" (source)
    • Map of tram service in Ulm (source)

• Development
  • Added monolingual language code tlb (Tobelo), thanks User:Mbch331! (T216798, will be deployed next week)
  • Integrating the termbox with Wikibase (phab:T214679)
  • Viewing historic revisions and fetching the termbox data from Special:EntityData (phab:T210615)
  • Fixing emoji breaking the termbox (phab:T217244)
  • Renamed special pages under Wikibase to avoid confusion with Schemas special pages (phab:T216719)
  • Removed unsupported php 7 constant in production, causing a notice and potential undefined behavior ([[phab:T217241
  • Investigated wb_term normalization solution (phab:T215902)
  • Fix for outdated cached WB datatypes on client-side (phab:T216728 (blocks enabling new datatypes, e.g. phab:T216730))
  • Allowing access to wikibase entities from multiple (wikibase) databases (phab:T214557)
  • Allowing to return a proper API error on 'wbformatvalue' action (phab:T207479)
  • Providing open-graph title and discretion meta-tags for lexemes (phab:T206414)
  • Allowing quickstatements to work out-of-the-box in wikibase-quickstatments docker image (phab:T205606)
  • Implementing “undo” for Schemass (phab:T214914, making it work via the API (phab:T217250)
  • Implementing “restore” for Schemas (phab:T214915)
  • Adding created and edited Schemas to the watchlist according to the user’s preferences (phab:T213725)
  • Splitting edit parts on Schemas (phab:T215395, phab:T215393, phab:T215392, phab:T215394)
  • Improving support for multilingual edit comments in MediaWiki (phab:T215637)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Suggested and open tasks!
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Lea Lacroix (WMDE) 16:19, 4 March 2019 (UTC)

Unclear semi-protection of all (?) items[edit]

FYI, reported on the Admin noticeboard, because the New York Times asked for a reliable and independent third party source. –84.46.53.245 17:54, 4 March 2019 (UTC)

• You never answered the question you were asked at Wikidata:Administrators'_noticeboard#Unclear_protections, so of course this hasn't moved forward. - Jmabel (talk) 21:46, 4 March 2019 (UTC)

"Field of work" and "Interested in"[edit]

General question: how do you distinguish field of work (P101) and interested in (P2650)? For organizations, writers, and historians, I've been using "interested in" (1) for very specific topics (field of work = history of costume; interested in = Ancient Greek clothing) and (2) for hobbies/interests outside of the subject's professional life. But the property proposal for "interested in" says it should be used only for the most general concepts ... which is how I use "field of work". How do you use these properties? - PKM (talk) 20:25, 4 March 2019 (UTC)

Your logic makes sense to me. interested in (P2650) seems woefully vague, arbitrary, and redundant. What's the basis for inclusion? if Angela Merkel (Q567) said in an interview she was interested in hiking or stamp collecting, should that sort of trivial detritus flood Wikidata? How about interested in Germany? Alternately, it stands to reason, and is likely verifiable that a lepidopterist would be interested in Lepidoptera, lepidopterology, entomology, biology, and maybe moths or Actias luna (Q135289), and also have the field of work (P101) lepidopterology, entomology, biology, taxonomy, etc. None of this matters, add whatever you want. -Animalparty (talk) 05:05, 9 March 2019 (UTC)

sugar substitute (Q626292) and sweetener (Q4368298)[edit]

I think that most of labels and interwikis of sugar substitute (Q626292) actually mean sweetener (Q4368298). We need to seperate them. --Sharouser (talk) 12:31, 5 March 2019 (UTC)

Editing is desperately slow today?[edit]

Is there a problem with editing today? (Or is it just my set up?)

Editing just now, I keep getting "technical error - timeout" edit messages the first time I try to make an edit. If I try to make the edit again, the second time it usually works; but this shouldn't be happening. Are other people getting this too, or is it just me? Jheald (talk) 14:38, 5 March 2019 (UTC)

Holocaust victim[edit]

I am trying to add the people from the German stumbling stone project to Wikidata, we have images of the markers but not entries for the people. Should "Holocaust victim" be an event as in Anne Frank (Q4583) where it gives a constraint error or should it be an "instance of" as in Käthe Salomon (Q58363991) with no constraint error? They seem to be a mix, mostly like Anne Frank, and probably added before the constraint error messages were developed. --RAN (talk) 17:58, 5 March 2019 (UTC)

while "instance of" sounds like it makes sense, I don't think we put people in classes like that anywhere else. ArthurPSmith (talk) 18:24, 5 March 2019 (UTC)

Personally, I think neither "statelessness" or "holocaust victim" ought to be listed as "significant events" to Anne Frank. For one, it should really be loss of citizenship (Q17144585), not "statelessness". "Significant event", as I understand it, is meant to cover events not otherwise included in other property. Her being a holocaust victim is not a significant event (strictly speaking, it's not even her claim to fame!), it's in my opinion better treated as part of her manner of death (P1196), and that has a separate property. Circeus (talk) 18:33, 5 March 2019 (UTC)

• Anyone else have an opinion "manner of death" or "instance of"? If we decide on one, we should migrate all of them. --RAN (talk) 23:49, 5 March 2019 (UTC)
  • My understanding has always been that humans should only ever have instance of (P31):human (Q5), and anything else should be expressed in a different way. (I have no real opinion on what that way should be here). --Oravrattas (talk) 00:25, 6 March 2019 (UTC)
•  Oppose this kind of usage of instance of (P31). ChristianKl ❪✉❫ 09:47, 6 March 2019 (UTC)
• Hm, how is this kind of thing handled more broadly? cause of death (P509) only deals with immediate cause and manner of death (P1196) (though it allows has immediate cause (P1478) and has contributing factor (P1479) as qualifiers) only deals with very general circumstances. How would we say someone died in any genocide, or war, or natural disaster, or epidemic? --Yair rand (talk) 23:16, 6 March 2019 (UTC)

Weird, I have no idea who thought it was OK to say someone was "instance of" their manner of death. This is definitely wrong. The usage of significant event on a person however is fine, but the object of the statement can be either a slow period or sudden event - both are acceptable. I use "nazi looting" for artworks confiscated as part of a policy wiith uncertain date, while "destruction" is often due to fire in a house or museum that has a specific date and place. So the object of the significant event statement in this case should be something general, like "holocaust" and then qith qualifiers "interment", "disease" or "murder", depending on the outcome. For people moved from one camp to another they can have more than one significant event I suppose. Jane023 (talk) 12:11, 10 March 2019 (UTC)

Please disjoin en:Margin of error and ru:Предел погрешности[edit]

Let's look at en:Margin of error. It's counted in percents.

Let's look at ru:Предел погрешности. Different names are mentioned, but the title is "предел погрешности". Then see the row "20 см — предел погрешности". It's counted in centimeters, not percents.

The terms are not equal (measured in different units). Please disconnect. 62.220.40.76 22:55, 5 March 2019 (UTC)

Duplicate surname Liu[edit]

There are two items for the surname Liu at Liu (Q804970) and Liu (Q39000092), one supposedly in Chinese and the other in Latin script. They both have quite a few items using them as family name (P734). Q804970 seems to be a bit more popular and has sitelinks to Wikipedias, while Q39000092 is linked to a Commons category. But what are the criteria by which one item or the other is used for a particular person? If I see a pattern, it's that many of the items using Q39000092 are researchers. Ghouston (talk) 10:27, 6 March 2019 (UTC)

@Harmonia Amanda: regarding surnames and @Sic19: regarding researchers. Mahir256 (talk) 17:23, 6 March 2019 (UTC)

I chose to use latin transliterations for Chinese surnames, if there is an existing item, because I often see multiple items for surnames which appear to be family name varients in the original language and I do not know which would be appropriate. For example, here are some of the items for the family name Li: Li (Q686223), Li (Q770891), Li (Q13588410), Li (Q15283218), Li (Q3447118), Li (Q10910874), Li (Q11983876), Li (Q17008106). The reason the Liu (Q39000092) is used on researchers is only because I am trying to improve the sparce items that have been created from ORCIDs. Simon Cobb (User:Sic19 ; talk page) 18:08, 6 March 2019 (UTC)

So if you are taking data from a source in Latin script, you'd use a matching name with Latin script, but taking data from a Chinese source you'd use a name with Chinese characters. This does result in splitting people somewhat arbitrarily between different items depending on where their data was found. But then which item should be used when you have both a Chinese and Latin version of the name, e.g., if they have articles on two Wikipedias, or if there are web pages with different scripts? Ghouston (talk) 22:47, 6 March 2019 (UTC)

The Latin-script name should be used for people with a Latin-script native language. There are quite a few American, French, German, etc. of Chinese descent who genuinely have "Liu" now as a family name (thinking of Alysa Liu (Q55356854) for example). Chinese researchers should definitely not have a Latin-script names, because it's not their names. If we don't know their family names, we don't add it. We certainly don't add one we know to be false! --Harmonia Amanda (talk) 10:50, 7 March 2019 (UTC) Edit: to be more clear Liu (Q39000092) is not an item about "Liu and other family names transliterated as 'Liu'", it's an item for "Liu, the Latin-script name". It should not be used for people whose names we know are transliterated as 'Liu' but is not 'Liu'. Liu (Q804970) is about the family name 刘, which is transliterated as 'Liu' (among other transliterations). --Harmonia Amanda (talk) 11:02, 7 March 2019 (UTC)

So what should we do when someone with a non-Latin script name has used a transliteration of their name and this is the data we are working with? And how are we suppose to establish whether someone is using a transliteration or whether or not the name we are working with is their genuine or native language name? All of the data I have used to add surnames is in Latin script and a lot of the data is created by the persons represented by the items I am editing thus I used the Latin script items Liu (Q39000092). For example, Yongsheng Liu (Q42834021) has ORCID iD (P496) linking to a profile for Yongsheng Liu, who is based in China and the source of the data in this ORCID. Even when the language setting in ORCID is changed the name remains Yongsheng Liu. If Chinese researchers definately should not have Latin-script names please can you tell me what Yongsheng's family name is? Also, I notice that Liu (Q39000092) has said to be the same as (P460) statements linking to Liu (Q804970) and Liu (Q13391498) - is this correct or not? Simon Cobb (User:Sic19 ; talk page) 17:59, 7 March 2019 (UTC)

There are also bilingual people who will use both a Latin and non-Latin version of their name, depending on which language they are using at the time. Besides that, we don't always know what a person's native language is. Ghouston (talk) 00:14, 8 March 2019 (UTC)

Would we potentially need multiple family name (P734) statements for the surnames a person uses in different languages? The constraints on family name (P734) don't currently include a language qualifier, and it may make it hard for users of the data (templates etc.) Ghouston (talk) 00:24, 8 March 2019 (UTC)

┌────────────────────────────────────────────────────────────────────────────────────────────────────┘ My two cents:

• If the database doesn't include information about the family name in the native language, I think we should keep the Latin transliteration because there can be several different family names that have the same transliterations. As a native speaker, I'm able to find out that Yongsheng Liu (Q42834021)'s family name is indeed Liu (Q804970) instead of Liu (Q13391498), but we cannot make this assumption by default. If we do find the family name in the native language, we can then switch it from the Latin version to the non-Latin version.
• For the cases like Alysa Liu (Q55356854), the situation is more complicated. Although she was born and grew up in US and should have the Latin version Liu (Q39000092) as her family name, one can definitely argue that Liu (Q804970) is also her family name since it is her father's family name. We may then ask is Liu (Q39000092) also her father's family name? (it's just an example, her father doesn't have an item yet) Although her father was born and grew up in China, he has been lived in US for 30 years and use his western name Arthur Liu in his daily life. I'm not sure what's the best way to deal with these cases.
• There are also different transliteration systems, for example Liu (Q804970) can be transliterated as Liu, Lau, Lieu, etc. Andy Lau (Q16766)'s family name is Liu (Q804970), but should we also add Lau (Q16871901)? How about Ted Lieu (Q7693450), whose Chinese family name is also Liu (Q804970)?
• As a side note, I notice that different Chinese family names that have the same transliteration are linked by said to be the same as (P460) or different from (P1889) or both. It doesn't make sense to me that said to be the same as (P460) is used here since they are totally different names that just happen to have the same transliteration. (Actually if we keep the tone marks in the transliterations, they might be different, for example Liu (Q804970) is Liú and Liu (Q13391498) is Liǔ.) I cannot see how the description of said to be the same as (P460) (this item is said to be the same as that item, but the statement is disputed) can be applied here. Using said to be the same as (P460) for linking the non-Latin version and the Latin version could be okay but I'm not sure.--Stevenliuyi (talk) 04:12, 9 March 2019 (UTC)

I seems to me that people who have a non-Latin script name, and also either publish in English (or other Latin script language) or live in a Latin-script country, basically have two names. In the case of living in another country, you'd probably have to supply some kind of translation for certain identity documents so you'd have an official transliteration. When publishing, I'd guess most people would tend to use the same transliteration consistently instead of choosing a different one for each publication. Ghouston (talk) 10:23, 9 March 2019 (UTC)

• You can add several values in P734. Ideally, I'd start with one matching the native language label, but others are possible. --- Jura 10:16, 10 March 2019 (UTC)

• Is Hadji (Q56244870) a Latin script or Arabic script name? An Moroccan footballer and a French television presenter are linked to it. Who knows. Ghouston (talk) 10:57, 10 March 2019 (UTC)

• Not all surname items are currently as developed as they should be. Please add "native label" and "script" properties to the item once determined.--- Jura 11:00, 10 March 2019 (UTC)

Edit action feed (Android app)[edit]

Background: Our readers mainly read the wikis on mobile phones; our editing tools are focused on desktop and keyboards. This will be a problem for us: Wikipedia and thus the Wikimedia wikis became a big thing because everyone who read it could add information. If this is not true in the future, we’ll have a harder time getting new editors. The developers are working on a number of different solutions, including, of course, trying to make the kind of typical content creation that we’ve always done easier on mobile. However, we’re also looking into if there are specific tasks that could be specifically well suited for mobile users. And Wikidata is of course not only one of these things, but also important for the future in general.

Users in the Android Wikipedia app will be invited to an edit action feed, where they’ll be fed Wikipedia articles in their chosen language and be asked to add Wikidata descriptions, where these are lacking, or translating existing descriptions. This will only be shown to editors who have made at least five unreverted Wikidata description edits in the app; the translations require fifty unreverted edits. If an edit gets reverted, the the count starts at zero again. This is an anti-vandalism measure: we don’t want to invite people to specifically do this unless they’ve shown basic competency at this kind of editing. You shouldn’t need to worry about an uncontrollable influx of edits since this only affects a subset of the Wikipedia Android app users, but we’ll be monitoring the stats to make sure everything’s going well. All Android app edits can be found with the Android app edit tag.

If you’ve got any comments or questions, the best place to leave or ask them is probably talk page on mediawiki.org. We aim to launch this towards the end of March. /Johan (WMF) (talk) 10:40, 6 March 2019 (UTC)

• @Johan (WMF): This sounds like a good idea. Moving forward I think it would be great to trigger edit actions when a user moves to a location who's GPS signal is linked to a Wikidata item. ChristianKl ❪✉❫ 16:07, 6 March 2019 (UTC)

Suggestion noted. (: /Johan (WMF) (talk) 17:58, 6 March 2019 (UTC)

Linking a person to the index of their personal archive[edit]

How should I best model the relationships described on this page? https://www.prm.ox.ac.uk/manuscripts

I can represent that fact that a person has archives in this collection with Darrell A. Posey (Q5224576) -> archives at (P485) -> Pitt Rivers Museum (Q1456119). I'd like to connect the individuals to the index pages of their archives, e.g. Darrell A. Posey (Q5224576) to https://www.prm.ox.ac.uk/posey-papers . I see that we have personal archive (Q27032347) which could be used with described at URL (P973) or official website (P856) but that seems to refer to institutions, and in the present case "archive" practically means a box of papers, or a collection of boxes. Thanks in advance for any suggestions. MartinPoulter (talk) 12:08, 6 March 2019 (UTC)

Would creating a property for "finding aid URL" (or similar) be appropriate here? It could thus be a qualifier on archives at (P485), or a primary property on items about a collection. Otherwise, I'd recommend described at URL (P973) as a qualifier on archives at (P485), though I don't know if the constraints would allow it. Andrew Gray (talk) 12:51, 6 March 2019 (UTC)

described at URL (P973) as a qualifier sounds like a good solution, because then we can distinguish between links to an online digital archive (full work available at (P953)) and links to a description or index (described at URL (P973)). MartinPoulter (talk) 14:14, 6 March 2019 (UTC)

It's a bit confusing/misleading, because when editing the items for archives at (P485), described at URL (P973) is one of the suggested qualifiers. However entering the URL (which clearly does describe the archives), gives the message "The property described at URL should not be used in this location (as qualifiers). The only valid location for this property is as main value.". Oh well I think I'll just ignore the non-issue. Animalparty (talk) 05:55, 7 March 2019 (UTC)

Help with complex constraint[edit]

I would like to create a constraint on has part (P527) such that a certain qualifier is allowed only if the value of the main statement is a class, not an instance. e.g.:

Marder I (Q156927)has part (P527)  turret front armor (Q38554489), with qualifier slope (P4184)  33 degree — qualifier is allowed, because turret front armor (Q38554489) is a class.

Memphite necropolis (Q10334749)has part (P527)  Pyramid of Unas (Q1478801), with qualifier slope (P4184)  56.3 degree — qualifier is not allowed, because Pyramid of Unas (Q1478801) is an instance of a class.

Thank you! Swpb (talk) 16:25, 6 March 2019 (UTC)

@Swpb:  Done, added to the property. (Currently there are only two violations, both because gun shield (Q4096972) is erroneously structured like a non-class.) --Yair rand (talk) 21:34, 6 March 2019 (UTC)

Please help with reviewing property proposals[edit]

It would be great to have a bit more activity on property proposals - quite a lot of them are left open for many months, with few people chiming in to give their opinion. Here is how you can help:

• Vote on open proposals to help them reach a consensus (big thumbs up to David who tirelessly voted on most proposals for the last few years I think);
• Help mark mature proposals with |status=ready when you see a clear consensus for creation (you can do that for your own proposals too!). At the moment the bulk of this work is done by ArthurPSmith alone - if we have other people doing that (for instance in other timezones), properties will get created more swiftly.
• Mark stale, inactive proposals with no consensus as |status=not done (or |status=withdrawn if it is your own);
• Don't forget to ping relevant wikiprojects, that generally helps attract eyeballs.

A good place to look for properties to review is Wikidata:Property_proposal/Overview - this table makes it easy to find recently proposed properties or old inactive ones that probably need closing.

The property proposal process can be a bit daunting when you see piles of old proposals full of unresolved heated debates, or properties that only created many months after being proposed. If the reviewing is more efficient, more newcomers will hopefully be keen to submit proposals. This is a space where key decisions about Wikidata's structure are made, so it's really worth getting involved. This is also rewarding work - you get to think about interesting data modelling problems, it is quite creative! − Pintoch (talk) 21:54, 6 March 2019 (UTC)

@Pintoch: I had no idea I could update the status myself. Happy to help. From observation, tt seems that a proposal should be open for at least 7 days before being marked "ready" - is that right? - PKM (talk) 22:32, 6 March 2019 (UTC)

@PKM: See Wikidata:Property creators for current policies, including the "no less than one week" rule. ArthurPSmith (talk) 22:52, 6 March 2019 (UTC)

(Note: I recently-ish proposed on the talk page to extend that time to a bit longer than a week.) --Yair rand (talk) 22:55, 6 March 2019 (UTC)

Subclasses and parts[edit]

(@Verdy p:.)

See Talk:Q58416391. There's a dispute over whether parts and subclasses are the same thing, unless I'm misunderstanding the argument. Anyone want to weigh in? --Yair rand (talk) 22:53, 6 March 2019 (UTC)

Litre per year[edit]

Hello. In Nesjavellir Power Station (Q693330), how do I add product or material produced (P1056) as "litre per year" or at least "litre per day". I think I'm close, but can't seem to figure out how to add the period. Is a new property required here? Rehman 10:50, 7 March 2019 (UTC)

@Rehman: You need an item for the unit - check whether it already exists, but if not you can create "litre per day" as an item and use that as the unit for the quantity. ArthurPSmith (talk) 16:11, 7 March 2019 (UTC)

Thanks, ArthurPSmith. I created litre per day (Q61992237), litre per month (Q61992243), and litre per year (Q61992246), by basing on the similar existing litre per kilogram (Q57175557). The items will be used for entities in the geothermal power and cogeneration industries, among other areas. Rehman 16:39, 7 March 2019 (UTC)

They look good, thanks. ArthurPSmith (talk) 16:44, 7 March 2019 (UTC)

Alternative text for images[edit]

Hello. Just like how we could state media legend (P2096) for image (P18), do we have a way to set alternative text for images? Rehman 11:30, 7 March 2019 (UTC)

We do not - see the discussion around a previous proposal for this here: Wikidata:Property proposal/alt. ArthurPSmith (talk) 16:12, 7 March 2019 (UTC)

Well that's a pity. Your last comment there made a lot of sense. Too bad it wasn't passed. Rehman 16:24, 7 March 2019 (UTC)

Image metadata is about to launch on Commons, another attempt can be made then. Matěj Suchánek (talk) 17:11, 7 March 2019 (UTC)

Not really. None of the developers seem to understand the difference between a caption and alt text, even when it's explained to them. --RexxS (talk) 22:54, 7 March 2019 (UTC)

Typography of labels[edit]

Hi,

Ludo29 raised an interresting question on the French Project chat (Topic:Uvhpolh1k8ylvkjt) : how to indicate that a label in one langage is foreign to this langage? (and consequently that when reused, it should often be in italic). The item concerned here is Deputy to the Dáil (Q654291) but it applies to many other items.

The first idea was to put wiki syntaxe directly inside the label. It kind of works for Wikimedia projects but could make a mess for re-use outside of Wikimedia projects so I think it is a bad good idea. Maybe it can be solved with a specific property or something else (Lexemes?) but I'm not sure how.

Does anybody has an idea or a solution for this?

Cheers, VIGNERON (talk) 13:58, 7 March 2019 (UTC)

Yes. This is an important question. If a word is usually displayed, in a given language, in italic, and if we decide to maintain our labels here wikicode-free, then we need some place to store the type of display that we are expecting to see whenever that word is used. It can be stored on Wikipedia but it seems to me that even if this is monolingual stuff, it should be here. Unfortunately, we can't use statements that would use items such as italic (Q344098) as values, for there are names or titles that can require both italic for one part and nothing at all for the rest. The value should thus mimic some kind of wikicode. Thierry Caro (talk) 14:16, 7 March 2019 (UTC)

It's an intractable problem for labels. In French or Spanish, you see Q344098's label as "Teachta Dála" which could be rendered (for example on enwiki) as something like "{{lang|ie|Teachta Dála}}". However in English we see the label as "Deputy to the Dáil", where the only foreign word is "Dáil"; so it would have to be rendered as something like "Deputy to the {{lang|ie|Dála}}". In Welsh, we see the label "Dirprwy y Dáil", so we would render it as "Dirprwy y {{lang|ie|Dála}}", and so on. Labels are free text and may be a mixture of local and foreign languages, so there's no way of demarking which parts of a label are to be rendered as foreign. The best you could do would be to create a new property of datatype monolingual text that allowed some sort of markup to be included that indicated the foreign part, for example, <Teachta Dála> (fr); Deputy to the <Dáil> (en); etc. (with a qualifier having the value "ie"). That sort of duplication of labels just for use on other Wikiprojects is something we probably ought to reach some consensus on. --RexxS (talk) 23:22, 7 March 2019 (UTC)

Spam or hoax items[edit]

Suppose a small wiki admin created spam/hoax/self-promotion articles on different wikipedia. A wikidata item is created by linking them. It is easy to weed them out on large wikis, but s/he manipulates and blocks deletion requests on the small wiki. Is wikidata bound to include this unencyclopaedic item, just because it contains at least one valid sitelink? What's the best approach to deal with this sort of admin misconduct on small wikis?--Roy17 (talk) 07:14, 8 March 2019 (UTC)

Wikidata isn't an encyclopaedia, so it's irrelevant whether or not an item is "unencyclopaedic". Our scope is wider. Storing data is a quite different task then storing articles to explain concepts.

Apart from that we have the https://meta.wikimedia.org/wiki/Small_Wiki_Monitoring_Team to fight misconduct that happens on small Wiki's and when an admin of a small Wiki includes hoax articles it's the job of the Small Wiki Monitoring Team to deal with the problem. ChristianKl ❪✉❫ 09:28, 8 March 2019 (UTC)

The Small Wiki Monitoring Team appears to be aimed at Wiki's with insufficient admin presence. It looks to me that there are real problems with small wiki admins, not limited to hoax items. There is not all that much that can be done from here, but obvious hoax items can be marked as "instance of: hoax", hoping that it will be dealt with in time. - Brya (talk) 07:29, 9 March 2019 (UTC)

Questions about correlating Wikipedia titles and Wikidata IDs[edit]

[I'm new to this chat page. If there's a better place to ask this sort of question, please let me know.]

I believe one of the first uses of Wikidata on the Wikipedias was to properly systematize interwiki language links. I always assumed this was done by having a template somewhere in each Wikipedia article containing its Wikidata ID, and then machinery somewhere used that Wikidata ID to look up the names of the articles in other language Wikipedias on the same topic. But that's evidently not the way it's done: I don't see Wikidata IDs in Wikipedia articles anywhere. (And indeed they'd be a nuisance to maintain, and subject to vandalism.)

So I guess that when displaying interwiki language links, a query is first done to discover the Wikidata ID corresponding to the original article's name. Am I correct?

Anyway, that's by way of background. I've been wanting to look up Wikidata IDs corresponding to Wikipedia article names myself. I finally constructed this SPARQL query:

SELECT DISTINCT ?id WHERE {
    ?article schema:about ?id; schema:inLanguage "en"; schema:name "Boston"@en .
}

And this seems to work, returning "Q100" for "Boston".

But is this the right way to do it, or is there a better way? (I'm particularly interested in avoiding anything that's needlessly inefficient. If indeed something like this has to be done every time a Wikipedia page is displayed, there's got to be a nice, efficient, indexed, optimized way to do it, and I'd like to make sure I'm accessing that way.)

Finally, I'm already pretty sure my query is not quite the right way to do it. For example, it returns two IDs for "Cambridge", both Q350 which is correct, and Q857732 which seems to correspond to the Wikipedia disambiguation page for Cambridge. Which makes a certain amount of sense, but how did it happen? The name of the Wikipedia disambiguation page for Cambridge is not "Cambridge"! (Other examples which yield multiple IDs include "Spain", "Jordan", and "Ensenada".) Scs (talk) 15:42, 8 March 2019 (UTC)

@Scs: The name of the Wikipedia disambiguation page for Cambridge is not "Cambridge"! No, but the name of the English Wikinews and Wikivoyage disambiguation pages is, as you can see by selecting the ?article as well:

SELECT ?article ?id WHERE {
  ?article schema:about ?id; schema:inLanguage "en"; schema:name "Cambridge"@en .
}

Try it! Instead, if you want to use the query service to discover the item corresponding to an English Wikipedia page, explicitly request that wiki –

SELECT ?id WHERE {
  ?article schema:about ?id;
           schema:isPartOf <https://en.wikipedia.org/>;
           schema:name "Cambridge"@en .
}

Try it! – or directly encode the title into the URL:

SELECT ?id WHERE {
  <https://en.wikipedia.org/wiki/Cambridge> schema:about ?id.
}

Try it! Alternatively, you can skip the query service completely and follow the Special:ItemByTitle/enwiki/Cambridge redirect. --TweetsFactsAndQueries (talk) 17:46, 8 March 2019 (UTC)

Got it! Thank you for all of those.

Related question: is there a good way to query across all languages at once? I tried variations on

SELECT DISTINCT ?lang ?id WHERE {
    ?article schema:about ?id; schema:inLanguage ?lang; schema:name "Boston"@?lang .
}

but had no success. (@ doesn't like ?, unsurprisingly.) Scs (talk) 18:02, 8 March 2019 (UTC)

You can also use the Wikipedia API, example, see API:Pageprops. Bovlb (talk) 22:13, 8 March 2019 (UTC)

How to ask for the president of some country using wqs?[edit]

Im new to wikidata query service, also im experimenting with wdq client and i'm struggling to ask for the president (p6 or p35 ?) of Argentina q414. My query was: #added before 2016-10

1. Demonstrates "no value" handling

SELECT ?country ?president WHERE { ?country wdt:P35 wd:414 . #find humans SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en" } }

--167.57.102.141 01:40, 9 March 2019 (UTC)

Do wd:Q414 wdt:P35 ?president. Matěj Suchánek (talk) 10:11, 9 March 2019 (UTC)

ok, how can i do the same with wdq in linux bash? is it there a better client for bash linux? sorry for my newbieness.--167.56.47.80 01:12, 10 March 2019 (UTC)

Other (multilingual) wikis as authority control[edit]

Can we use other wikis (such as Wikia wikis, OpenStreetMap wiki, etc.) as authority control? If so, how can we manage the multilingualism of some wikis? Should we:

1. add one value for each language version of an article or
2. add one property for every language of the wiki.

The first approach requires a lot fewer properties, but it creates some problems where wikis have a different subdomain for every language version (Wikipedia-style). The latter approach solves this problem but it treats two language version of the same wiki as completely different websites.--Malore (talk) 02:00, 9 March 2019 (UTC)

Let's talk about gender[edit]

The property sex or gender (P21) seems like it could use improvement.

The good: The property allows for an impressively diverse range of values including "two-spirit", "transfeminine", "agender", etc.

The bad: because the property only allows you to pick one single value, it is very inflexible. For example, when describing a woman you have to pick between "female" and "transgender female". This ghettoizes transgender people: the question of whether someone is female should be considered seperately from whether they are cisgender or transgender. Also, look at the case of Mauro Cabral Grinspan. Over on Wikipedia, sche pointed out to me that Grinspan identifies as transgender, male, and intersex, and all three are important parts of his identity as an activist and a human being. However, currently, P21 does not allow you to select all three. Instead you must choose between "transgender male" or "intersex". (Currently he's listed as transgender male.)

One obvious solution: allow multiple values. I found a report about cataloging gender that advocates this approach. Here is what that might look like:

• Mauro Cabral Grinspan: male, transgender, intersex

• Lana Wachowski: female, transgender

• Jeffrey Tambor: male, cisgender

• William Shakespeare: male (*)

• Jessica Chastain: female

• Ma-Nee Chacaby: two-spirit

• Mal Blum: nonbinary

• Rebecca Sugar: nonbinary, female (**)

• Hanne Gaby Odiele: female, intersex

Alternatively, instead of allowing multiple values, perhaps we could keep the one value constraint but open things up to qualifiers, to similar effect:

• Mauro Cabral Grinspan: male (qualifiers: transgender, intersex)

• Jeffrey Tambor: male (qualifier: cisgender)

etc.

Note that in my view, strong preference should be given to current self-identification (as recorded in reliable sources). For example, a trans woman should not be listed under both "female" and "male" but just "female". The RDA cataloging standard, which I believe is considered pretty authoritative in the library world, has a similar view. It says, under "instructions for recording gender": Gender is the gender with which a person identifies.

Related to the above, my biggest fear with opening up the gender category like this is that editors will just indiscriminately slap both "male" and "female" onto practically any trans or queer person. Perhaps, to avoid this kind of "excessive gendering", it would be better to go with a single value + qualifiers approach.

Anyway, that's my two cents, but note I'm very new to Wikidata don't claim to be an expert on either cataloging or gender. :)

(*) Why didn't you list Shakespeare or Chastain as cisgender? While it would seem fairly reasonable to describe them as cisgender, if someone hasn't identified as such in a reliable source, perhaps it's best to leave it out. (Jeffrey Tambor, meanwhile, has publicly called himself cisgender.)

(**) Why did you list Rebecca Sugar as both nonbinary and female? Because she identifies as a "nonbinary woman". Again, self-identification is king. (...Or queen. Or monarch.)

WanderingWanda (talk) 03:05, 9 March 2019 (UTC)

Note: There's quite a bit of previous discussion at Property talk:P21. Just a thought: if we're going to use self-identification as a qualifier, we should try to use qualifiers that are commonly and consistently used (as we should for any label, really). I myself am a cis-gender male, biologically. I identify simply as male, even though I just said I am cis-gender one sentence ago, and my future identification might change depending on whether I'm speaking on chromosomes or gender studies. The majority of male and female humans in history probably are or were cis-gender. As far as I know, Jeffrey Tambor (Q320204) referred to himself as a cis-gender man exactly once in a speech directly related to him playing a transgender character. Does that mean Tambor "identifies as cisgender male"? Is that enough for a qualifier? I'd argue no, unless he regularly corrects people when they call him an unqualified man. But gender and sexuality are certainly fluid and complex. I'm no expert either, and perhaps the rigid granularity of Wikidata doesn't fully allow for proper record keeping in this field. Animalparty (talk) 05:44, 9 March 2019 (UTC)

Animalparty I understand what you're saying but I think you're coming at this from the wrong angle. I don't think someone's cisness disappears just because they don't talk about it. Same with someone's transness or maleness or femaleness or straightness or gayness or whiteness or blackness. I rarely mention the fact that I'm white, but that doesn't mean I'm not white! It's also worth noting that people in a dominant majority group will naturally talk and think about that group a lot less than people in a marginalized minority group. Anyway, in my view Jeffrey Tambor said he's cisgender, and he's never indicated he's not cisgender, therefore, I think it's perfectly reasonable to label him as cisgender. WanderingWanda (talk) 07:12, 9 March 2019 (UTC)

I'll add that the only reason I used the word "qualifier" is because that's the Wikidata terminology and I was a little uncomfortable using that specific word. (Hmm, perhaps the fact the word "qualifier" is a little uncomfortable in this case is a reason to avoid using qualifiers to solve this.) WanderingWanda (talk) 07:21, 9 March 2019 (UTC)

I think it would be better to have two different properties. One for the sex just defined by the chromosomes and one for gender defined by the person them self. --GPSLeo (talk) 11:10, 9 March 2019 (UTC)

How do you propose we get people's chromosome data, exactly? Is Wikidata going to start commissioning large scale blood tests? :) WanderingWanda (talk) 16:26, 9 March 2019 (UTC)

I would only differ in has a Y-Chromosom or dose not have it. Of course we do not have the data in most cases, but then we just should not imply that we have that information like it is now. --GPSLeo (talk) 17:28, 9 March 2019 (UTC)

Unlike blood type (P1853), we do not actually need blood tests to determine this. Property_talk:P21#Reasonable_inferences. --Yair rand (talk) 18:41, 10 March 2019 (UTC)

I was going to argue but....it seems like the decision to combine sex and gender was made years ago, do we want to relitigate it? I feel like I went "what if we made these tweaks" and you came in with "ah but what if we just throw out what we have and start over?" :) WanderingWanda (talk) 04:36, 11 March 2019 (UTC)

(Was this a reply to my comment, or GPSLeo's? I'm in favor of maintaining one unified property using the current format.) --Yair rand (talk) 06:23, 11 March 2019 (UTC)

I might have misunderstood your position. WanderingWanda (talk) 15:38, 11 March 2019 (UTC)

@GPSLeo: (Via edit conflict) Very problematic. Just for some examples:

In most cases we have no idea who has XYY syndrome (Q267602) rather than simply being male.

Most transgender people see it as insulting to focus equally on their biological gender.

If we really want to model this, there is also presentational gender, which may be multiple for the same person: consider drag performers. And drag performers also can bring up some interesting issues about self-identified gender. Most identify with their biological gender. Some are transgender. Some start by identifying with their biological gender, then become increasingly transgender-identified over time. Many prefer a different set of pronouns depending on their presentation at the moment. - Jmabel (talk) 16:30, 9 March 2019 (UTC)

I admit I don't know much about drag culture, so maybe this is the wrong way to look at it, but: if we wanted to model a drag queen's in-drag gender presentation, my thought is that it should essentially be treated as the gender of a fictional character, like the gender of Harry Potter. WanderingWanda (talk) 16:51, 9 March 2019 (UTC)

The way Wikidata currently treats drag queens seems fine to me, though. As it is now: the label is the performer's drag/stage name, and then the performer's less-well-known non-drag name is listed as an alias, and the gender is listed as whatever the performer currently identifies as outside of drag. So the drag performer Eureka O'Hara is listed with the alias "David Huggard" and the gender of "non-binary" (because the performer identifies as, according to Wikipedia, "genderfluid and gender-neutral.") Meanwhile Alexis Michelle is listed with the alias "Alex Michaels" and the gender "male" because apparently the performer identifies as male outside of drag. WanderingWanda (talk) 17:54, 9 March 2019 (UTC)

Technical question: is it possible to set things so that a statement can have multiple values but certain combinations of values are constrained? For example, could the gender property be set so that you can combine the value “transgender” with the value “male” but there’s either a hard or soft restriction on combining “male” and “female”? WanderingWanda (talk) 01:34, 10 March 2019 (UTC)

I would support allowing the property to have multiple values to cover these cases. An alternative would be to simply expand the number of values, so that besides "transgender female" one could have "intersex female", "cisgender female", "intersex transgender female", etc, but the number of such values would be large (consider that it already allows things like "kathoey" and "two-spirit", and any of these might co-exist with "intersex"), and besides there are the other aforementioned conceptual reasons (the distictness of being trans/cs from being male/female) that simply allowing multiple values would be more sensible. (I would oppose a "chromosomal sex" parameter, since for almost all people, the parameter would be guesswork, and why add a field for something you know going in is going to be unverified and unverifiable guesswork in the vast majority of cases? Perhaps something like "assigned sex", while still very problematic, would at least be somewhat less farcical... but in most cases, we only know someone's gender: whether they present themselves, dress, etc as a man, woman, etc.) -sche (talk) 22:19, 10 March 2019 (UTC)

No, it is actually quite possible to infer it. See the linked section above. --Yair rand (talk) 00:03, 11 March 2019 (UTC)

One more thing: The fact that Caitlyn Jenner and other trans people have a "start time" qualifier added to their gender feels off to me. Gender transition is a lifelong, multistep process and someone coming out as trans is best thought of as a reveal rather than a sudden change. Caitlyn Jenner may have announced that she was a woman on "1 June 2015" but that doesn't mean that's the official start of her womanhood. In fact, if you read the Vanity Fair article that is used as a reference for that "1 June 2015" date, you'll discover that Caitlyn Jenner's family had been discussing her gender for decades before she publicly came out. I recommend we create a new "coming out date" property and use that instead of "start time". WanderingWanda (talk) 23:54, 10 March 2019 (UTC)

See significant event (P793), although I think that would be supplementary data rather than a replacement for start time. Note that start date properties can have variable precision. --Yair rand (talk) 00:03, 11 March 2019 (UTC)

Maybe instead of "coming out date", I'll propose new property "announcement time". That could be used for a lot of different things, including the date when someone came out as trans, and could also, presumably, be made to allow for variable precision. WanderingWanda (talk) 04:15, 11 March 2019 (UTC)

Personally, I think using P793 in more cases has many advantages over creating different properties, although some think otherwise. See Wikidata:Properties_for_deletion#.7B.7BPfD.7CProperty:P606.7D.7D for an ongoing discussion mostly about whether P793 should be used instead of many separate properties. --Yair rand (talk) 06:23, 11 March 2019 (UTC)

Looking into things a bit more, "sex or gender" originally did allow multiple values, and, unfortunately, it resulted in exactly the "excessive gendering" problem I was worried about. At one point Chelsea Manning, for example, was listed as "male" and "female" and "transgender female". Yikes.

The way Wikidata handles gender now is problematic but it apparently is a big improvement on how things used to be. Suddenly I'm much less inclined to try and change things, lest they regress.

Still, I think opening the gender property back up to multiple values could allow us to paint a better, more accurate, and more nuanced picture of who a person is, if we worked towards the goal of reflecting and respecting a person's latest self-identification and shared the basic understanding that trans women are women and trans men are men. WanderingWanda (talk) 16:00, 11 March 2019 (UTC)

commons category[edit]

in item like Q25966820 when you have to set the commons category in P373 and when in the "other sites" field? thanks--Pierpao (talk) 08:13, 9 March 2019 (UTC)

For category items, the sitelink is useful, but I don't think you gain anything adding P373. Ghouston (talk) 10:27, 9 March 2019 (UTC)

There should always be both because the sitelinke could also be a a gallery page. So it is better to search for the categories by using Commons category (P373) in a query. --GPSLeo (talk) 11:05, 9 March 2019 (UTC)

This is true for main items, where P373 is also very useful for finding Commons categories that are sitelinked to category items, but galleries shouldn't be sitelinked to category items. Ghouston (talk) 04:08, 10 March 2019 (UTC)

Solar irradiance[edit]

Hello. What is the best way to state solar irradiance in SI-units (i.e. kWh/m2/year)? I see we have solar irradiance (Q7556707) and solar irradiance (Q17996169) as well (very likely dupes), but do we need a new property here? Rehman 17:04, 9 March 2019 (UTC)

I think we would need a new property for this. But where do you want to ad this property? I think we do not even have properties for annual precipitation or mean annual ground temperature. --GPSLeo (talk) 19:19, 9 March 2019 (UTC)

Thanks GPSLeo, yes I thought so too. I will go ahead and propose it. This property will be used to indicate the solar resource at a solar power station site. Rehman 05:46, 10 March 2019 (UTC)

How to correct an automatically generated item description[edit]

Q18921708 was incorrectly marked as an "American basketball player" when the item was created. However, the subject is Senagalese, which I have corrected.[5] However, a bot added this old wrong description at various times.[6][7] Is there any way to get the bot to update them? Pinging User:Emijrp. Magog the Ogre (talk) 18:34, 9 March 2019 (UTC)

You have to blank all the incorrect descriptions, and the bot will add the new descriptions (for Senagalese basketball player) in the next run. Emijrp (talk) 19:14, 9 March 2019 (UTC)

But why do you say he is a Senegalese and not an American basketball player? As seen in the properties he was born in the Senegal but visited an university in Florida and plays for an US-Team, so I think he was just born in the Senegal and lives in the US. And he also has both citizenships. May just contain both in the description like "basketball player born in Dakar playing for an US basketball team" --GPSLeo (talk) 19:30, 9 March 2019 (UTC)

I have seen constructs like “American basketball player from Senegal” and “Senegalese-American basketball player”. I like the second form since he is known to have dual-citizenship. - PKM (talk) 02:42, 10 March 2019 (UTC)

It would be good to add a reference for the US citizenship claim, Wikipedia doesn't know anything about it. Ghouston (talk) 04:35, 10 March 2019 (UTC)

Maybe the error is there. If it's correct, the description doesn't seem incorrect. --- Jura 10:02, 10 March 2019 (UTC)

The claim in the decription that he is a US citizen was first added by PLbot on 2015-02-10T23:46:17. There's no apparent source for it. User:GPSLeo / User:PKM, why do you think he has US citizenship? Ghouston (talk) 01:07, 11 March 2019 (UTC)

I was following User:GPSLeo. Assuming that data is correct, this is how I’d record it. - PKM (talk) 01:58, 11 March 2019 (UTC)

I just looked at the statements but I see that RealGM (Q7300810) says something different. The English Wikipedia says nothing about his citizenships. --GPSLeo (talk) 11:07, 11 March 2019 (UTC)

Independent of this if someone lives in the US since he is 16 years old I would call him US-american if he has the citizenship dose not matter for me. --GPSLeo (talk) 11:10, 11 March 2019 (UTC)

Light-on-dark color scheme for wikidata[edit]

Checking Light-on-dark color scheme on the English Wikipedia this is what I want for my interface but on wikidata. If I hit Preferences --> Appearance my skin is Vector. Does anybody have any Custom CSS for me so I can enable night mode/dark theme/dark mode? Even if you recommend a resource on let's say Wikibooks or Wikiversity I'd be happy to read up on anything you might recommend that after studying it might help me learn how to do it. Btqfshfst (talk) 21:52, 9 March 2019 (UTC)

Ranking[edit]

Help:Ranking. Maybe I have missunderstood some things in wikidata.

The deprecated rank is used for statements that are known to include errors (i.e. data produced by flawed measurement processes, inaccurate statements) or that represent outdated knowledge (i.e. information that was never correct, but was at some point thought to be). It is often useful to indicate the reason for a deprecation with a reason for deprecation (P2241) qualifier. This does not apply to correct historical information, such as previous values of a statement, as long as they represent accurate information for the indicated time period. Such statements should instead be annotated with the apropriate ημερομηνία έναρξης (P580)/ημερομηνία τερματισμού (P582) qualifiers.

If an organization have a website we use official website (P856). But if this website no longer exist and the organization have not a new one, then what must be the ranking of the old website? We can't remove the old one since P856 description says:

URL of the official homepage of an item (current or former) [if the homepage changes, add an additional statement with preferred rank. Do not remove the former URL]

• I can't use deprecated rank. The old website was not error.
• I can't use preffered rank. There is not a new website.
• Normal rank is considered neutral. But, the information is sure that is not correct. We can't say that is believed to be correct.
• If the rank is normal rank, since there is no preferred rank, the infoboxes will show the old website.

Xaris333 (talk) 22:07, 9 March 2019 (UTC)

@Xaris333: in this kind of case, you can add an empty no value and put the preferred rank on it. Cheers, VIGNERON (talk) 23:08, 9 March 2019 (UTC)

@VIGNERON: I did that but now I had single value constraint (Q19474404). Q4700714#P856 Xaris333 (talk) 10:58, 10 March 2019 (UTC)

• You might want to add the "end date" qualifier. If the infobox doesn't want to support it, the former website can be displayed. --- Jura 10:11, 10 March 2019 (UTC)

@Jura1: I don't know when is the end date and I can't find it. Xaris333 (talk) 10:58, 10 March 2019 (UTC)

Then use "somevalue" as value for "end date". --- Jura 11:01, 10 March 2019 (UTC)

OK, thanks. The infobox is showing the url, I quess we have to do a change in the wikipedia template. Xaris333 (talk) 11:05, 10 March 2019 (UTC)

@Xaris333: you don't know the end date but you do know that there is an endate, so you can use some value (which also solves the constraint violation ). And even if you don't know the precise end date, maybe we can use an imprecise value, like 21st century or 2010s. Cdlt, VIGNERON (talk) 11:06, 10 March 2019 (UTC)

PS: with the Wayback Machine, I found that the end date is '2018'.

Journal de Bruxelles[edit]

How do you connect the specific editions of 'Journal de Bruxelles' Q45747062, Q46834135 and Q62015763 with the general 'Journal de Bruxelles' item Q25382985. And how can I place a specific dated newsitem such as De_Constantinople,_le_24_Brumaire_(15_novembre_1799) in Wikidata. These newsitems where printed in several newspapers as news dispatches where send around. (no telefone or telegraph). There is a date and place.Smiley.toerist (talk) 23:25, 9 March 2019 (UTC)

For the first question, I think with part of the series (P179), as in Journal de Bruxelles (1790-1800)/76-1799 (Q45747062) part of the series (P179) Q25382985. For the second question, I suppose you could make an item in Wikidata for the dispatch and pick one of the publications that it appeared in. Perhaps the earliest dated, if they differ. Ghouston (talk) 06:21, 10 March 2019 (UTC)

Dorvitsa[edit]

Hi there are many names a remote village in Greece went by throught the years. While I tried to add them all, a user always removes them. These names are not used anymore but there are found in historic sources like goverment gazettes which refered to this village with those names. The village is Dorvitsa (Dorvitsa (Q5299063)). Please take a look at the wikidata's item history and inform me who is wrong. Thank you.(TakisA1 (talk) 23:42, 9 March 2019 (UTC)) t @Chalk19: Xaris333 (talk) 10:54, 10 March 2019 (UTC)

@Chalk19: the summary is strange, for me this is exactly what aliases are here for (that's my interpretation of Help:Aliases anyway). Cheers, VIGNERON (talk) 11:12, 10 March 2019 (UTC)

@VIGNERON: "Obscure" or lost-in-time-and-space variations of place names like this, not in use for centuries, or perhaps with a very limited usage (like in a family circle, if one specific variation appeares just once in a dowry contract of 1774) does not mean "also known as". Variations, say, found in manuscripts layng in dust on the shelves of a local archive, or other similar sporadic versions or even misspellings by scribers or writers who put down a name as they thought it sounded etc. 300 years ago does not mean "also known as". "Also known as" means alternative, or even completely different names as recorded in older school textbooks, old encyclopeadias etc. ——Chalk19 (talk) 22:22, 10 March 2019 (UTC)

PS. Most places in Greece have tenths of variations of their names like those of Dorvitsa, starting from time immemorial: variations found in old manuscripts or some very old books, like with a "v" instead of a "b", or with a "p" in the place of a "b", or a "g" in the place of a "k", an accidental interchange of letters, a "t" replacing "d", or a "th" (Greek δ, sounds like in the) replacing "d", and an "o" instead of "ou", a sometimes missing "o", a "tz" in the place of "ts", just a stressing mark in another syllable etc. etc. etc. Several irregular and incontinuous forms that don't mean that the place is "also known" by all these alternate, sporadic forms, that most of them just appeared somewhere because in those days there was not a "standard" version of the name of the place, because a sriber or an author was changing the name accoding to what was closer to his (probably not "her" in those times) cultural backround (if he were of this or another ethnic origin etc.) Variations as the abovemationed are not "other common names", or "alternative names" to the "most common name […] known by to readers", as requiered in Aliases: Criteria for inclusion and exclusion.——Chalk19 (talk) 22:39, 10 March 2019 (UTC)

PS2. Sometimes variations of this kind may be included (according to the reliable sources available on them) in a summary in a section on older names, or name forms recodered of a place in its article in WP. ——Chalk19 (talk) 22:57, 10 March 2019 (UTC)

@Chalk19: hmm, I agree, too rare variations found in old manuscript are not what alias is intended for (but still can be used to store them) but here, according to TakisA1 these come from « goverment gazettes ». So it seems ~correct to me, and there is no such thing as having too much aliases, the more the better. Anyway, if not in aliases these names can also be stored in properties (name (P2561) or a more specific one) where references can explicitely be added. Cheers, VIGNERON (talk) 08:00, 11 March 2019 (UTC)

PS: « translations and transliterations, should be recorded as aliases » (Help:Aliases so yes a "tz" in the place of "ts" is acceptable per this rule (and it's a good thing as most people don't know that 'tz' and 'ts' are equivalent in Greek).

@VIGNERON: Well, does anybody really think that a Greek village actually has 17 (!!) different, alternative common names? Not even Constantinople, an imperial capital of a 1,600 years doesn't have so many! ("Βυζάντιο", "Νέα Ρώμη", "Κωνσταντινούπολη", "Πόλη", "Βασιλεύουσα", "Ισταμπούλ").

TakisA1 claim that all these "are found in historic sources like goverment gazettes" is a totally misguiding statement. According to his own source (provided in this edit summary), only Δοροβίτσα is from a 1836 goverment gazette, "Δοροβίτσα, (εφημερίδα κυβερνήσεως 1836)". For the rest we get no information, neither wher there have been found, nor (and this is crucial) how widespead was the use of them (if any, in public). Finally, please note that TakisA1 source is not a reliable source; it is just a post in the website of a local recreational club providing something written in 1973 by the amateur historian Sokratis A. Liakos (obviously a reproduction from a book or an article of his, not mentioned in the post). ——Chalk19 (talk) 09:05, 11 March 2019 (UTC)

@Chalk19: why do you think that aliases have to be « alternative common names », it's is just for « alternative names » (no matter how common they are, we do avoid the more rare variations but it doesn't have to be common, look at the examples on Help:Aliases). That said, TakisA1 could you provide good references, it would be useful for name (P2561) (and maybe also for Lexemes). Cheers, VIGNERON (talk) 10:32, 11 March 2019 (UTC)

@VIGNERON: According to Wikitada policy on the matter that I have already quoted above (Criteria for inclusion and exclusion): "The label on a Wikidata entry is the most common name that the entity would be known by to readers. All of the other common names [my emphasis] that an entry might go by, including alternative names; acronyms and abbreviations". So, we clearly talk about "other common names" (my emphasis). Furthermore we "should not include […] spelling mistakes". So, what is the proof that, say, the forms "Τεροβιτζιά" or "Τιροβήτσα" found somewhere (where? in an official document? in a entry by some semi-illiterate book-keeper of the area? on a gravestone?) in 1770 and 1791 respectively (according to TakisA1 source [8]) how widespread actually were? Meaning, were they "commmon names" or "other common names" of those times? Moreover, couldn't be "Τεροβιτζιά" the "common name" and the similar sounding "Τιροβήτσα" an accidental missplelling of it, or vice versa? And what about "Ντερβιτσά" recorded (according to the same source) by an anonymous French traveller who passed by the early 1800s? Did he put down the name in his notebook in Greek as it appears in the post? Or in French=latin srcipture, so what is the original entry, and who had it transliterated to the Greek alphabet? And, then, isn't it highly probable, as were the case with foreigner travellers in those days, that he didn't know Greek, so he misspelled the name of the village? Isn't it possible that, since he was French, he wrote a "D" in the place of the initial Greek letter "Δ", or a possible initial "Τ"? So, why we must include "his" version of the name, "Ντερβιτσά", in owr "Also known as" list of the "other common names"? In other words: has TakisA1 provide any reliable secondary source about all these 17 alternative forms of the village name as its "other common names"? Not, so far. ——Chalk19 (talk) 11:35, 11 March 2019 (UTC)

Updation on Wikidata for sdwiki namespaces[edit]

Hi, We have localised all the namespaces on Sindhi Wikipedia, after the localisation done via Phabricator, the Wikilinks to other Wikipedia's pages aren't showing on the Sindhi Wikipedia, So Here I request to perform this function on large scale to link Namespaces pages of Sindhi Wikipedia with Wikidata items, so that they can be wikilinked with other wikis similar pages. Namespace name in English => Localised name in Sindhi

   NS_WIKIPEDIA           => 'وڪيپيڊيا',
   NS_WIKIPEDIA_TALK    => 'وڪيپيڊيا_بحث',
   NS_PORTAL           => 'باب',
   NS_PORTAL_TALK    => 'باب_بحث',
   NS_MEDIA            => 'ذريعات',
   NS_SPECIAL          => 'خاص',
   NS_TALK             => 'بحث',
   NS_USER             => 'واپرائيندڙ',
   NS_USER_TALK        => 'واپرائيندڙ_بحث',
   NS_PROJECT_TALK     => '$1_بحث',
   NS_FILE             => 'فائل',
   NS_FILE_TALK        => 'فائل_بحث',
   NS_MEDIAWIKI        => 'ذريعات_وڪي',
   NS_MEDIAWIKI_TALK   => 'ذريعات_وڪي_بحث',
   NS_TEMPLATE         => 'سانچو',
   NS_TEMPLATE_TALK    => 'سانچو_بحث',
   NS_HELP             => 'مدد',
   NS_HELP_TALK        => 'مدد_بحث',
   NS_CATEGORY         => 'زمرو',
   NS_CATEGORY_TALK    => 'زمرو_بحث',
   NS_MODULE    => 'ماڊيول',
   NS_MODULE_TALK    => 'ماڊيول بحث',
   NS_GADGET    => 'گيجيٽ',
   NS_GADGET_TALK    => 'گيجيٽ بحث',
   NS_GADGET_DEFINITION    => 'گيجيٽ وصف',
   NS_GADGET_DEFINITION_TALK  => 'گيجيٽ وصف بحث,

Source:https://phabricator.wikimedia.org/T186943 JogiAsad (talk) 11:10, 10 March 2019 (UTC)

• Try Wikidata:Bot_requests. I assume sitelinks and possibly labels need to be updated.--- Jura 11:14, 10 March 2019 (UTC)

Example SEE THIS JogiAsad (talk) 11:16, 10 March 2019 (UTC)

Done BOT REQUESTED HERE JogiAsad (talk) 11:21, 10 March 2019 (UTC)

First French republic[edit]

I added to the 'replacement property' (P1365). However these are under Identificationcodes chapter, while it should be added to the Declaration chapter by the county of Flandres. There are other historic states wich need to be added.Smiley.toerist (talk) 14:07, 10 March 2019 (UTC)

I found the solution: delete and add to the correct place.Smiley.toerist (talk) 14:18, 10 March 2019 (UTC)

Not sure to understand what was your problem (when you add an information, it's automatically in the right chapter, just refresh the page to see them at the right place) but glad you found a solution. Also, thanks for adding these information but don't forget to add the reverse information, if you add French First Republic (Q58296)replaces (P1365)  Comtat Venaissin (Q1122980), you should also add Comtat Venaissin (Q1122980)replaced by (P1366)  French First Republic (Q58296) . Cheers, VIGNERON (talk) 16:50, 10 March 2019 (UTC)

iCarly (Q3013) could need some protection[edit]

Seems there is a Spanish Michael Jackson meme going the rounds that is somehow related to iCarly, the item is seeing quite a bit of vandalism. If an Admin could have a look that would be great. Moebeus (talk) 19:16, 10 March 2019 (UTC)

 Done, protected for three months--Ymblanter (talk) 20:02, 10 March 2019 (UTC)

Thank you! Moebeus (talk) 01:07, 11 March 2019 (UTC)

Difference between Commons category (P373) and linking commons category in "other sites"[edit]

What is the difference between Commons category (P373) and linking commons category in "other sites"? For example, the wikidata item Q3519973 is about the wikipedia article en:Comptroller and Auditor General of India and commons category commons:Category:Comptroller and Auditor General of India. Now, if I link the commons category as item Property:P373, it appears in the left side panel of wikipedia article but not on commons category (says "NO WIKIDATA ID FOUND!" when I add {{Wikidata infobox}}); whereas when I link the commons category in "other sites" section of wikidata item, it doesn't appear on wikipedia article left panel but show on commons category. So how are these two ways of linking commons category to wikipedia article different from each other, and which one is better? Thanks —Sarvatra (talk, contribs) 05:07, 11 March 2019 (UTC)

You need to link the Commons category in "other sites" (sitelink) to avoid the "NO WIKIDATA ID FOUND!" problem. The P373 statement is sometimes by software to find Commons categories, especially when the Commons category is linked to a different item (a category item vs a main item). There's a bot that will add it based on the sitelink. Ghouston (talk) 05:49, 11 March 2019 (UTC)

Noted. Thanks. —Sarvatra (talk, contribs) 06:27, 11 March 2019 (UTC)

Merge artistic creation (Q47407603) and artistic creation (Q29586009)?[edit]

I wonder whether artistic creation (Q47407603) and artistic creation (Q29586009) should be merged. - The former refers to the "process during which a work of art comes into being", while the latter is defined as "economic activity involving the creation of artistic works". Any thoughts? --Beat Estermann (talk) 07:54, 11 March 2019 (UTC)

@Valentina.Anitnelav, Andrawaag: who created these artistic items. Multichill (talk) 16:57, 11 March 2019 (UTC)

I'm not sure if I fully understand the scope of artistic creation (Q29586009), but according to the description and a catalog code (P528) for the Statistical Classification of Economic Activities in the European Community (Q732298) artistic creation (Q29586009) represents artistic creation as an economic activity, which is not the case with artistic creation (Q47407603) which also includes notions of artistic creation outside the economical system (e.g. as a self-sufficient activity). I think it is safe to say that artistic creation (Q29586009) is a subclass of artistic creation (Q47407603). - Valentina.Anitnelav (talk)

Is it possible to track articled nominated for deletion on Wikipedia using Wikidata?[edit]

I know that a few WikiProjects use Wikidata to track articles to be created using User:ListeriaBot. I'm wondering if it is possible to track articles for deletion as well. Do I need to create/propose a new property? Is it outside the scope of Wikidata? Thanks! Tetizeraz (talk) 11:03, 11 March 2019 (UTC)

You could propose a new property for this; I'm not sure what would be the best way to model it though. Perhaps an item-valued property "proposed for deletion" with value the item for the wikimedia site where the deletion is proposed? ArthurPSmith (talk) 13:09, 11 March 2019 (UTC)

@Tetizeraz: In SPARQL you can use the MediaWiki api so you can ask the MediaWiki API for the articles nominated for deletion (based on inclusion of a category or template usage) and combine that with Wikidata.

For example on the Dutch Wikipedia we use nl:Template:Artikelweg. This query will give the articles nominate for deletion on the Dutch Wikipedia. Multichill (talk) 16:42, 11 March 2019 (UTC)

Duplicate from Commons[edit]

There exists Alphons Huber (Q87180), having a Commons category statement, and the duplicate Alfons Huber (Historiker) (Q21082996), having the associated commons gallery statement. My question is: Is it possible to find this kind of duplicates, where a commons category is in one item, but the subpage gallery in a different item? 129.13.72.197 11:27, 11 March 2019 (UTC)

Good question.

As a start, here is a query that looks to find items with a Commons gallery (P935) but no Commons category (P373). It also looks to see if there is a topic's main category (P910) and whether that has a Commons category (P373). Over 12,000 hits, which is a lot more than I was expecting.

SELECT ?item ?itemLabel (URI(CONCAT('https://commons.wikimedia.org/wiki/', ?gallery)) AS ?gallery_url) ?cat ?catLabel ?ccat WHERE {
   ?item wdt:P935 ?gallery .
   MINUS {?item wdt:P373 ?commonscat} .
   OPTIONAL {
       ?item wdt:P910 ?cat .
       OPTIONAL {
          ?cat wdt:P373 ?ccat .
       }
   }
   SERVICE wikibase:label { bd:serviceParam wikibase:language "[AUTO_LANGUAGE],en". }
}

Try it!

The tricky bit is to go through those gallery pages, see what commons categories they are in, and to try to identify whether one of those commons categories corresponds to the main topic of the gallery. Then one can look to see whether that commons category has its own sitelinked item, and whether that is a category-type item, or whether it is an article-type item that ought to be merged with the one that currently has the gallery sitelink, with a new item created to be sitelinked to the category.

@Mike Peel: (and anybody else): Any thoughts on any steps that could make such a process more automated, or at least more machine-supported? Jheald (talk) 11:49, 11 March 2019 (UTC)

Suggestions based on constraints: next step[edit]

Hello all,

Last year, we enabled suggestions based on constraints values for the constraints section of a property as a beta feature. You can also have a look at the documentation and the list of supported constraint types.

After a few months of testing, we would like to enable it for all users. Before that, we would like to know more about your experience with that feature.

• Did you encounter issues or unexpected behaviours?
• Is there anything that should be improved before enabling it for all users?

When reporting an issue, please give specific examples and what you would have expected instead, so we can figure out the best way to solve it. You can also leave a comment in the related ticket.

Thanks! Lea Lacroix (WMDE) (talk) 13:21, 11 March 2019 (UTC)

I still have the feeling that the feature isn't ready for deployment yet. There hasn't been any work on it since it's release as a beta feature. Important things as sorting based on usage is still missing, making the feature useless for me. For example, genders are sorted very weirdly. Also a Phabricator task about the automated results not being linked (aka not possible to open the property or item in a new tab) is still open. Sjoerd de Bruin (talk) 13:34, 11 March 2019 (UTC)

Scholarly articles and main subject P921[edit]

I've been busy with disambiguating author strings in scholarly articles and I am wondering how main subject is added to them.

• Is it done programmatically ?
• What is the heuristics behind it ?
• Can it be done by humans ?

For example

RNA-Seq (Q2542347) has been added [9] as the main subject (P921) of

Exonuclease hDIS3L2 specifies an exosome-independent 3'-5' degradation pathway of human cytoplasmic mRNA (Q24294915)

How can one arrive at this decision ?
--Kpjas (talk) 14:16, 11 March 2019 (UTC)

I think its just done by taking keywords from the article title. 94.217.191.11 18:35, 11 March 2019 (UTC)

Wikidata weekly summary #355[edit]

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

• Discussions
  • Open request for adminship: Dimon2711
  • Closed request for adminship: Esteban16, welcome onboard!

• Events
  • Upcoming: Wikidata meetup in Berlin, on March 12th
  • Upcoming: Wikidata meetup in Paris, on March 15th
  • Upcoming: Wikidata & Wikipedia workshop in Aberdeen, Scotland, on March 19th
  • Upcoming: GLAM and Wikidata in National Library, Bern (Switzerland), on March 28th (in German and French).
  • Upcoming: Wikidata Workshop for GLAM in Lausanne (Switzerland), on March 29th (in French).
  • Upcoming: Where iNaturalist meets Wiki (Invasive plants) April 16th, Meise, Belgium
  • Upcoming: How does Wikimedia Solve the Problems of Biodiversity Informatics? Biodivesity Next (Leiden, the Netherlands), October 19th-25th 2019

• Press, articles, blog posts
  • Combining AI and Human Judgment to Build Knowledge about Art on a Global Scale by Andrew Lih
  • Data Quality Management in Wikidata – Workshop write-up, by Cristina Sarasua, Claudia Müller-Birn, and Mariam Farda-Sarbas
  • Museum Collections on Wikipedia: Opening Up to Open Data Initiatives by Elena Villaespesa and Trilce Navarrete

• Other Noteworthy Stuff
  • Client wikis calling geocoordinate statements from Wikidata using mw.wikibase.entity:formatStatements or the #statements parser function will now have it displayed using a Kartographer <maplink> if available. In case of bug or question, feel free to ask in phab:T210926. Thanks to Tpt for the change!
  • A Google Summer of Code/Outreachy project seeks to add structure to the Commons app. Photographers will be able to pick Wikidata items that are depicted by the picture they upload.
  • Suggestions based on constraints can be enabled for all users

• Did you know?
  • Newest properties:
    • General datatypes: key performance indicator, inscription mentions, taxa especially protected in area, number of words, collective noun for animals, Cook Partisan Voting Index, league system, endowment, highest break, maximum temperature record, OSM zoom level, hyperonym
    • External identifiers: Dimensions.guide ID, National Wrestling Hall of Fame University Team ID, Official Charts artist ID, Saxony-Anhalt protected area ID, AiF dossier ID, Google Play Movies & TV id, Brilliant Wiki ID, Musenor artwork ID, Indonesian Cultural Heritage Registration System ID, Florida Historical Marker List ID, ProQuest document ID, Klexikon-Article-ID, Libraries & Information Centers in the Czech Republic ID, Académie de Rouen member ID, Art Fund artwork ID, Cour des comptes report ID, MutualArt artist ID, National Book Foundation author ID, National Book Foundation book ID, Deportation Database transport ID, Dutch Instrument Makers ID, Lucerna person ID, Scripts.com script, Directorio Legislativo ID
  • New property proposals to review:
    • General datatypes: located in the constituency, feed-in tariff, General Material Designation, CDEC ID, Family progenitor, solar irradiance
    • External identifiers: film-documentaire.fr author ID, theatre-contemporain.net ID, SNISB ID, Rheinland-Pfalz Schutzgebiete-ID, Zagat, Zomato, Libreflix ID, JMdictDB ID, Bibliography of the History of the Czech Lands ID, EmacsWiki ID, FFS athlete ID, FSkate.ru skater ID, Plant Illustrations artist ID, FaroeSoccer coach ID, FaroeSoccer player ID
  • Deleted properties:
  • Query examples:
    • Calendar of Saints' feast days and other calendar queries
    • A bunch of new GLAM-related queries including image gallery of the most notable libraries and map of museums colour-coded by type.
    • the number of songs in Wikidata named after days of the week by day
    • Map of preserved Concorde aircrafts
    • Timeline of video games having at least 42 Wikipedia sitelinks (source)
    • Timeline of Microscopists (source)
    • Map of all the libraries in the world present on Wikidata (source)
    • People with songs named after them (source)
    • Animals most frequently depicted in artworks (source)
    • Field of work of the Austrian scientists with an Orcid ID (source)
  • Women from Africa sorted by number of sitelinks (source)

• Development
  • Work page to get the Schema Text by subpage syntax (phab:T214383)
  • Set up a page to set label, description and aliases for Schema (phab:T215392, phab:T217313)
  • Remove edit tab from Schema pages (phab:T215394)
  • Disable possibility to enter duplicate aliases for the same Schema (phab:T217634, phab:T217749)
  • Add ULS, Babel and CLDR support on wikidata-shex.wmflabs.org (phab:T216146)
  • Add the option to restore Schemas! (phab:T214915)
  • Undo edit on Schemas through API (phab:T217250)
  • Multilingual support on Special:NewSchema (phab:T216154)
  • Work on Termbox SSR integration (phab:T214679)
  • Provide meta tags for lexemes (phab:T206414)
  • Make Quickstatements work out of the box in wikibase docker image (phab:T205606)
  • Disabling RDF for Media Info (phab:T213483)
  • Add tooltips for statements linking to a lexeme form (phab:T205279)
  • Allowing multiple wikibase DBs access (phab:T214557)
  • Add baserevid to WikibaseLexeme API (phab:T217243)

You can see all open tickets related to Wikidata here. If you want to help, you can also have a look at the tasks needing a volunteer.

• Monthly Tasks
  • Add labels, in your own language(s), for the new properties listed above.
  • Comment on property proposals: all open proposals
  • Suggested and open tasks!
  • Contribute to a Showcase item.
  • Help translate or proofread the interface and documentation pages, in your own language!
  • Help merge identical items across Wikimedia projects.
  • Help write the next summary!

Read the full report · Unsubscribe · Lea Lacroix (WMDE) 15:55, 11 March 2019 (UTC)