Fees/Fines (UXPROD-792)

[UXPROD-3276] Future Fees/Fines: Change process used to determine time interval for overdue items Created: 10/Sep/21  Updated: 12/Jan/23

Status: Draft
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: None
Parent: Fees/Fines

Type: New Feature Priority: TBD
Reporter: Holly Mistlebauer Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: Unassigned-from-Holly
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Defines
is defined by MODFEE-213 Document calculation used for overdue... Closed
is defined by MODFEE-215 Are seconds used in calculating overd... Closed
Relates
relates to MODFEE-205 Fines charged are incorrect, being un... Closed
Epic Link: Fees/Fines
Development Team: Vega
PO Rank: 0
Rank: Cornell (Full Sum 2021): R2
Rank: Duke (Full Sum 2021): R1

 Description   

NOTE: This feature was created after we discovered that bug MODFEE-205 Closed is not really a bug, but rather how the overdue process was designed.  Please note that Erin N. has created a wiki page at https://folio-org.atlassian.net/wiki/x/7YxW that covers the issues related to this ticket.

Items that are overdue may be checked out for minutes, hours, days, etc.  The overdue fine associated with the item is also in minutes, hours, days, etc.  This would work easily if the loan and overdue fine used the same interval, but often they do not.  For example, a 3-day loan may have an overdue fine calculated by minutes.  To facilitate this, we designed the process to convert all intervals to minutes (the lowest interval), then break it into the correct interval for the overdue fine.  This mostly works, given we have not heard from any sites until recently, but there are at least two cases where we may not be charging one interval less than we should be.  These cases include:

  1. Items that are overdue by days, as described in MODFEE-205 Closed .  The patrons in this case are being charge one day too little. This appears to happen in cases where we don't count closed time.  (We don't tend to test the day/month calculations because of the testing environment, although they were tested initially.)
  2. I have noticed that the overdue fines in minutes also can be 1 minute short.  I have assumed this is because the calculation considers seconds, which we cannot see in the UI.  I am not sure if this only happens when not counting closed times or not. We should address that issue at the same time as we address the issue uncovered by MODFEE-205 Closed

*NOTE: Institutions should add any other scenarios in error to this UXPROD.



 Comments   
Comment by Erin Nettifee [ 10/Sep/21 ]

Holly Mistlebauer I think there may also be problems in here with the calculation when the policy says not to charge during closed hours - I think that was the main problem in modfee-205, since if they had calculated closed hours the intervals would have worked as expected.

Comment by Holly Mistlebauer [ 10/Sep/21 ]

Erin Nettifee: Thanks for the reminder! That is a critical piece of the puzzle...

Comment by Holly Mistlebauer [ 12/Jan/23 ]

Is this still happening? Per German libraries it appears to be an issue now...

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