Preparing Catalogers for Linked data

Terry [email protected]

http://marcedit.reeset.net

Preparing catalogers' for Linked data Using MarcEdit: what can

we do now?

It seems like the profession has been talking about linked data and linked data in library for a long-time

And they have

There are wild promises Linked Data will solve our data problems Linked Data will make cataloging easier Linked Data will stop climate change and bring back the

dinosaurs (That’s how they grew dinosaurs in Jurassic Park)

Why Linked Data

Objects not strings Probably the biggest reason people talk about linked

data is the notion of moving from strings to objectsStrings=100 1\$aNeustadt, Richard E.=650 \0$aSwine influenza$xVaccination$zUnited States.=650 \0$aMedical policy$zUnited States.=650 \2$aInfluenza A virus$zUnited States.=650 \2$aInfluenza Vaccines$zUnited States.=650 \2$aInfluenza, Human$xprevention & control$zUnited States.=650 \2$aPublic Policy$zUnited States.=700 1\$aFineberg, Harvey V.,$eauthor.

Objects not strings Probably the biggest reason people talk about linked

data is the notion of moving from strings to objectsObjects=100 1\$aNeustadt, Richard E.$0http://id.loc.gov/authorities/names/n79007283$0http://viaf.org/viaf/17283877=650 \0$aSwine influenza$xVaccination$zUnited States.=650 \0$aMedical policy$zUnited States.$0http://id.loc.gov/authorities/subjects/sh2008107275=650 \2$aInfluenza A virus$zUnited States.$0http://id.nlm.nih.gov/mesh/D009980=650 \2$aInfluenza Vaccines$zUnited States.$0http://id.nlm.nih.gov/mesh/D007252=650 \2$aInfluenza, Human$xprevention & control$zUnited States.$0http://id.nlm.nih.gov/mesh/D007251=650 \2$aPublic Policy$zUnited States.$0http://id.nlm.nih.gov/mesh/D011640=700 1\$aFineberg, Harvey V.,$eauthor.$0http://id.loc.gov/authorities/names/n79002951$0http://viaf.org/viaf/75118372

URIs provide actionable data Controlled terms can be updated without user intervention

(generally) And URIs can provide access to more information

I.E. – a URI to VIAF provides access not just to author information, but to all their related works and collaborators as well.

Objects Not Strings

Best Practices

Currently – there is *no* supported method for embedding linked data elements into MARC21 Records

OCLC actively discourages users from embedding URIs and Linked Data elements into current bibliographic records (http://www.oclc.org/bibformats/en/6xx/650.html)

Of course, this isn’t stopping them from embedding their own data related to FAST into records

Best Practices

But hope is not lost… PCC has created the URIs in MARC Task Group

Charge: http://www.loc.gov/aba/pcc/documents/URIs-MARC-taskgroup.docx

This group is currently made up of PCC members, as well as consultants (like myself) to discuss how linked data elements could or should be made available within MARC data.

And give current practice, how do we ensure that existing data (which is linked data like, but not actionable) can be taken forward.

Best Practices

Great Question! We aren’t ready

So why aren’t we doing this already?

Changing Strings to Objects is hard and expensive Most Controlled vocabularies used in the Libraries are

not available for consumption by linked data tools And those that are aren’t production ready Or – are proprietary

So why aren’t we doing this already?

We can experiment

We can start looking for ways to leverage data that is being made available.

So what can we do right now?

Over the past year, I’ve added to MarcEdit a linked data framework

Designed to support RDF, JSON-LD, SPARQL – and a wide range of library specific services currently providing one off access to controlled data

The framework has been utilized in MarcEdit for the development of a toolset called MARCNext

MarcEdit and Linked Data

These are Experimental services that allow catalogers to play with their data and visualize it through the BibFrame lens – as well as begin the process of turning strings to objects.

MARCNext

Linked Data Tool

So yes, its all fine and good to provide experimental work – but does this help me now?

Well until the PCC and MARBI provide guidance related to URI generation and insertion – this is really something up to local practice.

But who cares?

We can build new services Using Linked Data tools for

Heading Validation

How it works Working directly with the U.S. Library of Congress – MarcEdit

queries the NACO and SACO headings directly Returning information about URIs and variants/changes

MarcEdit then generates a report, automatically corrects headings (when possible) and can generate brief authority records if desired.

Validate Headings

At every major ILS user conference this year, there was a commitment made to support BibFrame

What does that mean – who knows But what we do know, is that it means ILS vendors are looking at

how they can leverage linked data concepts within their systems

The PCC is committed to providing guidance around embedding linked data in library data by Summer ALA

OCLC’s WMS platform is being developed and positioned as a potential linked data service point

i.e. – OCLC Works, OCLC Persons, etc.

Looking to the Future

Questions