User talk:PKM

From Wikidata
Jump to navigation Jump to search
Logo of Wikidata

Welcome to Wikidata, PKM!

Wikidata is a free knowledge base that you can edit! It can be read and edited by humans and machines alike and you can go to any item page now and add to this ever-growing database!

Need some help getting started? Here are some pages you can familiarize yourself with:

  • Introduction – An introduction to the project.
  • Wikidata tours – Interactive tutorials to show you how Wikidata works.
  • Community portal – The portal for community members.
  • User options – including the 'Babel' extension, to set your language preferences.
  • Contents – The main help page for editing and using the site.
  • Project chat – Discussions about the project.
  • Tools – A collection of user-developed tools to allow for easier completion of some tasks.

Please remember to sign your messages on talk pages by typing four tildes (~~~~); this will automatically insert your username and the date.

If you have any questions, please ask me on my talk page. If you want to try out editing, you can use the sandbox to try. Once again, welcome, and I hope you quickly feel comfortable here, and become an active editor for Wikidata.

Best regards! Liuxinyu970226 (talk) 06:21, 27 October 2014 (UTC)

Art UK venue ID (P1602)[edit]

Art UK venue ID (P1602) is ready. --Tobias1984 (talk) 18:04, 7 November 2014 (UTC)

Corrupted Bobbin lace item?[edit]

It looks like the Bobbin lace is somehow corrupt, editing does not work. As you seem to be the last to make changes, could that be the cause? Would you mind to undo? Poljo (talk) 08:35, 12 November 2014 (UTC)

Tried again and the save buttons reappeared. Sorry to have bothered you. Poljo (talk) 09:41, 12 November 2014 (UTC)

Juan de Alfaro y Gamez (Q2388565)[edit]

Hi PKM, I was wondering why you added multiple RKD claims? These all redirect to the same item. Multichill (talk) 22:09, 29 November 2014 (UTC)

@multichill: so the links would work both ways. Should we not do that? I can back them out. - PKM (talk) 02:14, 30 November 2014 (UTC)
These other links are like the redirects we have here: Don't delete them, but we keep them for convenience. The items are showing up in this report. Multichill (talk) 16:52, 30 November 2014 (UTC)

SIPA ID (P1700)[edit]

The property you requested is done. --Fralambert (talk) 03:08, 17 January 2015 (UTC)

@Fralambert: Thank you! - PKM (talk) 04:23, 17 January 2015 (UTC)

IGESPAR ID (P1702)[edit]

The property you requested is done. You can check the constraint in the talk page, to see if they are correct. --Fralambert (talk) 05:22, 17 January 2015 (UTC)

AAT white tie (tail coat)[edit]

Hi friend! About this revert: if you look at the non-EN articles (Фрак, Frac, Frak), they are about the formal coat. What would you match that AAT id to, if not this WD item?? --Vladimir Alexiev (talk) 12:57, 12 April 2017 (UTC)

Thanks :)[edit]

Hi

Just wanted to say thanks for all the matches you did on Mix n' Match for the UNESCO Atlas of World Languages in Danger dataset. I'm trying to get the dataset imported for the Wikipedia Language Conference in early July. Can I ask if you used any tricks to match so many or did you do it all by hand? It will be great once we also have the Glottolog database integrated as well but there are 15,000 matches to do for that one.....

Thanks again

--John Cummings (talk) 18:17, 24 June 2017 (UTC)

Adding the Glottolog catalogue to Wikidata[edit]

Hi

I started a discussion about matching the Glottolog catalogue a little more automatically on project chat that you might be interested in. I really don't want to have to match 15,000 items by hand :)

Thanks

--John Cummings (talk) 13:46, 26 June 2017 (UTC)

@John Cummings: Me neither. - PKM (talk) 18:34, 26 June 2017 (UTC)

Tidying up the Atlas of World Languages in Danger import[edit]

Hi

