In the article "Presenting Wikidata knowledge" [1], I've Been a bit Bold and specified a recipe:
1. Find existing interesting wiki pages in the domain of your application. 2. View the Wikidata information for those pages, choose interesting properties. 3. Associate Wikidata entity IDs with entities of your application. 4. Display their Wikidata information in the user's language. 5. Use the Wikidata "sitelinks" information about the item to provide links to the full Wikipedia (and Wikiquote, Wikivoyage, etc.) article about the entity in the user's language.
But I realize for something like a reference app there won't be Wikidata items for every entity in your app for step 3: not every book in print has a Wikidata item, nor does every musical recording, etc. For those there are already identifiers such as ISBNs and "MusicBrainz release group ID"s (mmm, brains). I assume reference app developers already use these more complete identifiers and so I'm inviting them to add Wikidata entity IDs where available.
I think these other identifiers are all "Wikidata property representing a unique identifier" and there are about 350 of them [2] But surprisingly, I couldn't find an easy way to look up a Wikidata item using these other identifiers.
I found you can do it one-by-one in Wikidata Query [3] and in Wikidata Query Serivce [4] but neither seems amenable to doing a query on the fly "Get me the Wikidata item for each of these 100 ISBNs "2-7071-1620-3", ...
Also, is this a temporary thing? Will Wikidata eventually have items for every book published, every musical recording, etc. and become a superset of all those unique identifiers?
Thanks!
[1] https://www.mediawiki.org/wiki/API:Presenting_Wikidata_knowledge [2] https://www.wikidata.org/wiki/Special:WhatLinksHere/Q19847637?limit=500 [2] https://wdq.wmflabs.org/api?q=string%5B957:%222-7071-1620-3%22%5D and [3] https://query.wikidata.org with the the SPARQL (mmm, sparkly) PREFIX wdt: http://www.wikidata.org/prop/direct/
SELECT ?book WHERE { ?book wdt:P957 "2-7071-1620-3" }
Hi!
I found you can do it one-by-one in Wikidata Query [3] and in Wikidata Query Serivce [4] but neither seems amenable to doing a query on the fly "Get me the Wikidata item for each of these 100 ISBNs "2-7071-1620-3", ...
At least in sparql, this would be easy to do:
PREFIX wdt: http://www.wikidata.org/prop/direct/ SELECT ?book ?isbn WHERE { VALUES ?isbn { "2-7071-1620-3" "2-7071-1620-4" "2-7071-1620-5" ... } ?book wdt:P957 ?isbn }
Unless I misunderstand what you mean here.
You could pass several ISBNs to wdq with OR (but I don't know if it will support 100 ISBNs in one go):
https://wdq.wmflabs.org/api?q=string%5B957:%222-7071-1620-3%22%5D%20OR%20STR...]
*Med vänliga hälsningar,Jan Ainali*
Verksamhetschef, Wikimedia Sverige http://wikimedia.se 0729 - 67 29 48
*Tänk dig en värld där varje människa har fri tillgång till mänsklighetens samlade kunskap. Det är det vi gör.* Bli medlem. http://blimedlem.wikimedia.se
2015-11-09 3:26 GMT+01:00 S Page spage@wikimedia.org:
In the article "Presenting Wikidata knowledge" [1], I've Been a bit Bold and specified a recipe:
- Find existing interesting wiki pages in the domain of your application.
- View the Wikidata information for those pages, choose interesting
properties. 3. Associate Wikidata entity IDs with entities of your application. 4. Display their Wikidata information in the user's language. 5. Use the Wikidata "sitelinks" information about the item to provide links to the full Wikipedia (and Wikiquote, Wikivoyage, etc.) article about the entity in the user's language.
But I realize for something like a reference app there won't be Wikidata items for every entity in your app for step 3: not every book in print has a Wikidata item, nor does every musical recording, etc. For those there are already identifiers such as ISBNs and "MusicBrainz release group ID"s (mmm, brains). I assume reference app developers already use these more complete identifiers and so I'm inviting them to add Wikidata entity IDs where available.
I think these other identifiers are all "Wikidata property representing a unique identifier" and there are about 350 of them [2] But surprisingly, I couldn't find an easy way to look up a Wikidata item using these other identifiers.
I found you can do it one-by-one in Wikidata Query [3] and in Wikidata Query Serivce [4] but neither seems amenable to doing a query on the fly "Get me the Wikidata item for each of these 100 ISBNs "2-7071-1620-3", ...
Also, is this a temporary thing? Will Wikidata eventually have items for every book published, every musical recording, etc. and become a superset of all those unique identifiers?
Thanks!
[1] https://www.mediawiki.org/wiki/API:Presenting_Wikidata_knowledge [2] https://www.wikidata.org/wiki/Special:WhatLinksHere/Q19847637?limit=500 [2] https://wdq.wmflabs.org/api?q=string%5B957:%222-7071-1620-3%22%5D and [3] https://query.wikidata.org with the the SPARQL (mmm, sparkly) PREFIX wdt: http://www.wikidata.org/prop/direct/
SELECT ?book WHERE { ?book wdt:P957 "2-7071-1620-3" }
-- =S Page WMF Tech writer
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Am 09.11.2015 um 03:26 schrieb S Page:
I think these other identifiers are all "Wikidata property representing a unique identifier" and there are about 350 of them [2] But surprisingly, I couldn't find an easy way to look up a Wikidata item using these other identifiers.
We discussed some loose plans for implementing this in Currus when Stas was in Berlin a few weeks ago. On Special:Search, you would ask for property:P212:978-2-07-027437-6, and that would find the item with that ISBN.
Stas: do we have a ticket for this somewhere? All I can find are the notes in the etherpad.
Also, is this a temporary thing? Will Wikidata eventually have items for every book published, every musical recording, etc. and become a superset of all those unique identifiers?
It's highly unlikely that wikidata will become a superset of any and all vocuabularies in existance. Better integration of external identifiers is high on our priority list right now. The first step will however be to property expose URIs for them, so we are no longer a dead end in the linked data web.
But since we need to work on Cirrus integration anyway, I expect that we will have search-by-property soonish, too. I certrainly hope so.
On 9 November 2015 at 08:45, Daniel Kinzler daniel.kinzler@wikimedia.de wrote:
Also, is this a temporary thing? Will Wikidata eventually have items for every book published, every musical recording, etc. and become a superset of all those unique identifiers?
It's highly unlikely that wikidata will become a superset of any and all vocuabularies in existance.
Agree.
*However*, there are some things where we may be able to say with confidence "Wikidata has a comprehensive set of X" (eg catalogues such as P1186). It might be worth thinking about whether we should record these identifier properties as "will always be incomplete", "probably complete", "expected to eventually be complete", etc. If a user queries for an ISBN we don't have, the chances are high that it's a good ISBN we don't cover - but if they query for a country code we don't have, the chances are high that it's an invalid code...
Hoi, What we could do for particular searches is to fallback on other resources that are known to be complete. When we do not find an ISBN, we can fall back to library systems, local libraries preferably.
There are many ways we can make a difference. When we do this for one field of knowledge at a time, it will entice people to do more for their own field. Thanks, GerardM
On 9 November 2015 at 10:28, Andrew Gray andrew.gray@dunelm.org.uk wrote:
On 9 November 2015 at 08:45, Daniel Kinzler daniel.kinzler@wikimedia.de wrote:
Also, is this a temporary thing? Will Wikidata eventually have items
for every
book published, every musical recording, etc. and become a superset of
all those
unique identifiers?
It's highly unlikely that wikidata will become a superset of any and all vocuabularies in existance.
Agree.
*However*, there are some things where we may be able to say with confidence "Wikidata has a comprehensive set of X" (eg catalogues such as P1186). It might be worth thinking about whether we should record these identifier properties as "will always be incomplete", "probably complete", "expected to eventually be complete", etc. If a user queries for an ISBN we don't have, the chances are high that it's a good ISBN we don't cover - but if they query for a country code we don't have, the chances are high that it's an invalid code...
--
- Andrew Gray andrew.gray@dunelm.org.uk
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 9 November 2015 at 09:28, Andrew Gray andrew.gray@dunelm.org.uk wrote:
It might be worth thinking about whether we should record these identifier properties as "will always be incomplete", "probably complete", "expected to eventually be complete", etc. If a user queries for an ISBN we don't have, the chances are high that it's a good ISBN we don't cover - but if they query for a country code we don't have, the chances are high that it's an invalid code...
Yes. We can do this with a property, to be applied to other properties; and an item for each of the categories you describe.
Will you propose the new property, or shall I?
I'll support it
On Mon, Nov 9, 2015 at 12:00 PM, Andy Mabbett andy@pigsonthewing.org.uk wrote:
On 9 November 2015 at 09:28, Andrew Gray andrew.gray@dunelm.org.uk wrote:
It might be worth thinking about whether we should record these identifier properties as "will always be incomplete", "probably complete", "expected to eventually be complete", etc. If a user queries for an ISBN we don't have, the chances are high that it's a good ISBN we don't cover - but if they query for a country code we don't have, the chances are high that it's an invalid code...
Yes. We can do this with a property, to be applied to other properties; and an item for each of the categories you describe.
Will you propose the new property, or shall I?
-- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
Please do, if you have a good idea how it would work!
A.
On 9 November 2015 at 11:00, Andy Mabbett andy@pigsonthewing.org.uk wrote:
On 9 November 2015 at 09:28, Andrew Gray andrew.gray@dunelm.org.uk wrote:
It might be worth thinking about whether we should record these identifier properties as "will always be incomplete", "probably complete", "expected to eventually be complete", etc. If a user queries for an ISBN we don't have, the chances are high that it's a good ISBN we don't cover - but if they query for a country code we don't have, the chances are high that it's an invalid code...
Yes. We can do this with a property, to be applied to other properties; and an item for each of the categories you describe.
Will you propose the new property, or shall I?
-- Andy Mabbett @pigsonthewing http://pigsonthewing.org.uk
Wikidata mailing list Wikidata@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikidata
On 9 November 2015 at 12:40, Andrew Gray andrew.gray@dunelm.org.uk wrote:
Please do, if you have a good idea how it would work!
Done:
https://www.wikidata.org/wiki/Wikidata:Property_proposal/Property_metadata#E...
Am 09.11.2015 um 09:45 schrieb Daniel Kinzler:
Stas: do we have a ticket for this somewhere? All I can find are the notes in the etherpad.
Lydia just found the ticket for me: https://phabricator.wikimedia.org/T99899
I'll add some notes from the etherpad.