Open main menu

Wikidata:Property proposal/Libris-URI

Libris-URIEdit

Originally proposed at Wikidata:Property proposal/Authority control

   Done: Libris-URI (P5587) (Talk and documentation)
Descriptionidentifier for an item in the catalogue of the Swedish National Library
Data typeExternal identifier
Domainhuman (Q5) literary work (Q7725634) organization (Q43229)
ExampleAugust Strindberg (Q7724)tr574vdc33gk2cc
External linksUse in sister projects: [ar][de][en][es][fr][he][it][ja][ko][nl][pl][pt][ru][sv][vi][zh][commons][species][wd].
Planned useit will be used as P906
Number of IDs in source>50000
Expected completenessalways incomplete (Q21873886)
Formatter URLhttps://libris.kb.se/katalogisering/$1
See alsoP906

Motivation

The Swedish National Library is changing to a system using BIBFRAME and will have a new URI identifier that will be used in parallel with the old one Property_talk:P906.

Task T200708

 – The preceding unsigned comment was added by Salgo60 (talk • contribs) at 16:06, 8 June 2018‎ (UTC).

Discussion

  •   Support--VisbyStar (talk) 07:46, 9 June 2018 (UTC)
  •   Strong oppose the given formatter URL is to their public test environment. All existing items will also get an new URI that has a lot of benefits therefor there is no need to create a new property (source (in Swedish)). When this new system is live we could just update the existing property. Abbe98 (talk) 09:35, 9 June 2018 (UTC)
Abbe98 (talkcontribslogs) please call me I feel your comments is very confusing +46-70-5937579 I cant understand your logic. The main reason to store the new identifier in a new field is that it is a new identifier and you will avoid problems with other solutions who use Property P906 so they don't break. Suggesting an one time conversion ==> that you need to coordinate that with other people using Property P906 something not needed if we create a new property.
My thought is: 1. Create an new property 2. Populate it.... 3. When other solutions like VIAF is also using the new ID upgrade scripts and when we know todays Property P906 is not used maybe delete it
  1. New system is planned to go live on monday 11 june
  2. E.g. todays Libris ID is used by VIAF and I guess they will have both the old and new ID...
    1. We have scripts used today getting eg. LIBRIS ID from VIAF that will be broken if you do an one time conversion and reuse the name for the new content without a lot of coordination
      1. I use User:Magnus_Manske/authority_control.js that finds matches at VIAF and e.g. populate P906 With what is stored in viaf.org/processed/SELIBR.... if we do an one time conversion scripts like this need to be changed at the same time and maybe we need to wait until VIAF is updated
- Salgo60 (talk) 21:03, 9 June 2018 (UTC)
To get a second opinion I asked a question at the LIBRIS support forum link what they recommend and if they know what e.g. VIAF will do - Salgo60 (talk) 10:37, 10 June 2018 (UTC)
Task set up that maybe will impact how this property should be designed/used T200067 - Salgo60 (talk) 08:16, 20 July 2018 (UTC)
  •   Comment From a Wikidata perspective, I don't think we should replace P906 with different identifiers. A property for an identifier can be created without a formatter url being available.
    --- Jura 11:27, 10 June 2018 (UTC)
Yes I agree the "cost" of having 2 properties in WD when a system part of an rather complex and loosely coupled echo system like Bibliographic Authority control is a good guarantee that we don't get any surprises - Salgo60 (talk) 12:23, 10 June 2018 (UTC)
  •   Support A new property is needed since the old identifier will still be useful as it is used by many third parties (and will be for some time). It could however get an constraint saying that items with that property should always also have this new property. Sadly there does not seem to be an easy way of looking up the new identifier based on the old one that does not involve downloading large datasets. I'll check with the library later this month to see if there are any planned solutions for this. The formatter URI for RDF resource (P1921) should probably be https://libris.kb.se/$1 (the canonical URI), I haven't checked if it supports content negotiation but e.g. .ttl is reachable under https://libris.kb.se/tr574vdc33gk2cc/data.ttl. The domain in the proposal is likely too narrow as the library will use this identifier for DVDs, editions of works and possibly other concepts such as events. /André Costa (WMSE) (talk) 15:34, 30 July 2018 (UTC)
Easy way of looking up new identifier preffered would be to have a solution that is easily "plugged into" a script like User:Magnus_Manske/authority_control.js - Salgo60 (talk) 18:32, 2 August 2018 (UTC)

@Salgo60, André Costa (WMSE), VisbyStar, Abbe98, Jura1:   Done: Libris-URI (P5587). − Pintoch (talk) 09:40, 5 August 2018 (UTC)