Release | Deliverables | Jira Requirements |
---|
Quesnelia | - Phase 1 - Define technical approach when creating/editing/deriving MARC bib/auth via quickMARC that also accounts for ECS.
- Implement several related MARC validation issues
MARC validation - Logic LDR contextual help |
Ramsons | - Phase 1 - Implement MARC record validation when creating/editing/deriving MARC bib/auth via quickMARC
- Includes ECS support
- Support Supports validation for
- MARC bib fields
- MARC authority fields
- Log errors that warn but do not prevent user from saving MARC bib/authority records.
- Access to help documentation - UI only (stretch)
| Sunflower | - LCCN structure validationField help documentation
- LCCN structure validation and duplication checking.
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-4537 |
---|
|
Jira Legacy |
---|
server | System Jira |
---|
serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
---|
key | UXPROD-4060 |
---|
|
|
Sunflower (TBD) | - UI configuration?
- Authority control - Subject validation?
- MARC punctuation handling (determine a front-end approach) - stretchAuthority control - Subject validation (stretch) Expose authority control mapping rules?Remove subfield 9 logic on linkable fields?
- Handle deprecated fields - https://www.loc.gov/marc/bibliographic/bdapndxh.html?
|
Trillium (TBD) | (can the existing tool be used?) UI configuration Reporting (Lists app?) | Umbrellaleaf | - Expose authority control mapping rules?
|
Umbrellaleaf (TBD) | - Data import support (including single record import)
|
Vetch (TBD) | - Data import support (including single record import)
|