MARC holdings create/edit: Split LDR by position

Description

Purpose: 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.

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 story).

Requirements

  • MARC holdings create/edit

    • For uneditable/system-generated positions, include values in a read-only box

    • For editable positions, split into separate box with a dropdown (see wiki page linked below)

Scenarios:

  1. Scenario - Create new holdings record and read-only/system generated positions 00-04:

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the first box should NOT have a header and it should be read-only and contain the placeholder for positions 00-04 as "00000"

  2. Scenario - Create new holdings record and editable position 05

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the second box should have the header "Status", with a dropdown box underneath, containing the default value "n"

  3. Scenario - Create new holdings record and editable position 06

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the third box should have the header "Type", with a dropdown box underneath, containing the default value "u"

  4. Scenario - Create new MARC holdings and read-only/system generated positions 07-08:

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the fourth box should NOT have a header and it should be read-only and contain the placeholder for positions 07-08 as "\""\"

  5. Scenario - Create new holdings record and editable position 09

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the fifth box should have the header "CharCode", with a dropdown box underneath, containing the default value "\"

  6. Scenario - Create new holdings record and read-only/system generated positions 10-16

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the sixth box should NOT contain a header and it should be be read-only and contain the placeholder for positions 10-16 as "2200000"

  7. Scenario - Create new holdings record and editable position 17 

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the seventh box should have the header "ELvl", with a dropdown box underneath, containing the default value "u"

  8. Scenario - Create new holdings record and editable position 18 

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opens

    • Then the eighth box should have the header "Item", with a dropdown box underneath, containing the default value "n"

  9. Scenario - Create new holdings record and read-only/system generated positions 19-23

    • Given a MARC holdings record does not exist

    • When the user selects "+ Add MARC holdings record" in the Instance action menu quickMARC opensThen the ninth box should NOT contain a header and it should be be read-only and contain the placeholder for positions 19-23  as "\4500"

  10. Scenario - Edit existing holdings record and read-only/system generated positions 00-04:

    • Given a MARC holdings record does exist

    • When the user opens the record in quickMARC

    • Then the first box should NOT have a header and it should be read-only and contain the system-generated values for 00-04

  11. Scenario - Edit existing holdings record and read-only 07-08:

    • Given a MARC holdings record does exist

    • When the user opens the record in quickMARC

    • Then the fourth box should NOT have a header and it should be read-only and contain "\""\" for 07-08

  12. Scenario - Edit existing holdings record and read-only/system generated positions 10-16:

    • Given a MARC holdings record does exist

    • When the user opens the record in quickMARC

    • Then the sixth box should NOT have a header and it should be read-only and contain the system-generated values for 10-16

  13. Scenario - Edit existing holdings record and read-only/system generated positions 19-23

    • Given a MARC holdings record does exist

    • When the user opens the record in quickMARC

    • Then the ninth box should NOT have a header and it should be read-only and contain the system-generated values for 19-23

Environment

None

Potential Workaround

None

Checklist

hide

TestRail: Results

Activity

Show:
Duplicate

Details

Assignee

Reporter

Priority

Story Points

Development Team

Spitfire

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 26, 2024 at 7:46 PM
Updated February 16, 2024 at 1:23 PM
Resolved February 1, 2024 at 2:55 PM
TestRail: Cases
TestRail: Runs