<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000066">
<font face="Arial">Hello all,<br>
<br>
I hope this makes sense as I'm coming from a Sirsi-Dynix world and my
understanding of Koha slim to none.<br>
<br>
Currently our version of the Holds to pull report (known as Pull List)
works like so:<br>
</font>
<ul>
<li><font face="Arial">Customer places request on title - when there
is at least one or more items with a status that is on shelf the
request gets placed in the pull list queue</font></li>
<li><font face="Arial">Staff member generates report (sorts by call
number and prints) at our main location library (biggest collection)<br>
</font></li>
<li><font face="Arial">Staff member then "binds" the items to that
branch. This steps keeps the same title from showing up on another
location's pull list that also has it "on shelf"</font></li>
<li><font face="Arial">Next library generates their report, sorts,
prints and binds until all branches have printed their pull list for
the morning (this is done again in the afternoon)</font></li>
<li><font face="Arial">Staff search shelves and carts for items</font></li>
<li><font face="Arial">Items are then checked in to trap the holds
(staff then distribute holds to proper location)</font></li>
<li><font face="Arial">Any items not found are set to "trace" status
so that it takes that branch's copy out of the queue for the next time
(if another branch has a copy on shelf it will appear on their pull
list)</font></li>
<li><font face="Arial">At any time if a copy comes across any of the
circulation desks and is checked in it can fill the hold for the item
on the pull list</font></li>
<li><font face="Arial">Because of the way Horzion's pull list works
we must schedule (and staff must stick to it) when the pull list is run
so there is no overlap. (e.g. Branch A is suppose to print at 8:30 but
is running late and prints at 8:35 instead [same time as Branch B's
scheduled printing] both branches {as long as they both have item with
on shelf status for that title} will have it appear on their pull
lists. Because Branch A didn't print and bind before Branch B's
scheduled time - both branch will be doing the same work and whoever
checkin the items first will trap the hold.)<br>
</font></li>
</ul>
<font face="Arial">Can anyone explain how the Holds To Pull report
works in Koha? <br>
Is it a combined list that each library draws from or is the list
specific to that branch?<br>
Do you have to stagger the running of this report in order to not
duplicate work?<br>
<br>
Any information on the ins and outs of this report would be a big help.<br>
<br>
Thanks in advance,<br>
<br>
</font>
<div class="moz-signature">-- <br>
Beth Tribe<br>
Coordinator of Software Support and Training<br>
Library Technology Services<br>
Howard County Library<br>
<a class="moz-txt-link-freetext" href="http://hclibrary.org">http://hclibrary.org</a><br>
<br>
<a href="http://liblime.com/koha">Koha and Liblime - "It's <i>our</i>
implementation decision!"</a></div>
</body>
</html>