Page Comparison

• Phase 1 - Define technical approach when creating/editing/deriving MARC bib/auth via quickMARC that also accounts for ECS.
• Implement several related MARC validation issues

• Phase 1 - Implement MARC record validation when creating/editing/deriving MARC bib/auth via quickMARC
  • Includes ECS support 
  • Support Supports validation for 
    • MARC bib fields
      • outlined https://www.loc.gov/marc/bibliographic/ecbdlist.html (including local fields)
      • AND MARC bib fields not outlined https://www.loc.gov/marc/bibliographic/ecbdlist.html 
    • MARC authority fields
      • outlined https://www.loc.gov/marc/authority/ecadhome.html (including local fields)
      • or MARC AND MARC authority fields not outlined https://www.loc.gov/marc/authority/ecadhome.html 
• Log errors that warn but do not prevent user from saving MARC bib/authority records. 
• Access to help documentation - UI only (stretch) 

• LCCN structure validationField help documentation 
• LCCN structure validation and duplication checking.
  

  • Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4537

  • Jira Legacy
    server System Jira serverId 01505d01-b853-3c2e-90f1-ee9b165564fc key UXPROD-4060

• UI configuration?
• Authority control - Subject validation?
• MARC punctuation handling (determine a front-end approach) - stretch
• Authority control - Subject validation (stretch) 
• Expose authority control mapping rules?
• Remove subfield 9 logic on linkable fields? 
• Handle deprecated fields - https://www.loc.gov/marc/bibliographic/bdapndxh.html?

• ISBN/ISSN validation 

UI configuration 

Reporting (Lists app?) 

• Expose authority control mapping rules?

• Data import support (including single record import)

• Data import support (including single record import)