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.