[OPEN-ILS-GENERAL] Recalling Circulating Items in 2.2
Dan Scott
dan at coffeecode.net
Wed May 16 22:34:14 EDT 2012
Sally:
Looking at the logic in
Open-ILS/src/perlmods/lib/OpenILS/Application/Storage/Publisher/action.pm,
the recall won't be triggered until the hold targeter runs. Did you
run the hold targeter after placing your hold?
Also, once the recall is triggered, a circ.recall.target event will be
generated, which in turn will generate an "Item Recall Email Notice"
(if enabled).
The relevant commit is c403d6bb54 and the (in my opinion fairly
carefully crafted for the purposes of documentation) commit message
was:
Initial support for recall of items triggered by placing a hold
In academic libraries, it is common for groups like faculty and graduate
students to have extended loan periods (for example, 120 days), while
others have more common loan periods such as 3 weeks. In these environments,
it is desirable to have a hold placed on an item that has been loaned out
for an extended period to trigger a "recall": truncating the loan period,
setting available renewals to 0, optionally changing the fines associated
with overdues for the new due date, and notifying the current patron of
the recall.
New actor.org_unit_setting entries and hold targeting logic enable
libraries to
control whether a hold will trigger a recall of a circulating item
as follows:
* "Recalls: Circulation duration that triggers a recall" (recall
threshold)
is specified as an interval (for example, "21 days"); any items with a
loan duration of less that this interval will not be considered for a
recall
* "Recalls: Truncated loan period" (return interval) is specified as an
interval (for example, "7 days"), such that the user who currently
has the item checked out will get the greater of either the recall
threshold, or the return interval.
* "Recalls: An array of fine amount, fine interval, and maximum fine"
is an optional setting that applied the new fine rules to the current
circulation period.
When a hold is placed and no available copies are found by the
hold targeter,
the recall logic checks to see if the recall threshold and return interval
settings are set; if so, then the hold targeter checks the currently
checked-out copies to determine if any of the currently circulating items at
the designated pickup library have a loan duration longer than the recall
threshold. If so, then the eligible item with the nearest due date will be
recalled.
Dan
On Wed, May 16, 2012 at 8:45 PM, Dan Scott <dan at coffeecode.net> wrote:
> Sally:
>
> The recall feature was added in 2.1 IIRC. With all of the changes in holds
> in the 2.2 cycle and a lack of automated testing for such scenarios, it
> wouldn't surprise me if something broke.
>
> On May 16, 2012 7:40 PM, "Sally Fortin" <sfortin at esilibrary.com> 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.
>>
>> Thanks,
>> Sally
>>
>>
>> --
>> Sally Fortin
>> Director of Education
>> Equinox Software Inc. / Your Library's Guide to Open Source
>> Tel: 770-709-5572
>> Email: sfortin at esilibrary.com
>> Fax: 1-866-497-6390
More information about the Open-ils-general
mailing list