We've now done with Mix n' Match (mainly thanks to you). I think there are two steps left to clean the data up:

  1. Find items with multiple AWLD ID numbers, I think this will be caused by several dialects being misunderstood as the same thing. I think I should create an item for each dialect and then somehow link them using a property to the main item. Any ideas how to do this?
  2. Find multiple items with the same ID number, I think this will be caused by duplicate items.

Does this sound like a sensible plan? Am I missing something? Can you think what property I should use to link dialects and languages? I don't think its 'has part'. I'll ask on the project chat.

Thanks again

--John Cummings (talk) 19:59, 2 July 2017 (UTC)

@John Cummings: For the dialects I have added, I used has dialect (DEPRECATED) (P134) on the parent language and made the dialect(s) <subclass of> the parent. See Selkup (Q34008).
Whether a "child" language is a dialect or just a separate community of speakers is a challenge. I think we should ideally have some sort of source for saying X is a dialect of Y (in the UNESCO records or in the Wikipedia info box for the parent language).
Here's an example: For Mohawk (Q13339), UNESCO has seven codes based on places/communities, but the en:Mohawk language article describes three "main" dialects only one of which is immediately identifiable as "matching" one of the UNESCO languages (Kanesatake). There's probably no harm in calling each of these variants a "dialect" (after all, there is not always consensus among linguists as to whether a particular language is a dialect or some other sort of variant). It would probably be better to have the separate records and if there's ever a comprehensive languages project in WD, the future project team can tweak whether an item is a dialect or not.
I do think we need to make a minimal set of statements for any items we create in this way: <instance of> dialect (Q33384), subclass of [parent language], indigenous to (P2341) [place or ethnic group or both]. - PKM (talk) 21:39, 2 July 2017 (UTC)

Nappes d'autel[edit]

Thank you for your work with textiles in the Palissy database. I am going to look into English translations for the labels and descriptions of these.

The items with dénomination: nappe d'autel in the database would be better as instance of (P31) altar cloth (Q869547) instead of tablecloth (Q536168). Is that a change that your bot could make? - PKM (talk) 19:51, 1 August 2017 (UTC)

It's ok :
SELECT ?item ?label WHERE { ?item wdt:P31 wd:Q869547. }
Try it!
Gzen92 [discuter] 08:53, 5 August 2017 (UTC)

Missing creator with RKDimages link[edit]

Hi PKM, thanks for helping with Wikidata:WikiProject sum of all paintings/Missing creator with RKDimages link! Last week I created a lot of the missing painters so we should be able to match most of them with existing items. Help much appreciated. Multichill (talk) 14:24, 7 October 2017 (UTC)

You're welcome! - PKM (talk) 19:22, 7 October 2017 (UTC)
Just created Wikidata:WikiProject sum of all paintings/Top collections missing creator. We seem to have a slight backlog ;-)
14190 paintings without a creator set. The top two collection account for more than half of these. Multichill (talk) 13:55, 8 October 2017 (UTC)
@Multichill: Wow, okay! Challenge accepted. On it, also working on ~6000 geographic items in NARA catalog, so I’ll work on one until I get burnt out and then switch back and forth. That’s been productive for me. - PKM (talk) 18:27, 8 October 2017 (UTC)
Yeah, switching between jobs before you hate any of them is a good way to stay motivated. Just cherry pick the collection. Take for example the Royal Collection, it still has all the easy ones! Normally I would upload collection, match it up, go to the next collection. Here I uploaded a bunch of collections in a row so that's why we have some backlog. Multichill (talk) 21:27, 8 October 2017 (UTC)

re call to the bar[edit]

I have been thinking about this with regard to significant event, and I believe that we should be qualifying with applies to jurisdiction (P1001), and I have chosen for rather than England to use England and Wales (Q1156248), well at least for the historic records that I am doing.  — billinghurst sDrewth 01:51, 11 October 2017 (UTC)

Welcome to the Structured Commons focus group![edit]

Hello! Thank you very much for signing up to the community focus group for Structured Commons :-)

How to organize ourselves?

