Hi Marlene,

> We are trying to place Title holds, and they are for the same org unit
> owning the item (we do have branches). We were aware that the
> "targeter" was on a 15 minute delay, but the delay in finding the item
> is much more than that, sometimes a day or two days

The targeter program sometimes takes much longer than every 15 minutes.  The 
script looks to see if the targeter is already running (by checking for the 
existence of the /tmp/hold_targeter-LOCK file), and if the lockfile is present, 
it checks again 15 minutes later.  In PINES, depending on the volume of holds 
placed, this can take hours rather than the expected 15 minutes.

> My current test
> is a title hold placed 2009-08-17T13:16:30-0400, which didn't show up
> on the pull holds list until this morning 8-19-09. It currently has a
> "previous check time" of
> 2009-08-19T14:15:14-0400. I'm not sure what that means (if that's
> really when the targeter checked for it last)....

As far as I understand things, the "previous check time" (prev_check_time field 
in action.hold_request at the database level) IS in fact the last time the hold 
targeter searched for a candidate for that hold.

> but I don't know how
> to determine when the targeter FIRST found the item for the hold. Is
> there a field for that that's visible by the client?

At the database level, this is capture_time within the action.hold_request 
table.  It's visible from within a patron account as "Capture Date" with a 
timestamp option from the column picker.  Also, when the targeter finds an 
item, that item stays targeted until it is captured or changed to a 
non-holdable status - only then does it start looking for another candidate for 
the hold.

Hope this is helpful - if someone sees any errors in my understanding, please 
feel free to correct me.

Thanks,
Chris

Chris Sharp
PINES Program Manager
Georgia Public Library Service
1800 Century Place, Suite 150
Atlanta, Georgia 30345
(404) 235-7147
csh...@georgialibraries.org
http://www.georgialibraries.org/pines

----- "Tara Robertson" <information.detect...@gmail.com> wrote:

> Hmmm...I have no idea. Hopefully someone else can help.
> 
> When I worked at SITKA we had log files for holds. I don't think this
> came out of the box, and I'm not sure how it was set up. I do know
> that they were useful in trying to puzzle through what happened with
> some holds. Perhaps someone from SITKA can explain or expand on this.
> I don't think there's anything in the client that shows when an item
> was first targeted.
> 
> Cheers,
> Tara
> 
> 
> 
> On Wed, Aug 19, 2009 at 12:13 PM, Coleman, Marlene <
> mcole...@bcgov.net > wrote:
> 
> 
> Hi Tara,
> 
> We are trying to place Title holds, and they are for the same org unit
> owning the item (we do have branches). We were aware that the
> "targeter" was on a 15 minute delay, but the delay in finding the item
> is much more than that, sometimes a day or two days. My current test
> is a title hold placed 2009-08-17T13:16:30-0400, which didn't show up
> on the pull holds list until this morning 8-19-09. It currently has a
> "previous check time" of
> 2009-08-19T14:15:14-0400. I'm not sure what that means (if that's
> really when the targeter checked for it last)....but I don't know how
> to determine when the targeter FIRST found the item for the hold. Is
> there a field for that that's visible by the client?
> 
> Holds on template records just aren't responding as a normal bib
> record would for holds.
> 
> Thanks for your response!
> 
> Marlene
> 
> 
> 
> Marlene F. Coleman, BA, MLS, CIM
> ILS Database Manager, Branch Manager
> Beaufort County Library, Beaufort Branch
> 311 Scott Street, Beaufort, SC 29902
> 843-470-6544 mcole...@bcgov.net
> www.beaufortcountylibrary.org
> For Learning ♦ For Leisure ♦ For Life
> 
> 
> I remember that for holds that are not opportunistic holds (i.e. holds
> captured on checkin) that it sometimes it takes the hold targeter 15
> minutes
> to match up the hold with the item that can fill the hold. Have you
> checked
> a few times and the holds are still not targeting?
> 
> I doubt that this is relevant, but I'm curious as to what type of hold
> are
> you placing on the brief records? Is it the same type of hold that you
> generally use for holds?
> 
> Cheers,
> Tara
> 
> On Mon, Aug 17, 2009 at 11:24 AM, Coleman, Marlene <
> mcole...@bcgov.net >wrote:
> 
> > Hi all,
> >
> > We're part of the newly developed SC LENDS consortium, up about 2.5
> months.
> > We've been trying to sort through this problem since early on.
> >
> > When we create a short record for an item with a template (similar
> to
> > creating an order record), instead of using a precat record for ILL,
> the
> > hold targeter doesn't seem to find the item, or the hold we've
> attached to
> > the item.
> >
> > We suspect it is a template problem, but don't know why. I've
> downloaded
> > OCLC records (as temp records) and placed holds on them for ILLs and
> they've
> > captured instantaneously. Even copy holds don't always find the item
> > immediately.
> >
> > Is there something about a temp/short record that the targeter
> doesn't like
> > or can't find an item attached to it?
> >
> > Anyone tried this out with or without success??
> >
> > Thanks,
> >
> > Marlene
> >
> > Marlene F. Coleman, BA, MLS, CIM
> > ILS Database Manager, Branch Manager
> > Beaufort County Library, Beaufort Branch
> > 311 Scott Street, Beaufort, SC 29902
> > 843-470-6544 mcole...@bcgov.net
> > www.beaufortcountylibrary.org
> > For Learning ? For Leisure ? For Life
> > *************
> >

Reply via email to