Bug 2658 - Issues Made with Offline Circulation Cannot be Renewed
Summary: Issues Made with Offline Circulation Cannot be Renewed
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Circulation (show other bugs)
Version: rel_3_0
Hardware: PC All
: P3 normal (vote)
Assignee: Galen Charlton
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-03 05:41 UTC by Kyle M Hall
Modified: 2016-04-15 10:27 UTC (History)
2 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 Chris Cormack 2010-05-21 00:54:06 UTC


---- Reported by kyle.m.hall@gmail.com 2008-10-03 05:41:14 ----

Susan Bennett at the Geauga County Library System reports that any borrower issues created using the Offline Circulation system are listed as nonrenewable in Koha. Checking the renewals field for these issues reveals that each of them has been marked as having been renewed 6 times, well above the library's renewal limit.



---- Additional Comments From oleonard@myacpl.org 2008-10-03 06:06:10 ----

I have a bunch of checkouts on my account from offline circ (on a test system, 3.0100002), and when I log in to the OPAC it says I have all available renewals available to me.



---- Additional Comments From kyle.m.hall@gmail.com 2008-10-03 07:38:52 ----

More from Susan Bennett:
I've done some more digging into the renew problem with Offline circ issues and discovered that it doesn't seem to be all the issues but for the ones that its a problem it is all the issues that were uploaded together in the same file. We are having a problem were some of the files are not completing the upload and Galen fixes a bad record for us and we upload again. I'm wondering if that is causing the problem. I wonder if we need a way to skip the bad records on upload instead of them stopping the upload.



---- Additional Comments From kyle.m.hall@gmail.com 2008-10-03 07:43:12 ----

Maybe the offline circ uploader could use the date/time ( which is listed up to the millisecond ) as a unique key to keep track of which actions have already been committed so they can be skipped over in the event of a re-upload. Also, the file itself should have a unique key in the configuration line, perhaps a combination of the data/time plus some identifier of the computer on which it was generated?



---- Additional Comments From oleonard@myacpl.org 2008-10-07 12:45:44 ----

May be off the wall, but could it be an itemtype problem? I was just testing a new installation and had a bunch of newly-imported records whose itemtypes didn't match up with Koha's preconfigured itemtypes. All of those records reported no more renewals available.



--- Bug imported by chris@bigballofwax.co.nz 2010-05-21 00:54 UTC  ---

This bug was previously known as _bug_ 2658 at http://bugs.koha.org/cgi-bin/bugzilla3/show_bug.cgi?id=2658

Actual time not defined. Setting to 0.0