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

Multiple fee/fine charges or actions (pay, waive, transfer, error or refund) on a single notice for a patron

    XMLWordPrintable

    Details

    • Template:
      UXPROD features
    • Epic Link:
    • Front End Estimate:
      Large < 10 days
    • Back End Estimate:
      XXXL: 30-45 days
    • Confidence factor:
      Medium
    • Development Team:
      Vega
    • Calculated Total Rank:
      104
    • Kiwi Planning Points (DO NOT CHANGE):
      43
    • PO Rank:
      95
    • PO Ranking Note:
      Hide
      This is important for UXPROD-2165 (aged to lost notices), since depending on the policy and how it's configured, they might have two fees charged at once (lost item fee as set cost or actual cost and processing fees).
      Show
      This is important for UXPROD-2165 (aged to lost notices), since depending on the policy and how it's configured, they might have two fees charged at once (lost item fee as set cost or actual cost and processing fees).
    • Rank: Chicago (MVP Sum 2020):
      R1
    • Rank: Cornell (Full Sum 2021):
      R1
    • Rank: Duke (Full Sum 2021):
      R1
    • Rank: 5Colleges (Full Jul 2021):
      R1
    • Rank: FLO (MVP Sum 2020):
      R1
    • Rank: GBV (MVP Sum 2020):
      R2
    • Rank: Grand Valley (Full Sum 2021):
      R1
    • Rank: hbz (TBD):
      R4
    • Rank: Lehigh (MVP Summer 2020):
      R1
    • Rank: Mainz (Full TBD):
      R2
    • Rank: MO State (MVP June 2020):
      R1
    • Rank: TAMU (MVP Jan 2021):
      R1
    • Rank: U of AL (MVP Oct 2020):
      R3

      Description

      Dec 2019 - split from:

      • UXPROD-1684 DONE (multiple items on overdue and courtesy notices)
      • UXPROD-2187 DONE (multiple items on check in and check out receipt notices)

      Jan 2020 - split from:

      • UXPROD-2188 OPEN (multiples items on request notices)

      Current Situation or Problem: A separate notice is sent for each new fee/fine charge and/or each action (payment, transfer, waive, refund or cancel) taken on a fee/fine. For an aged to lost scenario, if a lost item processing fee is charged in addition to a replacement fee, it would be preferred to send the patron a single notice instead of two (one for each charge) - see UXPROD-2165. Also, a patron's fee/fine may be partially waived, partially paid, or an action may be applied to multiple fees/fines at once. In all of these scenarios, it would be preferable to send a single notice with all actions taken on all charges. And lastly, this functionality is required for a fee/fine statement to be sent to a patron - see UXPROD-2113.

      In scope:

      • Need to be able to include several fees/fine charges in a single notice (aged to lost scenario above).
      • Need to be able to include several fees/fine charges of the same type in a single notice (i.e., several items age to lost at the same time and incur charges at the same time).
      • Need to be able to include multiple actions (payment, transfer, waive, refund or cancel (error) taken on a single fee/fine in a single notice (fee/fine detail page).
      • Need to be able to include multiple actions taken on multiple fees/fines in a single notice (fee/fine history page).
      • Need to be able to show historical actions on a fee/fine charge.

      Out of scope

      • Querying patrons to find all patrons matching a specific criteria and then sending an ad hoc notice to just those patrons (see UXPROD-1771). Examples include all patrons with a specific outstanding balance of $100 or greater or all patrons graduating this Spring with overdue loans.
      • Fee/fine statements (see UXPROD-2113).

      Use case(s)
      See stories for use cases (MODFEE-76 and MODFEE-74).

      Proposed solutions/stories:

      • Consider using sessions on the fee/fine history and/or details page for bundling multiple actions.
      • For actions not including a charge, the user (staff person) is prompted to send a notice or not. For a first implementation of this, consider the use of the "Notify patron" checkbox instead of sessions. A historical representation of a fee/fine charge and all actions taken on it would still be required (similar to the fee/fine detail page).
      • An automated fee/fine, such as aged to lost, would need to consider there's a possibility of two or more related charges, such as set cost and other processing fees. How to know they are related fees?
      • For multiple overdue fees/fines or multiple aged to lost fees/fines bundled and sent as one, how? Scheduled and nightly? As overdue notices are sent?

      Linked spreadsheet is a comprehensive summary of multiples on all types of notices with their priority as determined by the RA SIG.
      https://docs.google.com/spreadsheets/d/1I8i1IUbuDz9XgBgSZ8xXmFymIQ9_R-Gc63I8RndEWiI/edit?usp=sharing

        TestRail: Results

          Attachments

            Issue Links

              Activity

                People

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

                  Dates

                  Created:
                  Updated:

                    TestRail: Runs

                      TestRail: Cases