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

[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 40258] New: Option to only use item-level recalls and disable record-level recalls
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '26

05 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40258 Bug ID: 40258 Summary: Option to only use item-level recalls and disable record-level recalls Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com It would be good to essentially hide the "Recall next available item" options for libraries who do not want record-level recalls -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 32509] New: Embed see-also-from headings into bibliographic records export
by bugzilla-daemon＠bugs.koha-community.org 05 Jun '26

05 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32509 Bug ID: 32509 Summary: Embed see-also-from headings into bibliographic records export Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: fridolin.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Like Bug 31286 for see-also-forms 5xx -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 30484] New: Interlibrary Loans should have the ability to send notices based on request supplier updates
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30484 Bug ID: 30484 Summary: Interlibrary Loans should have the ability to send notices based on request supplier updates Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com It should be possible for the Interlibrary Loans module to inform a user when a request supplier makes a pertinent change to an outstanding request. Scenario defined by customer to be fulfilled by this bug: - A user places an ILL request for a journal article via the RapidILL backend. - RapidILL fulfil the request with an electronic resource. - The user is notified of the request fulfilment via their chosen communication method, the notice contains the link and password required to access the requested resource. The intended solution will add a mechanism to allow Koha ILL to periodically check outstanding requests with suppliers for updates and act accordingly. As an aside, there is a known customer requirement for notices to be sent when requests are modified locally, this requirement will be catered for in the design of the solution. Details of the intended implementation: - An ILL backend, or core Koha ILL, can define one or more "update processors", these are functions that can perform an action when supplied with an update meeting the criteria they're interested in - An ILL request will be given the ability to obtain its latest status with the supplier, known as an "update" - "Updates" can then be passed to "update processors" that are interested in them, which can then perform whatever actions they wish. Generic - Core Koha ILL will provide: - An object to encapsulate supplier updates - A base class from which "update processors" can be subclassed - Functions to gather updates from backends and orchestrate the processing - A notice template which will be used to send update notices - A shell script that can be run to initiate the process For the customer use case defined above: - The RapidILL backend will: - Provide the ability to retrieve the latest update from the RapidILL API - Define a SendArticleLink processor -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 45

[Bug 39790] New: ES server can timeout during matching process
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39790 Bug ID: 39790 Summary: ES server can timeout during matching process Change sponsored?: --- Product: Koha Version: Main 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 QA Contact: testopia(a)bugs.koha-community.org We have found on larger sites that when importing large batches we can cause enough load on an ES server to begin getting timeouts. The matching currently generates a query per matchpoint, and uses the standard query builder which adds fields etc that aren't needed. This bug will attempt to simplify the queries we are sending for matching -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 39520] New: Add lending status graph
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39520 Bug ID: 39520 Summary: Add lending status graph Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: pedro.amorim(a)openfifth.co.uk, tomascohen(a)gmail.com This is for tracking adding a lending status graph as an early step towards having supplying/lending agency in Koha core. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 23874] New: Advanced Editor is not loaded over HTTPS
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23874 Bug ID: 23874 Summary: Advanced Editor is not loaded over HTTPS Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: fraktik(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Symptoms: Loading, please wait... Editor of record is visually loaded in background, but over it is big endless running circle with announcement: "Loading, please wait... Source of problem: The script is by default blocked by browsers because there is some hardlink to HTTP content. Another details: - This is related both to 18.05 and 19.05, Firefox and Chrome, Win10 and Ubuntu, and it's behaving practically same. - We have in general disabled (forwarded) all unsecured traffic to https at our nginx rproxy server. Console output: Blocked loading mixed active content “http://demo.koha.cz/cgi-bin/koha/svc/cataloguing/framework?callback=define” editor.pl The resource from “https://demo.koha.cz/cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define” was blocked due to MIME type (“text/html”) mismatch (X-Content-Type-Options: nosniff). editor.pl <script> source URI is not allowed in this document: “https://demo.koha.cz/cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define”. editor.pl:1:1 Error: Script error for: /cgi-bin/koha/svc/cataloguing/framework?frameworkcode=&callback=define http://requirejs.org/docs/errors.html#scripterror -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 33413] New: Make staff notices digest-able for OPAC_REG and NEW_SUGGESTION
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33413 Bug ID: 33413 Summary: Make staff notices digest-able for OPAC_REG and NEW_SUGGESTION Change sponsored?: --- Product: Koha Version: 22.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: catrina(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The EmailPurchaseSuggestions and EmailPatronRegistration system preferences should be configurable to send a daily digest of the purchase suggestions or self-registered patrons for a given library. Especially for larger public libraries or consortia, the number of emails triggered by this system preference could quickly become overwhelming but the appropriate staff may still want to be notified when these actions occur. The corresponding notices are NEW_SUGGESTION and OPAC_REG. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9

[Bug 28736] New: Better error message when ES fails to understand the syntax of the search query
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28736 Bug ID: 28736 Summary: Better error message when ES fails to understand the syntax of the search query Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: stalkernoid(a)gmail.com "Unable to perform your search. Please try again." error message doesn't provide any information to the user about the problem and can be really confusing, it implies that by simply performing the search again the result may be different somehow, while in reality the search query probably has incorrect ES syntax which will never work no matter how many times you try, asking user to "Please try again" is redundant. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 38623] New: Suggestion management page does not show preferred name
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38623 Bug ID: 38623 Summary: Suggestion management page does not show preferred name Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org Depends on: 28633 Bug 28633 added a "preferred name" field to patrons, which was meant to be displayed instead of the first name (if enabled) whenever a patron name is displayed in the staff interface, with the first name being visible only on the patron's account details page. The purchase suggestions table is still displaying the first name in the "Suggested by", "Managed by", and "Last modification by" columns. The form for editing a purchase suggestion is also displaying the first name for the suggestor and suggestion manager. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28633 [Bug 28633] Add a preferred name field to patrons -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4