holdings in bibframe: a high level model
DESCRIPTION
Reviews the BIBFRAME model and holdings information fits in. Specifies the Holdings classes and properties established in the BIBFRAME vocabulary v. 1.0, made available by the Library of Congress in Jan. 2014. Reviews some holdings scenarios. This is a work in progress!TRANSCRIPT
Holdings in BIBFRAME: A High-level Model
Rebecca Guenther, Library of [email protected]
ALCTS CRS Holdings Information CommitteeJanuary 25, 2014
Outline• The BIBFRAME MODEL
– Core Classes– Relationships– Annotations
• Holdings in BIBFRAME– Multiple scenarios– Holdings classes and properties– Further work
Bibliographic Framework Transition Initiative
•Rethinking bibliographic control because of technological and environmental changes
•Translate MARC 21 to a Linked Data model retaining richness and benefits of existing data
•Based on Semantic Web and Linked Data technologies
•Foster reuse of existing rich metadata•Integrate library data and other cultural
heritage data on the Web
Goals•Inherit the robust nature of MARC•Be content standard agnostic (RDA, DACS,
CCO, etc.)•Handle description and management of
traditional and non-traditional materials•Integrate supporting data (Authorities,
Holdings, Classification, Community Information)
•Leverage what the Web has to offer (collaboration, linking, web triggers)
BIBFRAME milestones•Goal to re-imagine and implement a
bibliographic environment in a post-MARC world
•Key dates:– May 2011: Initiative announced– May 2012: Zepheira LLC contracted to evaluate
initiative and data modeling, develop tools– November 2012: LC publishes high level model
document and sets up Early Experimenters group– December 2012: LC makes early experimenter
code available– Jan.-Nov. 2013: Elaboration of BIBFRAME model – August 2013: Key discussion documents released– January 2014: Vocabulary updates and BIBFRAME
tools
http://id.loc.gov/authorities/names/n79007751
http://id.loc.gov/authorities/names/n92062246
http://id.loc.gov/authorities/names/n80016154
Core Classes
Work
Core Classes
Work
Resource reflecting the conceptual essence of the cataloged item
Core Classes
Work
Instance
Core Classes
Work
Instance
Resource reflecting a material embodiment of a BIBFRAME Work
Core Classes
Work
Instance
Authority
Core Classes
Work
Instance
Authority
Resource reflecting key authority concepts that have defined relationships to Works and Instances
Core Classes (cont'd)
Annotation
Core Classes (cont'd)
AnnotationAssertions about the other core class elements
Works – reviews, abstract
Instances – holdings, book cover images
Authorities– author information
Classes and Properties, introduced to support a proposed holdings model
• Classes– Held Material– HeldItem
• Properties– subproperties of bf:annotates
• bf:holdingFor• bf:componentOf
– For combining Works and Instances• bf:includesWork• bf:includesInstance
Some Holdings Scenarios
• Simplest Scenario: Single-volume Work, an Instance, one copy
• Multiple copies: Single-volume Work, an Instance, multiple copies
• New Work Created: for the purpose of combining two existing, related Works
• Bound With: Two unrelated books, published individually, are bound together by a library.
.
bf:Instance
Bf:instanceOf
Copy
bf:WorkSingle-volume
Simplest Scenario: Single-volume Work, an Instance, one copy.
bf:Instance
Bf:instanceOf
Copy
bf:WorkSingle-volume
bf:HeldItem
Holding for this copy
bf:holdingFor
bf:Instance
Bf:instanceOf
Copy
bf:WorkSingle-volume
bf:HeldItem
Holding for this copy
bf:holdingFor
Introduces:•property bf:holdingFor
•class bf:HeldItem
Scenario: Single-volume Work, an
Instance, multiple copies.
bf:Instance
Bf:instanceOf
Copy 1 Copy 2
bf:WorkSingle-volume
One Holding per Copy
bf:Instance
Bf:instanceOf
bf:HeldItemFor copy 1
bf:holdingForbf:holdingFor
bf:HeldItemFor copy 2
Copy 1Copy 2
bf:WorkSingle-volume
….. There may in addition be
summary holding information
bf:Instance
bf:HeldItem for copy 1
bf:HeldItem for copy 2
bf:holdingFor
HeldMaterial
bf:componentOf
Summary Holding
Detailed Holding
bf:componentOf
bf:Instance
bf:HeldItem for copy 1
bf:HeldItem for copy 2
bf:holdingFor
bf:HeldMaterial
bf:componentOf
Summary Holding
Detailed Holding
bf:componentOf
Introduces:
property bf:componentOf
Introduces:
class bf:HeldMaterial
• When there are detailed holdings BUT NO summary holdings, HeldItem annotates the Instance, via property bf:holdingFor.
• When there are detailed holdings AND summary holdings, HeldItem annotates HeldMaterial, via property bf:componentOf.
• Note in the latter case, since HeldMaterial is an Annotation, HeldItem annotates an annotation.
• HeldItem is a subclass of HeldMaterial; that is, it inherits its properties.
So for the single-volume scenario …
Scenario: New Work Created
• A new Work is created, for the purpose of combining two existing, related Works.
two existing, related Works …..
W1 W2
W1 W2
W12
bf:includesWork bf:includesWork
New Work, W12, combines W1 and W2
Introduces:
property bf:includesWork
Example
W1: The Adventures of Tom Sawyer
W2: The Adventures of Huckleberry Finn
New title for W12
W12
Title: Two Books by Mark Twain
W1: The Adventures of Tom Sawyer
W2: The Adventures of Huckleberry Finn
bf:includesWork bf:includesWork W12:
“Two Books by Mark Twain”
W2: The Adventures of Huckleberry Finn
W1: The Adventures of Tom Sawyer
… and an Instance is created for the new Work…
W12:“Two Books by Mark Twain”
bf:includesWork bf:includesWork
bf:Instance I12
bf:instanceOf
W1: The Adventures of Tom Sawyer
W2: The Adventures of Huckleberry Finn
W1: The Adventures of Tom Sawyer
W12:“Two Books by Mark Twain”
bf:includesWork bf:includesWork
bf:Instance I12
bf:instanceOf
W1: The Adventures of Tom Sawyer
W2: The Adventures of Huckleberry Finn
W1: The Adventures of Tom Sawyer
bf:Instance I1 bf:Instance I2
bf:instanceOf bf:instanceOf
bf:includesInstancebf:includesInstance
… which points to the two individual instances
W12:“Two Books by Mark Twain”
bf:includesWork bf:includesWork
bf:Instance I12
bf:instanceOf
W1: The Adventures of Tom Sawyer
W2: The Adventures of Huckleberry Finn
W1: The Adventures of Tom Sawyer
bf:Instance I1 bf:Instance I2
bf:instanceOf bf:instanceOf
bf:includesInstancebf:includesInstance
Introduces:
property bf:includesInstance
Holdings for this scenario …
bf:Instance I12
bf:Instance I1 bf:Instance I2
bf:HeldItem
bf:holdingFor
,,,, a single HeldItem annotates the new Instance.
“Scenario: Bound With”
Two unrelated books, published individually, are bound together by a library.
For each book, there is a Work. Each Work has an Instance for its book
W1 W2
I1I2
No new Work is created and no new Instance. Since there is no single Instance representing the binding, the
HeldItem Annotates both of the Instances, individually, via a single Annotation, which repeats the property bf:holdingFor.
I1 I2
bf:HeldItembf:holdingFor bf:holdingFor
HeldMaterial Properties• accessCondition • acquisitionSource • enumerationAndChronology • heldBy • holdingFor • lendingPolicy • reproductionPolicy • retentionPolicy • subLocation
HeldItem Properties• barcode • circulationStatus • componentOf • itemID• copyNote • shelfMark
Subproperties of shelfMark:– shelfMarkDdc – shelfMarkLcc – shelfMarkUdc– shelfMarkNlm– shelfMarkScheme
LC MARC record
BIBFRAME transformation tool
BIBFRAME Work
BIBFRAME Instance
LC OPAC holdings
BIBFRAME Holdings
Further work
• Develop additional use cases
• Model detailed holdings for serials
• Consider additional functionality for holdings in BIBFRAME
• Revise the vocabulary as needed for the above
Questions?
• Rebecca Guenther: [email protected]
• BIBFRAME update: Sunday Jan. 26 10:30-11:30 PCC 114
Thanks to Ray Denenberg for his slides