| Category | Requirement | Description | Story | Status |
|---|
| Leader UI | The leader should be split by positions, with the uneditable/system-generated positions read-only, within the sequence of positions: | Position(s) | Description | Header / abbreviations | Box type |
|---|
| 00-04 | Record length | None | Read-only | | 05 | Record status | Status | Box with dropdown | | 06 | Type of record | Type | Box with dropdown | | 07 | Undefined | None | Read-only (07-08) | | 08 | Undefined | None | Read-only (07-08) | | 09 | Character coding scheme | None | Read-only (09-16) | | 10 | Indicator count | None | Read-only (09-16) | | 11 | Subfield code length | None | Read-only (09-16) | | 12-16 | Base address of data | None | Read-only (09-16) | | 17 | Encoding level | ELvl | Box with dropdown | | 18 | Item information in record | Item | Box with dropdown | | 19 | Undefined | None | Read-only (19-23) | | 20 | Length of the length-of-field portion | None | Read-only (19-23) | | 21 | Length of the starting- character- position portion | None | Read-only (19-23) | | 22 | Length of implementation-defined portion | None | Read-only (19-23) | | 23 | Undefine | None | Read-only (19-23) |
| Some positions in the leader are system-generated and cannot be edited by the user. However, the contents in some of these positions are meaningful so the user still needs to be able to view them. For these positions, we need to present the position values in a read-only box (similar to the implementation for the 001, 005, 999). Additionally, not all of these values need to be broken into separate boxes and instead can be placed in the same field/box as others (highlighted in yellow in table to left). For the positions that can be edited, we need to add a dropdown for each. This dropdown is consistent with the implementation for the 006/007 "Type" field, and will contain the valid values for that position (separate requirement below). See dropdown implementation for 006/007 "Type" 
| | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| columnIds | issuekey,summary,issuetype,created,updated,duedate,assignee,reporter,priority,status,resolution |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIQM-616610 |
|---|
|
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | validated |
|---|
|
|
| Leader UI | For the editable positions of the leader, when the user hovers over the box or clicks into it, there should be hover over text with the full description name. | Position(s) | Hover over text |
|---|
| 05 | Record status | | 06 | Type of record | | 17 | Encoding level | | 18 | Item information in record |
| The abbreviations for the specific positions, though helpful for saving space in the UI, they may not provide enough information for the user. See implementation in Poppy for 006/007/008. | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIQM-617611 |
|---|
|
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | validated |
|---|
|
|
| Leader UI | For creating new holdings records, the following should be default values: - 00-04: 0000 (system generated)
- 05: n
- 06: u
- 07: \
- 08: \
- 09: \
- 10: 2
- 11: 2
- 12-16: 00000 (system generated)
- 17: u
- 18: n
- 19: \
- 20-23: 4500
|
|
|
|
| 05: Record status available values | For the 05 dropdown, the following values should be included: | c - Corrected or revised | | d - Deleted | | n - New |
| | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIQM-618612 |
|---|
|
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | validated |
|---|
|
|
| 06: Type of record available values | For the 06 dropdown, the following values should be included: u - Unknown | v - Multipart item holdings | x - Single-part item holdings | y - Serial item holdings |
| | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIQM-618612 |
|---|
|
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | validated |
|---|
|
|
| 17: Encoding level available values | For the 17 dropdown, the following values should be included: | 1 - Holdings level 1 | | 2 - Holdings level 2 | | 3 - Holdings level 3 | | 4 - Holdings level 4 | | 5 - Holdings level 4 with piece designation | | m - Mixed level | | u - Unknown | | z - Other level |
| | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIQM-618-612 |
|---|
|
| Jira Legacy |
|---|
| server | System JIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | MODQM-402 |
|---|
|
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | validated |
|---|
|
|
| 18: Item information in record available values | For the 18 dropdown, the following values should be included: | i - Item information | | n - No item information |
| | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIQM-618612 |
|---|
|
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | validated |
|---|
|
|
| Data import validation | If the record that is imported (DI/Single record import) contains values in the leader that are not valid per the dropdowns, allow the record to be opened in quickMARC, but if the user does not change the value, do not allow save and produce the following error toast: "Record cannot be saved. Leader contains invalid values." | | | Jira Legacy |
|---|
| server | System JiraJIRA |
|---|
| serverId | 01505d01-b853-3c2e-90f1-ee9b165564fc |
|---|
| key | UIQM-618612 |
|---|
|
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | validated |
|---|
|
|