Patron Notices (UXPROD-18)

[UXPROD-2112] New triggers for overdue then recalled, and recalled and overdue Created: 11/Oct/19  Updated: 23/Feb/23

Status: Draft
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Patron Notices

Type: New Feature Priority: P2
Reporter: Darcy Branchini Assignee: julie.bickle
Resolution: Unresolved Votes: 3
Labels: new_notice, patron_notice, round_iv
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Relates
relates to CIRC-1163 Notices scheduled in the past are bei... Closed
relates to UXPROD-2424 RTAC | Patron empowerment - EDGE-PAT... Closed
Epic Link: Patron Notices
Front End Estimate: Small < 3 days
Front-End Confidence factor: Low
Back End Estimate: XXL < 30 days
Development Team: Volaris
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


 Comments   
Comment by Holly Mistlebauer [ 17/Jun/20 ]

Chicago comment from Round IV Outliers spreadsheet: Currently even if we recall an item, the notices go out on the schedule of the original loan. So while they patron gets the initial recall notices, the reminders (and the language of the reminder) are on based on the original due date. Also, it would calculate fines and age to lost on the schedule of the original loan, not based on the recall due date.We do few recalls these days, but when we do it's for things like course reserve, where we can't have this ambiguity. -Tod Olson

Comment by Cate Boerema (Inactive) [ 30/Jun/20 ]

Hi Darcy Branchini, as I was writing this comment on CIRC-810, it occurred to me that you might need two separate notice triggers for the following scenarios:

  1. Recalled item becomes overdue - Here you want to say "Your recalled item is now overdue. When recalled items are overdue, elevated fees and fines apply."
  2. Overdue item is recalled - Here you might want to say "Your overdue item has now been recalled meaning elevated fees and fines will now apply"

My point is that wording might need to be slightly different. I could be wrong about this, but it's probably something to discuss with the RA SIG if you haven't already.

Holly Mistlebauer, I don't know if you have considered how fees and fines will be applied to loans that were already overdue when the item was recalled. Will the elevated fees and fines apply to all days overdue or only the days after which the item was recallled.

Comment by Darcy Branchini [ 15/Jul/20 ]

I think you're right about this Cate Boerema, thanks for bringing this to my attention.

Comment by David Bottorff [ 17/Nov/21 ]

There doesn't seem to have been any recent actions on this, Is there a way to prioritize this?

Comment by David Bottorff [ 27/Jan/22 ]

I see there's been no response to my query about this from November. Any update?

Comment by julie.bickle [ 31/Jan/22 ]

Sorry, I have been (trying to) working on features that were higher up in the Kiwi pointing excercise + looking at what availabilty Vega has.

Comment by Brooks Travis [ 14/Feb/22 ]

Massey is also interested in this functionality.

Comment by julie.bickle [ 14/Mar/22 ]

Note to Julie: When this feature gets addressed, should CIRC-1163 be part of the feature?

Comment by David Bottorff [ 09/Sep/22 ]

I'll note that Chicago has discovered that it an item's due date is truncated (by for example a recall) such that multiple courtesy or overdue notices would be sent, FOLIO combines those into a single email notice but repeats the loan info for the item as many times as the notice template would be invoked.

It's also not clear to me if this feature takes into account the need to send a different type of courtesy notice for recalled items that are not yet due, in addition to the original recall notice AND any overdue recall notices. Is there another Jira that specs that out?

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