Embedding ISNI and Wikidata in MARC

1. Embedding ISNI and Wikidata in MARC Paul Frank Chew Chiat Naun PCC OpCo 2019

2. Why put URIs in MARC? Long half-life of MARC “Linky MARC” as transition strategy More effective conversion to linked data Ability to use wider range of sources Ability to adopt mixed workflows

3. “Explore and advocate for the use of Wikidata identifiers (“Q IDs”) or equivalent uniform resource identifiers (URIs) in library and archival systems, repositories, and platforms.” -- ARL White Paper on Wikidata, April 2019

4. Recent changes in MARC $0 and $1 throughout MARC format, including authority 024 $4 for relator URIs $2 to indicate name vocabularies 758 for work IDs

6. 100 1_ $a Naarendorp, Frank $1http://isni.org/isni/000000038853085X 245 10 $a Hugo Kooks (1928-2011) : $b een progressieve leider in dienst van de Surinaamse gemeenschap in Amsterdam / $c Frank Naarendorp 260 __ $a Amsterdam : $b Vereniging Ons Suriname, $c 2018.

7. 610 24 $a Melbourne General Post Office $1 http://wikidata.org/entity/Q6811781

8. Opportunities Linking library authorities with external sources Direct use of alternative sources in cataloguing Reconciliation and enrichment of existing data Mixed MARC/non-MARC workflows

9. Why a pilot? Share information and experiences Understand use cases Learn by trial and error Road test best practices Assess tooling requirements, including implications for existing platforms Provide feedback to vendors, standards bodies

10. Examples of possible projects Faculty and institutional data Academic dissertation workflows Conversion of legacy authorities Embedding vendor sourced data

11. What do I need to participate? A project - a small-scale one is fine Availability to contribute to group discussions Willingness to document findings for broader community

12. Resources PCC ISNI pilot Formulating URIs URIs in MARC FAQ OCLC Technical bulletin 268 Connexion and Record Manager functionality Contact: naun_chew@harvard.edu