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

New triggers for overdue then recalled, and recalled and overdue

    XMLWordPrintable

    Details

    • Type: New Feature
    • Status: Draft (View Workflow)
    • Priority: P2
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      Small < 3 days
    • Back End Estimate:
      XXL < 30 days
    • Confidence factor:
      Low
    • Development Team:
      Vega
    • Calculated Total Rank:
      61
    • PO Rank:
      90
    • Rank: Chalmers (Impl Aut 2019):
      R2
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R2
    • Rank: 5Colleges (Full Jul 2021):
      R2
    • Rank: GBV (MVP Sum 2020):
      R4
    • Rank: Grand Valley (Full Sum 2021):
      R4
    • Rank: hbz (TBD):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R2
    • Rank: MI State-Lib of MI (Sum 2021):
      R2
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R3

      Description

      Current situation or problem:

      • Overdue and recall triggers are both available as separated triggers now in FOLIO. This feature would support two new types of combined triggers in order to allow administrators to define a separate or different notice template for overdue loaned items that are then recalled by another patron or recalled items that are also overdue. This is needed because different language and policies are applied for these loans in order to express the urgency and inflated fee/fines since another patron is waiting for the item.

      Proposed solution/stories:

      • Two scenarios need to be supported so it'll be two new triggers:
        • Loan/item is first overdue, and then it is recalled – considered a special recall notice (would be sent once upon recall)
        • An item is recalled and overdue – considered a type of overdue notice (would be sent one times or more as reminder notices)
      • Stories:
        • BE story for storage for each of the two new triggers
        • BE story for processing/logic for each of the two new triggers
        • BE story to stop "regular" overdue notices when an item is overdue and it's recalled (if that trigger is being used)
        • FE story to add new trigger to notice policy for each of the two new triggers

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

                Assignee:
                JulieBickle_LMU Julie Bickle
                Reporter:
                dbranchini Darcy Branchini
                Votes:
                0 Vote for this issue
                Watchers:
                6 Start watching this issue

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases