that does not involve downloading large datasets from Property_proposal:Libris-URI
Description
Description
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Open | None | T199977 Test Federated search Wikidata SPARQL with TORA sparql (LIBRIS) | |||
| Stalled | None | T200065 Define Libris and Tora as endpoints in Wikidata | |||
| Stalled | None | T200067 Define Libris XL as an endpoint in Wikidata | |||
| Invalid | None | T201268 Get Libris <-> Wikidata in LOD - Linked Open Data Cloud | |||
| Resolved | Salgo60 | T200708 Property proposal/Libris-URI | |||
| Open | None | T200710 Libris XL: is there an easy way of looking up the new identifier based on the old one |
Event Timeline
Comment Actions
@Alicia_Fagerving_WMSE imported all of the new URIs so for the ids known to Wikidata it can be used as a hub for looking up the new uris based on the old ones.
For the ones not known to Wikidata we will have to wait for Libris.
Comment Actions
Since this popped up in my watched tasks... You can convert the old ID's to the new ones via the Libris API, for both authority posts and editions.
For authorities (SELIBR)
curl https://libris.kb.se/resource/auth/207435 -H "Accept: application/json"
yields
{
"@id": "https://libris.kb.se/zw9cd5zh025njcf",
"@type": "Record",
"sameAs": [{
"@id": "http://libris.kb.se/auth/207435"
}],
........And for editions
curl https://libris.kb.se/resource/bib/20008293 -H "Accept: application/json"
yields
{
"@id": "https://libris.kb.se/r93gg4j33dz3kt8",
"@type": "Record",
"sameAs": [{
"@id": "http://libris.kb.se/bib/20008293"
}],
.............