Hi Geoff,
Evergreen has two systems of policy for holds and circ, the in-db policy which
is the currently recommended method, and the legacy javascript method. This is
set in the opensrf.xml file, just look for something like this:
<legacy_script_support>true</legacy_script_support>
If set to true, it will use those javascript files, if set to false, it will
use the in-db settings which are set in the Admin -> Local Admin -> Hold
Policies area of the staff client. It's possible that during the upgrade this
setting got switched off and you are using in-db settings. You will need to
restart opensrf when you change this setting.
You may also want to check these settings in the opensrf.xml correctly point to
where your scripts are located:
<script_path>/openils/lib/javascript</script_path>
<script_path>/openils/var</script_path>
<script_path>/openils/var/catalog</script_path>
~James
BC Libraries Cooperative
On 2012-01-17, at 9:26 AM, Geoff Sams wrote:
> Hello,
>
> Our consortium is running 2.0.10 currently and we are having some issues with
> an old setting that has since lost itself. We had our holds limits set to be
> 5 for 3 libraries and 25 for the rest, and recently noticed that it was
> forcing us to have 20 instead across the board. I went and found what I
> believed to be the pertinent file, one circ_permit_hold.js and noticed that
> the effect that we wanted was stated between lines 22 and 33. Is there any
> reason it wouldn’t be running from this file?
>
> Thanks,
> Geoff Sams
> Roanoke Public Library
> 817-491-2691
> Chairman
> North Texas Library Consortium Board
>
