Details
-
Story
-
Status: Closed (View Workflow)
-
P1
-
Resolution: Done
-
None
-
None
-
None
-
-
Vega
Description
Context
Paging requests include items that are currently available (and not checked-out by another patron). These items are pulled from their home shelf and put on the service point's hold shelf for pick-up by the patron that requested the item.
The paging request process prompts several patron notices. Specific notices are outlined below.
For each of these scenarios, exact timing and conditions are determined by a combination of notice policies and circulation rules, and exact wording is determined by templates. Each of these specific scenarios may or may not be used by every institution. If there's no corresponding policy defined in settings, then these scenarios won't apply.
Scenario 1 - Available
Given a page requested item
When it is scanned in at requested location, item status is changed to "available - awaiting pickup," and it's put on hold shelf for the patron
And there's a matching circulation rule, notice policy and template
Then send an available notice to the requester at the top of the queue
TestRail: Results
Attachments
Issue Links
- has to be done after
-
CIRC-256 Send request-related notices (item status change)
-
- Closed
-
- relates to
-
CIRC-389 Send paging request- related notices (time based)
-
- Closed
-
-
UICIRC-155 End to End Testing: Send paging request- related notices (user initiated)
-
- Closed
-
-
UXPROD-1589 Send patron notices for item status changes (request related), such as available - awaiting pickup (i.e., available notice for recalled item) via email
-
- Closed
-