quickMARC: MARC Validation (UXPROD-3985)

[UXPROD-4549] MARC21 record validation support - Phase 2 - Implementation Created: 12/Nov/23  Updated: 06/Feb/24

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: Ramsons (R2 2024)
Parent: quickMARC: MARC Validation

Type: New Feature Priority: P3
Reporter: Khalilah Gambrell Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: LC-priority2, SolutionArchitecture, cataloging, galileo, loc, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Blocks
is blocked by UIQM-600 FE - MARC validation\Bib Rec.\Only on... Open
is blocked by UXPROD-4575 Create\Edit\Derive quickMARC Bibliogr... Open
is blocked by UXPROD-4388 MARC\Holding\validation support Open
is blocked by UXPROD-4402 MARC\Authority\validation support Open
is blocked by UXPROD-4403 MARC validation\Bib Rec. Open
is blocked by UIQM-469 Create\Edit\Derive quickMARC Bibliogr... Closed
is blocked by UIQM-398 Create\Edit quickMARC Authority: Add ... Draft
is blocked by MODQM-388 BE - MARC validation\Bib Rec.\Only on... Blocked
is blocked by UXPROD-4375 MARC21 record validation support\Gene... In Refinement
Cloners
clones UXPROD-3940 MARC21 record validation support - Ph... Draft
Defines
is defined by MODQM-402 Add available values for position 17 ... In Refinement
Relates
relates to UIQM-382 quickMARC Bib Validation: Make 010 a ... Closed
relates to UIQM-123 Characters in block type "a", " t " a... Closed
relates to MODQM-378 Tenant level configuration - Make 010... Draft
relates to UIQM-495 Add more tests for MARC records valid... Draft
relates to MODQM-256 User can enter {dollar} or {$} to han... Open
relates to UXPROD-4286 Feature: MARC validation rules | BF C... Open
relates to UIQM-526 Jest tests for quickMARC validation r... Closed
relates to UIQM-103 Edit/DeriveMARC bib record and View S... Closed
relates to UIQM-131 Add "guidance" to LDR field Closed
relates to MODELINKS-131 Authority: Restrict authority to have... Draft
relates to MODQM-235 POC: quickMARC: Extend MARC validation Draft
relates to MODQM-328 Formalization of error messages Draft
relates to MODQM-380 Inaccuracies in the definition of the... Draft
relates to UIQM-398 Create\Edit quickMARC Authority: Add ... Draft
relates to UIQM-461 Display positions (subfields) numbers... Draft
Epic Link: quickMARC: MARC Validation
Front End Estimate: XL < 15 days
Front-End Confidence factor: 10%
Back End Estimate: XXL < 30 days
Back-End Confidence factor: 10%
Development Team: Spitfire
PO Rank: 0

 Description   

Goal: When a user creates/updates a record then more robust MARC validation should happen. Feature intent is to define default validation rules and allow the library (tenant level setting) to set custom rules

To be considered:

  • The tech design should not be MARC centric meaning that it should be flexible enough to assign a set of validation rules per record type + format. 
  • The tech design should also allow for any flow that creates/updates MARC to opt-in to using these validation rules 
  • This feature will however focus on MARC. Additional features must be created to support other formats. 

Requirements/Scope:

  • Implement standard MARC21 validation rules
    • Repeatability
    • Valid values (fields, indicators, subfields)
    • Mandatory/optional
  • Ability to revise default validation rules
  • Ability to add new, local rules
    • Repeatability
    • Valid values (fields, indicators, subfields)
    • Mandatory/optional
  • Ability to bypass validation:
    • Default (MARC21)
    • ISBN/ISSN Validation
  • Ability to set whether validation rules should be a warning (warn, but permit save) OR error that prevents user from saving record
  • Need to consider migration workflows where these rules can be ignored/bypassed. Same for data import workflows. 

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