STORY: Inventory edit instance | source=LINKED_DATA

CSP Request Details

None

CSP Rejection Details

None

CSP Approved

None

Description

This card is related to - collectively adding changes to the Inventory Action drop down menu that support linked data.

The purpose of this card is to address the ‘Edit Instance’ option when the source type = LINKED_DATA.

The action should be enabled from the Action drop down, and it should function the same as for an Instance record with source type=MARC. Some fields and buttons displayed in the Edit Instance workform are enabled and editable when source type=MARC, including:

  • Suppress from discovery

  • Staff suppress

  • Previously held

  • Cataloged date

  • Instance status term

  • Add statistical code

  • Add administrative note

  • Add nature of content term

  • Add child instance

  • Add parent instance

All other fields and buttons are read only.

1. Default, Edit Instance with source type=LINKED_DATA

GIVEN that the cataloger has selected an Instance record with source type = LINKED_DATA in the Inventory application

AND that the Action drop down menu is displayed

WHEN ‘Edit Instance’ has been selected from the Action drop down

THEN the selected Instance is displayed in the Edit Instance workform

AND all of the fields and buttons in the workform are read only, except for

  • Suppress from discovery

  • Staff suppress

  • Previously held

  • Cataloged date

  • Instance status term

  • Add statistical code (button)

  • Add administrative note (button)

  • Add nature of content term (button)

  • Add child instance (button)

  • Add parent instance (button)

which are all enabled and editable

AND the ‘Cancel’ button is enabled by default

AND the ‘Save & close’ button is disabled by default

AND the 'X' button in the top left of the workform screen is enabled

2. Edits

GIVEN scenario 1

WHEN the cataloger makes any edits in the Edit Instance workform

THEN the ‘Save & close’ button is enabled

AND the ‘Cancel’ button is still enabled

3. Save & close

GIVEN scenario 2

WHEN the cataloger selects the ‘Save & close’ button

THEN the edits are saved to the back end

AND the Edit Instance workform is no longer displayed

AND the cataloger returns to the search result set in the Inventory app

AND the selected Instance record is displayed in the full record panel on the right of the screen

4. Cancel

GIVEN scenario 2

WHEN the cataloger selects the ‘Cancel’ button

THEN a prompt is presented alerting the cataloger that there are unsaved changes

5. Keep editing

GIVEN scenario 4

WHEN the cataloger selects the ‘Keep editing' button

THEN a prompt is no longer displayed

AND the cataloger returns to the Edit Instance workform

6. Close without saving

GIVEN scenario 4

WHEN the cataloger selects the ‘Close without saving' button

THEN the prompt is no longer displayed

AND the edits made in the Edit Instance workform are not saved to the back end

AND the Edit Instance workform is no longer displayed

AND the cataloger returns to the search result set in the Inventory app

AND the selected Instance record is displayed in the full record panel on the right of the screen

NOTE: Repeat scenario 6 by selecting the exit icon ('X') in the upper left of the screen

7. Read only fields

GIVEN scenario 1

WHEN the cataloger tries to make any changes to read only fields (e.g. selecting a drop down, clicking the trash can icon)

THEN no changes are made

AND the same values (where applicable) display

Environment

None

Potential Workaround

None

Attachments

3

Checklist

hide

Activity

Show:

Yury Barsukou July 19, 2024 at 11:35 AM

tested on 310 env, ok for me. Evidences and cases added.

Doug Loynes July 4, 2024 at 12:34 PM
Edited

Open question from front end: will developers be able to easily tap into existing functionality, so that source=LINKED_DATA behaves the same as a record with source=MARC currently behaves?

Done

Details

Assignee

Reporter

Priority

Story Points

Sprint

Development Team

Citation

Fix versions

Release

Ramsons (R2 2024)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created July 3, 2024 at 10:05 PM
Updated October 31, 2024 at 3:59 PM
Resolved July 22, 2024 at 1:53 PM
TestRail: Cases
TestRail: Runs