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

[Bug 42607] New: Holds queue: Remove intermediate filter page now that results are API-driven
by bugzilla-daemon＠bugs.koha-community.org 18 May '26

18 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42607 Bug ID: 42607 Summary: Holds queue: Remove intermediate filter page now that results are API-driven Initiative type: --- Sponsorship --- status: 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: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, lisette(a)bywatersolutions.com, tomascohen(a)gmail.com Depends on: 42503 Now that the holds queue page is fully API-driven with server-side pagination, filtering, and sorting (bug 42503), the intermediate step where the user must choose a library filter before seeing results is unnecessary. The table can load immediately with all results (paginated) and the library filter can be a column filter or a dropdown above the table, like other API-driven pages. Additionally, the breadcrumbs still show a 'Results' level that no longer makes sense with the single-page approach. Changes needed: - Remove the initial filter form / two-step flow - Load the holds queue table directly on page load - Move the library filter to a table filter control - Remove 'Results' from breadcrumbs Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42503 [Bug 42503] Render the holds queue using the REST API -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 42631] New: Empty value in authorised_values_category from auth_val_cat.sql
by bugzilla-daemon＠bugs.koha-community.org 18 May '26

18 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42631 Bug ID: 42631 Summary: Empty value in authorised_values_category from auth_val_cat.sql Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com in installer/data/mysql/mandatory/auth_val_cat.sql, there is : 1 INSERT IGNORE INTO authorised_value_categories( category_name, is_system ) 2 VALUES 3 ('', 1), This leads to the existance of an empty value in concerned dropdown that does not appear to have any role in Koha. Does anyone knows what is its purpose ? Note: I'm not quite sure about the category, feel free to change -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 42540] New: Trap and throw elastic too_many_clauses errors instead of just dying
by bugzilla-daemon＠bugs.koha-community.org 18 May '26

18 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42540 Bug ID: 42540 Summary: Trap and throw elastic too_many_clauses errors instead of just dying Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org This started out as an issue with Connexion gateway, but it's not actually directly related. The issue is that during import, a record may contain so many fields to match on that it exceeds the max clauses an es server is configured for. In this case Koha 500's and connex emits the generic "Unsuccessful request" error. It seems the best patch forward would be to trap this error and propagate it as a Koha Exception, rather than simply die. There may be other elastic errors we could add to this pattern but I've not encountered any others so far. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 42468] New: Add systemd support for OCLC Connexion daemon
by bugzilla-daemon＠bugs.koha-community.org 18 May '26

18 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42468 Bug ID: 42468 Summary: Add systemd support for OCLC Connexion daemon Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For some reason, connexion was never bundled into koha-common. We should add that to systemd which is added by bug 40901. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 42629] New: Capitalization: The Permitted staff only permission has no effect while this list is private.
by bugzilla-daemon＠bugs.koha-community.org 17 May '26

17 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42629 Bug ID: 42629 Summary: Capitalization: The Permitted staff only permission has no effect while this list is private. Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Found while translating main: The Permitted staff only permission has no effect while this list is private. The Staff only permission has no effect while this list is private. koha-tmpl/intranet-tmpl/prog/en/modules/virtualshelves/shelves.tt:74 Permitted and Staff should not be capitalized. Maybe we should use '' instead to make it clear what the name of the option is? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 42628] New: Terminology: Biblio ID:
by bugzilla-daemon＠bugs.koha-community.org 17 May '26

17 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=42628 Bug ID: 42628 Summary: Terminology: Biblio ID: Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Found while translating main: Biblio ID: koha-tmpl/intranet-tmpl/prog/en/modules/tools/restore-records.tt:116 • koha-tmpl/intranet-tmpl/prog/en/modules/tools/restore-records.tt:144 Biblio should not be used, we should use bilbionumber or bibliographic record ID instead. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 40935] New: Terminology: Biblio was already issued
by bugzilla-daemon＠bugs.koha-community.org 17 May '26

17 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40935 Bug ID: 40935 Summary: Terminology: Biblio was already issued Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: anneli.osterman(a)koha-suomi.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com koha-tmpl/intranet-tmpl/prog/en/includes/action-logs.inc:233 Biblio was already issued According to Koha's Terminology the word "biblio" should not be used. Use "bibliographic record". Is the word bibliographic record correct in this context? Should it be item? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 41350] New: Terminology: Biblio was already issued
by bugzilla-daemon＠bugs.koha-community.org 17 May '26

17 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41350 Bug ID: 41350 Summary: Terminology: Biblio was already issued Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Keywords: Academy Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Biblio was already issued koha-tmpl/intranet-tmpl/prog/en/includes/action-logs.inc:239 Biblio should be replaced with bibliographic record. -- You are receiving this mail because: You are watching all bug changes.

1 17

[Bug 13823] Item search should include note fields
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

1 0

[Bug 13823] Item search should include note fields
by bugzilla-daemon＠bugs.koha-community.org 15 May '26

15 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13823 --- Comment #8 from David Nind <david(a)davidnind.com> --- Created attachment 199209 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=199209&action=e… Bug 13823: Add item notes to item search results This patch adds the public and non-public item note fields to the staff client item search results. Both fields can now be displayed in the item search results table, configured through table settings, and included in CSV exports. 1. Apply the patch. 2. Edit an item and add text to both: - Public note - Non-public note / Internal note 3. Go to Cataloging > Item search. 4. Run a search that returns the edited item. 5. Open the Columns menu. 6. Confirm Public note and Internal note appear as toggleable columns. 7. Toggle both columns on. 8. Confirm the notes display correctly in the item search results table. 9. Go to Administration > Table settings > Catalog > Item search > results. 10. Confirm itemnotes and itemnotes_nonpublic appear in the table settings. 11. Export the item search results to CSV. 12. Confirm the CSV includes Public note and Internal note columns with the expected values. 13. Sign off and have an incredible day! :D Signed-off-by: David Nind <david(a)davidnind.com> -- You are receiving this mail because: You are watching all bug changes.

1 0