Re: Copy returned soonest holds for items available on the shelf
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Date: Fri, 20 Oct 2000 18:39:12 +0100 (BST)
- From: Mieko Yamaguchi <iss053@xxxxxxxxxx>
- Subject: Re: Copy returned soonest holds for items available on the shelf
I cannot tell you what paging lists are but a broken hold is a hold where
a link between the patron record and the item (or bib?) record is broken.
Typically a patron record may be pointing to an item but the item is not
pointing back to the patron. You notice it when you try to view a
patron's held items and see an error message.
There are two things you can do:
1. Report it to the Help Desk every time you notice one. You cannot fix
a broken hold yourself.
2. Ask the Help Desk to install a cron job which finds and fixes broken
holds overnight. Apparently this cron job is not compatible with
the feature to transfer paged items, so if you want to use this feature
it may not be an answer for you.
One of our staff has a theory why there are so many broken holds in his
branch - he thinks some students place a hold in the OPAC and immediately
check their patron record again to make sure that a hold has been
recorded. This may be busying the patron record and preventing the hold
link from being established properly. I don't know if there's any
substance to this theory but he started telling students not to try and
check their patron records immediately after placing a hold and we have
not seen a lot of broken holds on our system so far this semester.
On Thu, 19 Oct 2000, Lois Gillespie wrote:
> Excuse me (I'm sorta new), but what are "paging lists", and can
> someone explain what a "broken hold" is and what I should do with it?
Mieko Yamaguchi m.yamaguchi@xxxxxxxxxx
Technical Services Manager/System Coordinator +44 (0)1248 382970
Main Library, University of Wales Bangor, UK +44 (0)1248 382979 (Fax)
This message was distributed through the Innovative Users Group INNOPAC list.
Private replies: Mieko Yamaguchi <iss053@xxxxxxxxxx>
Public replies: INNOPAC@xxxxxxxxxx