March 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 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #217 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 147803 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147803&action=e… Bug 8367: (follow-up) Fix tests Signed-off-by: Emmi Takkinen <emmi.takkinen(a)koha-suomi.fi> Signed-off-by: Nick Clemens <nick(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 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #216 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 147802 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147802&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> Signed-off-by: Nick Clemens <nick(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 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #215 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 147801 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147801&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> -- 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 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #214 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 147800 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147800&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> -- 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 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 --- Comment #213 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 147799 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147799&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> -- 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 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #144097|0 |1 is obsolete| | Attachment #144098|0 |1 is obsolete| | Attachment #144099|0 |1 is obsolete| | Attachment #144100|0 |1 is obsolete| | Attachment #144101|0 |1 is obsolete| | Attachment #144102|0 |1 is obsolete| | Attachment #144146|0 |1 is obsolete| | Attachment #145657|0 |1 is obsolete| | --- Comment #212 from Nick Clemens <nick(a)bywatersolutions.com> --- Created attachment 147798 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147798&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> -- 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 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8367 Nick Clemens <nick(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Passed QA -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 33065] New: moremember.pl showing duplicate items
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33065 Bug ID: 33065 Summary: moremember.pl showing duplicate items Change sponsored?: --- Product: Koha Version: 22.11 Hardware: PC OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: rudy.hinojosa(a)lifeafter.solutions QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Created attachment 147347 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=147347&action=e… Screen shot of duplicate item When using offline circulation imports, the checkouts tab in the moremember.pl patron view shows duplicate items/barcodes. After reviewing the mysql database, the items table did not contain duplicate items thankfully. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 26571] New: Add REST API endpoint for patron checkout history
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26571 Bug ID: 26571 Summary: Add REST API endpoint for patron checkout history Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org The options for retrieving and displaying a patron's reading history are limited right now. In the staff client it fetches the whole data set, and in the OPAC it offers the option of either all or 50. I think a REST API endpoint would expand the options we could provide, including features like the one described in Bug 26570, "Search Functionality in Borrowing History." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 33142] New: display the operation number in the table of transactions
by bugzilla-daemon＠bugs.koha-community.org 06 Mar '23

06 Mar '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33142 Bug ID: 33142 Summary: display the operation number in the table of transactions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: mathsabypro(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In the table of transaction, it should be useful, for control and for a better understanding of complex situations, to display the operation number (I mean the accountlines_id field). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2