<!-- TMPL_IF NAME="RESERVE_WAITING" --> <p>Reserve waiting for <!-- TMPL_VAR NAME="RESERVE_WAITING" -

-></p> <!-- /TMPL_IF -->

<!-- TMPL_IF NAME="RESERVED" --> <p>Reserved by <!-- TMPL_VAR NAME="RESERVED" --></p>

What is the difference between 'reserved by' and 'reserve waiting for'?

You'll notice that the other cases accompanying these are under the heading '<!-- TMPL_IF NAME="NEEDSCONFIRMATION" -->'. These are cases where Koha requires the librarian to confirm an issue because of some special circumstance. In the example you quote, those cases are related to reserves. There are two different cases a librarian might encounter when someone brings up a book that happens to be on reserve for another patron. The first case is when someone has placed an available item on reserve, but it hasn't been pulled off the shelf and set aside by the librarian. A patron tries to check it out, and Koha warns the librarian that the item is on reserve for another patron (<!-- TMPL_IF NAME="RESERVED" --

).

The other (probably more rare) case is when a patron tries to check out a book which is on reserve *and* which has a 'waiting' status on it. When a reserved item is returned, the librarian has the opportunity to mark the item as 'waiting,' meaning the reservation is confirmed and that item (with that barcode) is allocated to fill the reserve. So that's the second (and distinct) situation the template allows for (<!-- TMPL_IF NAME="RESERVE_WAITING" -->). The returns script and tempalate have their own mechanisms for dealing with reserves too, of course. -- Owen