[OPEN-ILS-DOCUMENTATION] [OPEN-ILS-GENERAL] Recalling Circulating Items in 2.2

[Dan Scott]

On Wed, May 16, 2012 at 07:40:32PM -0400, Sally Fortin wrote:
> Hi everyone,
> 
> I've been testing the recalls feature in Evergreen version 2.2RC1
> that enables a user to configure automatic recalls of circulating
> items that are needed for another patron.  Dan Scott provided some
> information regarding this feature via email, but I'm encountering
> some problems when trying to use the feature and would like to know
> if anyone else is using it successfully.  In short, if I configure
> the library settings for the recall and if I place a hold on the
> circulating item via the jspac or the tpac in RC1, then the item is
> not recalled.
> 
> As an aside, if I do the same process in 2.2beta2 using the jspac,
> then the item is recalled but the truncated loan period is
> incorrect.  If I do the same process in 2.2beta2 using the tpac,
> then the item is not recalled at all.
> 
> The steps that I took are the following:
> 
> 1. In the library settings editor, I configured the following:
> 
>  * Recalls: An array of fine amount, fine interval, and maximum fine -
>    I used the example in the definition - [5.00,"1 day",50.00]
>  * Recalls: Circulation duration that triggers a recall - I entered the
>    value, 7 days
>  * Recalls: Truncated loan period  - I entered the value 2 days.
> 
> 2. I checked out the only copy of a title to Patron A. The
> circulation duration for the item was 2 weeks.
> 
> 3. Patron B placed a hold on the copy.  I believed that this would
> trigger the automatic recall in which the item's due date would be
> shortened and renewals would drop to zero.  However, nothing
> changed.
> 
> If you are using this feature successfully, would you describe the
> steps that you take to use it? I'm happy to document this feature
> for the community if it has not been documented elsewhere.

Also, I just tested this out with exactly the values from the example
definitions for the OU settings and it works fine for me with current
master.

The steps you're missing are:

1. Run `hold_targeter.pl` (to trigger the event, including the change
   in fine levels and due date)

2. Run action_trigger_runner.pl --run-pending (to generate the email
   notification to the current holder of the item)

Both of these would be scheduled on production systems, but are often
not scheduled on test systems, which is why the commit message drew
attention to the hold targeter in particular.

Since I dredged up all of this stuff to test anyway, I've gone ahead and
added a new section to the 2.2 docs, under Local System Administration,
that covers hold-driven recalls, based largely on the original commit
message.