Inventory. Viewing Item Requests on Instance Record

Purpose

For staff to be aware of the requests queue of each item on the title (instance) record.

As a circulation staff person
I want to be able to view an items requests on instance record
So that I can understand which copy will be available in the nearest future.

Use cases

• Patron comes to circ desk and wants to know if the library has a title
• If library has a title but it’s not currently available, patron wants to request it
• Staff wants to know which copy is least requested so they can put the request on that item*
• Staff wants to tell patron where they are in the (item) request queue to set expectations around when they might receive the item*

* Note: These use cases will change when we have title level requests. Still, they will remain valid for institutions using item-level requests.

Scenarios

1. Scenario
   • Given the Inventory app
   • When an instance is selected
   • Then:
     • The Actions drop-down menu of an instance record is displayed with new “View requests” button (see slide 7 “Enhanced mockup due to UX designer suggestion” here).
     • Should be at bottom of menu
2. Scenario CB: Nice-to-have. This scenario may pose the same performance challenges we are tyring to avoid by putting the request count in a separate popup. Discuss with team
   • Given an instance with X number of open requests on it
   • When the "View requests" option is displayed in the Actions menu
   • Then:
     • The count of open requests across all items in the instance should display in parentheses (e.g. "View requests (5)" OR
     • If displaying the total count is not possible, there should be some visual indication that there are any requests at all (we can ask UX for what this looks like when/if we've decided it's possible). Even when there are zero requests, it should still be possible to open the popup.
3. Scenario
   • Given the Inventory app
   • When an instance is selected
   • And an instance doesn't have a single item related
   • Then:
     • The Actions drop-down menu of an instance record is displayed without “View requests” button.
4. Scenario
   • Given the Inventory app
   • And the “View requests” button is presented in the Actions drop-down menu of an instance record (as per Scenario 1)
   • When the “View requests” button is clicked
   • Then:
     • The “Requests on items” page is launched
     • The pop-up window “Requests on items” includes
       • Header: Requests on items - <InstanceResourceTitle>, <InstancePublicationDate> (should look just like the header for the Instance record)
       • Count of the found records (total items in instance)
       • A list of instance items from all holdings presented as a table with next columns
         • Barcode - link to item record
         • Item status
         • Due - due date for items in status “Checked out” (format should be driven by locale)
         • Request queue - requests count calculated as all opened requests related to a certain item
           • This would include all requests with status "Open - Not yet filled", "Open - Awaiting pickup", "Open - Awaiting delivery" and "Open - In transit"
           • This count should match the count labeled "Requests" on the individual item records
           • This count should link to a pre-filtered view of the Requests app just as the request count on the item record does
         • Location - Item effective location
         • Loan type - Temporary loan type, if available, otherwise permanent loan type
         • Enumeration
         • Chronology
         • Material type
       • A scroll bar appears in case listed items don’t fit the window size
5. Scenario
   • Given an instance is selected in the Inventory app
   • And the “View requests” button is clicked (as per Scenario 3)
   • When item’s barcode is clicked
   • Then:
     • Close the request item list and open the item record view detail (this is nice-to-have - if it's difficult to develop, let's let it just stay open (we can always adjust later if user feedback suggests it is really annoying))
     • The item record (standard item details page) opens as a full page
     • All standard actions are available from the opened page
6. Scenario
   • Given an instance is selected in the Inventory app
   • And the “View requests” button is clicked (as per Scenario 3)
   • When request queue number is clicked
   • Then:
     • Close the request item list (this is nice-to-have - if it's difficult to develop, let's let it just stay open (we can always adjust later if user feedback suggests it is really annoying))
     • Open the pre-filtered view of the request app (per scenario 4 request queue bullet)
7. Scenario
   • Given an instance that has many associated items (could be in hundreds)
   • When “View requests” button is clicked (as per Scenario 3)
   • Then the system needs to handle the resulting performance hit gracefully (system shouldn't crash, should be some user feedback etc)

Mockups: https://drive.google.com/drive/folders/1-24vqFzpO5fKXbOYs3twg2uuQbRtgesE