ALA & PCC BIBFRAME and Linked Data Update Prospector Catalog/Reference Committee Meeting July 21, 2016

New Training Materials from LC Catalogers Learning Workshop (CLW) website: ■RDA refresher training: refreshers.html refreshers.html ■NACO series training: ■RDA Record Examples: Records%20TG/index.html Records%20TG/index.html ■Online Library of Congress Subject Headings Training: ■LC’s BIBFRAME Training: ■PCC’s Report on Available Linked Data Training Resources: DataTrainingResources.docx DataTrainingResources.docx

New Vocabularies from LC ■LC Genre/Form Terms (LCGFT)and Manual (draft): ■LC Demographic Group Terms (LCDGT) and Manual (draft): o Describes characteristics of creators/contributors (386 field) and the intended audience (385 field) in both bibliographic and authority records ■LC Medium of Performance Thesaurus for Music:

Updated Linked Data Models FRBR-LRM (Library Reference Model) LRM%20overview.pdf LRM%20overview.pdf ■Consolidation and revision of FRBR, FRAD and FRSAD o Remains a high-level conceptual model, with an entity- relationship framework o Changes to the model reflect insights gained since these were first published ■Same four user tasks from FRBR plus one from FRSAD: o Find, Identify, Select, Obtain, Explore

FRBR-LRM ■No more grouping of entities: o Former Group 1 entities remain the core of the model: Works, Expressions, Manifestations, Items (WEMI) o Former Group 2 entities replaced by superclass Agent  Collective Agent (corporate bodies & families)  Person (individual human being) o Former Group 3 entities Concept, Object, Event, and Place are all deprecated ■New entities added like Place (repurposed) and Time-span

FRBR-LRM ■Why is this important? o FRBR is the foundation of RDA o RDA is the set of cataloging rules used in most BIBFRAME applications o BIBFRAME is the presumptive replacement for MARC ■Significant changes to the underlying model will cause related changes to RDA: o Placeholder chapters for FRBR Group 3 entities will be removed o New entities (Place, Time-span) will need to be defined o Opportunity for other changes to structure of RDA instructions at the same time

Updated Linked Data Models BIBFRAME ■What is BIBFRAME? o An initiative to evolve bibliographic description standards to a linked data model, in order to make bibliographic information more useful both within and outside the library community. ■Why did BIBFRAME need to be changed? o BIBFRAME 1.0 did not conform well to some linked data best practices o

BIBFRAME 1.0BIBFRAME 2.0 Work Instance AuthorityItem Annotation  Agent  Event  Subject

2.01.0

Current Linked Data Initiatives ■We are moving away from simply transforming existing MARC records into BIBFRAME and towards experimenting with ways to create, store, and query native BIBFRAME resource descriptions ■LC’s BIBFRAME Pilot Project ■LD4P (Linked Data For Production) ■BIBFLOW

LC BIBFRAME Pilot ■Phase 1 of the pilot project lasted from Oct. 1, 2015 to March 31, 2016 o AV and photograph cataloging is still ongoing ■40 LC catalogers created resource descriptions in both MARC and native BIBFRAME ■Phase 1 was carried out using BIBFRAME 1.0. BIBFRAME 2.0 is now available so the BIBFRAME Editor (cataloging interface) needs to be updated ■Going forward, catalogers will spend 1 day per week cataloging only in BIBFRAME to retain knowledge ■LC will use the test data for training, developing workflow processes, and BIBFRAME data analysis ■In the fall, LC will bring together different cataloging sections and explain to them that they must get rid of the MARC “crutch” and learn RDA and FRBR better

LC BIBFRAME Pilot Next Steps  Next pilot will use BIBFRAME 2.0 and won’t begin until at least Oct  All of the metadata created from first pilot ultimately will be discarded  LC needs to write programs to … o convert MARC to BF 2.0 (for legacy data) o store BF 2.0 data in a triple store o convert BF 2.0 to MARC for libraries that won’t implement BF immediately  PCC has created CONSER and BIBCO task groups to map BF 2.0 to the BIBCO Standard Record (BSR) and CONSER Standard Record (CSR)

LD4P (Linked Data For Production) ■LD4P Goals o Reinvent metadata production for any resource a library curates making use of linked data in a cooperative, distributed environment o Essential tool and system configuration to pilot this metadata production o Develop a community/collaborative framework for coordinating the ontology and technical work ■How will we describe resources in a linked data world? ■What tools will we need to do it? ■How will we share these resource descriptions?

LD4P Partners ■Columbia: art objects ■Cornell: o rare materials o LP’s from their Hip Hop collection ■Harvard: cartographic resources ■LC: o audiovisual, sound recordings, print, and photographic resources o continued development of BIBFRAME 2.0 o best practices for creating linked data descriptions using BIBFRAME and RDA

LD4P Partners ■Princeton o special collections materials o data modeling for manuscript annotations (e.g., personal dedications addressed to Jacques Derrida in their collection of his library) ■Stanford o performed music o “tracer bullets”  end-to- end process examining the workflows needed in a linked data environment from acquisition to discovery, for original and copy cataloging and deposits of both single items and large collections into a digital repository o identity management issues

BIBFLOW ■2-year project of the UC Davis University Library and Zepheira, funded by Institute of Museum and Library Sciences (May 2014 – April 2016) ■Official title is “Reinventing Cataloging: Models for the Future of Library Operations” ■Is a research project that will address questions like “What impact will adoption of BIBFRAME have on technical services workflows in an academic library”? o BIBFLOW = BIBframe + workFLOW ■One of the major deliverables is a roadmap that can help library community transition cataloging work to a linked data/BIBFRAME native ecosystem

Automated process (weekly done by Systems Dept) Bib Auth OCLC WorldCat New Name Auth? Propose to LC yes Auth Control Melvyl (UC OPAC) Aleph Auth Bib Harvest (UCD OPAC) Original Cataloging Workflow for Print Monographs Create holdings record Add/complete item record Physical Processing Unit Vendor Service New Sub Heading?

Major Takeaways for the Linked Data Future ■Catalogers need to uncouple our brains from MARC and learn RDA and FRBR better ■More local authority work will likely be necessary in a linked data world o Every identity needs a unique identifier, a URI o All of these cannot be created using our existing NACO structure o How will they be created, how will they be shared? ■Few librarians, including LC staff, have a complete understanding of all aspects of linked data and what a future linked data environment will look like for libraries