July 2023 - Koha-bugs - lists.koha-community.org

[Bug 33645] New: koha-foreach always returns 1 if --chdir not specified
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '23

21 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33645 Bug ID: 33645 Summary: koha-foreach always returns 1 if --chdir not specified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz If you don't provide --chdir to koha-foreach it will always return an exit code of 1, because the final if statement in the script will return false -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13

[Bug 33196] New: Terminology: remove mention of GDPR in Pseudonymization system preference
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '23

21 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33196 Bug ID: 33196 Summary: Terminology: remove mention of GDPR in Pseudonymization system preference Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: aude.charillon(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The Pseudonymization system preference description in the staff interface is: "Disable/Enable pseudonymization to comply with GDPR for personal information. Patrons and transactions will be copied to a separate table for statistics purpose." GDPR is a European Union (and, at time of writing, UK) law; it makes the system preference look irrelevant for libraries outside this area. However, this is not correct: pseudonymization may be useful for libraries anywhere. The system preference description should be changed to reflect this. Instead, it could be something like: "Disable/Enable pseudonymization to help improve security in the way you store personal information. Selected patron and transaction fields will be copied to a separate table for statistics purposes." -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 31405] New: Set focus for cursor to setSpec input when adding a new OAI set
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '23

21 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31405 Bug ID: 31405 Summary: Set focus for cursor to setSpec input when adding a new OAI set Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org When adding a new OAI set from administration, the focus/cursor should be in the first field of the entry form: setSpec -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 26169] New: Run plugins from the CLI / as a script
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '23

21 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26169 Bug ID: 26169 Summary: Run plugins from the CLI / as a script Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Plugin architecture Assignee: koha-bugs(a)lists.koha-community.org Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org I have some ideas where it could be useful to be able to run a Koha plugin as a script. For example: "echo <oaipmh>records</oaipmh> | koha-plugin --run Koha::Plugin::Dcook::Oaipmh::Harvester --method import kohadev" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 20454] New: Suspend Holds if patron wouldn't be able to check items out
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20454 Bug ID: 20454 Summary: Suspend Holds if patron wouldn't be able to check items out Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a person can't check out an item due to hitting the fine limit, it would be great if the holds could be suspended automatically so it wasn't filled until the account was cleared off. This would be a good system preference so systems that didn't want to use it wouldn't be forced into it. Currently in our system patrons can't check out if they have more than $5 in fines. Sometimes they place a hold, rack up fines, and can't check out the book when it comes in for them. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 33573] New: Holds cancellation for waiting holds via the API don't generate a cancellation request
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33573 Bug ID: 33573 Summary: Holds cancellation for waiting holds via the API don't generate a cancellation request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com DELETE request to /api/v1/holds/{holdkey} simply cancels a waiting hold if that is allowed. It should instead generate a cancellation request We should add a new endpoint: DELETE /api/v1/public/patrons/:patron_id/holds/:hold_id And it should return a 202 accepted response as the actual deletion doesn't happen until the library confirms -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 33471] New: Improve performance of hold pickup location verification for next available holds
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33471 Bug ID: 33471 Summary: Improve performance of hold pickup location verification for next available holds Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com When placing a new hold, or updating the location of an existing hold, we verify that the pickup location is valid. To do so we call 'pickup_locations' on the bib, or the item. The item case is trivial, however, for bibs we call Item->pickup_locations for every item on the bib. If we are simply validating a single location this can be quite expensive and unnecessary. I propose adding a new function to specifically validate pickup location for a biblio -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 15

[Bug 34327] New: maintenance mode after upgrade to 23.05.01-1
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34327 Bug ID: 34327 Summary: maintenance mode after upgrade to 23.05.01-1 Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: afrane55(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Opac dispalys maintenance mode after upgrading to 23.05.01-1 Staff portal is asking for onboarding -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 30013] New: Limit/throttle SMTP connections
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30013 Bug ID: 30013 Summary: Limit/throttle SMTP connections Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org We have a setup where Koha is sending email through the SMTP server of the library's mother institution. We are seeing a problem with sending lots of emails in one go, where the first emails are sent ok, but then the rest fail with an error like this: unable to establish SMTP connection to (mail.x.y) port 25 It looks like this is due to some limit on the server, making it unresponsive if there are too many connections from the same source in a short time. I don't know a lot about SMTP but I can imagine a couple of solutions: - Introduce a configurable "sleep" period between each call to the external SMTP server (or batches of a configurable number, with a configurable sleep between each batch) - Looking at the response from the server and if "unable to establish SMTP connection" is received, wait for a configurable amount of time before trying to resend the failed message and the rest of the queue -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 25466] New: Review 'problem_reports' column names and types
by bugzilla-daemon＠bugs.koha-community.org 20 Jul '23

20 Jul '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25466 Bug ID: 25466 Summary: Review 'problem_reports' column names and types 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org reportid => id borrowernumber => patron_id (created_by_id?) branchcode => library_id problempage => problem_page status => Looks like an ENUM About borrowernumber, I'm not sure it should default to 0, we are leaning to default to NULL. In the code it would probably default to the anonymous patron id? I might be wrong, just putting my notes here for discussion. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6