...
A tenant/library may have cataloging rules for MARC bib field 906 (as an example). The library's cataloging practices may state that MARC bib field 906 is required and must always have a $b. In this case, the library's cataloging staff cannot create/derive/edit a MARC bib record via quickMARC that does not have a MARC bib field 906 $b.
Assumptions
- Initial development: Validation will be implemented for create/derive/edit MARC bib and authority records via quickMARC UI.
- In future releases, this implementation should span extend to supportsupport
- 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 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
...
Feature | Description / Jira issue(s) | Notes | |||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Global MARC bib rules validation that includes
|
|
| |||||||||||||||||||||||||
Global MARC authority rules validation that includes
|
Global list - Authority Tags/Subfields |
| |||||||||||||||||||||||||
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
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. |
| ||||||||||||||||||||||||||
Allow a tenant to clone/customize/override MARC authority global rules validation to create/edit via quickMARC
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. |
| ||||||||||||||||||||||||||
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. |
| ||||||||||||||||||||||||||
Track/log/display
|
| ||||||||||||||||||||||||||
Authority control validation support |
Supporting Materials
- quickMARC - MARC21 Validation (
)Status colour Yellow title In progress - quickMARC – Error handling
Status title Under Review - MARC bib: logic and rules in FOLIO
Status title Under Review - MARC Authority - System updates and quickMARC validation rules
Status title Under Review - MARC Holdings - System updates and quickMARC validation rules
Status title Under Review - Some Jira issues related to MARC validation
Status title Under Review
...