My understanding (from writing a patch for trunk/2.1 to change it) is
that the grace period is defined on the fine generator cronjob as a
number of fine intervals before fines are generated. This is a global
value, but due to other issues (in 2.0 at least) only works for fine
intervals that are a number of days.
In trunk/2.1 it works differently, where the recurring fine rule has
an absolute duration of the grace period for the circulation and the
cronjob no longer takes the parameter.
Thomas Berezansky
Merrimack Valley Library Consortium
Quoting Deborah Lipoma <[email protected]>:
I would also be interested in knowing how a grace period works since we will
be migrating to v.2. We have a one-week grace period on our current ILS
before fines kick in and would like to keep that policy.
Thanks.
On Wed, Mar 30, 2011 at 8:21 AM, Vicki Reeves <[email protected]> wrote:
We've just come up in 1.6.0.8. We plan to upgrade to 2.x in the near
future but we're setting up a new server first. Most things seem to be
working ok except that we have lost our circulation grace period on
returns. Since we have branches with exterior bookdrops which are only
open a few days a week, we want a 3 day grace period before the fines
kick in on all overdues. Can someone point me to instructions for
making this happen? Thanks.
--
Deborah Lipoma
Librarian, Library IT
Santa Cruz Public Libraries
224 Church St.
Santa Cruz, CA 95060
831-427-7707 ext. 7755
[email protected]
