Details
-
Story
-
Status: Closed (View Workflow)
-
P3
-
Resolution: Done
-
None
-
None
-
-
EPAM-Veg Sprint 23, EPAM-Veg Sprint 24
-
5
-
Vega
Description
Note: Split last two scenarios into a separate issue – CIRC-462.
As a library user, I want one email that includes all information and items from my library based on an action [listed below*] because I do not want to receive several emails or an email for each item.
In summary, notices are sent when a check out session ends, which includes:
- When FOLIO operator hits End Session on Check-out App Screen
- When FOLIO operator scans (or enters) a new Patron ID, which starts a new check out session
- When a check out session times out due to inactivity
When FOLIO operator closes browser, which closes the existing sessionCIRC-462When FOLIO operator logs out, which closes the existing sessionCIRC-462
Scenarios
Scenario 1 - Check out
- FOLIO operator opens check out screen
- Then enters the barcode or scans Patron A's info
- Then scans Patron A's 10 items
- Then enters the barcode or scans Patron B's info (switching to new patron/new session, so notice is sent to Patron A with their 10 items)
- Then scans Patron B's 3 items
- Then enters the barcode or scans Patron C's info (switching to new patron/new session, so notice is sent to Patron B with their 3 items)
- Then scans Patron C's 8 items
- Then ends session (notice is sent to Patron C with their 8 items)
Scenario 2 - If a check out session is ended in between a patron's check out (unlikely)
- FOLIO operator opens check out screen
- Then enters the barcode or scans Patron A's info
- Then scans Patron A's 7 of 10 items
- Then ends session (notice is sent to Patron A with their 7 items)
- Then starts a new session
- Then scans Patron A's remaining 3 of 10 items
- Then enters the barcode or scans Patron B's info (switching to new patron/new session, so notice is sent to Patron A with their remaining 3 items)
- Then scans Patron B's 3 items
- Then ends session (notice is sent to Patron B with their 3 items)
Scenario 3 - If a check out session times out
- FOLIO operator opens check out screen
- Then enters the barcode or scans Patron A's info
- Then scans Patron A's 10 items
- Then 30 minutes expires
- Session automatically times out and ends due to inactivity based on tenant configuration* (notice is sent to Patron A with their 10 items)
*Settings > Circulation > Other settings > Automatically end checkout session after period of inactivity [ ] minutes
Requirements
- Must support user-initiated loan notices (e.g. checkout items in one session)
- No expectations of sending an email that includes multiple notice types (e.g. an email should not include loan info and request info)
- No expectations of sending an email that includes multiple templates
- Items may span different loan policies
Spike Deliverables
- Technical approach must address scenarios outlined in
UICIRC-238and https://docs.google.com/document/d/1OylEJ6eDx8h7PvuwBa2jKO4dKrgDjnQ4H13oXA57TnY/edit#heading=h.hbd6j2t3hjc9 (see Problem 1, 2, 3 tables) . Please add approach to JIRA as a comment and present to team for approval - Generate or update user stories based on approved technical approach
- Identify dependencies
TestRail: Results
Attachments
Issue Links
- is cloned by
-
CIRC-385 [SPIKE] Define technical approach for sending a time-based patron loan notice with multiple items
-
- Closed
-
-
CIRC-412 [SPIKE] Define technical approach for ending a CHECK IN session to support multiple items on a notice
-
- Closed
-
- relates to
-
CIRC-431 Add session record on CHECK OUT
-
- Closed
-
-
CIRC-432 Create API endpoint to end session for a patron
-
- Closed
-
-
CIRC-433 Create processor to define and end expired sessions
-
- Closed
-
-
CIRC-559 Add session record on CHECK IN
-
- Closed
-
-
CIRC-560 Modify CHECK-OUT processor to support CHECK-IN end expired sessions
-
- Closed
-
-
CIRCSTORE-147 Create DB table to store check-in/check-out session information
-
- Closed
-
-
CIRCSTORE-149 Create API endpoint to retrieve patron IDs with expired sessions
-
- Closed
-
-
UXPROD-1684 Ability to add multiple items to a single courtesy or overdue notice
-
- Closed
-
-
CIRCSTORE-148 Create CRUD API endpoints for patron session
-
- Closed
-
-
MODSENDER-8 [SPIKE] Investigate sending multiple messages at the same time.
-
- Closed
-
- requires
-
UICIRC-238 Ability to include multiple items on a single patron notice - courtesy and overdue only
-
- Closed
-