This focus group is new and experimental, and I welcome your tips and thoughts on how we can organize this in the most convenient and productive way. For now, I have posted a few separate topics on the focus group's talk page. Please add your questions there too! If we all add that page to our watchlist, that's probably a good way to stay up to date with current discussions. Steinsplitter has also initiated a brand new IRC channel specifically for Structured Commons: wikimedia-commons-sd (webchat) which we invite you to join. Please let me know if you have other ideas on how to work together.

Current updates

Warmly, your community liaison, SandraF (WMF) (talk)

Message sent by MediaWiki message delivery - 13:34, 25 October 2017 (UTC)

Structured Commons focus group update, Nov 21, 2017[edit]

Hello! You are receiving this message because you signed up for the the community focus group for Structured Commons :-)

IRC office hour today, 21 November, 18.00 UTC
  • The IRC office hour about Structured Commons takes place at 18:00 UTC in wikimedia-office webchat. Amanda, Ramsey and I will give updates about the project, and you can ask us questions. The log will be published afterwards.
Tools update

Many important community tools for Commons and Wikidata will benefit from an update to structured data in the future. You can help indicate which tools will need attention:

Warmly, your community liaison SandraF (WMF) (talk) 16:26, 21 November 2017 (UTC)

Structured Commons focus group update, December 11, 2017[edit]

Hello! You are receiving this message because you signed up for the community focus group for Structured Commons :-)

Later this week, a full newsletter will be distributed, but you are the first to receive an update on new requests for feedback.

Three requests for feedback
  1. We received many additions to the spreadsheet that collects important Commons and Wikidata tools. Thank you! Now, you can participate in a survey that helps us understand and prioritize which tools and functionalities are most important for the Wikimedia Commons and Wikidata communities. The survey runs until December 22. Here's some background.
  2. Help the team decide on better names for 'captions' and 'descriptions'. You can provide input until January 3, 2018.
  3. Help collect interesting Commons files, to prepare for the data modelling challenges ahead! Continuous input is welcome there.

Warmly, your community liaison SandraF (WMF) (talk)

Message sent by MediaWiki message delivery (talk) - 16:40, 11 December 2017 (UTC)

Structured Commons - Design feedback request: Multilingual Captions[edit]

Hello! You are receiving this message because you signed up for the the community focus group for Structured Data on Wikimedia Commons.

The Structured Data on Commons team has a new design feedback request up for Multilingual Captions support in the Upload Wizard. Visit the page for more information about the potential designs. Discussion and feedback is welcome there.

On a personal note, you'll see me posting many of these communications going forward for the Structured Data project, as SandraF transitions into working on the GLAM side of things for Structured Data on Commons full time. For the past six months she's been splitting time between the two roles (GLAM and Community Liaison). I'm looking forward to working with you all again. Thank you, happy editing. Keegan (WMF) (talk) 15:09, 24 January 2018 (UTC)

Structured Data feedback - What gets stored where (Ontology)[edit]

Greetings,

