Versions Compared

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 via quickMARC UI.
  • In future releases, this implementation should extend 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 
    • Bulk-edit support 
  • 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 existing 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 add/update/delete to MARC bib/authority validation rules can be done easily and not require an update to 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 to all bib and authority records. 
    • If the tenant adds/updates/deletes 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

...