EPIC: cataloging in BIBFRAME / Linked Data (UXPROD-4215)

[UXPROD-4286] Feature: MARC validation rules | BF Cataloging Created: 09/May/23  Updated: 04/Feb/24

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: EPIC: cataloging in BIBFRAME / Linked Data

Type: New Feature Priority: TBD
Reporter: Doug Loynes Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: bf-alpha, bf-beta, emwg
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
is cloned by UXPROD-4592 Feature: Data Rules BF2 | BF Cataloging Open
Relates
relates to UXPROD-4201 MARC Definition Open
relates to UXPROD-4377 Templates Support - MARC \ Validation... Open
relates to UXPROD-4549 MARC21 record validation support - Ph... Open
relates to UXPROD-4451 Feature: Clone resource description |... Open
relates to UXPROD-4060 010 LCCN Validation (structure valida... Draft
relates to MODQM-390 MARC\validation\BIB Rec\Indicators Draft
relates to UXPROD-3940 MARC21 record validation support - Ph... Draft
relates to UXPROD-4293 Feature: Data transformation --> MARC... Draft
relates to UXPROD-4375 MARC21 record validation support\Gene... In Refinement
relates to UXPROD-4376 MARC21 record validation support\Addi... In Refinement
relates to UXPROD-4537 010 LCCN Validation (Prevent duplica... Analysis Complete
Release: Ramsons (R2 2024)
Epic Link: EPIC: cataloging in BIBFRAME / Linked Data
Front End Estimate: XL < 15 days
Front-End Confidence factor: 70%
Back End Estimate: XL < 15 days
Back-End Confidence factor: 80%
Development Team: Citation
PO Rank: 0

 Description   

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 Marva application to ensure that the MARC records derived from these resources adhere to quality standards.

PRINCIPLES

  • Validation rules are not applied for data imports
  • Validation rules applied at record saving within the Marva interface
  • All MARC records derived from resource descriptions must have
    • LDR
    • 008
    • 245
  • All MARC fields for records derived from resource descriptions must have at least one subfield which starts from: $
    • except for LDR, 001-009
    • Some MARC tags require $a
  • LCCN rules apply to MARC records derived from resource descriptions 
    • 010 $a
    • 010 $z
    • LCCNs following Structure 'A' rules
  • Rules for linking MARC bib record with MARC authority record(s)
  • Mandatory requirements prevent a cataloger from saving a resource in Marva
    • multiple 1XXs (Creator)
    • multiple 245s (Main Title)
  • Warning requirements suggest best practices, but don't prevent saving a resource
    • TBD

Additionally

  • the library must be able to
    • define
    • revise
    • delete
    • create new validation rules
    • or bypass them

Out of scope

Use case(s)

The system will regularly create MARC records from work completed in Marva, including:

  • Updating existing resource descriptions
  • Creating resource descriptions from scratch

Applying MARC validation rules, therefore, will happen regularly

Proposed solution/stories

Links to additional info

Questions

  1. For MARC, Khalilah Gambrell will provide a list of validation rules and principles used in FOLIO currently. She has held more requirement gathering sessions with LC staff and will be writing up Jiras for additional validation rules, which she'll share with Citation.
  2. LC will be drafting a document of "Core principles" for cataloging, which will help direct details for this card
  3. Overlaps with 'Preview' feature - the ability to view a resource description in MARC format within the Marva application
  4. Overlaps data governance, e.g. how bulk data operations will be supported with dual cataloging standards

Generated at Fri Feb 09 00:38:42 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.