There is a new feedback request for Structured Data on Commons (link for messages posted to Commons: , regarding what metadata from a file gets stored where. Your participation is appreciated.

Happy editing to you. Keegan (WMF) (talk) 22:58, 15 February 2018 (UTC)

First structured licensing conversation on Commons[edit]

Greetings,

The first conversation about structured copyright and licensing for Structured Data on Commons has been posted, please come by and participate. The discussion will be open through the end of the month (March). Thank you. -- Keegan (WMF) (talk) 17:26, 16 March 2018 (UTC)

Share your experience and feedback as a Wikimedian in this global survey[edit]

WMF Surveys, 18:57, 29 March 2018 (UTC)

Reminder: Share your feedback in this Wikimedia survey[edit]

WMF Surveys, 01:40, 13 April 2018 (UTC)

Multilingual captions testing is available[edit]

Greetings,

The early prototype for multilingual caption support is available for testing. More information on how to sign up to test is on Commons. Thanks, happy editing to you. - Keegan (WMF) (talk) 17:06, 24 April 2018 (UTC)

Representation of Wikidata at the Wikimedia movement strategy process[edit]

Hi PKM, I'm contacting you because I would like your support and your comments on my proposal to represent the Wikidata community at the Wikimedia movement strategy process. I'm contacting you in private because you are a member of the Wikidata Community User Group and I thought that this could be relevant for you.--Micru (talk) 17:26, 19 June 2018 (UTC)

Structured Data on Commons IRC Office Hour, Tuesday 26 June[edit]

Greetings,

There will be an IRC office hour for Structured Data on Tuesday, 26 June from 18:00-19:00 UTC in #wikimedia-office. You can find more details, as well as date and time conversion, at the IRC Office Hours page on Meta.

Thanks, I look forward to seeing you there if you can make it. -- Keegan (talk) 20:54, 25 June 2018 (UTC)

What properties does Commons need?[edit]

Greetings,

Structured Commons will need properties to make statements about files. The development team is working on making the software ready to support properties; the question is, what properties does Commons need?

You can find more information and examples to help find properties in a workshop on Commons. Please participate and help fill in the list, and let me know if you have any questions. Thanks! -- Keegan (WMF) (talk) 18:53, 28 June 2018 (UTC)

Mapping relation type[edit]

Sorry not to have picked up your question at Project Chat earlier, re mapping relation type (P4390).

My honest answer is: I have no idea. I simply don't know what sort of relations should be considered close match (Q39893184). It is good to have clarified that the match is not exact match, broader match, or narrower match. What does that leave? close match (Q39893184) and related match (Q39894604). What do these mean? The platypus/eggs example [1] given by w3.org for related match (Q39894604) seems a lot more distant; but might be right.

It would be useful to find some more examples of close match (Q39893184) in the wild, in professionally-made thesauruses, to get a better idea of how exactly it is customarily used -- what sort of relationships, that aren't superset/subset/exact match.

Pinging @Vladimir Alexiev, Jneubert: who I think have rather deeper experience in this area. Jheald (talk) 14:01, 12 July 2018 (UTC)

@Jheald: Example of closeMatch: some Peoples to their Culture or Language (AAT has more Cultures than WD). relatedMatch is just any associative relation, like skos:related but between thesauri --Vladimir Alexiev (talk) 21:21, 22 July 2018 (UTC)


Sorry, too, for having missed your question, and thanks to Jheald for pinging.
If I got you right, you interpret AATs S-Twist as a class, and you want to make clear that this is differerent from the intended use of S-twist (Q55296333) as a property value. Well, if your interpretation of AAT is right (I'm no AAT expert), that could be done, but I'm not sure if it's worth the hazzle: Apparently, both seem to designate the same thing, and I wouldn't expect that the subtle distinction really helps users who come across the external id entry. -- But this is my personal take on the example.
As for the more general question about the use of "close match" and "related match": They may cover diverse cases, and often the descision if something is the same or close or broder/narrower or related can be disputed. Examples of the use of mapping relation type (P4390) exist in an ongoing and still quite incomplete approach of mapping STW Thesaurus for Economics (Q26903352) to Wikidata. For maintenance, I've created a list of all non-exact relationships (with a link to search Wikidata for possible newly introduced better matches). Sometimes differences between the Wikidata item and the external concept are subtle, sometimes obvious. E.g., Wikidatas Yugoslavia (Q36704) covers, according to its English description, the "1918–1992 country", while the close-matching STW descriptor is Yugoslavia (until 1990). An example for "related match" is the item Assessment center (Q265558), to which STW's Executive selection is related. It's clearly not the same, and it is not of the same kind, too (instrument vs. process), so I wouldn't use "close match" here, but of course literature about Executive selection also covers the Assesment Centers as a prominent means, so the link should be helpful here. -- Hope this helps a bit. I'm happy to discuss more, here or at Property_talk:P3911 (or on the talk pages of mapped items, if only one item is concerned). Jneubert (talk) 17:58, 12 July 2018 (UTC)
@Jheald, Jneubert: Thank you both for your responses. You have confirmed my general understanding of the use of "close match"; thanks for that. As far as this specific item is concerned, I am probably overthinking things (again), but yes, we have been using AAT as guide or proxy for a class hierarchy of fashion objects, lacking any other. - PKM (talk) 20:46, 12 July 2018 (UTC)

buckle (Q1135567)[edit]

I actually think the fastener (Q2002016) as you changed me were a better superclass. joining technology (Q266328) does not seem to be about objects. Re-revert? What do you think? Cheers, --Marsupium (talk) 19:28, 15 July 2018 (UTC)

@Marsupium: Agreed! Changed it back. I'll making "buckling" for the technology. - PKM (talk) 19:31, 15 July 2018 (UTC)
Ah very good also the buckling (Q55568280)! :) --Marsupium (talk) 19:42, 15 July 2018 (UTC)
Hm, but http://vocab.getty.edu/page/aat/300072663 is something different. Perhaps rename to "buckle buckling"??? --Marsupium (talk) 19:44, 15 July 2018 (UTC)

And by the way could we better point out the difference between malespenne (Q19380920) and clasp (Q2239762) if there is one? :) --Marsupium (talk) 19:57, 15 July 2018 (UTC)

