Page Comparison

• Phase 1 - Define technical approach when creating/editing/deriving MARC bib/auth via quickMARC
• Implement required MARC bib rules – structural based on LOC documentation
• Implement required MARC authority rules – structural based on LOC documentation
• Access to help documentation - UI only 

• Phase 1 - Implement MARC record validation when creating/editing/deriving MARC bib/auth via quickMARC
  • Includes ECS support 
  • LCCN structure validation
  • Global MARC bib / MARC authority rules validation via config file/API endpoint
  • Customize MARC bib/MARC authority rules validation per tenant via config file/API endpoint 
• Continue to implement required MARC bib rules – structural based on LOC documentation
• Continue to implement required MARC authority rules – structural based on LOC documentation
• Authority control - Subject validation (stretch) 

• Phase 1 - Complete implementation 
  • View Errors that do not prevent save
  • Logging 
  • Reporting
• MARC punctuation handling 
• Possibly expose authority control mapping rules 
• Remove subfield 9 logic on linkable fields 

Phase 2 - ISBN/ISSN validation  (can the existing tool be used?)

Phase 2 - Reporting (Lists app?) 

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

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

Global MARC bib rules validation that includes 

• MARC tags (repeatable/non-repeatable) 
• MARC tags (required/not required) 
• MARC indicators (required/not required)
• MARC subfields (repeatable/non-repeatable) 
• MARC subfields (required/not required)
• MARC subfield values?  
• MARC fixed fields 
• Specify whether rules violation is a Error that prevents saving a record OR just logs as a warning and allows save to continue
• Help documentation link

• Potential UI work to show help documentation

Global MARC authority rules validation that includes 

• MARC tags (repeatable/non-repeatable) 
• MARC tags (required/not required) 
• MARC indicators (required/not required)
• MARC subfields (repeatable/non-repeatable) 
• MARC subfields (required/not required)
• MARC subfield values? 
• MARC fixed fields 
• Specify whether rules violation is a Error that prevents saving a record OR just logs as a warning and allows save to continue
• Help documentation link

• No front-end dev
• Potential UI work to show help documentation

Implement required MARC bib rules – structural based on LOC documentation

Select fields only. Will include FE/BE development.

Implement required MARC authority rules – structural based on LOC documentation

Allow a tenant to clone/customize/override MARC bib global rules validation to create/edit/derive via quickMARC  

• Ability to add new, local rules
  • Repeatability
  • Valid values (fields, indicators, subfields)
  • Mandatory/optional

Allow tenant to specify whether rules violation is a Error that prevents saving a record OR just logs as a warning and allows save to continue.

• Potential UI work to show help documentation

Allow a tenant to clone/customize/override MARC authority global rules validation to create/edit via quickMARC

• Ability to add new, local rules
  • Repeatability
  • Valid values (fields, indicators, subfields)
  • Mandatory/optional

Allow tenant to specify whether rules violation is a Error that prevents saving a record OR just logs as a warning and allows save to continue.

• Potential UI work to show help documentation

• No front-end dev

Track/log/display

• Errors that prevent record from being saved 
• Errors that do not prevent record from being saved saved 

• Possible frontFront-end work

Authority control validation support