MARC Holdings- Leader contextual help

Owned by Christine Schultz-Richert
Last updated: Feb 07, 2024
3 min read
Target releaseQuesnelia (R1 2024)
Feature

UXPROD-3940 - MARC21 record validation support - Phase 1 DRAFT

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

Requirements

CategoryRequirementDescriptionStoryStatus
Leader UI

The leader should be split by positions, with the uneditable/system-generated positions read-only, within the sequence of positions:

Position(s)DescriptionHeader / abbreviationsBox type
00-04Record lengthNoneRead-only
05Record status

Status

Box with dropdown
06Type of recordTypeBox with dropdown
07UndefinedNoneRead-only (07-08)
08UndefinedNoneRead-only (07-08)
09Character coding schemeNoneRead-only (09-16)
10Indicator countNoneRead-only (09-16)
11Subfield code lengthNoneRead-only (09-16)
12-16Base address of dataNoneRead-only (09-16)
17Encoding levelELvlBox with dropdown
18Item information in recordItemBox with dropdown
19UndefinedNoneRead-only (19-23)
20Length of the length-of-field portionNoneRead-only (19-23)
21Length of the starting- character- position portionNoneRead-only (19-23)
22Length of implementation-defined portionNoneRead-only (19-23)
23UndefineNoneRead-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"

UIQM-610 - 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. 

Position(s)Hover over text
05Record status
06Type of record
17Encoding level
18Item 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. 

UIQM-611 - Getting issue details... STATUS

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


UIQM-612 - Getting issue details... STATUS

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


UIQM-612 - Getting issue details... STATUS

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


UIQM-612 - Getting issue details... STATUS

MODQM-402 - Getting issue details... STATUS

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


UIQM-612 - 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-612 - Getting issue details... STATUS

VALIDATED