@Marsupium: AAT 300072663 is probably Buckling (Q693104), but I'd need to read the Enwiki article in detail. We have lots of items with the same label in English; I don't think it's a problem as long as we have good descriptions (in fact I think it's helpful for editors who are looking for the right item to link).
malespenne (Q19380920) is a specific type of Norwegian clasp called a Maljespenne. The Norwegian-English dictionaries I've found translate it just as "clasp". I expect the right move is to make 'maljespenne' the default EN label and make it a subclass of "clasp". WE do that with many non-English clothing items in EN wiki. I can do that now. - PKM (talk) 20:46, 15 July 2018 (UTC)
“I don't think it's a problem as long as we have good descriptions” Yes, you're right. The name is fine, yes!
Ah, that's good to know clasp (Q2239762) is the general clasp, so I will use it for c:Template:I18n/objects now, and it gets http://vocab.getty.edu/page/aat/300239507. Thank you! --Marsupium (talk) 21:11, 15 July 2018 (UTC)

complete edition (Q16968990) and complete works (Q1978454)[edit]

Did you check the only available sitelink before completely repurposing complete edition (Q16968990)? de:Gesamtausgabe refers to a book that collects all literary "completed works" (de:Gesamtwerk included in complete works (Q1978454)) of an author. Thanks to your edits, the item has currently no correlation with the only sitelink contained in it. Andreasm háblame / just talk to me 23:42, 30 July 2018 (UTC)

