Bug 32415 - Holds on transport from another libraries still appear on holds list on our library as if it is not sent.
Summary: Holds on transport from another libraries still appear on holds list on our ...
Status: CLOSED INVALID
Alias: None
Product: Koha
Classification: Unclassified
Component: Hold requests (show other bugs)
Version: 20.11
Hardware: All All
: P5 - low normal
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-07 11:20 UTC by Naib Bedho
Modified: 2024-07-04 20:38 UTC (History)
2 users (show)

See Also:
GIT URL:
Initiative type: ---
Sponsorship status: ---
Comma delimited list of Sponsors:
Crowdfunding goal: 0
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Naib Bedho 2022-12-07 11:20:55 UTC
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.
Comment 1 Paul Derscheid 2022-12-14 09:18:18 UTC
Please provide some steps to reproduce the issue.
Comment 2 Naib Bedho 2022-12-19 10:10:11 UTC
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).
Comment 3 Katrin Fischer 2022-12-19 11:07:35 UTC
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.
Comment 4 Katrin Fischer 2023-10-28 18:07:56 UTC
(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.