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 
  • LCCN structure validation
  • Support validation for 
    • MARC bib fields outlined
      • outlined https://www.loc.gov/marc/bibliographic/ecbdlist.html (including local fields)
      • MARC bib fields not
      outlined
      • outlined https://www.loc.gov/marc/bibliographic/
      OR is a 9XX field https://www.loc.gov/marc/bibliographic/bdapndxh
      • ecbdlist.html 
    • MARC authority fields
      • outlined https://www.loc.gov/marc/authority/ecadhome.html
      MARC
      •  (including local fields)
      • or MARC authority fields not
      outlined
      • outlined https://www.loc.gov/marc/authority/ecadhome.html 
• Log errors that warn but do not prevent user from saving MARC bib/authority records. Authority control - Subject validation (stretch) 
• Access to help documentation - UI only (stretch) 

• Phase 1 - Complete implementation 
  • View Errors that do not prevent save
  • Additional Logging 
• MARC punctuation handling LCCN structure 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  (can the existing tool be used?)Phase 2 -

UI configuration 

Reporting (Lists app?) 

Phase 3a  - Data import support (including single record import)

Phase 3b  - Data import support (including single record import) 

)