KCR5 has been mapped to official RDA and BIBFRAME Entities and Properties accounting for model discrepancies such as RDA's WEMI stack and BIBFRAME's WII stack #bfwe2026

KCR5 has been mapped to official RDA and BIBFRAME Entities and Properties accounting for model discrepancies such as RDA's WEMI stack and BIBFRAME's WII stack #bfwe2026
"Mapping KCR5 as content rules to BIBFRAME" with Mihwa Lee, Kongju National University, Jee-Hyun Rho, Pusan National University, & Eun-Ju Lee, Dong-eui University.
The necessity of interoperability between conceptual models and cataloguing rules in Korea #bfwe2026
This raises the issue of other 'copy specific' information in MARC bib records, such as for rare print, and where they should map to in BIBFRAME eg. Provenance & Binding information #bfwe2026
This extension to the ontology has not yet been published as National Library of Finland is still testing it out - & grappling with where the data should sit - in MARC21 583 fields can sit at bib record or holding record level - it needs to map to Item level in BIBFRAME not Instance level #bfwe2026
National Library of Finland opted for :hasItemAction
as Action is the common starting point - semantics is in the data not the model, it is flexible & scalable, and gives Actions as Entities rather than Notes. #bfwe2026
SPA modelling options in BIBFRAME include creating properties for
:hasRetentionPolicy
:isPartOfDistributedCollection
:hasPreservatioActivity
:hasSPAStatement
or
:hasItemAction #bfwe2026
SPA terminology has 6 actions - a mix of declarative, analytical and operational actions - this poses a challenge when modelling as Linked Data #bfwe2026
Action notes (field 583) are used in MARC21 to record a "Committed to retain" status for items in a Shared Print Program. - See Shared Print Actions Terminology (SPA) sharedprint.org/standing-com... #bfwe2026
"Modelling Shared Print Actions" with Andreas Andersson, National Library of Sweden. - Shared Print Programs are important to research libraries to ensure long term preservation of and access to print collections - they require national coordination & shared collections including metadata #bfwe2026
The divergence between RDA's WEMI model (Work, Expression, Manifestation, Item) and BIBFRAME's Work, Instance, Item model requires an alignment via property chains using OWL (Web Ontology Language) #bfwe2026
One RDA element can map to a whole chain of BIBFRAME elements - e.g. an 'editor person' is a bf:agent bf:Person with bf:role of 'editor person' #bfwe2026
RDA las a limited number of classes but a large number of properties used to describe these classes.
BIBFRAME does not have as many properties - it keeps its hierarchies relatively simple with limited properties and subclasses #bfwe2026
The RSC has on its Roadmap to develop further mappings with BIBFRAME - There are Maps and Alignments already available in the RDA Registry maintained by the RSC's Technical Working Group, and an RDA to MARC21 map maintained by the RDA/MARC21 Alignment Group #bfwe2026
"Mapping from RDA to BIBFRAME: Logistical and Technical Issues" with Chris Holden, Library of Congress and RDA Steering Committee.
RDA: Resource Description and Access is a package of data elements, guidelines, and instructions for creating library and cultural heritage resource metadata
#bfwe2026
BFFI is a flavour of BIBFRAME that allows for cataloguing using Official RDA as well as taking into account the characteristics of existing Finnish MARC data and cataloguing conventions. repository.ifla.org/handle/20.50...
#bfwe2026
The National Library of Finland solved discrepancies between RDA and standard BIBFRAME by splitting bf:Work into disjoint bffi:Work and bffi:Expression classes #bfwe2026
Add Aggregating Work as a subclass of Work and add Aggregator as a Role in BIBFRAME.
To be fully compliant with RDA, you would also need an Aggregating Expression but this is not neatly doable in BIBFRAME because it does not use the WEMI stack #bfwe2026
The Complete way = an Aggregating Work with an Aggregator Agent - connevted to Aggregate Instance with the BIBFRAME property instanceOf
Cannot be used for Diachronic Aggregates #bfwe2026
2 methods - Lean and Complete.
The Lean way = an Aggregate Manifestation Instance contains information related to the whole Aggregate
Needs a new subclass of Instance called Aggregate in BIBFRAME #bfwe2026
An RDA aggregate is a resource manifestation that embodies multiple distinct expressions, such as a collection, an augmentation, or parallel language versions #bfwe2026