Versions Compared

Version Old Version 20 New Version 21
Changes made by

Khalilah Gambrell

Khalilah Gambrell

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Initial development: Validation will be implemented for create/derive/edit MARC bib and authority records. In future releases, this implementation should span to support
    • Data import (support MARC bib and MARC authority records only)
    • Data export (support MARC bib and MARC authority records only)
    • MARC holdings support via quickMARC/Data import/Data export 
  • Configuration 
    • Each tenant will have a default MARC bib record validation that can be customized per workflow. Initial development: Create/Derive/Edit MARC bib via quickMARC
    • Each tenant will have a default MARC authority record validation that can be customized per workflow. Initial development: Create/Edit MARC authority via quickMARC
    • Initial implementation - No UI will be provided. Future releases will support a UI to customize validation rules. 
    • The library/tenant will not be able to customize/override global MARC bib record validation rules for the following fields: Leader, 001, 005, 999 ff $s / $i, 006, 007, 008. Future implementation - we may allow for customization/override of select Leader/006/007/008 positions. 
  • Localization and Unicode support 
  • Enhanced Consortia Support  
  • Release upgrade
    • When initial development is complete and released, there should be minimal impact to existing libraries. It should not require multiple hours to update records. 
    • It should not require significant work for hosting providers. 
    • Ideally existing libraries will not be asked to update all bib and authority records once this capability is released. 
  • Migrations from one ILS to FOLIO
    • Customizations should be setup prior to loading records
    • If loading records outside of data import, then we need to assume that MARC bib/authority validation is bypassed and if so, we need to ensure that the user can view and edit the record when the record has errors. 
  • Changing rules expectations 
    • Ideally a global change to MARC bib/authority validation rules can be done easily and not require an update all bib and authority records. 
    • A tenant should be able to customize MARC bib/authority validation rules at anytime AND does not require an update all bib and authority records. 
    • If the tenant updates a rule and it now conflicts with existing records then we need to ensure that the user can view and edit the record when the record has errors. 
  • Data import 
    • Initial development: No impact (includes single record import) 
    • If the imported record conflicts with validation rules then we need to ensure that the user can view and edit the record when the record has errors. 
  • Reporting
    • TBD
  •  Performance
    • No change to performance when Create/Derive/Edit via quickMARC

Technical Design High-Level Requirements - Phase 1

  • 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/export MARC to opt-in to using these validation rules (this includes data import and data export) 
  • Technical design will focus on MARC bibliographic and MARC authority records. MARC holdings will be handled at a later release. 

Phased approach (covers Phase 1- 3) 

ReleaseDeliverables
Quesnelia
  • Phase 1 - Define technical approach for phase 1 to create/edit/derive 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 
Ramsons
  • Implement technical approach for phase 1 to create/edit/derive 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) 
SunflowerComplete implementation (phase 1) 
  • Phase 1 - Complete implementation 
    • Logging 
    • Reporting
  • MARC punctuation handling 
  • Possibly expose authority control mapping rules 
  • Remove subfield 9 logic on linkable fields 
Trillium

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

Phase 2 - Reporting (Lists app?) 

Umbrellaleaf

IF-Then-Else logic > Phase 1

Technical Design High-Level Requirements - Phase 1

...

Phase 3a  - Data import support 

Vetch

Phase 3b  - Data import support 

Feature Matrix - Phase 1


FeatureDescription / Jira issue(s)Notes 

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 
  • 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 
  • 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


Select fields only. Will include FE/BE development.

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


  • Potential UI work to show help documentation

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


  • Potential UI work to show help documentation

Allow a user to view and edit a MARC bib/MARC authority that bypasses rules validation and has errors. Examples: a record imported via data import or direct to the db. 
  • No front-end dev

Track/log/display

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

  • Possible front-end work

Authority control validation support 



Supporting Materials 

...