I noticed that when a reserved book is under transport from another libreries (those libraries working jointly with our library) to the library which is the home library of the patron, still the book appearse on our reservation list as if it is not managed or not sent to the respektive patron's library.
Please provide some steps to reproduce the issue.
Because of GDPR I can only give the example. For example: ( within cooprating (working together)libraries) - Go to your librarie's (X) Holds queue - if you take one book from the hold's queue which is going to be sent to another library (y) - Go to katalogu and check the status of the same book within the other libraries - you may find that one of the cooprating libraries book is intransit to (y) So it was not necessary the reserved book to appear on Holds queue on (x) if other libraries book is on its way to that library (y).
Naib, if you are not using RealTimeHoldsQueue the holds queue won't be updated immediately, but only after a cronjob is run. As you are using 20.11 which is very old, RealTimeHoldsQueue is not available to you yet. Please check how often the build_holdsqueue.pl cronjob is run and if the display problem persists after it was run.
(In reply to Katrin Fischer from comment #3) > Naib, if you are not using RealTimeHoldsQueue the holds queue won't be > updated immediately, but only after a cronjob is run. As you are using 20.11 > which is very old, RealTimeHoldsQueue is not available to you yet. Please > check how often the build_holdsqueue.pl cronjob is run and if the display > problem persists after it was run. Didn't get a reply here, closing INVALID.