Requests (UXPROD-790)

[UXPROD-2729] Allow Recalls to Extend Due Dates on Overdue Loans (Configurable) Created: 06/Oct/20  Updated: 10/May/21  Resolved: 10/May/21

Status: Closed
Project: UX Product
Components: None
Affects versions: None
Fix versions: R1 2021
Parent: Requests

Type: New Feature Priority: TBD
Reporter: Cate Boerema (Inactive) Assignee: Cheryl Malmborg
Resolution: Done Votes: 0
Labels: Showstopper-Cornell
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by CIRC-994 Extend overdue loans when recalled (i... Closed
is defined by CIRC-1018 Modify logic for setting "dueDateChan... Closed
is defined by CIRCSTORE-257 BE: Loan policy: Allow recalls to ext... Closed
is defined by UICIRC-525 Loan policy: Allow recalls to extend ... Closed
Epic Link: Requests
Front End Estimate: Medium < 5 days
Front End Estimator: Cate Boerema (Inactive)
Back End Estimate: Large < 10 days
Estimation Notes and Assumptions: CB: Spoke with Marc about the estimate. He thought 10 days assuming that we put some kind of toggle in a policy (loan policy?) that would allow libraries to switch between how recalls affect overdue loans (to support both Chalmers and Chicago's needs)
Development Team: Prokopovych
PO Rank: 102
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R3
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: MO State (MVP June 2020): R1
Rank: U of AL (MVP Oct 2020): R4

 Description   

Current situation/problem: When an overdue item is recalled, the due date is not extended. Recalls on overdue loans used to extend the due date in FOLIO, but that behavior was seen as a bug by Chalmers and it was fixed (see CIRC-801 Closed ). It turns out that Chicago (and others?) actually want recalls on overdue items to extend the due date. The reason is that, for Chicago, overdue items without recalls don't accrue fees and fines while recalled overdue items do. Consider this situation:

  • Loaned item is due today
  • Patron is getting themselves organized to return the item (they aren't in a rush because they know they won't be charged fees and fines until it has been late for 3 weeks (at which time Chicago assigns a lost item fee))
  • Item is recalled and, per current FOLIO behavior, no notice is sent to the patron because the item is already overdue
  • Patron returns the item 5 days after it was due only to find out that they have unexpectedly been charged a daily fine

In scope: Introduce a setting either in the loan policy or at the tenant level that would allow institutions to indicate whether they want post-overdue recalls to extend the due date of a loan.

Out of scope:

Use case(s):

Proposed solution/stories:

Links to additional info:

Questions:



 Comments   
Comment by Brooks Travis [ 30/Oct/20 ]

Along with some other issues around recall fees/fines/lost item timing, this is actually proving to be a significant point of concern for us. We haven’t been able to utilize recalls on items the way we’d like as a result.

Comment by Marie Widigson [ 09/Nov/20 ]

Introducing a setting for this would be great. As mentioned, Chalmers do not want the loan period to be prolonged when the item is recalled but understand that others might need this. However, a notice to the patron that the overdue loan ALSO is recalled would be very nice.

Comment by Marie Widigson [ 09/Nov/20 ]

Ranking as Not needed as we don't need the feature itself, but if it's regarding a setting we would rank it higher. We do not want the (for us) bug to reappear.

Comment by Cate Boerema (Inactive) [ 09/Nov/20 ]

Marie Widigson, I promise we will make this configurable so the bug won't reappear for Chalmers

Also, if you are interested in a notice when an item is overdue and recalled, you may be interested in UXPROD-2112 Draft

Comment by Anya [ 22/Apr/21 ]

Cheryl Malmborg will this be included in Iris? If so could it be added to the release notes?- thanks 

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