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

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

04 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 35948] New: cleanup_database.pl should remove not only finished background jobs
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35948 Bug ID: 35948 Summary: cleanup_database.pl should remove not only finished background jobs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 Bug 31969 changed cleanup_database.pl so it removes only finished background jobs. But old background jobs with other statuses will never be removed. I see no use to that -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 37762] New: Expand ILL to allow for Supplying Agency/Lending Library workflows
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37762 Bug ID: 37762 Summary: Expand ILL to allow for Supplying Agency/Lending Library workflows 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)ptfs-europe.com, tomascohen(a)gmail.com Currently Koha's ILL module allows for the Koha library to be a borrowing library/institution but does not currently allow for the Koha library to be a supplying agency/lending library. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 106

[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 27428] New: Show the number of records in the bibliographic record detail page with ElasticSearch.
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27428 Bug ID: 27428 Summary: Show the number of records in the bibliographic record detail page with ElasticSearch. 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: ivan.dziuba(a)inlibro.com This preference only for OPAC to show the number of records next to search links in the bibliographic record detail page. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 105

[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 39207] New: Improve usability of search when holding a specific item
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39207 Bug ID: 39207 Summary: Improve usability of search when holding a specific item Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lauri.hanninen(a)lahti.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Created attachment 178779 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=178779&action=e… Image showing how user's set library blocks filtering due to allowed pickup locations When filtering for a specific item on holds page using the search bar, it's currently not feasible to filter by user's set library. When entering the user's set library in the search field, search results won't narrow down because they include the active selection in the Allowed pickup locations column which by default is the user's set Library. Filtering by user's own library would be one of the common usages for the search field when placing a hold on a specific item, so it would have more usability if it could be fixed. See attached image as an example. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 17387] New: Add an undelete feature for items/biblios
by bugzilla-daemon＠bugs.koha-community.org 04 Jun '26

04 Jun '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17387 Bug ID: 17387 Summary: Add an undelete feature for items/biblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Some libraries would like to be able to restore items accidentally deleted. This should be possible, rows can be copied over as long as there are checks in place for unique ids. -- You are receiving this mail because: You are watching all bug changes.

1 272

[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