1 / 18

Development & Testing of BIBFRAME at the Library of Congress

This presentation discusses the background, general overview, challenges, steps, and conclusion of the development and testing of BIBFRAME at the Library of Congress. It also covers the relationship between BIBFRAME and the MARC formats.

tshannon
Download Presentation

Development & Testing of BIBFRAME at the Library of Congress

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Development & Testing of BIBFRAME at the Library of Congress Presented by Randall K. Barry Presentation to the Council on East Asian Libraries Seattle, WA - March 31, 2016

  2. Background General Overview of BIBFRAME Relationship to the MARC formats Testing and Pilot Project at the Library of Congress Challenges for Developing BIBFRAME Project Steps Scenario for Replacement of MARC Handling of Nonroman Data (CJK, and others) BIBFRAME Pilot Phase II (2017) Conclusion Presentation Outline

  3. 1989: The World Wide Web: developed by Tim Berners-Lee to connect separate document systems for sharing of information 2006: Four Linked Data principles, articulated by Tim Berners-Lee 1) Name things using Universal Resource Identifiers (URIs) (www.domain.org/thing) 2) Encode things to be compatible with the Hypertext Transfer Protocol (HTTP) (http://www.domain.org/thing) 3) Provide information about what a thing is using the Resource Description Framework (RDF) and SPARQL (an RDF-based Structured Query Language) 4) Include useful URI links in things to other things (a Semantic Web so that data can be reused across platforms) Background

  4. 2007: On the Record: Report of the Library of Congress Working Group on the Future of Bibliographic Control Recommended use of technology to promote broader use of library data, particularly vocabularies (name authorites, subject headings, code lists) Replace the MARC formats with a web-compatible interchange framework, specifically something compatible with RDF 2009: LC’s Linked Data Service is created (id.loc.gov) Library of Congress Subject Headings (LCSH) is made available as the first “curated vocabulary” Name authorities are made available as the next vocabulary (9 million records) Other vocabularies: language codes; country codes; geographic area codes; content, media, carrier types; genre/form terms, etc. Background - continued

  5. 2012: Start of the Bibliographic Framework Initiative (BIBFRAME) Replacement for the MARC formats. Why? Age of the standard and its inherent structure (from 1969) Adoption of Resource Description & Access (RDA) for describing and providing access to bibliographic materials Modelling being done by the museum and archival community Shift in materials themselves to electronic (digital) formats Provide for the creation and access to bibliographic data as “linked data” (following the W3C model) Provide better exposure to library data on the internet End the isolation of library data in MARC-based systems General Overview of BIBFRAME

  6. Establishes four main classes of data: creative works, instances, authorities, and annotations Instance combines elements of the FRBR and RDA expression and manifestion entities Annotations is where holdings and item-level information would be found General Overview of BIBFRAME - continued

  7. BIBFRAME, based on RDF, will replace the MARC record as the vehicle for sharing (providing access to) information about library material and specific holdings The rich set of MARC data elements will be used to help shape the vocabularies needed for linked library data MARC-based library systems will evolve to support the creation, update, and access to BIBFRAME (linked) data Existing MARC-based information (cataloging data) will be transformed to be compatible with BIBFRAME and BIBFRAME-based systems Library will move beyond the limitations of MARC The rich access provided by MARC will be enhanced Relationship to the MARC Formats

  8. 2015-2016: The first BIBFRAME pilot was begun to test what works Transformation of existing MARC data: merging and splitting of data originally stored in 18 million individual bibliographic and 8 million authority records Development of an editor (cataloging interface) for librarians creating BIBFRAME-compatible data for new items Enhancement of id.loc.gov to support the pilot project Training of staff to understand linked data and the BIBFRAME editor Keep in touch with other linked data pilot projects Testing & Pilot Project at the Library of Congress

  9. Training for the first phase completed in August 2015 Staff handling print material started first Staff create cataloging data using LC’s MARC-based library system and repeat the process to create linked data using the BIBFRAME editor and techniques Standard RDA instructions are followed for all data regardless of the system or framework used For monographs, serials, music and cartographic material, the Phase I pilot will end March 31, 2016 Testing for sound recordings and audio visual materials phase will continue through May 31, 2016 Testing for prints & photographs will end July 31, 2016 Status of Testing & Pilot Project at LC

  10. Revisions to BIBFRAME’s RDF vocabulary are needed Incorporating community input Benefitting from expert advice Guided by the experiences of the pilot Updates to the BIBFRAME editor will be made based on the experiences of the pilot and the next BIBFRAME vocabulary and model (Version 2.0) New/improved MARC-to-BIBFRAME transformations will be developed based on Version 2.0 Vocabulary lists within id.loc.gov will be enhanced and with more linkages A second BIBFRAME pilot will be performed (not before October 2016) Challenges for Developing BIBFRAME

  11. Updated BIBFRAME vocabularies and will be made available to implementers (at LC and elsewhere) An updated BIBFRAME editor to support the input and update of linked library data will be made available Training of staff to test BIBFRAME will continue Encourage library system vendors to get involved Share information about LC’s BIBFRAME pilot project with other testers and with those who have a vested interest in the technology Project Steps

  12. Linked Data for Production (LD4P) : Mellon Foundation funded projects to begin the transition to BIBFRAME Core members: Columbia University, Cornell University, Harvard University, the Library of Congress, Princeton University, and Stanford University The group will develop an Linked Open Data (LOD) bibliographic dataset based on BIBFRAME The overarching goal is to integrate library data with the much larger world of data in the semantic web Similar work in other communities for linked data include: Schema.org, CIDOC-Conceptual Reference Model, and the Europeana Data Model (EDM) Cooperation in Research & Development

  13. Work on BIBFRAME Vocabulary 2.0 is ongoing Long-term plans will focus on several aspects of library data Transform MARC record data to BIBFRAME linked data 18 million bibliographic records at LC 8 million authority records at LC Over 300 million bibliographic records in OCLC databases Enhance BIBFRAME for non-print material (AV, etc.) Shift the huge MARC-based automation infrastructure to one that is compatible with BIBFRAME Duplicate the acceptance and success of MARC Replacement of MARC

  14. The BIBFRAME editor accommodates nonroman data in most elements of bibliographic description and access There is nothing equivalent to the “880” embedded alternate graphic representation field in BIBFRAME Creators of linked bibliographic data have been imaginative in how and where they record information in nonroman scripts Test data should not be interpreted as prescriptive for how nonroman data will be represented once BIBFRAME is finalized Policies on handling data involving nonroman scripts (or any script) need to be agreed upon and implemented Handling of Nonroman Data (CJK, and others)

  15. BIBFRAME Vocabulary 2.0 will be used 2.0 is expanded for library material, cultural heritage environment, & unique material (archival collections and museum objects) Testing will focus more on non-print material (especially still images and cartographic material) and serials Incorporate experience and input form partners in LD4P Explore the relationships between BIBFRAME & RDA Make improvements in the BIBFRAME editor to facilitate creation linked data in BIBFRAME Improvements for handling of nonroman data will be made BIBFRAME Pilot Phase II (2017)

  16. BIBFRAME: represents a new distributed model for sharing linked bibliographic data through the web Will allow libraries to get away from centralized, monolithic data stores (cataloging databases) Traditional authority control will yield to broad-based identify management Cataloging will shift from primarily data transcription to focus on the linking of useful information Libraries and service providers must work together to develop and implement standards and protocols to promote the shift to BIBFRAME and linked data Conclusion

  17. Contact information: Randall Barry (rbar@loc.gov) Library of Congress Asian & Middle Eastern Division 101 Independence Ave., SE Washington, DC 20540-4220 For the BIBFRAME Pilot Project: Sally McCallum (smcc@loc.gov) Beacher Wiggins (bwig@loc.gov) For more information about ongoing work at LC

  18. Website – http://www.loc.gov/bibframe/

More Related