To follow up, a quick grep on the code this morning finds the holdCancelLength only in admin/systempreferences.pl installer/data/mysql/uk-UA/mandatory/system_preferences_optimal.sql installer/data/mysql/fr-FR/1-Obligatoire/unimarc_standard_systemprefs.sql installer/data/mysql/ru-RU/mandatory/system_preferences_optimal.sql installer/data/mysql/updatedatabase.pl installer/data/mysql/en/mandatory/sysprefs.sql It does not seem to be in any active script. ReservesMaxPickUpDelay is in the various installer scripts, but also used in circ/waitingreserves.pl, and that's the syspref we've been working with. It looks like holdCancelLength may never have been activated. Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@ptfs.com -----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Nicole Engard Sent: Thursday, October 15, 2009 7:51 AM To: Koha-Mailingliste Subject: [Koha] Fwd: manual confusion? Can someone confirm whether this is true or not - it would take days for me to test :) So if someone knows for sure if I need to make manual edits I'd appreciate the feedback. Thanks Nicole C. Engard ---------- Forwarded message ---------- From: Wagner, Jane <jwagner@ptfs.com> Date: Wed, Oct 14, 2009 at 8:40 PM Subject: manual confusion? To: nengard@gmail.com Cc: "Wagner, Jane" <jwagner@ptfs.com>, "Bavousett, David" <dBavousett@ptfs.com> Nicole, I was looking at the manual site to clarify a couple of syspref settings, and I think a couple are mixed up: holdCancelLength Specify how many days after a hold has been confirmed, pulled from the shelf and patron contacted before a hold is canceled. Default Value: no value The number you enter represents 'days'. For instance, if you enter '14', then Koha will cancel a hold and change the item's status to 'available' 14 days after the patron has been contacted to pick up the hold. IMPORTANT: This does not take into account a person's place in the hold queue, if they're 200th on the list of holds, and this limit is reached, their hold will be dropped. If you have a big library with a lot of holds, you may want to set this to an insanely high number of days. 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. My understanding is that the first one (holdCancelLength) applies to holds that have NOT been triggered and pulled from the shelf -- it's meant to cancel holds that have been around for a long time without ever getting triggered. The second one is the one that applies after the hold has been triggered. Can you confirm? Jane Wagner Library Systems Analyst PTFS Inc. Content Management and Library Solutions 6400 Goldsboro Road, Suite 200 Bethesda, MD 20817 (301) 654-8088 x 151 jwagner@ptfs.com _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha