[OPEN-ILS-GENERAL] ILL templaterecords with Holds not targeting
mcoleman at bcgov.net
Thu Aug 20 16:21:59 EDT 2009
Thanks for the update. I too suspected indexing/ingest problems awhile back, when talking/emailing with Don re this. Then I believed that that problem had been resolved or a fix had happened. I thought I would put the issue out to the list to see if others were having the same problem (with v1.4 or whichever). The most recent example that I sent in to Equinox for investigation, didn't show up on the 'pull holds list' for two days (placed 8/17, appeared 8/19).
Does the "Previous check time" change or is it a good indication of when the item was first found for a hold? Also what is the "targeting interval expiration"?
Thanks for your response!
Marlene F. Coleman
ILS Database Manager
Branch Manager, Beaufort Branch
Beaufort County Library
311 Scott Street
Beaufort, SC 29902
mcoleman at bcgov.net
For Learning ~ For Leisure ~ For Life
Date: Thu, 20 Aug 2009 10:10:43 -0400
From: Mike Rylander <mrylander at gmail.com>
Subject: Re: [OPEN-ILS-GENERAL] Holds for ILLs on Template bib records
To: Evergreen Discussion Group
<open-ils-general at list.georgialibraries.org>
<b918cf3d0908200710x75625066w1aa98f6f4529e478 at mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
On Thu, Aug 20, 2009 at 6:36 AM, Sharp,
Chris<csharp at georgialibraries.org> wrote:
> 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.
The 15 minute time (well, strictly speaking, the configured
re-targeting run time) is just for re-targeting after the targeting
interval has expired. Initial targeting occurs when the hold is
placed, so something else is going on here.
I suspect that this is another side-effect of the intermittent ingest
issue that has shown up recently. If the record fails to ingest
properly then some required data (extracted from the fixed fields, and
used to determine the record type) won't be there and can cause the
targeting to exit early. There is a more aggressive workaround than
the hourly cleanup (Marlene, this has been proposed to your
consortium, in fact) that we believe will address this until we have
completely pinned down the root cause of this intermittent issue.
| VP, Research and Design
| Equinox Software, Inc. / The Evergreen Experts
| phone: 1-877-OPEN-ILS (673-6457)
| email: miker at esilibrary.com
| web: http://www.esilibrary.com <http://www.esilibrary.com/>
End of Open-ils-general Digest, Vol 38, Issue 23
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 6645 bytes
Desc: not available
Url : http://libmail.georgialibraries.org/pipermail/open-ils-general/attachments/20090820/7f75fb5c/attachment.bin
More information about the Open-ils-general