November 2021 - Koha-bugs - lists.koha-community.org

[Bug 29189] New: Expired serial subscriptions still automatically generate issues
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '22

16 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29189 Bug ID: 29189 Summary: Expired serial subscriptions still automatically generate issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I know this is like a Pandora's box, But I just can't get my head around why expired subscriptions would still generate issues even after the expiry date. To replicate : Create a subscription that would end in the past 1. Search for a record in the staff interface 2. Click on the title to go to the record details page 3. Click on New > New subscription 4. Click Next 5. Fill in the second part of the new subscription form - First issue publication date : enter a date in the past, e.g. 2020-01-01 - Frequency : choose a frequency, e.g. 1/3month - Subscription length : enter a number of issues for the subscription, e.g. 4 - Subscription start date : enter a date on or before your first issue publication date, e.g. 2020-01-01 - Numbering pattern : choose a numbering pattern, e.g. Number - Begins with : enter a number, e.g. 42 6. Click on Test prediction pattern 7. Click Save subscription Receive one issue for this subscription 8. Click Receive 9. Change the status to Arrived 10. Change the Expected on date to something close(r) to the Published on date, e.g. 2020-01-01 11. Click Save Make one issue late 12. Click Generate next Receive the rest of the issues normally 13. Repeat steps 8-11 for all remaining issues -- Once you have received all issues in the subscription, it should say "Subscription expired" in the Serial collection page. -- Note that the next issue was automatically generated even though it's not supposed to be in the subscription Like Katrin said in the chat, I don't think receiving should be completely forbidden in expired subscriptions as there can be late issues that you might receive in the future. And the act of "receiving" is actually editing the issues, so if I need to mark one as "Missing" in the future, I need to be able to do that even when the subscription is expired. But, I don't think additional issues should be generated after the prescribed number of issues/weeks/months in the subscription or after the subscription end date. My problem is rally with the automatic creation of issues. Although I must say, I don't work in a library, so maybe what I'm saying doesn't make sense in a day-to-day serial workflow. But I did receive a question from a client asking why issues were still being generated even after the subscription is expired and I can't find a logical explanation. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 28797] New: Hold reminder email should use All Libraries notice
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '22

16 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28797 Bug ID: 28797 Summary: Hold reminder email should use All Libraries notice Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Depends on: 15986 Bug 15986 introduces a hold reminder email. It only knows how to use branch-specific notices and will fail if your only HOLD_REMINDER notice is for All Libraries. To confirm: - have a patron with a valid email address and Hold notices set to go out via email in their messaging prefs - place a hold for your patron, get it to Waiting status - confirm that you have the default HOLD_REMINDER email notice for All Libraries but no library-specific HOLD_REMINDER notice - perl misc/cronjobs/holds/holds_reminder.pl -c -v to run the holds reminder cron - get "Message 'HOLD_REMINDER' content not found for [your branch]" - create the notice for your branch - re-run the cron - patron gets notice Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=15986 [Bug 15986] Add a script for sending hold waiting reminder notices -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 29287] New: Display of funds on acquisitions home is not consistent with display on funds page
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '22

16 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29287 Bug ID: 29287 Summary: Display of funds on acquisitions home is not consistent with display on funds page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Acquisitions home does not have a place for totaling the child funds into the parent funds. When funds are collapsed it can appear nothing is spent The total available also does not subtract any money spent from child funds -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20

[Bug 22329] New: Parent funds showing incorrect amounts for Ordered, Spent, Available on Acquisitions Home
by bugzilla-daemon＠bugs.koha-community.org 16 Aug '22

16 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22329 Bug ID: 22329 Summary: Parent funds showing incorrect amounts for Ordered, Spent, Available on Acquisitions Home Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- On acqui-home.pl, the amounts for Ordered and Spent for parent funds to no reflect orders charged to their child funds, only orders charged to the parent fund directly. I can see some room for argument here if libraries are are sometimes charging a parent fund directly, but overall it may be more clear if ordered and spent for a parent fund showed totals for all orders charged to the parents AND its children. Total Available for the parent is also based only on orders charged to the parent directly and this is definitely misleading. Total available for a parent fund should display as total allocated to parent minus (total ordered/spent for parent plus total ordered spent for all children). These changes would bring acqui-home.pl in line with the numbers shown on aqbudgets.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 29444] New: 404 Not Found pages come back as 200 OK under plack
by bugzilla-daemon＠bugs.koha-community.org 15 Aug '22

15 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29444 Bug ID: 29444 Summary: 404 Not Found pages come back as 200 OK under plack Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org See bug 29420 and old bug 3797 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 29055] New: Focus on keyword field when subscription biblio search window opens
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '22

13 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29055 Bug ID: 29055 Summary: Focus on keyword field when subscription biblio search window opens Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org To reproduce: 1. Go to Serials and Add a new subscription 2. Search for a record 3. There is only one search field (keyword), and you have to click into it to use it. It should be focussed as the window opens so the cursor starts in there. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 29454] New: Stash branches and itemtypes in plugin objects to reduce DB calls
by bugzilla-daemon＠bugs.koha-community.org 13 Aug '22

13 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29454 Bug ID: 29454 Summary: Stash branches and itemtypes in plugin objects to reduce DB calls Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Moved from bug 28436 -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 30

[Bug 17814] New: koha-plack --stop should make sure that Plack really stop
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '22

12 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17814 Bug ID: 17814 Summary: koha-plack --stop should make sure that Plack really stop Change sponsored?: --- Product: Koha Version: 16.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: pongtawat(a)punsarn.asia QA Contact: testopia(a)bugs.koha-community.org koha-plack --stop doesn't ensure that Plack was really stopped before returning. So in case that koha-plack --stop was quickly follows by koha-plack --start (e.g. logrotate), it could leave Plack in stop state. This is due to koha-plack --start think that Plack was already started, while it actually is being stopped. For me I think this is the cause why I got random Plack stop when logrotate is run. It should be similar to the case of Zebra in Bug #16885, and the solution might be the same: adding "--retry=TERM/30/KILL/5;" to start-stop-daemon command. I just try that on our server and will see if the problem goes away. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 25080] New: Make patron clubs accessible as runtime parameter category in reports
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '22

12 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25080 Bug ID: 25080 Summary: Make patron clubs accessible as runtime parameter category in reports Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It'd be great to be able to write a report that allows one to pick on of your patron clubs out of a dropdown as a runtime parameter. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 18631] New: Cleanup_database.pl should take an option for modules in action_logs
by bugzilla-daemon＠bugs.koha-community.org 12 Aug '22

12 Aug '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18631 Bug ID: 18631 Summary: Cleanup_database.pl should take an option for modules in action_logs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Cataloging log is a big one that often needs to be cleaned, other logs can be useful to keep longer, we should take the modules as an option and clear only those specified or exclude specified logs -- You are receiving this mail because: You are watching all bug changes.

1 21