March 2022 - Koha-bugs - lists.koha-community.org

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Needs Signoff |Signed Off --- Comment #180 from Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> --- Tested, works as described. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #131300|0 |1 is obsolete| | -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #131647|0 |1 is obsolete| | --- Comment #179 from Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> --- Created attachment 131724 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131724&action=e… Bug 8367: (follow-up) Fix tests Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #131646|0 |1 is obsolete| | --- Comment #178 from Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> --- Created attachment 131723 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131723&action=e… Bug 8367: (follow-up) Remove pickup delay message from OPAC It adds unnecessary complexity and information. Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #131302|0 |1 is obsolete| | --- Comment #177 from Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> --- Created attachment 131722 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131722&action=e… Bug 8367: (follow-up) Fix pickup delay text on OPAC and other bits Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #131301|0 |1 is obsolete| | --- Comment #176 from Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> --- Created attachment 131720 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131720&action=e… Bug 8367: Make database update idempotent (across different MariaDB versions) but it didn't work on MariaDB 10.3.29 (default in Debian 10 as of this writing), but this patched query works on both indempotently. Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #175 from Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> --- Created attachment 131719 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131719&action=e… Bug 8367: Make database update idempotent Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 8367] How long is a hold waiting for pickup at a more granular level
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #131299|0 |1 is obsolete| | --- Comment #174 from Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> --- Created attachment 131718 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=131718&action=e… Bug 8367: Add holds_pickup_period circulation rule So that pickup delay can have a different value per patron category, item type or branch. To test: 1) Update database, restart services 2) Set ReservesMaxPickUpDelay syspref (if not already set) 3) Edit your circulation rules and set a value under 'Holds pickup period (day) that is DIFFERENT from ReservesMaxPickUpDelay. Set a few different numbers for different branches as well. 4) Place a hold on a biblio from the staff client. 5) Check in an item from that biblio and confirm the hold as waiting 6) Confirm the expiration date is calculated using the 'Holds pickup period' value instead of the ReservesMaxPickUpDelay syspref 7) Revert the waiting status and delete the hold 8) Re-place the hold on the biblio on the OPAC. Notice that when you change the pick up location, the number of days in the pickup message below the dropdown changes based on the circ rules. 9) Create a holiday with a date that will overlap with the 'Holds pickup period' 10) Check in an item from that biblio and confirm the hold as waiting 11) Confirm the expiration date is calculated using the 'Holds pickup period' value AND considers the special holiday 12) Confirm tests pass t/db_dependent/Holds/WaitingReserves.t 13) Test Talking Tech: 13a) Enable TalkingTechItivaPhoneNotification 13b) Go to Tools -> Notices & slips. Add content to the HOLD phone (itiva) notice. 13c) In your terminal, run perl /path/to/koha/misc/cronjobs/thirdparty/TalkingTech_itiva_outbound.pl -o ~/itiva.tmp -w 0 --type=RESERVE Sponsored-by: Catalyst IT Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 25710] New: On ElasticSearch only system zebraqueue table is never purged
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '22

15 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25710 Bug ID: 25710 Summary: On ElasticSearch only system zebraqueue table is never purged Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: didier.gautheron(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Depends on: 21820, 16248 Even if there's no zebra server zebraqueue table is populated (with done == 0). misc/cronjobs/cleanup_database.pl is only deleting zebraqueue table with done == 1 But without a zebra indexer daemon nothing is setting zebraqueue.done to 1. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16248 [Bug 16248] ModZebra doesn't update zebraqueue if ES is enabled https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21820 [Bug 21820] Zebraqueue should not be added to -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 14364] Allow automatically canceled expired waiting holds to fill the next hold
by bugzilla-daemon＠bugs.koha-community.org 14 Mar '22

14 Mar '22

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14364 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Patch doesn't apply --- Comment #54 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- I am sorry, but patches no longer apply, could you please rebase? Bug 14364 - Allow automatically canceled expired waiting holds to fill the next hold 128757 - Bug 14364: Allow automatically canceled expired waiting holds to fill the next hold 128758 - Bug 14364: (QA follow-up) Generate message for transfers as well 128759 - Bug 14364: (follow-up) Cleanup duplicate code and adjust notices and prefs Apply? [(y)es, (n)o, (i)nteractive] y Applying: Bug 14364: Allow automatically canceled expired waiting holds to fill the next hold Using index info to reconstruct a base tree... M C4/Reserves.pm M Koha/Hold.pm M installer/data/mysql/mandatory/sysprefs.sql M koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/circulation.pref Falling back to patching base and 3-way merge... Auto-merging koha-tmpl/intranet-tmpl/prog/en/modules/admin/preferences/circulation.pref Auto-merging installer/data/mysql/mandatory/sysprefs.sql Auto-merging Koha/Hold.pm Auto-merging C4/Reserves.pm Applying: Bug 14364: (QA follow-up) Generate message for transfers as well Applying: Bug 14364: (follow-up) Cleanup duplicate code and adjust notices and prefs error: sha1 information is lacking or useless (C4/Reserves.pm). error: could not build fake ancestor Patch failed at 0001 Bug 14364: (follow-up) Cleanup duplicate code and adjust notices and prefs hint: Use 'git am --show-current-patch=diff' to see the failed patch When you have resolved this problem run "git bz apply --continue". If you would prefer to skip this patch, instead run "git bz apply --skip". To restore the original branch and stop patching run "git bz apply --abort". Patch left in /tmp/Bug-14364-follow-up-Cleanup-duplicate-code-and-adj-QGOiaL.patch -- You are receiving this mail because: You are watching all bug changes.

1 0