FEATURE: MARC derived records

Description

Creation of MARC derived records is a condition for the Linked data editor, since libraries typically rely on MARC records for downstream services.

The creation of MARC derived records must adhere to the Library of Congress' MARC2BIBFRAME conversion rules.

Generally speaking, the development sequence for mapping to / from MARC will ‘pair’ the work. In other words, any MARC field that rolls up to a Work entity or an Instance entity will have a corresponding rule for mapping back to a MARC field (as covered in ).

As development executes in incoming MARC transformation, mapping for outgoing transformation should closely follow . . . until the mappings are ‘done’ with respect to any given metadata element.

NOTE (1): The rules for converting linked data to MARC do not (and are not intended to be) mirror images of the rules for converting MARC records into linked data. Consequently, if a linked data resource has an underlying MARC record, the MARC derived record may differ from the original. For example, MARC records with 260 or 264 fields are mapped to ProvisionActivity class in linked data. However, MARC derived records will map ProvisionActivity metadata to MARC 264 only. Additionally, a number of MARC fields are not mapped to linked data at all, in which case data in those fields will be lost and not captured in the MARC derived record.

NOTE (2): the conversion documentation spans across bibliographic formats. The scope of the Linked data editor will start with monographs. Conversion rules for components that are non-monograph specific will be de-prioritized as a consequence.

NOTE (3): rules tied to the Hub entity are covered in the documentation for converting Works to MARC.

NOTE (4): the Item entity is outside scope entirely for the Linked data module.

 

Out of scope

  • Item (Excel, 78 KB, 11/22/2023)

 

The scope of this feature is limited to

  • resource descriptions created for a new Work or Instance

  • resource descriptions seeded from underlying MARC records

See spreadsheet with LC's conversion of BIBFRAME 2 to MARC specifications (versions 2.3 and 2.4), BF2 to MARC LC - v2.4 and v.2.3

Priority

Development Team

Citation

Assignee

Solution Architect

Parent Field Value

None

Parent Status

None

Checklist

hide

TestRail: Results

Activity

Show:

Anuar Nurmakanov February 28, 2025 at 11:21 AM

, , can we extract not finished stories into another feature and move it to Trillium release?

Doug Loynes January 6, 2025 at 3:14 PM

The Linked Data Editor supports the ability to create MARC records derived from linked data resource descriptions, which will be included in the Sunflower release. However, the scope of this feature is to be inclusive of all mappings needed for compliance with the BIBFRAME standard. Notably absent from the Sunflower release, for example, will be support for MARC 880 fields and corresponding MARC derived records. This feature slotted for the Trillium release.

Anuar Nurmakanov October 9, 2024 at 11:13 AM

Architecture Review is Required

Details

Reporter

PO Rank

0

Back End Estimate

XL < 15 days

Back-End Confidence factor

90%

Release

Trillium (R2 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created May 10, 2023 at 7:43 PM
Updated February 28, 2025 at 11:21 AM
TestRail: Cases
TestRail: Runs