- Article Type: General
- Product: Voyager
- Product Version: 2001.2
Bug Report for Issue # 17208
Other Modules that are affected or might have an affect:
PC O/S (if this is PC specific): n/a
Server Platform(s) affected: all
Browser type & version (if WebVoyage): n/a
If you attempt to cancel a UB hold request from the patron request information section of the
patron record, the cancel should either work successfully or give a message explaining why
the cancel could not be processed.
If you attempt to cancel a UB hold request from the patron request information section of the patron
record, the request appears at first to be cancelled (it disappears from the items available for pickup
section); however, if you close the patron record and re-open it, you'll see that the cancel has now
reappeared. Canceling the same request through WebVoyage works successfully.
Operators may believe they've cancelled a request when they actually have not.
Create patron in db A
Log into db A's WebVoyage and request db B item
Process callslip in db B
Log into db A's Circulation and discharge the item
Open patron's record in db A
Click Hold/Recall icon
See request in Items Available for Pickup
Select request there and hit Cancel -- it disappears.
Close patron record and then call it up again -- you'll see the same request still hanging out there.
If you log into webv and cancel the request from there, it automatically disappears in circulation.
See previous problem 42208.
- Article last edited: 10/8/2013