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

CRUD Patron Notice Policies - Loan-related notices only (part 1)

    XMLWordPrintable

Details

    • Large < 10 days
    • XL < 15 days
    • XXL < 30 days
    • Hide
      Modified issue - logic in notice policies instead of workflow or other policies (loan, fee/fine, request). Need new estimates. BE estimates assumes the scheduling, event triggers/listener logic is built specifically for PN rather than relies on existing functionality provided though UXPROD-594 and UXPROD-729

      Jakub: XXL for the backend since this may include coding internal scheduling logic. XL for the UI, the assumption is all logic lives on the server and UI is merely a configuration interface.
      Show
      Modified issue - logic in notice policies instead of workflow or other policies (loan, fee/fine, request). Need new estimates. BE estimates assumes the scheduling, event triggers/listener logic is built specifically for PN rather than relies on existing functionality provided though UXPROD-594 and UXPROD-729 Jakub: XXL for the backend since this may include coding internal scheduling logic. XL for the UI, the assumption is all logic lives on the server and UI is merely a configuration interface.
    • Vega
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1
    • R1

    Description

      IMPORTANT NOTE: As a first pass, this feature has been modified for notices sent via email related to loan activities only. There are new features created for request-related notices and fee/fine-related notices as well as SMS and print notices.

      Needs to allow for scheduling, event triggers/listeners, and other conditions. This function will be configured using in policies, including loan, request and fee/fine policies, and general configuration for notices. Early hand-drawn mockups are attached.

      See UXPROD-110 for earlier reference to patron notices, as well as UXPROD-675 and UXPROD-723 for setting up the name, description and templates.

      –
      Initially thought Workflow would be the right solution. Here's the original thinking on that:
      A visual representation of one use case is attached. It assumes a UI will be developed for the workflow engine. The attached visual shows two different notices sent at different points in time, overdue notice #1 is sent at Day 1 (maybe immediately is more appropriate here), and then overdue notice #2 is sent at Day 3. Additional criteria might include loan type, patron type (group), and/or loan policy.

      TestRail: Results

        Attachments

          1. fee fine lost.png
            fee fine lost.png
            376 kB
          2. fee fine overdue.png
            fee fine overdue.png
            445 kB
          3. fee fine overdue options.png
            fee fine overdue options.png
            379 kB
          4. loan policy - notice 1.png
            loan policy - notice 1.png
            414 kB
          5. loan policy - notice 2.png
            loan policy - notice 2.png
            684 kB
          6. receipts.png
            receipts.png
            612 kB
          7. request available.png
            request available.png
            606 kB
          8. request available options.png
            request available options.png
            620 kB
          9. request - recall.png
            request - recall.png
            545 kB
          10. Screen Shot 2018-05-25 at 10.25.17 AM.png
            Screen Shot 2018-05-25 at 10.25.17 AM.png
            19 kB

          Issue Links

            relates to

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. MODSENDER-4 SPIKE: Determine Technical approach for sending patron notices

            • 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-110 SPIKE: CRUD patron notice policies

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

            New Feature - New feature requests UXPROD-1386 Send patron notices via email for user initiated loan events, such as check in/out (i.e., check in or out receipt)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-1387 Add Request-Related Notice Settings to Patron Notice Policy

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-1585 Send patron notices for user initiated request events, such as recall request, page request, hold request, cancel, etc (via email)

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            New Feature - New feature requests UXPROD-1587 Send patron notices for time based request events, such as hold expiration or request expiration via email

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

            New Feature - New feature requests 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

            • P1 - highest priority item, drop everything else before this is resolved, reserved for critical bugfixes
            • Closed

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-98 New/edit notice policy

            • 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-108 View notice policy

            • 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-109 Delete notice policy

            • 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-167 Settings - list of notice policies

            • 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-181 Permission Set for Notice Policy CRUD

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

            Story - Created by Jira Software - do not edit or delete. Issue type for a user story. UICIRC-198 Add toggle for user initiated v. time based events to notices

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

            New Feature - New feature requests UXPROD-1217 Extending Loan Rules Editor to target additional policy types

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

            New Feature - New feature requests UXPROD-1392 Extend patron notices to print

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

            New Feature - New feature requests UXPROD-1393 Extend patron notices to SMS

            • P4 - lowest priority level, nice-to have things that require future discussion and design
            • Draft

            Activity

              People

                dbranchini Darcy Branchini
                dbranchini Darcy Branchini
                Darcy Branchini Darcy Branchini
                Jakub Skoczen Jakub Skoczen
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Dates

                  Created:
                  Updated:
                  Resolved:

                  TestRail: Runs

                    TestRail: Cases