Holdings in BIBFRAME: a high level model

715 views
549 views

Published on

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!

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
715
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
18
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • Eric Miller’s background
  • Key documents: annotation model, use cases, authority
  • Links that don’t work: componentOf, shelfMarkNlm; shelfMarkScheme
  • Holdings in BIBFRAME: a high level model

    1. 1. Holdings in BIBFRAME: A Highlevel Model Rebecca Guenther, Library of Congress rgue@loc.gov ALCTS CRS Holdings Information Committee January 25, 2014
    2. 2. Outline • The BIBFRAME MODEL – Core Classes – Relationships – Annotations • Holdings in BIBFRAME – Multiple scenarios – Holdings classes and properties – Further work
    3. 3. 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
    4. 4. 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)
    5. 5. 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
    6. 6. http://id.loc.gov/authorities/names/n92062246 http://id.loc.gov/authorities/names/n79007751 http://id.loc.gov/authorities/names/n80016154
    7. 7. Core Classes Work
    8. 8. Core Classes Work Resource reflecting the conceptual essence of the cataloged item
    9. 9. Core Classes Work Instance
    10. 10. Core Classes Work Instance Resource reflecting a material embodiment of a BIBFRAME Work
    11. 11. Core Classes Work Instance Authority
    12. 12. Core Classes Work Instance Authority Resource reflecting key authority concepts that have defined relationships to Works and Instances
    13. 13. Core Classes (cont'd) Annotation
    14. 14. Core Classes (cont'd) Annotation Assertions about the other core class elements Works – reviews, abstract Instances – holdings, book cover images Authorities– author information
    15. 15. 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
    16. 16. 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.
    17. 17. Simplest Scenario: Single-volume Work, an Instance, one copy. bf:Work Single-volume Bf:instanceOf bf:Instance Copy
    18. 18. bf:Work Single-volume Bf:instanceOf bf:Instance bf:holdingFor bf:HeldItem Copy Holding for this copy
    19. 19. Introduces: •property bf:holdingFor •class bf:Work Single-volume bf:HeldItem Bf:instanceOf bf:Instance bf:holdingFor bf:HeldItem Copy Holding for this copy
    20. 20. Scenario: Single-volume Work, an Instance, multiple copies. bf:Work Single-volume Bf:instanceOf bf:Instance Copy 1 Copy 2
    21. 21. One Holding per Copy bf:Work Single-volume Bf:instanceOf bf:Instance bf:holdingFor Copy 1 bf:HeldItem For copy 1 bf:holdingFor bf:HeldItem For copy 2 Copy 2
    22. 22. ….. There may in addition be summary holding information bf:Instance bf:HeldItem for copy 1 bf:HeldItem for copy 2 bf:holdingFor bf:componentOf bf:componentOf HeldMaterial Summary Holding Detailed Holding
    23. 23. Introduces: property bf:componentOf bf:Instance bf:HeldItem for copy 1 bf:HeldItem for copy 2 bf:holdingFor bf:componentOf bf:componentOf bf:HeldMaterial Introduces: class Summary Holding Detailed Holding bf:HeldMaterial
    24. 24. So for the single-volume scenario … • 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.
    25. 25. Scenario: New Work Created • A new Work is created, for the purpose of combining two existing, related Works.
    26. 26. two existing, related Works ….. W1 W2
    27. 27. New Work, W12, combines W1 and W2 W2 W1 bf:includesWork bf:includesWork W12 Introduces: property bf:includesWork
    28. 28. Example W2: W1: The Adventures of Tom Sawyer The Adventures of Huckleberry Finn
    29. 29. New title for W12 W12 Title: Two Books by Mark Twain W2: W1: The Adventures of Tom Sawyer The Adventures of Huckleberry Finn
    30. 30. W2: W1: The Adventures of Huckleberry Finn The Adventures of Tom Sawyer W12: bf:includesWork “Two Books by Mark Twain” bf:includesWork
    31. 31. … and an Instance is created for the new Work… W1: bf:Instance I12 The Adventures of Tom Sawyer W2: The Adventures of Huckleberry Finn bf:instanceOf W12: “Two Books by Mark Twain” bf:includesWork bf:includesWork
    32. 32. … which points to the two individual instances bf:Instance I1 bf:includesInstance bf:Instance I2 bf:includesInstance bf:instanceOf bf:instanceOf W1: bf:Instance I12 The Adventures of Tom Sawyer W2: The Adventures of Huckleberry Finn bf:instanceOf W12: “Two Books by Mark Twain” bf:includesWork bf:includesWork
    33. 33. Introduces: property bf:includesInstance bf:Instance I1 bf:includesInstance bf:Instance I2 bf:includesInstance bf:instanceOf bf:instanceOf W1: bf:Instance I12 The Adventures of Tom Sawyer W2: The Adventures of Huckleberry Finn bf:instanceOf W12: “Two Books by Mark Twain” bf:includesWork bf:includesWork
    34. 34. Holdings for this scenario … bf:Instance I1 bf:Instance I2 bf:Instance I12 bf:holdingFor bf:HeldItem ,,,, a single HeldItem annotates the new Instance.
    35. 35. “Scenario: Bound With” Two unrelated books, published individually, are bound together by a library.
    36. 36. For each book, there is a Work. Each Work has an Instance for its book W2 W1 I1 I2
    37. 37. 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 bf:holdingFor I2 bf:holdingFor bf:HeldItem
    38. 38. HeldMaterial Properties • • • • • • • • • accessCondition acquisitionSource enumerationAndChronology heldBy holdingFor lendingPolicy reproductionPolicy retentionPolicy subLocation
    39. 39. HeldItem Properties • • • • • • barcode circulationStatus componentOf itemID copyNote shelfMark Subproperties of shelfMark: – – – – – shelfMarkDdc shelfMarkLcc shelfMarkUdc shelfMarkNlm shelfMarkScheme
    40. 40. LC MARC record
    41. 41. BIBFRAME transformation tool
    42. 42. BIBFRAME Work
    43. 43. BIBFRAME Instance
    44. 44. LC OPAC holdings
    45. 45. BIBFRAME Holdings
    46. 46. 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
    47. 47. Questions? • Rebecca Guenther: rgue@loc.gov • BIBFRAME update: Sunday Jan. 26 10:30-11:30 PCC 114 Thanks to Ray Denenberg for his slides

    ×