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

[Bug 37856] New: Some SUSHI providers require the platform parameter
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '25

06 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37856 Bug ID: 37856 Summary: Some SUSHI providers require the platform parameter Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ERM Assignee: pedro.amorim(a)ptfs-europe.com Reporter: pedro.amorim(a)ptfs-europe.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, michaela.sieber(a)kit.edu, pedro.amorim(a)ptfs-europe.com The harvest_sushi method produces the following URL when harvesting SUSHI data: <provider_url>/reports/<report_type>?customer_id=<customer_id>&requestor_id=<requestor_id>&api_key=<api_key>&begin_date=<begin_date>&end_date=<end_date> Some providers require the 'platform' parameter. Docs here: https://app.swaggerhub.com/apis/COUNTER/counter-sushi_5_0_api/5.0.2#/defaul… We need to look for a way to identify when/if a provider requires this parameter, and add it to the URL if so. The provider in question is ScienceDirect: https://registry.countermetrics.org/platform/ab4d3560-1165-491d-a67e-9359d0… The 'platform parameter required' entry is unchecked even though this provider requires it. We should consider using this to identify if the parameter is required or not. -- You are receiving this mail because: You are watching all bug changes.

1 53

[Bug 39828] New: QuickAdd skips fields from PatronQuickAddFields in some cases
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '25

