Skip to end of banner
Go to start of banner

2024-09-24 Metadata Management Working Meeting @ WOLFcon 2024

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Next »

Meeting time: 11:00 AM BST

Meeting URL: See https://wolfcon2024.sched.com/event/1eeqO/metadata-management-sig-working-meeting (warning)Online participants have to login into Sched to see the Zoom room.

\uD83D\uDDD3 Date

✍️ Note taker

📹 Recording

To be announced

🗣️ Session agenda and notes

Item

Notes

Welcome and introduction

potential changes to Inventory to better support various non-MARC metadata. Related to pre-conference session https://wolfcon2024.sched.com/event/1eevQ/linked-data-production-foundations-where-are-we-now-where-are-we-going-how-do-we-get-there

Findings from the Linked Data Foundations session on September 23rd:

  • Instance metadata source: Can’t store source of record and source format in one property. Would be interesting to store the source (e.g. Libris) and the source format (e.g. MARC or JSON-LD). Felix' thoughts from 2020 on this: Metadata Source Codes -- Instance

  • The National Library of Sweden has identified more needs for their management of metadata:

    • Store statistical data

    • Can’t distinguish multiple languages (e.g. original language and language of translation)

    • Need more granularity when recording year of publication.

    • Need to store properties to retrieve records for bulk edit operations

  • Revisit the role of Inventory.

  • Do we need to store (more) URI’s in Inventory?

  • When looking at the source record via Actions > View source:

    • Should there be an option to switch between multiple serializations of a schema, e.g. MARC 21 plain, MARC 21 XML, JSON-LD, Turtle etc.

    • When looking at a linked data source record, should the URI’s display as is or should the actual values be retrieved and displayed? Maybe the latter would be more helpful to the staff user.

🧑‍💻 Chat

  • No labels