The ou setting circ.max_accept_return_of_lost should prevent restoration of overdues if lost items are checked in beyond the set interval

Bug #1792408 reported by Michele Morgan on 2018-09-13
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

If the library setting circ.void_lost_on_checkin is set to True, the lost item billing will be voided when the item is checked in.

The circ.max_accept_return_of_lost org unit setting allows configuring a max allowed return time. If the lost item is checked in after this interval, the lost billing will not be voided.

When using the following library settings:

circ.void_overdue_on_lost' - TRUE
circ.void_lost_on_checkin - TRUE
circ.restore_overdue_on_lost_return - TRUE
circ.lost.generate_overdue_on_checkin - TRUE
circ.max_accept_return_of_lost - "5 years"

If the item is checked in after being Lost for more than 5 years, the Lost billing remains, as the setting dictates. However the overdue fine is also restored.

The circ.max_accept_return_of_lost setting should work similar to the circ.max_accept_return_of_longoverdue, the desription of which states:

Long-overdue check-in processing (voiding fees, re-instating overdues, etc.) will not take place for items that have been overdue for (or have last activity older than) this amount of time

Lost check-in processing should likewise not happen beyond the circ.max_accept_return_of_lost interval.

Sample use case:

When an item is overdue for more than more than 1 year, it is marked Lost. Any overdue fines the patron has accrued for the item are voided in favor of the Lost billing. When the item is 5 years overdue, it is presumed that the item will never be returned. The item is then checked in and deleted. The Lost billing should remain on the patron's record, but the overdue fine should not be restored.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers