Presentation give to our local cataloging and discovery unit. The meeting discussed the current state of Linked Data in Libraries, as well as how we can experiment with tools like MarcEdit.

1. Terry Reese
reese.2179@osu.edu
http://marcedit.reeset.net
Preparing catalogers' for Linked
data Using MarcEdit: what can
we do now?

2.  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

4. Objects not strings
 Probably the biggest reason people talk about linked
data is the notion of moving from strings to objects
Strings

5. Objects not strings
 Probably the biggest reason people talk about linked
data is the notion of moving from strings to objects
Objects

6.  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

7. Best Practices

8.  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

9.  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

10.  Great Question!
 We aren’t ready
So why aren’t we doing this already?

11.  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?

12.  We can experiment
 We can start looking for ways to leverage data that is
being made available.
So what can we do right now?

13.  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

14.  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

15. Linked Data Tool

16.  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?

18. We can build new services
 Using Linked Data tools for
Heading Validation

19.  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

20.  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

21. Questions