Bug 8560 - renewing lost items
Summary: renewing lost items
Status: RESOLVED DUPLICATE of bug 9805
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low major
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-02 12:47 UTC by Nicole C. Engard
Modified: 2014-06-25 11:37 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Nicole C. Engard 2012-08-02 12:47:38 UTC
I got this report from a library:

When items age to long overdue lost, they assess a fee equivalent to the
replacement price of the item.

That makes sense.

When those items are checked in, the fee is removed and the titles no longer
display as checked out. The overdue does remain in the patron's history under
fines.

That also makes sense.

However, if we renew one of those items, it assigns a new due date, but does
not remove the fee or the long overdue lost designation.

And, if we take payment on the item, it balances out the fee, reducing the
amount due accordingly, but the title continues to display in the list of items
out as long overdue lost. The result of this is that our staff members continue
to mention these overdue items to the patron even after they've been taken care
of.

Other categories of lost - those that are manually set - remove the title from
the list of items out.

Renewing an item should also remove the fees and the long overdue designation.

And paying for the item should remove it from items out and show it only in
payment history.
Comment 1 Christopher Brannon 2014-04-21 18:03:34 UTC
We would like to see this addressed.  This is pretty significant.

Christopher
Comment 2 Kyle M Hall (khall) 2014-06-25 11:37:02 UTC

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