Transcript Seely and Carlson: Practical Applications of Linked Data Concepts

Practical Applications
of Linked Data Concepts
at Rice University's
Fondren Library
Amber Seely
Database & Metadata Management
Coordinator
Scott Carlson
Metadata Coordinator
Part 1: a Practical
Preparation Using
MARC’s Subfield 0
Subfield 0
• Early testers of BIBFRAME recommended
use of subfield 0 in MARC access points.
• Rules for |0 require an organizational code in
parentheses followed by a control number.
EX. 100 1_ Thompson, Janice, |d1962|0(LoC)n00000997
Bibframe testers recommend use of |0: http://hangingtogether.org/?p=4487
MARBI rules for |0: http://www.loc.gov/marc/marbi/2007/2007-06.html#p1
Automatic Authority
Processing
MarcEdit
•
•
•
•
It’s free!
It’s available at: http://marcedit.reeset.net/
It will make you a super-powerful cataloger
There is also a function under MARC Next
called Link Identifiers that will add $0
A Few Decisions to Make
• I chose to adopt a loose interpretation of “control
number” and use the URI for a record
o Example:
http://id.loc.gov/authorities/names/n00000
997
• I decided to ignore the requirement for the
parenthetical organizational code, since it is
understood within the URI
• I asked my system administrator suppress |0
from public display in the OPAC
Karen Coyle on $0: http://kcoyle.blogspot.ca/2013/07/linked-data-first-steps-catch-21.html
Steven Folsom on URIs in MARC:
https://docs.google.com/document/d/1fuHvF8bXH7hldY_xJ7f_xn2rP2Dj8o-Ca9jhHghIeUg/edit?pli=1
The Mechanics
• I wrote a Task list for authority records that
takes the control number from the 010, formats
it and creates a URI, then inserts it into the
1xx|0
• This is NOT a link resolver -- the program does
not go out to id.loc.gov and check the link
• However in the thousands of records I’ve tested,
less than 1% of the links do not work, and those
were due to an LC issue which has been resolved
Let Me Show You…
Back in the ILS…
Holt, Peter $c (Engineer) $0 http://id.loc.gov/authorities/names/no2015110250
And the next day…
Holt, Peter $c (Engineer) $0 http://id.loc.gov/authorities/names/no2015110250
$e author.
The Goal
Part 2: Verifying
Name Headings
Using Linked Data
Concepts in
OpenRefine
Background: Historical Images
Refine’s Reconciliation Mode
• Automatically matches known
headings in collections with thesauri
• Finds potential matches for
incorrectly formatted headings
• Alerts for headings not yet known in
thesauri
Our
reconciliation
purpose
≠
Refine’s
reconciliation
purpose
For this project, we simply
wanted to automatically
confirm that the headings
in our collection data
match our thesauri data.
Valid SKOS Labels Under “Concept”
• The Big Three:
–skos:prefLabel, skos:altLabel and
skos:hiddenLabel
• The Slightly-Less-Big Three:
–skos:broader, skos:narrower, and
skos:related
• The Way-Smaller Six:
–skos:scopeNote, skos:definition,
skos:example, skos:historyNote,
skos:editorialNote, and skos:changeNote
An RDF extension for Refine allows
us to reconcile data against a
locally-created RDF file, instead of
our nonexistent linked data
After some tweaks...
99.6% match
Okay, so
what next?
Name App
MarcEdit: http://marcedit.reeset.net/
Subfield 0 TaskList: https://github.com/redginn/subfield0
OpenRefine: http://openrefine.org
OpenRefine RDF Extension: http://refine.deri.ie
Rice Name App: http://namecheck.library.rice.edu/name/
Name App Git: https://github.com/unt-libraries/django-name
Amber Seely, Database & Metadata
Management Coordinator
[email protected]
Scott Carlson, Metadata Coordinator
[email protected]