...
- 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 + per workflow.
- 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.
- See MARC validation - Logic for rules to be implemented for Phase 1.
Phased approach (covers Phase 1- 3)
Release | Deliverables | Jira Requirements | ||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Quesnelia |
|
| ||||||||||||||||||||||||||||||||||||
Ramsons |
| |||||||||||||||||||||||||||||||||||||
Sunflower |
| |||||||||||||||||||||||||||||||||||||
Trillium | Phase 2 - ISBN/ISSN validation (can the existing tool be used?) Phase 2 - Reporting (Lists app?) | |||||||||||||||||||||||||||||||||||||
Umbrellaleaf | Phase 3a - Data import support (including single record import) | |||||||||||||||||||||||||||||||||||||
Vetch | Phase 3b - Data import support (including single record import) |
...
Feature | Description / Jira issue(s) | Notes | |||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Global Tenant level - Configure MARC bib rules validation that includes supports logic outlined - MARC validation - Logic
|
|
| Global | quickMARC front-end work
| |||||||||||||||||||||||||||
Tenant level - Configure MARC authority rules validation that includes supports logic outlined - MARC validation - Logic
|
Global list - Authority Tags/Subfields | No quickMARC front-end dev | 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. work
| |||||||||||||||||||||||||
Allow a tenant to clone/customize/override MARC bib global rules validation to create/edit/derive via quickMARC Ability to add new, local rulescreate/modify validation rules for local bib fields or fields not outlined in LOC MARC documentation
|
| ||||||||||||||||||||||||||||||
Allow a tenant to clone/customize/override MARC authority global rules validation to create/edit via quickMARC Ability to add new, local rulescreate/modify validation rules for local authority fields or fields not outlined in LOC MARC documentation
| |||||||||||||||||||||||||||||||
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 Allow a tenant to delete validation rules for local bib fields or fields not outlined in LOC MARC documentation | |||||||||||||||||||||||||||||||
Allow a tenant to delete validation rules for local authority fields or fields not outlined in LOC MARC documentation | |||||||||||||||||||||||||||||||
Authority control subject validation | Frontend dev
| ||||||||||||||||||||||||||||||
Ability to export validation rules in a json/text file |
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
...