[UXPROD-3985] quickMARC: MARC Validation Created: 25/Jan/23  Updated: 27/Dec/23

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None

Type: Epic Priority: P2
Reporter: Christine Schultz-Richert Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: cataloging, metadatamanagement
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Epic Name: MARC Validation
Development Team: None
PO Rank: 0
Epic Color: ghx-label-1

 Description   

Current situation or problem: The ability to apply validation to MARC21 records allows libraries to rely on standard validation rules for quality checks and makes it easier for catalogers to adhere to the rules.  

Requirements/Scope:

  • Separate validation rules based on record type (bibliographic, holdings, authority)
  • Ability to revise/add to default validation rules (where default rules = MARC21 standards
    • Repeatability
    • Valid values (fields, indicators, subfields)
    • Mandatory/optional
  • Ability to bypass validation:
    • Default (MARC21)
    • ISBN/ISSN Validation
  • Dropdown menus for leader and fixed fields
  • Set whether specific validation rules should be a warning (warn, but permit save) OR error that prevents user from saving record
  • LCCN 010$a Validation:
    • Check for duplicates
    • Structure validation
  • If/Then logic

Use case(s):

  • Quality checks/easy to adhere to the standard
  • Ability to apply custom rules allows libraries to define local fields/practices that are required by their institution
  • Ability to bypass certain rules that are not applicable to the institution (like NLS ISBN/ISSN validation)

Questions:


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