[SPIKE] Define technical approach for ending a CHECK IN session to support multiple items on a notice

Split - see CIRC-537.

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 in session ends, which includes:

• When FOLIO operator hits End Session on Check-In App Screen
• When a check in session times out due to inactivity
• When FOLIO operator closes browser, which closes the existing session CIRC-537
• When FOLIO operator logs out, which closes the existing session CIRC-537

Scenarios

Scenario 1 - Check in

• FOLIO operator opens check in screen
• Then scans 7 items borrowed by Patron A
• Then scans 10 items borrowed by Patron B
• Then scans 2 items borrowed by Patron C
• Then ends session (notices are sent to Patrons A with the 7 items, B with the 10 items and C with the 2 items)

Scenario 2 - Check in

• FOLIO operator opens check in screen
• Then scans 30 items (picked up at the overnight drop off bin) borrowed and returned by a variety of patrons (and in a random order)
• Then ends session (a single notice is sent to each patron represented in this session and each notice will contain all items returned for that patron)

Scenario 3 - If a check in session is ended in between a patron's check out (unlikely)

• FOLIO operator opens check in screen
• Then scans Patron A's 4 of 7 borrowed items
• Then ends session (notice is sent to Patron A with the 4 items)
• Then scans Patron A's remaining 3 of 7 items
• Then scans Patron B's 10 items
• Then scans Patron C's 2 items
• Then ends session (notices are sent to Patrons A (3 items), B and C)

Scenario 5 - If a check in session times out

• FOLIO operator opens check in screen
• 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)

*Settings > Circulation > Other settings > Automatically end check in session after period of inactivity [ ] minutes – THIS WILL BE ADDED TO FOLIO (separate story)

Requirements

• Must support user-initiated loan notices (e.g. check in 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-238 and 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