| Summary: | Holds on transport from another libraries still appear on holds list on our library as if it is not sent. | ||
|---|---|---|---|
| Product: | Koha | Reporter: | Naib Bedho <norrvinter> |
| Component: | Hold requests | Assignee: | Bugs List <koha-bugs> |
| Status: | CLOSED INVALID | QA Contact: | Testopia <testopia> |
| Severity: | normal | ||
| Priority: | P5 - low | CC: | gmcharlt, paul.derscheid |
| Version: | 20.11 | ||
| Hardware: | All | ||
| OS: | All | ||
| 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: | |||
|
Description
Naib Bedho
2022-12-07 11:20:55 UTC
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. |