Purpose: Libraries need a mechanism for binding multiple pieces associated with the same title into one single item.

User story statement(s):

As a staff user responsible for binding materials,
I want a mechanism for selecting materials to be bound together
so that the bound item is properly represented in the system

Scenarios:

1. Bind button (no items)

   • Given UIREC-321

   • When user clicks Bind

   • Then the Bind items screen disappears

   • AND the Receiving title details pane appears

   • AND the newly created item is visible in the "Bound items" accordion

   • AND the barcode of that item is a link to the item record

   • AND the newly created item has an item status of "In process"

   • AND a green toast message appears: "Item (barcode) created successfully"

   • AND the receiving pieces Bound flag is active

2. Bind button (items associated with receiving pieces, no requests)

   • Given UIREC-321

   • AND given at least one receiving piece has an associated item record

   • AND NO associated items have outstanding requests

   • When user clicks Bind

   • Then the Bind items screen disappears

   • AND the Receiving title details pane appears

   • AND the newly created item is visible in the "Bound items" accordion

   • AND the barcode of that item is a link to the item record

   • AND the newly created item has an item status of "In process”

   • AND ALL items previously associated with receiving pieces receive item statuses of “Unavailable”

   • AND a green toast message appears: "Item (barcode) created successfully"'

3. Bind button (items associated with receiving pieces, at least one request)

   • Given UIREC-321

   • AND given at least one receiving piece has an associated item record

   • AND at least one associated items has outstanding requests

   • When user clicks Bind

   • Then an alert appears: “There are requests on the following pieces: (barcodes of pieces). Transfer requests to the new record?”

   • AND there are “Transfer”, “Do not transfer” and “Cancel” buttons

   • AND “Transfer” is the default

4. Cancel button

   • Given UIREC-321

   • When user clicks cancel

   • Then the pop-up alert disappears

   • AND user remains on the bind pieces screen

   • AND all selected pieces remain selected

5. Bind button (ECS-enabled system, items associated, at least one request, bound item to go to different tenant than requests)

   • Given UIREC-321

   • AND given at least one receiving piece has an associated item record

   • AND at least one associated item has outstanding requests

   • AND the new item being created is associated with a DIFFERENT tenant than the item with outstanding requests

   • When user clicks Bind

   • Then an alert appears: There are requests on the following pieces: (barcodes of pieces). Please delete requests before proceeding.”

   • AND there is ONLY a Cancel button.