We cannot make the archival record whole - there will always be gaps in our ability to reconcile entities based on historical ambiguity or lack of information #bfwe2026

There is anxiety about automation coming for our jobs - but you have to keep the judgement with the cataloguer, because while machines are good at reproducibility, they are also good at repeating errors. - Retrieving a possible connection is no the same as asserting one #bfwe2026

This also has to work at scale for 3000 records and their access points - using Python to better interrogate the LC Name Authority File and reconcile entities as access points #bfwe2026

A new data model doesn't necessarily mean better representation - with archival materials reconciliation and disambiguation requires historical research into the Works and Persons that need to be described #bfwe2026

"From the Shadows: Building Archival Entity Workflows
Toward BIBFRAME" with Isabella Pilar Brouse, University of New Mexico. Using OCLC's Meridian as a Entity Management software for Archives and Special Collections
#bfwe2026

It is interesting to think about real-world physical objects and how they relate to the Work-Instance-Item model of BIBFRAME - how much information about the object is actually 'Item-specific' ? #bfwe2026

Realia cataloguing - a Marva profile for 3D objects is also in development #bfwe2026

Films and videos cataloguing - testing a new Marva profile for videocassette recordings - Events could also be useful here for Television broadcasts and news. #bfwe2026

Maps cataloguing - bf:geographicCoverage can be created from several places in a MARC record: fields 043, 052, and 522.
There are also multiple places to record Scale in MARC: 034, 255 fields.
BIBFRAME to MARC conversion is therefore not straightforward #bfwe2026

Events in BIBFRAME will need to be addressed and added to id.loc.gov #bfwe2026

Sound recordings present a challenge as they are like Expressions of Expressions - a live performance of a musical work by a specific performer - so there's a need to use Event/Capture in the ontology #bfwe2026

LoC created the option for "Music Related Works" in Marva using terminology from the Performed Music Ontology.
There is a need to consider the data flow between Marva BIBFRAME and Folio MARC. This is still in testing.
#bfwe2026

When moving to look at other types of resources, the system needed to be stress-tested.
Music division cataloguers were less concerned about converting BIBFRAME data into MARC, plus they wanted to record specific info about musical works in greater detail than a Hub provides #bfwe2026

"Moving Marva Beyond Monographs" with Jodi Williamschen, Library of Congress.
Monograph-cataloguers requested changes to Marva between 2024-2025 to support their workflows including creating Name Authority records in MARC
#bfwe2026

Open Vlacc cataloguers are now considering if they can move to a truly shared collaborative cataloguing environment rather than 'copy cataloguing' #bfwe2026

Different skills are needed - cataloguers need to think about relationships between resources rather than just cataloguing the thing in front of them #bfwe2026

What happens when Linked Data stops being a project & becomes the way cataloguers work every day?
Maintenance & converting external data is easier but clustering can go wrong when converting from MARC21
Metadata works differently in the new system; cataloguers have to make clear choices
#bfwe2026

Elody launched on 29th June 2026 - there were a few last minute bug fixes needed, everyone was in live-contact over Teams to help with the go-live process.
Cataloguers like how easy the new system is for linking entities together (no manual copying of URIs) #bfwe2026

Training and feedback helped influence the build of the system - 65 cataloguers were involved in the development process, this helped them feel they had ownership over the change and of the new system #bfwe2026

Cataloguers were already familiar with the LRM model of Work, Expression, Manifestation, Item, and how this was presented to users in the OPAC.
The data model also introduces some additional Expression types to meet local needs
#bfwe2026