July 2023 - 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 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #148539|0 |1 is obsolete| | --- Comment #244 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 153239 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=153239&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> Signed-off-by: Nick Clemens <nick(a)bywatersolutions.com> Signed-off-by: Kelly <kelly(a)bywatersolutions.com> -- 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 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #148538|0 |1 is obsolete| | --- Comment #243 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 153238 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=153238&action=e… Bug 8367: Make database update idempotent (across different MariaDB versions) The previous query seemed to work on MariaDB 10.1.48 (used by koha-testing-docker), 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> Signed-off-by: Nick Clemens <nick(a)bywatersolutions.com> Signed-off-by: Kelly <kelly(a)bywatersolutions.com> -- 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 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #148537|0 |1 is obsolete| | --- Comment #242 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 153237 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=153237&action=e… Bug 8367: Make database update idempotent Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> Signed-off-by: Nick Clemens <nick(a)bywatersolutions.com> Signed-off-by: Kelly <kelly(a)bywatersolutions.com> -- 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 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #148536|0 |1 is obsolete| | Attachment #150437|0 |1 is obsolete| | --- Comment #241 from Aleisha Amohia <aleisha(a)catalyst.net.nz> --- Created attachment 153235 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=153235&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> Signed-off-by: Nick Clemens <nick(a)bywatersolutions.com> Signed-off-by: Kelly <kelly(a)bywatersolutions.com> -- 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 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Aleisha Amohia <aleisha(a)catalyst.net.nz> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Patch doesn't apply |Signed Off -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11690] 'Most popular' in OPAC should ignore suppressed titles/items
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11690 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |DUPLICATE Status|NEW |RESOLVED CC| |dcook(a)prosentient.com.au --- Comment #2 from David Cook <dcook(a)prosentient.com.au> --- *** This bug has been marked as a duplicate of bug 19704 *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11839] Zebra I/O 100 percent usage during merge
by bugzilla-daemon＠bugs.koha-community.org 10 Jul '23

10 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11839 --- Comment #3 from David Cook <dcook(a)prosentient.com.au> --- (In reply to Katrin Fischer from comment #2) > (In reply to David Cook from comment #1) > > I imagine this issue could be closed now? > > Do you remember if this was fixed? I don't recall why I made my comment. I'm guessing it was because it was reported a long time ago and there was no follow-up. Usually I have the database on a separate server, but I do have a Koha instance with many records that has Zebra indexes and MySQL databases on the same disk, and I don't think that we've had any noticeable issues. It is on SSDs though. I wonder if Bywater can comment on whether they still have this issue? I've had similar issues on other systems, but it's usually related to poor disk performance. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 11113] Title of pages are not easy to translate in some languages, especially in french
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '23

09 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11113 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |DUPLICATE See Also|https://bugs.koha-community |https://bugs.koha-community |.org/bugzilla3/show_bug.cgi |.org/bugzilla3/show_bug.cgi |?id=32507 |?id=33906 --- Comment #5 from Owen Leonard <oleonard(a)myacpl.org> --- I think the patches blocking Bug 33906 will resolve this. I have patches ready for all templates, I'm just waiting to see if the first few make it through QA before I submit them all. *** This bug has been marked as a duplicate of bug 33906 *** -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 34242] New: Split checkouts in OPAC in normal and onsite checkouts like for reading history
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '23

09 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34242 Bug ID: 34242 Summary: Split checkouts in OPAC in normal and onsite checkouts like for reading history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org I am not sure if that was always the case, but right now there is no way to distinguish on-site checkouts from normal checkouts in the checkouts tab in the OPAC. You can only see it in the checkout history, if enabled. As you can't see the difference at all I am marking this as a bug. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 34241] New: Editing an authority from the authority search popup should return you to result list
by bugzilla-daemon＠bugs.koha-community.org 09 Jul '23

09 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34241 Bug ID: 34241 Summary: Editing an authority from the authority search popup should return you to result list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When using the authority liking plugin in cataloguing you can edit authorities from the result list. But when you save your changes, you are stuck on the detail view of the authority with no option to return to the search form or even - previous result list. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0