[Bug 4949] New: holds don't expire
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4949 Summary: holds don't expire Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: major Priority: P5 Component: Hold requests AssignedTo: kyle.m.hall@gmail.com ReportedBy: nengard@gmail.com QAContact: koha-bugs@lists.koha-community.org CC: gmcharlt@gmail.com Estimated Hours: 0.0 Created attachment 2314 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2314 expired hold still waiting see attached - there is a hold on that report that has long since expired, but it's still on the list. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4949 --- Comment #1 from Owen Leonard <oleonard@myacpl.org> --- I see a script in misc/cronjobs/holds: cancel_expired_holds.pl. Has this been run? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4949 Nicole C. Engard <nengard@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID --- Comment #2 from Nicole C. Engard <nengard@gmail.com> --- not it has not - but i also didn't know that existed so i need to document that so others know what to do. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4949 Katrin Fischer <katrin.fischer@bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer@bsz-bw.de --- Comment #3 from Katrin Fischer <katrin.fischer@bsz-bw.de> --- I'm not sure, but I think there were 2 sys prefs to control the behaviour for expired holds: holdcancellength and maxreservespickupdelay (http://lists.koha.org/pipermail/koha-bugs/2009-October/012906.html). Holdcancellength is not present in 3.2, and maxreservepickupdelay has perhaps a wrong description. The description for maxreservespickupdelay in 3.2 is: Mark a hold as problematic if it has been waiting for more than days. The description from the old manual on koha.org: ReservesMaxPickUpDelay Define the maximum number of days that a user gets to pick up an item on hold before Koha changes the item's status to 'available' (or assigns the hold to the next patron on the holds list) Default Value: 7 Enter a number (the number represents 'days') TIP: If you don't want Koha to automatically 'do' something to items on hold that haven't been picked up, set the value to '0' or leave blank. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4949 --- Comment #4 from Nicole C. Engard <nengard@gmail.com> --- The missing pref you talk about wasn't used in the code: http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3714 as for the description, I need someone else to tell me if the description is wrong, it's possible it was wrong in the old system :) -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
participants (1)
-
bugzilla-daemon＠bugs.koha-community.org