@Andreasmperu: Sorry to have caused this problem. Can you suggest a better way to separate "complete works" and "collected works" since they are not the same thing? I know that the labels in some languages on "collected works" translate literally "complete works" (probably based on the translations in the Getty AAT. Would you suggest moving the site link, or some other solution?

- PKM (talk) 00:10, 31 July 2018 (UTC)

No problem. Gesamtausgabe literally translates as "complete edition", whereas Gesamtwerk refers to "complete works". No idea who came out with the label "collected works", but it is not precise (although it could be clarified in the descriptions). complete edition (Q16968990) should be a subclass of an edition or a book, i.e. literary works of an author collected in one place. That is why complete edition (Q16968990) used to be a subclass of book, but also a subclass of complete works (Q1978454) (this item is not just limited to literary works, but could be anything created by one single person). Andreasm háblame / just talk to me 00:25, 31 July 2018 (UTC)
@Andreasmperu: I will revert my changes then, and change the English label. Based on your explanation, it seems to me that the AAT link should be moved to "complete works" which totally resolves the problem of these things "said to be the same". Would you agree? - PKM (talk) 14:32, 31 July 2018 (UTC)
Further - based on the structure at Wikidata:WikiProject Books, complete edition (Q16968990) should be a subclass of version, edition, or translation (Q3331189) rather than "complete works" - "works" (the intellectual content} and "books" (the publications that house works) are separate hierarchies. Would you be okay with that change? (It would be consistent with limited edition (Q6549529), critical edition (Q680458) and diplomatic edition (Q5394558).) - PKM (talk) 14:52, 31 July 2018 (UTC)
Hi, I’ve just checked the FRBR ontology, and realised that both “collected works” and “complete works” mentioned in there refer to a collection of literary works, whereas in the case of Wikidata items only complete edition (Q16968990) is circumscribed to literary works (complete works (Q1978454) deals about all possible works including literary ones, but also musical ones for instance). So, no I don’t think the exact match of Complete Works is correct as it is now, but it should rather be with complete edition (Q16968990), even though the label seems to point the relation into the other item. Maybe a solution would be to have the same label for both items, given that “complete edition” doesn’t sound that familiar in English (I might be wrong on this, of course), and make the distinction on the descriptions. A new item that corresponds with “collected works” (only literary ones) would need to be created to match the FRBR ontology, because currently there is no equivalent.
As for your second point, yes, I agree. Edition is closer to the meaning. --Andreasm háblame / just talk to me 15:59, 31 July 2018 (UTC)
@Andreasmperu:. Good points. FaBio, the FRBR ontology has "complete works" = "A collection of all the literary or scholastic works of a single person", but you're right, not including music or drawings or whatever. Your proposal sounds good - please go ahead and make those changes, since you seem pretty clear on what you want it to look like. And I agree, "complete works" with aliases "collected works", "complete edition" sounds good to me. - PKM (talk) 19:05, 31 July 2018 (UTC)

Structured Data feedback - Depicts statements draft requirements[edit]

Greetings,

A slide presentation of the draft requirements for depicts statements on file pages is up on Commons. Please visit this page on Commons to review the slides and discuss the draft. Thank you, see you on the talk page. -- Keegan (WMF) (talk) 21:20, 7 August 2018 (UTC)

Highland[edit]

Hi PKM! I didn't quite understand this edit (diff) on Highland (Q208279). The statements on the Wikidata item appear to be those for a geographic area, so the original sitelink en:Highland (council area) would seem to be correct. If en:The_Highland_Council was unlinked, it would seem appropriate to create a new item for it, connected to the previous by applies to jurisdiction (P1001); with legislative body (P194) or perhaps authority (P797) in the inverse direction. Similarly for City of Edinburgh (Q2379199). Jheald (talk) 21:04, 9 August 2018 (UTC)

@Jheald: Ah, I was going through enwiki articles with no Wikidata item. You're right, I should make those changes. - PKM (talk) 21:11, 9 August 2018 (UTC)
btw, if you happened to be anywhere near Inverness or Highland in the next three weeks (as opposed to your usual 7000 miles away), we just got in to Mrs Jheald's house above Loch Ness this afternoon, and you would be most welcome. Jheald (talk) 21:14, 9 August 2018 (UTC)
@Jheald:Thank you, that would be a treat! But alas, 7000 miles and one expired passport away. Enjoy! - PKM (talk) 21:17, 9 August 2018 (UTC)
@Jheald: Argh, Highland Council (Q28530249) already exists and Duplicity (or my eyes) missed it. This one is all fixed now I think. - PKM (talk) 21:27, 9 August 2018 (UTC)

Structured Data feedback - structured licensing and copyright[edit]

Mockups of structured licensing and copyright statements on file pages are posted. Please have a look over the examples and leave your feedback on the talk page. -- Keegan (WMF) (talk) 20:32, 7 September 2018 (UTC)

New discussion on Commons talk:Structured data[edit]

Hello. I've started a new, important discussion about creating properties for Commons on Wikidata. Please come join in, if the process is something that interests you or if you can help. Keegan (WMF) (talk) 16:48, 19 September 2018 (UTC)