Uploaded image for project: 'UX Product'
  1. UX Product
  2. UXPROD-1684

Ability to add multiple items to a single courtesy or overdue notice

    XMLWordPrintable

Details

    • Large < 10 days
    • Medium
    • XXL < 30 days
    • Vega
    • 130.2
    • Hide
      Darcy
      - Already in progress
      - Hasn't been ranked by everyone, those that did rank it, ranked it highly
      - If multiple items are not supported, then patrons might receive several notices at the same time or near same time. A notice would be sent for each individual item coming due, checked out, etc.
      Show
      Darcy - Already in progress - Hasn't been ranked by everyone, those that did rank it, ranked it highly - If multiple items are not supported, then patrons might receive several notices at the same time or near same time. A notice would be sent for each individual item coming due, checked out, etc.
    • R2
    • R1
    • R1
    • R1
    • R1
    • R4
    • R1
    • R1
    • R1

    Description

      Purpose/Problem: Frequently a single patron will have several items borrowed, and all (or some) of those items will come due at the same time. Instead of sending several separate courtesy (or reminders of an impending due date/time) notices, it is preferred to send a single notice that refers to all items. Other examples with multiple items include overdue notices. Use cases include libraries where a patron might borrow 300 items at once, so it would be especially problematic (and annoying) to receive 300 separate emails for each item.

      Description:

      • Need to be able to include several items – OR – fees on a single notice sent to a patron.
      • For a check in receipt, all items within a check in session* for a patron should be included in a single notice.
      • For a check out receipt, all items within a check out session* for a patron should be included in a single notice.
      • Fora courtesy or overdue notice, any items within a certain threshold of a few minutes should be included in the same notice. For example, if there are 10 borrowed items by a patron that have various due dates/times, but they are within a 5 minute period of each other, then one notice should be sent including all 10 items. (Note to self: does this align with a check out session? Does that matter?)
      • Other notices might be defined to contain multiple items too, such as a request expiration, although these are probably rarer.

      *You can check in several items before closing the session.

      Implementation Thoughts:

      • Configure timing threshold (few minutes in description above) for time-based notices, such as courtesy and overdue notices.
      • Define UI for adding multiple items or fees to a notice template.

      https://docs.google.com/spreadsheets/d/1I8i1IUbuDz9XgBgSZ8xXmFymIQ9_R-Gc63I8RndEWiI/edit?usp=sharing

      TestRail: Results

        Attachments

          Issue Links

            is cloned by

            New Feature - New feature requests UXPROD-2187 Multiple items to a single check in receipt or check out receipt notice

            • P2 - normal priority level, must be included in the current development cycle
            • Closed
            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-412 [SPIKE] Define technical approach for ending a CHECK IN session to support multiple items on a notice

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-431 Add session record on CHECK OUT

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-432 Create API endpoint to end session for a patron

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-433 Create processor to define and end expired sessions

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-537 [SPIKE] Define technical approach for ending a CHECK IN session when operator closes browser or logs out of FOLIO

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-559 Add session record on CHECK IN

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-560 Modify CHECK-OUT processor to support CHECK-IN end expired sessions

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRCSTORE-149 Create API endpoint to retrieve patron IDs with expired sessions

            • TBD - To be determined
            • Closed

            Bug - A problem which impairs or prevents the functions of the product. CIRCSTORE-158 Add extra checks to patron notice policy form, loan section

            • TBD - To be determined
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSENDER-15 Performance testing - time-based patron loan notices (multiple items)

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Open

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-354 [SPIKE] Define technical approach for sending a CHECK OUT initiated patron loan notice with multiple items

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. CIRC-385 [SPIKE] Define technical approach for sending a time-based patron loan notice with multiple items

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-238 Ability to include multiple items on a single patron notice - courtesy and overdue only

            • P3 - low priority level, item will be considered for inclusion in the next dev cycle
            • Closed
            requires

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSENDER-10 [SPIKE] Learn JMETER and how to write/run performance tests

            • P2 - normal priority level, must be included in the current development cycle
            • Closed

            Activity

              People

                dbranchini Darcy Branchini
                dbranchini Darcy Branchini
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases