Current situation or problem:

The project will need to create MARC records derived from resource descriptions. We will need to enforce validation rules within the Linked Data Editor application to ensure that the MARC records derived from these resources adhere to quality standards.

NOTE: Linked data rules generally attempt to accommodate the MARC 21 standard. The rules below are conscribed within the conversion rules detailed in the BIBFRAME standard.

PRINCIPLES

Reference:

• Validation rules are not applied for data imports

• Validation rules are applied at record saving within the Linked Data Editor application

• All MARC bibliographic records derived from resource descriptions must have

  • LDR Leader

  • 001 Control Number

  • 005 Date and Time of Latest Transaction

  • 008 Fixed Length Data Elements

  • 010 Library of Congress Control Number

  • 1xx Main Entry Person (MARC 100), Main Entry Corporation (MARC 110), Main Entry Meeting (MARC 111)

  • 245 Title Statement

  • 999 999 f f $s $i 

  • NOTE: Inquire about values for $9 and $0, especially with respect to sharing / distributing MARC-derived records.

• LDR / Leader

  • Must have 24 characters, inclusive of null spaces

  • All positions in the Leader are non-editable, except for following positions, which must have valid values:

    • 5, 6, 7, 8, 17, 18 and/or 19

    • NOTE: For LDR/18, use code of 'c' by default for MARC records derived from linked data

    •  

• 001

  • Required 

  • Non-repeatable in the MARC derived record

  • System generated and non-editable in the Linked data editor

• 005 - Date and Time of Latest Transaction

  • Required 

  • Non-repeatable in the MARC derived record

  • System generated and non-editable in the Linked data editor

• 008 - Fixed Length Data Elements

  • Required

  • Non-repeatable in the MARC derived record

• 010 - LCCN

  • Required 

  • Format follows ‘Structure A’ or ‘Structure B’

  • Non-repeatable in the MARC derived record

  • Editable - can be manually assigned or edited within the Linked data editor

• 1xx - Main Entry Person (MARC 100), Main Entry Corporation (MARC 110), Main Entry Meeting (MARC 111)

  • Required

  • Non-repeatable in the MARC derived record

  • Editable - can be manually assigned within the Linked data editor, but not directly edited

• 245 - Title Statement

  • Required

  • Non-repeatable

  • Editable - can be manually assigned and edited within the LInked data editor

• 999 f f $s $i 

  • Required 

  • Non-repeatable

  • System generated and non-editable in the Linked data editor

• All MARC tags for MARC derived records must

  • have at least one subfield (except for LDR, 001-009) → NOTE: Some MARC tags require $a

  • follow field-level indicator rules as specified in the MARC standard

  • follow field-level and subfield-level repeatability / non-repeatability rules as specified in the MARC standard

• Warning requirements suggest best practices, but don't prevent saving a resource (TBD)

Links to additional info

• FOLIO data export error table https://folio-org.atlassian.net/wiki/display/FOLIJET/Data+Export+redesign#DataExportredesign-ActivityDiagram

• MARC documentation

  • LDR - https://www.loc.gov/marc/bibliographic/bdleader.html

  • 008 - https://www.loc.gov/marc/bibliographic/bd008.html

• LC conversion rules (versions 2.3 and 2.4): BF2 to MARC LC - v2.4 and v.2.3

Questions

1. LC will be drafting a document of "Core principles" for cataloging, which will help direct details for this card

2. Overlaps with 'Preview' feature - the ability to view a resource description in MARC format within the Marva application

3. Overlaps data governance, e.g. how bulk data operations will be supported with dual cataloging standards