Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
customfield_11100 15484
-
None
-
Very Small (VS) < 1 day
-
High
-
Estimate assumes proxy work, locations and other not-yet-existent elements are estimated separately
-
Medium < 5 days
Description
Purpose: To refine the layout and styling of the New request screen in FOLIO to align with decisions by the Resource Access SIG and UX designers
Scenarios:
- Scenario
- Given New request screen
- When displayed prior the input of item and requester
- Then the following sections should appear, as shown in the attached wireframe 1_CreateRequest.png:
- Request information - Not collapsible
- Item information - Not collapsible
- Requester information - Not collapsible
- Scenario
- Given the Request information section on New request screen, prior to input of item and requester
- When displayed
- Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequest.png:
- Request type
- Request expiration date
- Scenario
- Given the Item information section on New request screen, prior to input of item and requester
- When displayed
- Then the following data element should appear, as shown in the attached wireframe 1_CreateRequest.png:
- [unlabelled field to input item barcode]
- Scenario
- Given the Requester information section on New request screen, prior to input of item and requester
- When displayed
- Then the following data element should appear, as shown in the attached wireframe 1_CreateRequest.png:
- [unlabelled field to input requester barcode]
- Scenario
- Given New request screen
- When displayed after the input of item and requester
- Then the following sections should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
- Request information - Not collapsible
- Item information - Not collapsible
- Requester information - Not collapsible
- Scenario
- Given the Request information section on New request screen, after input of item and requester
- When displayed
- Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
- Request type
- Request expiration date
- Scenario
- Given the Item information section on New request screen, after input of item and requester
- When displayed
- Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
- [unlabelled field to input item barcode]
- Item barcode
- Title
- Author
- Shelving location
- Call number
- Volume
- Enumeration
- Copy
- Item status
- Current due date
- Requests (the number of active requests on this item)
- Scenario
- Given the Requester information section on New request screen, after input of item and requester, with
- Fulfillment preference = “Hold shelf”
- When displayed
- Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy-HoldShelf.png:
- [unlabelled field to input requester barcode]
- Requester name and Requester barcode
- Patron group
- Fulfillment preference
- Pickup location
- Requester’s Proxy (if the request is being placed by a proxy on behalf of their sponsor)
- Given the Requester information section on New request screen, after input of item and requester, with
- Scenario
- Given the Requester information section on New request screen, after input of item and requester, with
- Fulfillment preference = “Delivery”
- When displayed
- Then the following data elements should appear, as shown in the attached wireframe 1_CreateRequestProxy.png:
- [unlabelled field to input requester barcode]
- Requester name and Requester barcode
- Patron group
- Fulfillment preference
- Delivery address
- Requester’s Proxy (if the request is being placed by a proxy on behalf of their sponsor)
- Given the Requester information section on New request screen, after input of item and requester, with