Deana,
Try re-targeting the hold. That usually works for us. If you have holds stalling set for opportunistic capture and the hold on the item is within the timeframe of the stall, it won't capture when you check it in. But, the holds targeter should capture it if you retarget - actions for these holds - find another target. Elaine J. Elaine Hardy PINES & Collaborative Projects Manager Georgia Public Library Service 1800 Century Place, Ste 150 Atlanta, Ga. 30345-4304 404.235-7128 404.235-7201, fax [email protected] www.georgialibraries.org www.georgialibraries.org/pines From: [email protected] [mailto:[email protected]] On Behalf Of Deana Cunningham Sent: Wednesday, February 26, 2014 5:05 PM To: [email protected] Subject: [OPEN-ILS-GENERAL] Holds placed prior to status change 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 [email protected]
