August 2025 - Koha-bugs - lists.koha-community.org

[Bug 37839] New: /api endpoint stops working on strict firewall
by bugzilla-daemon＠bugs.koha-community.org 08 Jun '26

08 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37839 Bug ID: 37839 Summary: /api endpoint stops working on strict firewall Change sponsored?: --- Product: Koha Version: 23.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: adifbbk1(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com Created attachment 171045 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=171045&action=e… Screenshot of the issue My firewall doesn't allow access to the site http://json-schema.org/draft-04/schema and the Koha logs shows below- Warning: "Could not load REST API spec bundle: GET http://json-schema.org/draft-04/schema: Service unavailable at /usr/share/perl5/JSON/Validator/Store.pm line 190. And, the /api endpoint now suddenly stops working. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 37325] New: Automatically add punctuation to Marc21 field 260 / 264
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '26

06 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37325 Bug ID: 37325 Summary: Automatically add punctuation to Marc21 field 260 / 264 Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexander.wagner(a)desy.de QA Contact: testopia(a)bugs.koha-community.org If the record leader 18 specifies `c` or `n` the Marc record in question does not hold any punctuation chars. IOW the record would look like ``` 264 _1 |a Berlin |a Boston, Mass. |b de Gruyter |c 2011 ``` This should display like Berin ; Boston, Mass. : de Gruyter, 2011 A similar handling is required for both 260 and 264. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 28182] New: Elastic search exact authorities search includes punctuation
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '26

06 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28182 Bug ID: 28182 Summary: Elastic search exact authorities search includes punctuation Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com Bug 26533 fixes the 'exact' search option to search exactly This reveals that the ES search includes punctuation In koha testing docker search for: Addison-Wesley professional computing series And then: Addison-Wesley professional computing series. You get different records -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 24833] New: Field ending punctuation needs to consider abrreviations and exceptions
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '26

06 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24833 Bug ID: 24833 Summary: Field ending punctuation needs to consider abrreviations and exceptions Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 24094 made some improvements to reconciling the ending punctuation form the bibliographic record to the authority, however, it still lacks consistency. >From comment 10 on bug 24094: *If* one wanted to build a list of exceptions of authority punctuation that would need to be kept, here are a few places to start (from an incomplete U.S./Library of Congress perspective): - etc. - B.C. - A.D. - a period following a single letter (as in an initial) - Dr. - Jr. - Mrs. - Co. - Dept. - Inc. - hyphen (-) - closing parenthesis ) - question mark ? - exclamation point ! If this is the path taken, I strongly recommend this list be expanded to be inclusive of punctuation and abbreviations used in authority records of languages other than American English. It could probably use a few more English exceptions, too. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 17656] New: Irregularities in serial prediction pattern are planned only for the current year
by bugzilla-daemon＠bugs.koha-community.org 06 Jun '26

06 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17656 Bug ID: 17656 Summary: Irregularities in serial prediction pattern are planned only for the current year Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P2 Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: koha(a)univ-lyon3.fr QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When you se, through test prediction pattern, a serial pattern including planned irregularities (for example a 1/month serial that you know there's no issue on july), this is only valid fot the current subscription. Over the next renewal, you will have to set it again which is very tedious. We should be able to configure this in the long run (as it was possible in previous version of Koha before 3.14, I think) Olivier Crouzet -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 391

[Bug 27734] New: OpacHiddenItems produces a 404 from borrower holds list
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '26

05 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27734 Bug ID: 27734 Summary: OpacHiddenItems produces a 404 from borrower holds list Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: mfuerst(a)hmcpl.org QA Contact: testopia(a)bugs.koha-community.org When a borrower clicks on a hold in their holds list they have placed on a title that was subsequently hidden with OpacHiddenItems, it results in a 404 error instead of the "This record is blocked" error page. It seems like OpacHiddenItems should work the same as individually suppressed records and how they are handled in OpacSuppressionRedirect. This would make more sense from the user's perspective. -- You are receiving this mail because: You are watching all bug changes.

1 46

[Bug 40171] New: ILL Patron Has No Email Address on File message upon "Send Notice To Patron"
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '26

05 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40171 Bug ID: 40171 Summary: ILL Patron Has No Email Address on File message upon "Send Notice To Patron" Change sponsored?: --- Product: Koha Version: 24.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: tech(a)bethlehemlibraryct.org QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com In using the ILL module, I noticed that when using the "Send Notice to Patron" button, I get no feedback as to whether the notification was sent successfully. Specifically, I had an ILL request from a patron with no email address on file. I assumed that an email was sent to the patron after clicking the button, but since he had no email address on file, he wasn't notified. It would be really helpful to have a message pop up saying "Patron has no email address on file. Please call XXX-XXX-XXXX to let them know that their ILL request has arrived." (or something similar) so that the staff member knows they need to call the patron. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 34

[Bug 35292] New: Define itemtype specific rules in the UpdateNotForLoanStatusOnCheckOut system preference
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '26

05 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35292 Bug ID: 35292 Summary: Define itemtype specific rules in the UpdateNotForLoanStatusOnCheckOut system preference Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com For parity and more workflow options, adding the same option to the new status that updates not for loan on checkout should also have the ability to limit by item type like Bug 25560 did for check in. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 80

[Bug 39944] New: Metadata should be trimmed before creating an ILL request
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '26

05 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39944 Bug ID: 39944 Summary: Metadata should be trimmed before creating an ILL request Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: pedro.amorim(a)openfifth.co.uk Reporter: pedro.amorim(a)openfifth.co.uk QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com When creating an ILL request, if the form data contains leading or trailing whitespaces, this may cause issues for backends. Example: A DOI is entered as ' 123', instead of '123'. If the backend needs to use that data entry, it'll need to first trim and/or sanitize it. It's better if core Koha does this trimming before delegating the creation of the request to the backend, so it's maintained in a single place. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 40492] New: Pending offline circulation actions - barcode link should link to item details
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '26

05 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40492 Bug ID: 40492 Summary: Pending offline circulation actions - barcode link should link to item details Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: emily.lamancusa(a)montgomerycountymd.gov Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle(a)bywatersolutions.com In the pending offline circulation actions table, the barcode links to the biblio record, but it would be more helpful if it linked to the item details of the specific item. -- You are receiving this mail because: You are watching all bug changes.

1 18