06 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39828 Bug ID: 39828 Summary: QuickAdd skips fields from PatronQuickAddFields in some cases Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: slavashishkin(a)gmail.com Reporter: slavashishkin(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When using PatronQuickAddFields to add fields to the Quick Add form, fields that exist in the main form but contain multiple input elements (especially hidden/disabled ones) may be silently skipped during QuickAdd form generation. Example: "userid" field exists in the full patron form (entryform) as: > <li> > <label for="userid">Username:</label> > <input type="text" id="userid" name="userid" ...> > <input type="text" disabled="disabled" style="display:none" ...> > </li> The current JavaScript logic to detect and clone these fields uses: > let orig_input_id = orig_li.children("input,textarea,select").last().attr("id"); In this example, .last() selects the hidden disabled input without an id → orig_input_id becomes undefined → and the field is not cloned into QuickAdd form. Result: userid is missing from Quick Add even though it's included in PatronQuickAddFields. Steps to reproduce: 1. Add userid (or any other field that matches above structure) to PatronQuickAddFields. 2. Open the Add Patron form and use Quick Add. 3. Observe → the field is missing. -- You are receiving this mail because: You are watching all bug changes.

1 7

[Bug 40341] New: Patron Category Messaging Preferences Not Applied to Existing Patrons
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '25

06 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40341 Bug ID: 40341 Summary: Patron Category Messaging Preferences Not Applied to Existing Patrons Change sponsored?: --- Product: Koha Version: 25.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: samrocks1011(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 28492] New: Hyphen in branchcode gives wrong search results
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28492 Bug ID: 28492 Summary: Hyphen in branchcode gives wrong search results Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org A client noticed that when limiting by branch, some search results were wrong and after a bit of digging, I found that it happens when the branchcode contains a hyphen. I was able to recreate the situation as follows: 1) Go to Administration > Libraries and add the libraries - Fairfield (branchcode FFL) -- if you have the default database, this library should already exist - Fairfield North (branchcode FFL-N) - Fairfield South (branchcode FFLS) 2) Add an item to record A with holding branch FFL-N 3) Add an item to record B with holding branch FFLS 4) reindex if necessary 5) In Advanced search, search for record A and limit to Fairfield North library -- record is in the results - OK 6) In Advanced search, search for record A and limit to Fairfield library -- record is in the results! - NOT OK 7) In Advanced search, search for record B and limit to Fairfield South library -- record is in the results - OK 8) In Advanced search, search for record B and limit to Fairfield library -- record is not in results - OK As you can see, the search for branchcode FFL-N and for branchcode FFL give the same results. The problem was originally found by a client using 18.05.03. I was able to recreate in 20.05.08 and master (21.06.000), always with Zebra. I didn't try with ES because mine is currently broken :( -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 40439] New: We cannot use the arrow keys to navigate through all the items in the navigation menus
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40439 Bug ID: 40439 Summary: We cannot use the arrow keys to navigate through all the items in the navigation menus Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Accessibility Assignee: koha-bugs(a)lists.koha-community.org Reporter: nina.martinez(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: martin.renvoize(a)openfifth.co.uk, matt.blenkinsop(a)openfifth.co.uk, oleonard(a)myacpl.org We cannot use the arrow keys to navigate through all items in the navigation menus. Specifically, the arrow keys do not work for navigating the user menu “Welcome, ” in the navigation bar. While all other dropdown menus are navigable using the arrow keys like List and Languages (in the Languages menu, navigation is possible only with the arrow keys), this one is not. We can navigate it only with the Tab key, which can be confusing for users. Keyboard navigation is one of the most important accessibility features. We could improve this to enable navigation in this menu using the arrow keys like the other menus. To test this issue: 1- Log in to an account 2- Navigate with the tab key through the navigation bar, test to navigate in the different menus (List, Languages) with the arrows keys. 3- Go to ‘Welcome, ’ press Enter, and try to navigate through the options with the arrow keys. https://webaim.org/techniques/keyboard/ -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 40979] New: Item group level holds are not shown correctly on Holds to pull
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40979 Bug ID: 40979 Summary: Item group level holds are not shown correctly on Holds to pull Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Available item count is incorrect. Barcodes, call numbers, etc. circ/pendingreserves probably needs another refactoring? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 39243] New: Display Item Group in patron’s list of checked out items
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39243 Bug ID: 39243 Summary: Display Item Group in patron’s list of checked out items 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: rpalermo(a)oslri.net QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In Koha, when a patron has an item attached to an item group checked out, the item group does not show on their checked out screen. We use item groups for individual periodical issues and it would be helpful to be able to let the patron know which issue they have checked out by looking at that screen. We would like to see Item Group as one of the options when selecting Columns Settings so we could add that to the display. Currently the only way for library staff to tell the patron which periodical issue (item group) they have checked out is to go into bib record, click the normal tab to go to the holdings table, search for barcode to see the item group. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 38976] New: "Clear filter" on log entries table in log viewer does not work
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38976 Bug ID: 38976 Summary: "Clear filter" on log entries table in log viewer does not work Change sponsored?: --- Product: Koha Version: 24.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: kkrueger(a)cuyahogalibrary.org QA Contact: testopia(a)bugs.koha-community.org This one is similar to Bug 38071 "Clear filter" on catalogue details page always disabled" To recreate: 1 - From tools > log viewer, select a module and a date range 3 - Select/type in a search term 4 - Note 'Clear filters' is grayed out 5 - Try to click it, no response -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 19220] New: Allow XSLT procsessing for Z39.50 authority targets like for bibliographic targets
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19220 Bug ID: 19220 Summary: Allow XSLT procsessing for Z39.50 authority targets like for bibliographic targets Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Z39.50 / SRU / OpenSearch Servers Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When configuring a bibliographic Z39.50 targets it's possible to list XSL scripts that change the record on import. While the option is also offered when adding authority Z39.50 targets, it doesn't work/hasn't been implemented. It would be great if this feature was available for both types of targets. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 58

[Bug 32380] New: There should be a staff side equivalent to PatronSelfRegistrationEmailMustBeUnique
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '25

05 Nov '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32380 Bug ID: 32380 Summary: There should be a staff side equivalent to PatronSelfRegistrationEmailMustBeUnique Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: lucas(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We have the ability to enforce unique email address from self reg. We should have a staff side equivalent. When using SSO it can be problematic to have the same email address on different accounts. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3