On 9 November 2015 at 12:40, Andrew Gray wrote:
> Please do, if you have a good idea how it would work!
Done:
https://www.wikidata.org/wiki/Wikidata:Property_proposal/Property_metadata#Expected_completeness
--
Andy Mabbett
@pigsonthewing
Please do, if you have a good idea how it would work!
A.
On 9 November 2015 at 11:00, Andy Mabbett wrote:
> On 9 November 2015 at 09:28, Andrew Gray wrote:
>
>> It might be worth thinking about whether we should record
>> these identifier
On 9 November 2015 at 09:28, Andrew Gray 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
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
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
On 9 November 2015 at 08:45, Daniel Kinzler 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
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
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%20STRING[957:%222-7071-1562-2%22]
*Med vänliga hälsningar,Jan Ainali*
Verksamhetschef, Wikimedia Sverige
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
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:
10 matches
Mail list logo