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 - Request
Given an item with a status of available for check-out
When it is paged (page requested)
And there's a matching circulation rule, notice policy and template
Then send a paging request confirmation notice to requester.
Scenario 2 - Cancel
Given a page requested item
When a FOLIO operator (or patron) cancels the request
And there's a matching circulation rule, notice policy and template
Then send a cancellation confirmation notice to requester.
TestRail: Results
Attachments
Issue Links
- is blocked by
-
CIRC-262 Implement sending request-related notices (user-initiated events)
-
- Closed
-
- relates to
-
CIRC-389 Send paging request- related notices (time based)
-
- Closed
-
-
MODSENDER-4 SPIKE: Determine Technical approach for sending patron notices
-
- Closed
-
-
UICIRC-220 End to End Testing: Send paging request- related notices (item status change)
-
- Closed
-
-
UXPROD-1585 Send patron notices for user initiated request events, such as recall request, page request, hold request, cancel, etc (via email)
-
- Closed
-