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

[Bug 36801] New: Allow un-resolving of a catalog concern
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36801 Bug ID: 36801 Summary: Allow un-resolving of a catalog concern Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We didn't allow for re-opening a resolved catalog concern before, but with the introduction of the update status's I think we managed to change the logic a bit and the 'Update' button now displays. This effectively allows for re-opening a resolved ticket; However, the actual ticket state isn't properly updated and should be so the new state is properly reflected in the display table and filtering options. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 42526] New: Bib record of an title with a Cataloging Concern, click on the "Concerns" tab, and then click on the "Details" button under "Actions, " nothing happens
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42526 Bug ID: 42526 Summary: Bib record of an title with a Cataloging Concern, click on the "Concerns" tab, and then click on the "Details" button under "Actions," nothing happens Initiative type: --- Sponsorship --- status: Product: Koha Version: 25.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: sam.young(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We can access our Cataloging Concerns from our Koha homepage. However, if we navigate to the bib record of an title with a Cataloging Concern, click on the "Concerns" tab, and then click on the "Details" button under "Actions," nothing happens--the pop-up window does not appear. See screenshot for https://staff-fayetteville.bywatersolutions.com/cgi-bin/koha/catalogue/deta…. This Error appears: Uncaught TypeError: $(...).kohaSelect is not a function at HTMLDivElement.<anonymous> ( VM1501 display_ticke…5.1102000.js:135:27 ) at HTMLDivElement.dispatch ( jquery-3.6.0.min_25.1102000.js:2:43064 ) at v.handle ( jquery-3.6.0.min_25.1102000.js:2:41048 ) at Object.trigger ( jquery-3.6.0.min_25.1102000.js:2:71515 ) at HTMLDivElement.<anonymous> ( jquery-3.6.0.min_25.1102000.js:2:72110 ) at S.each ( jquery-3.6.0.min_25.1102000.js:2:3003 ) at s.fn.init.each ( jquery-3.6.0.min_25.1102000.js:2:1481 ) at s.fn.init.trigger ( jquery-3.6.0.min_25.1102000.js:2:72086 ) at Object.trigger ( bootstrap.bundle.min…5.1102000.js:6:5314 ) at On.show ( bootstrap.bundle.min….1102000.js:6:51861 ) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21889] New: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21889 Bug ID: 21889 Summary: Include Staff Client entered Purchase Suggestions with System Preference maxopensuggestions Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently only Purchase Suggestions made by patrons through the OPAC are the only suggestions counted in the system preference MaxOpenSuggestions. It would be nice if this system preference also connected to the staff client, so a purchase suggestion done on the patrons account by staff alerted the staff that the patron already had the maximum number of purchase suggestion allowed. At this time, even if a patron has maxed out the number of open purchase suggestions on the OPAC, a staff member can still enter more purchase suggestions for that patron through the staff client without knowledge of the maxopensuggestions being reached. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 37645] New: Add ability to batch waive fines
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37645 Bug ID: 37645 Summary: Add ability to batch waive fines Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: enica(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org It would be nice if there's an ability in Koha to waive fines/fees in a batch. This is part of a regular workflow for libraries, especially those who regularly purge patron accounts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 80

[Bug 35325] New: Add the ERM module to Library Groups
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35325 Bug ID: 35325 Summary: Add the ERM module to Library Groups Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart+koha(a)gmail.com Reporter: kelly(a)bywatersolutions.com CC: jonathan.druart+koha(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com For multi-library systems in Koha currently, to use the ERM module, there is no separation to identify what agreements and licenses go to which library. It would be fantastic to add the ERM module to Library Groups to allow a way to separate and identify between libraries. -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 27859] New: Marc export for search result
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27859 Bug ID: 27859 Summary: Marc export for search result 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: glasklas(a)gmail.com This patch provides the option of exporting a search result as MARCXML or iso 2709. Ideally the export should be asynchronous but it was much trickier than first thought to fork and detach from Apache so gave that up for now. A link to the export is sent to the current user as an email as a simple way of delivering the response asynchronously (keeping it this way so don't have to refactor when/if the export is made asynchronous). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 114

[Bug 37502] New: Holdings table needs an ERM tab
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37502 Bug ID: 37502 Summary: Holdings table needs an ERM tab Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: jonathan.druart(a)gmail.com Reporter: esther.melander(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)gmail.com, jonathan.field(a)ptfs-europe.com, martin.renvoize(a)ptfs-europe.com, matt.blenkinsop(a)ptfs-europe.com, pedro.amorim(a)ptfs-europe.com If a bibliographic record is generated via an import in the ERM, the resulting bibliographic record should have an ERM tab in the holdings table. The ERM tab could have the Package and Title info, even if an item record does not exist. Similar to the Acquisitions tab for acquisitions info. -- You are receiving this mail because: You are watching all bug changes.

1 42

[Bug 42270] New: Log the date a framework changed
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '26

24 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42270 Bug ID: 42270 Summary: Log the date a framework changed Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: mnero(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl We would like to be able to find out when a record was changed from FA to Default. In our workflow, we overlay brief records with full ones and change the framework during import. This overlay gets logged as action "Modify" but there's no indication of a framework change, so we can't differentiate an overlay modification from any other type of modification that might happen. Ideally, we would be able to find the timestamp of when the framework was changed and by which user, but having something in the Info that indicates what the frameworkcode is/was would be useful. A solution for bug 24843 might be related. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 38198] New: Expired patrons can still make purchase suggestions through OPAC
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38198 Bug ID: 38198 Summary: Expired patrons can still make purchase suggestions through OPAC 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: rkuiper(a)roundrocktexas.gov QA Contact: testopia(a)bugs.koha-community.org We would like to add the ability to block expired patrons from placing purchase suggestions. Maybe add this to the BLOCKEXPIREDPATRONOPACACTION system preference as an option? -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 35452] New: Provide more info when using Link authorities automatically
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35452 Bug ID: 35452 Summary: Provide more info when using Link authorities automatically Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: adolfo.rodriguez(a)xercode.es QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl There are records with many entries that can be linked to authorities, be it secondary authors (7xx) or subjects (6xx) As it is, when you use "Automatic authority link" the results list only indicate the field number, so you see something like this. * 650 - More than one local match found. Possibly a duplicate authority! * 650 - More than one local match found. Possibly a duplicate authority! * 650 - More than one local match found. Possibly a duplicate authority! * 700 - No matching authority found. * 700 - No matching authority found. * 700 - No matching authority found. To figure out which are the entries the results refer to you have to manually check the fields in the record. I think this could improved by adding info about the entries. Something like this. * 650 - Rock music. - More than one local match found. Possibly a duplicate authority! * 650 - Alternative rock music. - More than one local match found. Possibly a duplicate authority! * 650 - Country music. - More than one local match found. Possibly a duplicate authority! * 700 - Ikeda, Elaiza - No matching authority found. * 700 - Okada, Nana - No matching authority found. * 700 - Tsuchiya, Anna - No matching authority found. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27