[minervacirc] Frozen Holds
lynn.uhlman at maineinfonet.org
Tue Jul 5 14:57:52 EDT 2016
There has been some questions regarding the Not Needed Before and Not
Needed After sections when modifying a patron hold from the Sierra Desktop
Application (SDA). The consensus of the Round Table was to remove the
function from the patrons ability to "freeze" or suspend holds, which may
or may not have encompassed the staff side. I took it to mean the overall
features governing how to freeze a hold both from the patron and staff
Currently, the *Not Needed Before* and *Not Needed After* sections have
active "known issues" that are being reviewed by software engineering. So,
I'm not sure that it's wise to continue using these aspects of Freezing a
Hold based on how problematic it all has been in the past for the majority
*Please note* that the list I compiled is for any frozen hold in the system
since there is no way to ascertain if it was done through the SDA or
through the catalog.
For now, I would suggest not using *Not Needed Before* or *Not Needed After*
from the SDA. This is something that will be discussed at the next
Circulation Round Table meeting to ensure clarity.
*Lynn A. Uhlman*
*Systems Training and Support Librarian*
5784 York Village, Suite 58
Orono, Maine 04469-5784
Email: lynn.uhlman at maineinfonet.org <mail+to:lynn.uhlman at maineinfonet.org>
On Tue, Jul 5, 2016 at 1:13 PM, Lynn Uhlman <lynn.uhlman at maineinfonet.org>
> Good Afternoon,
> I hope everyone had a lovely Independence Day weekend. Now its time to
> redirect your thoughts back from tasty BBQs, day trips and lake/ocean side
> reading to more mundane matters.
> At the last Circulation Round Table in April, we yet again discussed the
> continued problems associated with Frozen Holds. Originally, we had
> discussed it at the January 2015 meeting and decided to try it out a while
> longer to see if things improved. Alas, they did not.
> To recap...a minority of patrons have been able to use the Frozen Holds
> feature without any problems over the years, while the majority of patrons
> and staff find it problematic and clunky. Additionally, "bugs" regarding
> this feature continue to crop up in the system upgrades which makes it not
> very useful and a mite difficult to train patrons and staff successfully.
> So, the long and the short is that it was decided to turn the ability to
> freeze holds off. This was recently done by Maine InfoNet staff and a list
> has been compiled of patrons with frozen holds.
> *What do library staff need to do?*
> 1. Review the list of frozen holds for your library in the Google
> spreadsheet at
> *Libraries with frozen patron holds:*
> bfl, bml, cam, cml, edl, fml, fre, gar, gpl, kbk, lit, lpl, mca, opl,
> pfl, ric, rkd, roc, sca, spp, tho, tml, tpl, wel, win, wlk, wpl
> 2. As
> certain if
> patron want
> to have the hold replaced
> or request it themselves at a later date.
> - If they want the hold replaced, cancel the existing frozen hold and
> request it again for them. Change the priority of the hold to place the
> patron in the queue where they originally were
> . Use the *Hold Placed* date in the Google spreadsheet as your guide.
> Directions on how to *Change Priority* can be found at
> - If they want to replace it themselves at a later date, let them
> know the title and then cancel the hold.
> Additionally, staff can guide patrons in adding it to to their
> *referred *
> *earch* list
> to use as a reminder. Directions can be found at
> As always, please feel free to submit a ticket to
> http://support.maineinfonet.org if you have any questions, concerns, or
> need further guidance.
> Thank you,
> *Lynn A. Uhlman*
> *Systems Training and Support Librarian*
> *Maine InfoNet*
> 5784 York Village, Suite 58
> Orono, Maine 04469-5784
> (207)581-3095 (fax)
> Email: lynn.uhlman at maineinfonet.org <mail+to:lynn.uhlman at maineinfonet.org>
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the MinervaCirc