libraries and linked data: looking to the future (2)
DESCRIPTION
TRANSCRIPT
![Page 1: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/1.jpg)
AFTER MARC: OPTIONSNew bibliographic framework
![Page 2: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/2.jpg)
Aside: what we need to do
• Identify the resources we are describing, e.g. http://lccn.loc.gov/agr52000278
• Identify the data elements we are using, e.g. http://rdvocab.info/Elements/title
• Identify (where possible) the information of our description, e.g. http://www.geonames.org/4984247/ann-arbor.html
![Page 3: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/3.jpg)
Aside: what we need to do
http://www.worldcat.org/oclc/474017053 http://viaf.org/viaf/27068555
http://purl.org/dc/terms/creator
![Page 4: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/4.jpg)
RDA scenarios
1. Relational/object-oriented2. Linked bibliographic and
authority records3. Flat file (no links)
5editor2rev.pdf
RDA Database Implementation Scenarios
![Page 5: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/5.jpg)
![Page 6: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/6.jpg)
![Page 7: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/7.jpg)
![Page 8: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/8.jpg)
New bibliographic framework scenarios
1. Go native2. Extract3. Serialize
according to Coyle
![Page 9: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/9.jpg)
Serialize
“To put data into a particular data format that can be stored or transmitted.”
![Page 10: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/10.jpg)
Serialize
dc:title=“Scheduling Ourselves to Death”dc:date=“2003”dc:description=“The use of office scheduling software has led to an increase in
meetings, to the point that I am definitely scheduled for meetings after retirement, and probably even after death. The fault is in the basic premise of the software: you are either in a meeting, or available to be in a meeting.”
dc:creator=“Karen Coyle”
key/value pairs
![Page 11: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/11.jpg)
Serialize
<dc:title>Scheduling Ourselves to Death</dc:title> <dc:date>2003</dc:date> <dc:description>The use of office scheduling software has led to an increase in meetings, to the point that I am definitely scheduled for meetings after retirement, and probably even after death. The fault is in the basic premise of the software: you are either in a meeting, or available to be in a meeting.</dc:description> <dc:creator>Karen Coyle</dc:creator>
XML
![Page 12: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/12.jpg)
Serialize
{ "title": "Scheduling Ourselves to Death", "date": "2003", "description": "The use of office scheduling software has led to an increase in meetings, to the point that I am definitely scheduled for meetings after retirement, and probably even after death. The fault is in the basic premise of the software: you are either in a meeting, or available to be in a meeting.", "creator": "Karen Coyle"}
JSON
![Page 13: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/13.jpg)
MARC & MARCXML
100 $a Coyle, Karen
245 $a Scheduling…
<datafield tag="100" ind1="1" ind2=" "><subfield code="a”>Coyle, Karen
</subfield></datafield>
<datafield tag="245" ind1="1" ind2="0">
<subfield code="a">Scheduling…</subfield></datafield>
![Page 14: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/14.jpg)
MARC to RDF
001 1234567
100 $a Coyle, Karen
245 $a Scheduling ourselves to death
![Page 15: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/15.jpg)
MARC to RDF
1234567 100 $a Coyle, Karen
1234567 245 $a Scheduling ourselves to death
![Page 16: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/16.jpg)
MARC to RDF
http://mystuff/1234567
100 $a Coyle, Karen
http://mystuff/1234567
245 $a Scheduling ourselves to death
![Page 17: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/17.jpg)
MARC to RDF
http://mystuff/1234567
http://mystuff/100$a
Coyle, Karen
http://mystuff/1234567
http://mystuff/245 $a
Scheduling ourselves to death
![Page 18: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/18.jpg)
MARC to RDF
http://mystuff/1234567
http://mystuff/100$a
Coyle, Karen
http://mystuff/1234567
http://mystuff/245 $a
Scheduling ourselves to death
subject URI relationship URI “Text”
![Page 19: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/19.jpg)
“things and strings”
id:1234 id:abcd
id:3n5bid:$%^&
“Herman Melville”
![Page 20: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/20.jpg)
MARC to RDF
http://mystuff/1234567
http://mystuff/100$a
Coyle, Karen
http://mystuff/1234567
http://mystuff/245 $a
Scheduling ourselves to death
http://mystuff/1234567
http://mystuff/830$v
457
http://mystuff/1234567
http://mystuff/100$d
1949
![Page 21: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/21.jpg)
advantages• mechanical• doesn’t change the data• doesn’t require system
changes
disadvantages• doesn’t change the data• keeps library data in a
library-only silo• doesn’t link to any data
outside of libraries
![Page 22: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/22.jpg)
Extract
id:1234 id:abcd
id:3n5bid:$%^&
“Herman Melville”
“things and strings”
database of MARC records
![Page 23: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/23.jpg)
What’s a “thing”?
![Page 24: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/24.jpg)
What’s a “thing”?
Family
Expression
PersonObjectWork
Manifestation
Item
Corp
Place
Concept
Event
FRBR
![Page 25: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/25.jpg)
![Page 26: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/26.jpg)
![Page 27: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/27.jpg)
![Page 28: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/28.jpg)
![Page 29: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/29.jpg)
![Page 30: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/30.jpg)
National Library of Spain (BNE)
![Page 31: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/31.jpg)
![Page 32: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/32.jpg)
![Page 33: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/33.jpg)
![Page 34: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/34.jpg)
![Page 35: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/35.jpg)
![Page 36: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/36.jpg)
OCLC “linked data”
• Uses microformats (RDFa and schema.org)
• Is embedded in the record display
• Was announced June 20, 2012
![Page 37: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/37.jpg)
Extract
Advantages• Does not require library
system changes• Can be re-extracted as we
learn more• Isn’t visible to catalogers
Disadvantages• Isn’t visible to catalogers, so
no human QC• Key identifiers are not part
of the base metadata• Limited by what we put into
records today
![Page 38: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/38.jpg)
“go native”
• things, elements and values that have URIs• a data design that stores things and
relationships• a creation interface that hides this from
creators but maintains the integrity of the data
![Page 39: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/39.jpg)
“go native”
Advantages• Interoperability with web
resources• Interoperability with intent
of RDA• Possibilities for a richer
library catalog, and one that does not require the user to choose between the library and the web as information resources
Disadvantages• Requries replacement of
library systems• Difficult to make the
cost/benefit argument
![Page 40: Libraries and Linked Data: Looking to the Future (2)](https://reader034.vdocument.in/reader034/viewer/2022051816/54593967af79594e128b4ea4/html5/thumbnails/40.jpg)
… MORE THOUGHTS?