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

[Bug 39516] New: Record and display record matching rule composite scores
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39516 Bug ID: 39516 Summary: Record and display record matching rule composite scores Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When viewing a batch of staged biblio or authority records, those records which found matches show their final match score. It would be helpful to store and display the composite values that are added together to make that final score. An example matching rule: Match threshold: 100 Match point 1: - search index: title - score: 50 - tag: 245$a Match point 2: - search index: author - score: 50 - tag: 100$a Match point 3: - search index: isbn - score: 100 - tag: 020$a Currently, a staged bib that found a match via the combination of title and author would just show "(score=100)" in the staged batch view. A bib that matched just on ISBN would show the same thing, "(score=100)." It'd be helpful to instead show something like "(score= title:50, author:50)" or "(score= isbn:100)" -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 66

[Bug 34353] New: We don't need 'SpineLabelShowPrintOnBibDetails' anymore
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34353 Bug ID: 34353 Summary: We don't need 'SpineLabelShowPrintOnBibDetails' anymore Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Surely we don't need this preference anymore.. one can enable/disable the option to display this button from the table settings page instead? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 40659] New: Allow "My virtual card" format and content to be set using a Notices & Slips template
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40659 Bug ID: 40659 Summary: Allow "My virtual card" format and content to be set using a Notices & Slips template Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Libraries would like more flexibility in the virtual card shown to patrons via the OPAC. Making that virtual card use a notice template would make is highly customizable. -- You are receiving this mail because: You are watching all bug changes.

1 111

[Bug 40255] New: Allow custom debit descriptions
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40255 Bug ID: 40255 Summary: Allow custom debit descriptions Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 24865 made it possible to use a notice to replace the default wording of the description for overdue fines. It would be helpful to expand that functionality to all debit types, both system-defined and local. It might make more sense to put this within the Debit Type setup than to continue using notices, though. These custom descriptions would allow Template Toolkit as notices do, however, for formatting, logic, and value transformation -- for example, one library wants the description to tell what portion of the fee goes to local tax. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 73

[Bug 39158] New: Reduce code duplication in marc_records_to_documents
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39158 Bug ID: 39158 Summary: Reduce code duplication in marc_records_to_documents Change sponsored?: --- Product: Koha Version: unspecified 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 QA Contact: testopia(a)bugs.koha-community.org There is currently a block in Koha::SearchEngine::Elasticsearch::marc_records_to_documents that in my opinion should be brokwn out to its own method for increased maintainability and readability. It's easily done that these two blocks will drift apart with time (when they should be the same), fixing a bug in one place, forgetting in another etc. Here is a patch to fix this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 40841] New: Limit z39.50 targets to specific branches
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40841 Bug ID: 40841 Summary: Limit z39.50 targets to specific branches Change sponsored?: --- 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Within larger systems, catalogers at each individual library have different z39.50 targets that they prefer to use or are allowed access to. It would be good to limit z39.50 targets based on the user's logged-in branch. Bug 5316 proposes limiting access per user. While that could also be helpful, limiting by branch offers a more lightweight and flexible option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 85

[Bug 40853] New: ElasticsearchBoostFieldMatch - needs to boost results more
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=40853 Bug ID: 40853 Summary: ElasticsearchBoostFieldMatch - needs to boost results more 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 When searching for book titles that may have words in many fields, e.g. 'book of hope', the boost is not enough, especially when other fields like 'title' are boosted. In production with title boost of 32 the general results are getting a score of ~600 The boost query is getting a score of ~10 - not enough to boost past the general results We can try a few things: 1 - Use the 'boost' field from 'title-cover' matching in the extra query 2 - Add a system preference (or hard code) to define how much to boost the additional query by 3 - Try using a boost query rather than a bool query: https://www.elastic.co/docs/reference/query-languages/query-dsl/query-dsl-b… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 39

[Bug 41107] New: Create an API endpoint to get Koha version
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=41107 Bug ID: 41107 Summary: Create an API endpoint to get Koha version Initiative type: --- Sponsorship --- status: Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: tomascohen(a)gmail.com It would be helpful to have an API endpoint from which to get the Koha version of a system -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 36853] New: Enhance Elasticsearch Notes/Comments MARC21 index mappings
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36853 Bug ID: 36853 Summary: Enhance Elasticsearch Notes/Comments MARC21 index mappings Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: aleisha(a)catalyst.net.nz We would like to add the following tags and subfields to the existing note index for Elasticsearch MARC21, as used by the "Notes/Comments" advanced search dropdown option: * 501a * 503a * 504a * 508a * 511a * 521a * 538a * 547a * 591a * 592a * 593a * 594a * 595a * 596a * 597a * 598a * 599ab -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 36506] New: Processing Fee should be configurable by branch
by bugzilla-daemon＠bugs.koha-community.org 24 May '26

24 May '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36506 Bug ID: 36506 Summary: Processing Fee should be configurable by branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org In a consortia environment, some branches might want a process fee and others might not. This could be worked around with multiple item types, but that can cause other issues. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 75