Change Details

**Question LIBRIS** Asked question 10 jun 2018 to LIBRIS about [[ https://kundo.se/org/librisxl/d/viaf-libris-uri-gamla-librisnumret-plantankar-for-/ | plans VIAF/LIBRIS link ]] **Answer:** dont know right now - Anna Berggren Product owner and Libris-coordinator **Question OCLC 21 oct 2018 06:37: **about plans **Answer Moreno,Hayley <morenoh@oclc.org> 6 dec. 2018 18:33** //We are aware of this change and are in discussions with the National Library of Sweden on updating their links in the VIAF database. We hope to have this implement this change in the future. // == Odd things at VIAF and no announcement As we are start seeing odd things in VIAF regarding LIBRIS with both old IDs and new IDs - URI new question [[ https://kundo.se/org/librisxl/d/viaf-libris-uri/ | asked 28 Apr 2019 ]] {F29051755,width=800} VIAF [[ https://viaf.org/viaf/8167155566470213380005/ | 8167155566470213380005 ]] LIBRIS [[ https://viaf.org/processed/SELIBR%7C9k6xhg7d75gscx47 | https://viaf.org/processed/SELIBR%7C9k6xhg7d75gscx47 ]] i.e. New LIBRIS id in the old field OCLC links back to LIBRIS [[ https://libris.kb.se/resource/auth/9k6xhg7d75gscx47 | 9k6xhg7d75gscx47 ]] ==> get error in LIBRIS **Answer in two emails from Anna LIBRIS 2019-05-xx**: yes there is a problem that is reported to VIAF (Magnus comment: no task id or description) === Record with error * LIBRIS XL = [[ https://libris.kb.se/katalogisering/9k6xhg7d75gscx47 | 9k6xhg7d75gscx47 ]] * WIkidata [[ https://www.wikidata.org/wiki/Q6063138 | Q6063138 ]] * VIAF = [[ https://viaf.org/viaf/8167155566470213380005/ | 8167155566470213380005 ]] {F29051752,width=900} === See also * When implementing Linked data solutions lesson learned is that we need a dialogue and tools I have created an EPIC see {{T202530}} = Change management is needed I guess this is an example f the more complex Authority Ecosystem we will see and we need * Change management ** Unique identifiers for all open tasks so we can track them ** Public Workboards so we can coordinate who is ding what and when ** A prioritized public backlog --> we understand what and when things are done ** Possibility to subscribe on tasks to get notified

**Question LIBRIS** Asked question 10 jun 2018 to LIBRIS about [[ https://kundo.se/org/librisxl/d/viaf-libris-uri-gamla-librisnumret-plantankar-for-/ | plans VIAF/LIBRIS link ]] **Answer:** dont know right now - Anna Berggren Product owner and Libris-coordinator **Question OCLC 21 oct 2018 06:37: **about plans **Answer Moreno,Hayley <morenoh@oclc.org> 6 dec. 2018 18:33** //We are aware of this change and are in discussions with the National Library of Sweden on updating their links in the VIAF database. We hope to have this implement this change in the future. // == Odd things at VIAF and no announcement As we are start seeing odd things in VIAF regarding LIBRIS with both old IDs and new IDs - URI new question [[ https://kundo.se/org/librisxl/d/viaf-libris-uri/ | asked 28 Apr 2019 ]] {F29051755,width=800} VIAF [[ https://viaf.org/viaf/8167155566470213380005/ | 8167155566470213380005 ]] LIBRIS [[ https://viaf.org/processed/SELIBR%7C9k6xhg7d75gscx47 | https://viaf.org/processed/SELIBR%7C9k6xhg7d75gscx47 ]] i.e. New LIBRIS id in the old field OCLC links back to LIBRIS [[ https://libris.kb.se/resource/auth/9k6xhg7d75gscx47 | 9k6xhg7d75gscx47 ]] ==> get error in LIBRIS **Answer in two emails from Anna LIBRIS 2019-05-xx**: yes there is a problem that is reported to VIAF (Magnus comment: no task id or description) === Record with error * LIBRIS XL = [[ https://libris.kb.se/katalogisering/9k6xhg7d75gscx47 | 9k6xhg7d75gscx47 ]] * WIkidata [[ https://www.wikidata.org/wiki/Q6063138 | Q6063138 ]] * VIAF = [[ https://viaf.org/viaf/8167155566470213380005/ | 8167155566470213380005 ]] {F29051752,width=900} === See also * When implementing Linked data solutions lesson learned is that we need a dialogue and tools I have created an EPIC see {{T202530}} = Change management is needed I guess this is an example of the more complex Authority Ecosystem we will see and we need * Change management ** Unique identifiers for all open tasks so we can track them ** Public Workboards so we can coordinate who is doing what and when ** A prioritized public backlog --> we understand what and when things are done ** Possibility to subscribe and get notified when tasks change

**Question LIBRIS** Asked question 10 jun 2018 to LIBRIS about [[ https://kundo.se/org/librisxl/d/viaf-libris-uri-gamla-librisnumret-plantankar-for-/ | plans VIAF/LIBRIS link ]] **Answer:** dont know right now - Anna Berggren Product owner and Libris-coordinator **Question OCLC 21 oct 2018 06:37: **about plans **Answer Moreno,Hayley <morenoh@oclc.org> 6 dec. 2018 18:33** //We are aware of this change and are in discussions with the National Library of Sweden on updating their links in the VIAF database. We hope to have this implement this change in the future. // == Odd things at VIAF and no announcement As we are start seeing odd things in VIAF regarding LIBRIS with both old IDs and new IDs - URI new question [[ https://kundo.se/org/librisxl/d/viaf-libris-uri/ | asked 28 Apr 2019 ]] {F29051755,width=800} VIAF [[ https://viaf.org/viaf/8167155566470213380005/ | 8167155566470213380005 ]] LIBRIS [[ https://viaf.org/processed/SELIBR%7C9k6xhg7d75gscx47 | https://viaf.org/processed/SELIBR%7C9k6xhg7d75gscx47 ]] i.e. New LIBRIS id in the old field OCLC links back to LIBRIS [[ https://libris.kb.se/resource/auth/9k6xhg7d75gscx47 | 9k6xhg7d75gscx47 ]] ==> get error in LIBRIS **Answer in two emails from Anna LIBRIS 2019-05-xx**: yes there is a problem that is reported to VIAF (Magnus comment: no task id or description) === Record with error * LIBRIS XL = [[ https://libris.kb.se/katalogisering/9k6xhg7d75gscx47 | 9k6xhg7d75gscx47 ]] * WIkidata [[ https://www.wikidata.org/wiki/Q6063138 | Q6063138 ]] * VIAF = [[ https://viaf.org/viaf/8167155566470213380005/ | 8167155566470213380005 ]] {F29051752,width=900} === See also * When implementing Linked data solutions lesson learned is that we need a dialogue and tools I have created an EPIC see {{T202530}} = Change management is needed I guess this is an example of the more complex Authority Ecosystem we will see and we need * Change management ** Unique identifiers for all open tasks so we can track them ** Public Workboards so we can coordinate who is doing what and when ** A prioritized public backlog --> we understand what and when things are done ** Possibility to subscribe on tasks to get notifiedand get notified when tasks change