Skip to end of banner
Go to start of banner

Bulk Edit - Suppressing Bound-with Items

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Identifying records by holdings UUIDs

Inventory has following records:
Holdings A has related Items: Item A and Item B (bounded-with)
Holdings B has related Items: Item B
Holdings C has related Items: Item C and Item B (bounded-with)


Scenario 1:  User triggers bulk edit by submitting Holdings A's UUID

Expected behavior:
1. Preview of matched records includes item A only
2. The Error accordion contains:

  • Item B's barcode
  • Error/Warning message:  Updates will not be applied to the bound-with item - verbiage to be verified

3. When the user proceeds with bulk edit only Item A is updated

Scenario 2: User triggers bulk edit by submitting Holdings B's UUID

Expected behavior:
1. Preview of matched records includes item and the Barcode column contains bound-with  icon. 
2. When the user proceeds with bulk edit Item B is updated

Scenario 3:  User triggers bulk edit by submitting Holdings C's UUID

Expected behavior:
1
Preview of matched records includes Item C
2
. The Error accordion contains:

  • Item B's barcode
  • Error/Warning message:  Updates will not be applied to the bound-with item - verbiage to be verified

3. When the user proceeds with bulk edit only Item C is updated

Scenario 4: User triggers bulk edit by submitting UUIDs of holdings A, B and C

Expected behavior:
1
Preview of matched records includes Item  A, B and C.  Item B has an icon indicating bound-with.
2
. When the user proceeds with bulk edit all items are updated

Scenario 5: User triggers bulk edit by submitting Identifier of Item B (barcode, UUID, HRID)

Expected behavior:
1. Preview of matched records includes item. 
2. When the user proceeds with bulk edit Item B is updated


  • No labels