Patron Notices (UXPROD-18)

[UXPROD-3998] Bundle aged to lost fee/fines into a single notice (“Multiples”) when charging: Overnight Created: 30/Jan/23  Updated: 08/Feb/24  Resolved: 10/May/23

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: Poppy (R2 2023)
Parent: Patron Notices

Type: New Feature Priority: P2
Reporter: julie.bickle Assignee: julie.bickle
Resolution: Done Votes: 0
Labels: patron_notice
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
defines CIRC-1725 BE: Bundle multiple aged to lost fees... Closed
defines CIRC-1735 BE: Closed aged to lost fee/fines are... Closed
defines STRIPES-856 stripes-template-editor: Should have ... Closed
defines UICIRC-895 FE: Update patron notice policy: Mult... Closed
defines UICIRC-896 Mock-up for UXPROD-3998 Closed
defines UICIRC-904 FE: Add new multiples token: "Multipl... Closed
is defined by CIRC-1725 BE: Bundle multiple aged to lost fees... Closed
Issue split
split from UXPROD-2252 Multiple fee/fine charges or actions ... Open
Relates
relates to UICIRC-911 FE: In Add token modal, replace capit... Closed
Release: Poppy (R2 2023)
Epic Link: Patron Notices
Front End Estimate: Large < 10 days
Front End Estimator: Dmitriy Litvinenko
Front-End Confidence factor: 80%
Back End Estimate: XL < 15 days
Back End Estimator: Alexander Kurash
Back-End Confidence factor: 80%
Development Team: Vega
Report Functional Area(s):
Resource Access
PO Rank: 0
Rank: Cornell (Full Sum 2021): R1

 Description   

Current situation or problem:

  • Aged to lost fees (processing fee) and fines (aged to lost set cost) are generated according to the settings in the lost item fee policy (i.e. item ages to lost x time after being overdue >> patron is billed/charged x time after item aged to lost)
  • The patron notice policy contains a trigger (Lost item fee(s) charged) to send a notice when the patron is charged aged to lost fees/fines.
  • Currently, a SINGLE notice is sent out for every SINGLE fee/fine.
  • The aim of this feature = Send MULTIPLE fees/fines in a SINGLE notice.
  • The bundling happens OVERNIGHT ; using the same logic as for the due/date multiples.

 

Proposed solution/stories:

  • Create new multiples tokens for the Fee/Fine Charge section:
    • FE: Add new multiples token: "Multiple fee/fine charges" for the Fee/Fine Charge section: UICIRC-904
    • BE: Add the "Multiple fee/fine charges" tokens to the Fee/Fine Charge in the Notice context - Vega to add/edit as necessary
    • BE: Populate the "Multiple fee/fine charges" tokens in the notices, with the data provided by the context - Vega to add/edit as necessary
  • Update the notice policy:
    • FE: Update patron notice policy: Multiples options for Lost item fee(s) charged: UICIRC-895 Closed
    • BE: Bundle mutliple aged to lost fees/fines into one single notice: CIRC-1725
    • BE: Closed aged to lost fee/fines are not included in bundled notices: CIRC-1735 Closed
  • Update UI in keeping with FOLIO's sentence case style: 
    • FE: In Add token modal, replace capital F, C and A with lowercase f, c and a: UICIRC-911

Out of scope:

  • Bundling aged to lost fees/fines during the day.

Questions

  • What timing issues could arise?


 Comments   
Comment by julie.bickle [ 10/May/23 ]

I confirm this works in Snapshot.

Generated at Fri Feb 09 00:36:28 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.