[OPEN-ILS-GENERAL] Holds placed prior to status change

[Elisabeth Keppler]

We're new to Evergreen and have been struggling with holds on new items.
 We've had issues with Find Another Target messing up the holds queue, but
we may have been doing it incorrectly.

When you say to "Find Another Target for the hold on top of the queue",
Tina, do you mean the first hold that appears when we click on View Holds
for the record?  This seems to be the newest hold and might not be for our
library's patron.  (We're in the NC Cardinal consortium.  Since we use
6-month age hold protection, holds outside Forsyth County won't be filled
by new items we add here.)  We tried filtering to holds for just the branch
where the new item was added, but that seems to have caused problems.
 Would you mind elaborating on your recommendation?

Thanks very much,
Lise Keppler
Forsyth County Public Library


On Wed, Feb 26, 2014 at 6:36 PM, Tina Ji (Project Sitka) <
tji at sitka.bclibraries.ca> wrote:

> Hi Deana,
>
> If your 'missing' and 'trace' statuses are non-holdable, this is probably
> the expected behaviour. We experience the same thing with our hold targeter
> running every 15 mins for new holds (placed within 24 hours) and daily for
> old holds (placed 24 hours ago). So new holds may be targeted by a copy
> with newly achieved holdable status, but not the old ones.
>
> The opportunistic capture is related to the hold_copy_map, which is
> updated by the hold targeter, thus updated daily for old holds. Items with
> newly achieved holdable status is not in that table for old holds.
>
> We advise our sites doing Find Another Target for the hold on top of the
> queue or waiting for a day. The checkin modifier: Retarget Local Hold may
> help, to some extent.
>
>
>
> Tina
>
>
>
> Quoting Deana Cunningham <deana.cunningham at granvillecounty.org>:
>
>  Hi great brain!
>>
>> I was playing around today on our test server and have a question  about
>> hold triggering. After an item has a status change to  "missing" or
>> "trace", any holds placed prior to that change are not  getting triggered
>> upon item check in. I have tried checking the item  in numerous times (to
>> see if maybe the first time when it changes  the status back to
>> "reshelving" it would activate the hold for  capture at the next check in,
>> but it did not. Placing a new hold on  the item after the status has been
>> changed back to "reshelving"  causes that hold to be triggered on
>> subsequent check ins, but the  hold placed before changing to "trace" or
>> "missing" is not triggered.
>>
>> Something I'm missing here?
>>
>> I also realize the item should be caught during the regular "check  for
>> holds" cron job (which is another problem we're having) but I am  only
>> looking at opportunistic hold capturing right now.
>>
>> Thanks!
>>
>> Deana
>>
>> Deana Cunningham
>> Branch Manager, South Branch Library
>> 1550 S. Campus Dr.
>> Creedmoor, NC 27522
>> Phone: (919) 528-1752
>> Fax: (919) 528-1376
>> deana.cunningham at granvillecounty.org
>>
>>
>
>
> Tina Ji
> 1-888-848-9250
> Trainer/Help Desk Specialist
> BC Libraries Cooperative/Sitka
>
>
>


-- 
Lise Keppler
Forsyth County Public Library
660 W 5th St
Winston Salem NC 27101
336-703-3070
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20140227/e965643a/attachment-0001.htm>