Details
Description
Purpose: To begin work on item Requests in FOLIO. First request type will be recall. The scope of this story is viewing search results.
As a circulation staff person
I want to be able to create a recall request on a loaned item
So the patron will know they need to return the item to the library so it can be loaned to someone else
Scenarios:
- Scenario
- Given the search results list in the Requests app
- When displayed
- Then the columns should be:
- In scope for this story:
- Title - Title associated with requested item -(default primary sort) -
- Item barcode - Requested item's barcode
- Request type
- Requester
- Requester barcode - Barcode associated with requester
- Request date - Date and time request was first saved in FOLIO (default primary sort)
- Out of scope for this story:
- Author - Author associated with requested item (default secondary sort)
- In scope for this story:
- Scenario
- Given any column in the Requests app search results list
- When header is clicked
- Then the list should sort by that column (secondary sort should be the previous primary sort column)
- Scenario
- Given any column in the Requests app search results list
- When header is clicked a second time
- Then the list should sort reverse by that column
TestRail: Results
Attachments
Issue Links
- is blocked by
-
CIRC-27 create an endpoint for requests objects
-
- Closed
-
-
CIRC-29 Store requesting patron name and barcode as part of request
-
- Closed
-
-
CIRCSTORE-14 create an endpoint for requests objects
-
- Closed
-
-
UIREQ-4 set up a new "Requests" app
-
- Closed
-
-
UIREQ-20 Create Request Results in Error in Folio-testing
-
- Closed
-
-
UIREQ-49 refactor using SearchAndSort
-
- Closed
-
- relates to
-
CIRC-25 Aggregate metadata for ui-requests
-
- Closed
-
-
STRIPES-462 Factor out shared code in search-based modules
-
- Closed
-