Bug 20769 - Duplicate fine generated when lost item is returned
Summary: Duplicate fine generated when lost item is returned
Status: RESOLVED DUPLICATE of bug 22877
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: 17.11
Hardware: PC Windows
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-15 11:33 UTC by Lucy Vaux-Harvey
Modified: 2019-05-14 09:54 UTC (History)
6 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Lucy Vaux-Harvey 2018-05-15 11:33:18 UTC
User has an overdue item with a status of Longoverdue (Lost) which has been set from the DefaultLongOverdueLostValue DefaultLongOverdueDays preference.  The maximum fine per loan has been accumulated (5 GBP).

BlockReturnOfLostItems set to Block

Item is checked in – check in is blocked as required however the Longoverdue (Lost) status is removed. 

Item can now be checked in again as it no longer has a Lost status and at this point a second max fine of 5 GBP is charged to the account.
Comment 1 Andrew Fuerste-Henry 2018-07-03 20:41:01 UTC
Lucy, are you forgiving the accumulated fine when the item becomes lost? So that there's a $5 fine, it gets cleared when the item becomes lost, and then re-accumulates when the item later becomes found and is turned in?
Or does the original $5 fine remain and then duplicate, creating a total fine of $10?
Altogether, I'm not sure this syspref performs as most users will expect -- it blocks *only* the return of the item, still allowing it to be marked as found and generate a refund. My sense is most users would expect this to perform more like BlockReturnofWithdrawn items, which stops Koha from interacting with the item at all.
Comment 2 Lucy Vaux-Harvey 2018-07-12 13:51:34 UTC
Hi Andrew, WhenLostForgiveFine is set to Don't forgive so a full duplicate fine is being charged.
Comment 3 Lisette Scheer 2019-03-19 22:21:32 UTC
This is happening for us as well and our settings are:
 BlockReturnofLostItems to Not Block. 

Lisette
Comment 4 Donna 2019-03-29 12:58:31 UTC
Another library has reported this also.  Item is lost, returned, and charged max fine twice.  Settings are Do Not BlockReturnofLostItems and Don't forgive  WhenLostForgiveFine.
Comment 5 Lisette Scheer 2019-05-09 20:23:27 UTC

*** This bug has been marked as a duplicate of bug 22877 ***