View
1.500
Download
0
Tags:
Embed Size (px)
Citation preview
NISO Webinar: Experimenting with BIBFRAME:
Reports from Early Adoptersof Granular Discovery
Wednesday, April 8, 2015Speakers:
Nancy Fallgren Metadata Specialist Librarian, National Library of Medicine,
National Institutes of Health, US Department of Health and Human Services (DHHS)
Jeremy NelsonMetadata and Systems Librarian, Colorado College
Nancy LorimerHead, Metadata Dept, Stanford University Libraries
http://www.niso.org/news/events/2015/webinars/bibframe_adopters/
Nancy FallgrenCataloging and Metadata Management Secti on, TSD
Nati onal Library of MedicineNati onal Insti tutes of Health
U.S. Department of Health and Human Services
NISO WebinarApril 8, 2015
BIBFRAME Experimentation Update
Per LC Working Group on the Future of Bibliographic Control, U.S. RDA Test Coordinating Committee, and BIBFRAME primer --
Building a MARC Replacement +
3
Web based Rule agnostic
FlexibleExtensible
Useful beyond the bibliographic cataloging community
Broadly understandableUsable
LC Early Experimenters, October 2012-November 2013
LC Early Implementers Registration, April 2014Analysis of the Library of Congress’ published
BIBFRAME vocabulary using LC’s BIBFRAME editor (BFE) and LC’s MARC2BF conversion
Analysis of Zepheira’s BIBFRAME vocabulary using its Scribe and MARC2BF conversion
4
BIBFRAME at NLM
“The sheer number of metadata standards in the cultural heritage sector is overwhelming . . .”
- Jenn Riley, 2009-10 http://www.dlib.indiana.edu/~jenlrile/metadatamap/
5
LC Early Implementers Registration update, November 2014 Develop a BIBFRAME vocabulary based on
generating new data, rather than legacy data conversion
Create flexibility and extensibility for broad adoption with a ‘modular’ approach to BIBFRAMEDevelop a core BIBFRAME vocabulary that can be
extended with data elements or properties from existing descriptive metadata schema
BIBFRAME as a data interchange
6
BIBFRAME at NLM, Phase 2, Round 2
7
A Modular BIBFRAME Approach
Use the descriptive standards already developed by resource experts
Not focused on any one existing standard
Connect equivalent data across descriptive standards
Flex with changes to descriptive standards
8
A Data Interchange
RDA
VRA
PressOO
EAD
MODS
Dublin Core
Local Schema
. . .
BIBFRAME Core Data Elements
bf:titlebf:creatorbf:subject
bf:identifierbf:date
. . .
1. Compared and mapped Zepheira’s BF Lite vocabulary to PCC/RDA BIBCO Standard Record (PCC/RDA Core, updated 2/2015) as applicable to print monographs
2. Removed PCC/RDA Core elements that we believed would not be broadly used across cultural heritage communities, e.g., date of Expression
3. Mapped the resulting list to RDA RDF and other schema as needed (e.g., MODS RDF and Schema.org)
4. Added or revised definitions to enhance understanding
9
BIBFRAME Core Methodology
10
BF Property BF Definition RDA RDF/Other Scheme Property
bf:title Title of the resource rdaw:preferredTitleForTheWork
bf:startDate First date associated with the resource rdaw:dateOfWork
bf:language language(s) associated with the resource rdae:languageOfTheContent
bf:creator or Agent + bf:role
An entity (e.g., person, organization, etc.) associated with a resource
rdaw:creator, rdaw:otherPFCWork, and other Work creator roles
bf:contributor or Agent + bf:role
An entity (e.g., person, organization, etc.) associated with a resource
rdae:contributor and other appropriate contributor roles
bf:related a resource related to the origin resource rdaw:relatedWork
bf:authoritylinkActionable IRI linking to an authoritative controlled vocabulary rdaw:identifierForTheWork
bf:genre The 'is-ness' of the resource rdaw:formOfWork
bf:description Description of the content of the resource rdae:summarizationOfTheContent
bf:subjecta term or representative alphanumeric code which captures the ‘aboutness’ of a resource modsrdf:subject
bf:audience
class of user for which the content of a resource is intended, or for whom the content is considered suitable rdaw:intendedAudience
BIBFRAME Core is not PerfectComplete
Print monographs onlyNo items, holdings, or annotations
BIBFRAME Core is good enough to test the viability of a modular approach
If a modular vocabulary approach is adopted, we propose that a BIBFRAME Core vocabulary should be developed iteratively and collaboratively by multiple communities
11
Managing BIBFRAME Core Expectations
Collaborating with Zepheira and UC Davis to design a BIBFRAME cataloging user interface
Labels use RDA terminology, where it existsCatalogers add RDA RDF extensions from the RDA
registry as neededExtend BIBFRAME and RDA with other schema as
needed, e.g., modsrdf:subjectMapping to BIBFRAME takes place under the hood
Re-Thinking Cataloging Tools
12
13
Fictitious BIBFRAME/RDA Profile Cataloging Interface
Work DataPreferred Title For The WorkDate of Work
Language Of The Content
Creator
Expression Data
+ Add data elements
Summarization Of The Content
SubjectPlace Of Origin Of The Work
Contributor
+ Add data elements
14
Fictitious BIBFRAME/RDA Mapping from Cataloging Input
Work Datardaw:preferredTitleForTheWorkrdaw:dateOfWork
rdae:languageOfTheContent
rdaw:creator
Expression Data
+ Add data elements
rdae:summarizationOfTheContent
modsrdf:subjectrdaw:placeOfOriginOfTheWork
rdae:contributor
+ Add data elements
BF Workbf:title
bf:date
bf:creator
bf:subjectrdaw:placeOfOriginOfTheWork
bf:language
bf:description
bf:contributor
BF Instance
Jackie Shieh, George Washington UniversityBIBFRAME Core vocabulary development and data
modelingMarshall Nirenberg proof of concept project
Zepheira and UC Davis / BIBFLOW projectBF Lite / BIBFRAME Core vocabularyKuali OLE cataloging moduleCataloging user interface design
Library of CongressParallel experimentation using BIBFRAME in the creation of
new bibliographic data, expected Summer 2015
15
Collaborations
BIBFRAME for discovery; BIBFRAME for production… LINKED DATA FOR LIBRARIES; LINKED DATA FOR TECHNICAL SERVICES PRODUCTION
Nancy LorimerStanford UniversityExperimenting with Bibframe (NISO webinar)April 8, 2015
Linked Data for LibrariesLOD CONNECTING ACADEMIC INFORMATION RESOURCES
LD4L Project Outcomes
Create an open source extensible LD4L ontology for scholarly resources◦ Encompasses traditional MARC metadata, non-traditional metadata from
digital repositories and special collections, joined with contextual elements indicating community engagement
Create semantic editing, display, and discovery systems, that will support incremental ingest from multiple information sources
Project Hydra based interface, supporting search across multiple LD4L instances
Bibliographic Data• MARC• MODS• VRA• EAD
Person DataVIVO ORCIDISNIVIAF
Usage DataCirculation
CitationCurationExhibitsResearch GuidesSyllabiTags
LD4L Data Sources
LD4L
Ontology guiding principles
Be sufficiently expressive to encompass traditional catalog metadata of the 3 partners
Reuse appropriate parts of currently available ontologies rather than building a new, self-contained ontology
Prioritize the ability to convert references within library metadata records from “strings” to “things”
Seek out persistent global identifiers whenever possible
Conversion of bibliographic data
MARCBibliographic Data
BIBFRAME
Non-MARCBibliographic Data
LC converter
LD4L conversion
Other ontologies Library resources: BIBFRAME
Additional bibliographic types and partonomy relationships: FaBiO, Music Ontology, Schema
People/Organizations: VIVO-ISF (includes FOAF)
Annotations: OpenAnnotation
Provenance: PAV
Virtual Collections and Structured Relationships: OAI-ORE
Concepts: SKOS (or vocabularies such as Getty with stable URIs)
Many identifiers: VIAF, ORCID, ISNI, OCLC Works
Use Cases Annotations (Bibliographic + Curation data)
◦ 1.1 Build a Virtual Collection◦ 1.2 Tag Scholarly Resources to Support Reuse
Authorities (Bibliographic + Person data)◦ 2.1 Discover Works via People and their Relationships◦ 3.1. Discover Works via Locations and their Relationships◦ 3.2. Discover Works via Concepts and their Relationships
Linked Open Data (Leveraging External data)◦ 4.1 Leverage the Deeper graph◦ 5.1 Leverage Usage Data◦ 6.1 Cross-Institution Discovery
Linking the Cornell University Catalog and VIVO (Use Case 2)Discover Works via People and their Relationships
See and search on works by people to discover works of interest based on connection to people, and to understand people based on their relation to works
Demonstrate links between catalog and VIVO
Round-trip from catalog to VIVO and back to catalog
Sample data: Cornell thesis records
Linking hip-hop flyer data to MusicBrainz/LinkedBrainz (Use case 4)
Use Case 4: Leveraging the deeper graph
…making use of complex graph relationships via queries or patterns (rather than direct connections) to allow discovery that would not be possible without the semantics of different relationships between items and types of items included in the graph
Model non-MARC metadata to RDF
Use of LinkedBrainz URIs for performers to discover relationships to other entities…
Ontology decision—Flyers
Ontology decisions—events, performers
Ontology challenges Limitations of an work-centric model (BIBFRAME)
Pulling in other vocabularies
Granularity distinctions
Instability of the BIBFRAME model/vocabulary
From Data Conversion to Data Production
LD4L based on conversion from some other format◦ Not about original cataloging (where will we get that data in the future?)◦ Conversion is a complex process, with much post processing◦ Internal links in MARC lack formal structure and convert poorly
The next logical step:
WORK NATIVELY IN BIBFRAME!◦ Adapt technical services workflow to integrate linked data creation
Linked Data for Technical Services ProductionCREATING LINKED OPEN DATA WITH BIBFRAME
The Group of Six (Les Six)
Stanford
Cornell
Columbia
Harvard
Princeton
Library of Congress
Kuali OLE
Partners Cataloging vendors
◦ What can they do to supply linked data?◦ Can they enhance their MARC records to make conversion better
Authority vendors◦ Can we send them a linked data graph and receive URIs?
General Acquisitions vendors◦ EDI, shelf-ready?
Our ILS◦ How do we link with our acquisitions data?
OCLC◦ Sharing our data
Individual institutional interests
Stanford◦ Copy cataloging using vendor-supplied data◦ Original cataloging in most formats
Cornell◦ Hip-hop recordings, mostly non-commercial
Harvard◦ Geospatial data◦ Law
Columbia◦ Art objects
Stanford’s focus Copy cataloging
◦ Most of material comes this way◦ Will still require conversion for some time to come, and that will require
manual remediation◦ Who will do this?◦ How do we link to ILS?
Original cataloging◦ All our catalogers want to participate!so…◦ All formats!
CLOUD SPACE
The Cloudspace
Possible Outcomes Specifications for needed infrastructure
◦ Cloud space◦ Tools
Best practices for metadata creation◦ Profiles ◦ Use of cataloging standards in the linked data environment◦ How BIBFRAME coexists with other ontologies◦ Metrics for assessment of effort, added value, staffing levels & skills
A large pool of native BIBFRAME data for developers to use
Thank you…
LD4L demos (from 2015 workshop): https://wiki.duraspace.org/display/ld4l/LD4L+Workshop+Agenda
NISO Webinar • April 8, 2015
Questions?All questions will be posted with presenter answers on the NISO website following the webinar:
http://www.niso.org/news/events/2015/webinars/bibframe_adopters/
NISO Webinar Experimenting with BIBFRAME: Reports from Early Adopters
Thank you for joining us today. Please take a moment to fill out the brief online survey.
We look forward to hearing from you!
THANK YOU