Bug 8506 - return date of lost items recorded wrong
Summary: return date of lost items recorded wrong
Status: CLOSED WORKSFORME
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: Main
Hardware: All All
: P5 - low major (vote)
Assignee: Bugs List
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-25 18:54 UTC by Nicole C. Engard
Modified: 2020-01-06 20:14 UTC (History)
5 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 Nicole C. Engard 2012-07-25 18:54:40 UTC
Patron returned several long overdue/lost items yesterday.  They had been due
in December of 2011 and were flagged as lost in February 2012.  The item
history shows they were last seen yesterday--when they were returned, while the
checkout history for that items shows that it was returned on 2/17/12 which is
actually the day it was flagged as lost. This is misleading because if you look
at the item checkout record it shows the items returned when in fact it is not.
Comment 1 Barton Chittenden 2014-06-09 15:07:42 UTC
This should be escalated, because it causes an inconsistency between issues.date_due and items.onloan... this is one of the avenues for items to show up as both "Checked out" and "Available" at the same time.

I've marked this as "Major".

This may also be linked to Bug 12363 (Marking an item as lost in koha always returns it, but longoverdue.pl may no)

To replicate:

1) Check out an item.
2) Change the following dates in the database, so that the item will trigger as long overdue:
-- items.onloan
-- issues.date_due
The following fields should probably also be back-dated, for the sake of consistency with koha:
-- items.datelastseen
-- items.datelastborrowed
-- items.timestamp
-- issues.timestamp
-- issues.issuedate
3) Run longoverdue.pl
4) Navigate to the item in moredetail.pl. Change the lost status from 'Longoverdue (Lost)' to blank.
5) Navigate back to detail.pl, and note that the item now shows as both 'Available' and 'Checked out to <patron> : due <due date>'
Comment 2 Katrin Fischer 2019-03-11 22:18:43 UTC
I can't replicate this issue on current master.