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

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

    XMLWordPrintable

    Details

    • Template:
    • Epic Link:
    • Analysis Estimate:
      Large < 10 days
    • Front End Estimate:
      XL < 15 days
    • Back End Estimate:
      XXL < 30 days
    • Estimation Notes and Assumptions:
      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.
    • Development Team:
      Vega
    • Calculated Total Rank:
      90
    • Rank: BNCF (MVP Feb 2020):
      R1
    • Rank: Chalmers (Impl Aut 2019):
      R1
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: GBV (MVP Sum 2020):
      R1
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      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

              Activity

                People

                Assignee:
                dbranchini Darcy Branchini
                Reporter:
                dbranchini Darcy Branchini
                Analysis Estimator:
                Darcy Branchini Darcy Branchini
                Front End Estimator:
                Jakub Skoczen Jakub Skoczen
                Back End Estimator:
                Jakub Skoczen Jakub Skoczen
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                  Dates

                  Created:
                  Updated:
                  Resolved:

                    TestRail: Runs

                      TestRail: Cases