| Target release | Quesnelia (R1 2024) |
|---|---|
| Feature |
|
| Document Scope | Leader contextual help - MARC holdings record |
Contents
Overview
Populating fixed field positions is difficult and likely requires consulting additional resources to ensure the right codes are used. Adding dropdowns with available codes for each position supports both efficiency as well as accurate data entry.
Mock-up
Example of read-only vs editable
.png?version=1&modificationDate=1706297988000&cacheVersion=1&api=v2&width=439&height=250)
Requirements
| 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:
| 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"
| UIQM-616 - Getting issue details... STATUS | 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.
| 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. | UIQM-617 - Getting issue details... STATUS | VALIDATED | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 05: Record status available values | For the 05 dropdown, the following values should be included:
| UIQM-618 - Getting issue details... STATUS | VALIDATED | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 06: Type of record available values | For the 06 dropdown, the following values should be included:
| UIQM-618 - Getting issue details... STATUS | VALIDATED | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 17: Encoding level available values | For the 17 dropdown, the following values should be included:
| UIQM-618 - Getting issue details... STATUS | VALIDATED | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| 18: Item information in record available values | For the 18 dropdown, the following values should be included:
| UIQM-618 - Getting issue details... STATUS | 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." | UIQM-618 - Getting issue details... STATUS | VALIDATED |
