koha-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Koha-bugs] [Bug 651] Change the way reserves, 'waiting' status are hand


From: bugzilla-daemon
Subject: [Koha-bugs] [Bug 651] Change the way reserves, 'waiting' status are handled
Date: 30 Dec 2004 12:41:48 -0000

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=651

address@hidden changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Version|CVS                         |2.2.0



------- Additional Comments From address@hidden  2004-12-31 01:41 -------
No, but there are intermediate steps that can be taken to make this bug less of
a problem.  The essence of the problem is the fact that the 'waiting' status is
inaccurate much of the time.  The interim solution is to use information already
in the database to override the display of the 'waiting' status and replace it
with something like 'in-transit' when the book isn't at its destination.

We have the information required already in the database.  The reserves table
has the destination branch information, and the items table has the
holdingbranch information.  If these two things match, then the item really is
at its destination and should be shown to be waiting.  If the two branch fields
don't match, then Koha should display "In-Transit" or "In-Transit from
{items.holdingbranch} to {reserves.destinationbranch}.

I've already managed to get this working in the NPL template for request.pl:

<!-- TMPL_IF NAME="atdestination" -->
<strong>Waiting</strong> at <!-- TMPL_VAR Name="wbrcode" -->
<!-- TMPL_ELSE -->
In transit from <!-- TMPL_VAR NAME="holdingbranch" --> to <!-- TMPL_VAR
Name="wbrcode" -->
<!-- /TMPL_IF -->

Other places this is needed: OPAC screens, Intranet catalog screens, etc.  The
solution is pretty simple as long as both those branch variables are available
in the script.



------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]