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

[Bug 31736] New: Context for translation: "All"
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31736 Bug ID: 31736 Summary: Context for translation: "All" Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: caroline.cyr-la-rose(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr "All" is used all over Koha, and refers to different things. In French, those different things have different genders and the "All" must be in that gender ("tous" for "male-gendered" things and "toutes" for "female-gendered" things). In fr-CA-staff-prog, it says "All" is used in these places #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:313 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/invoices.tt:380 #: koha-tmpl/intranet-tmpl/prog/en/modules/acqui/parcel.tt:347 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:121 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/columns_settings.tt:123 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:208 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:216 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:387 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:918 #: koha-tmpl/intranet-tmpl/prog/en/modules/admin/smart-rules.tt:939 #: koha-tmpl/intranet-tmpl/prog/en/modules/catalogue/itemsearch.tt:45 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:247 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:254 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:261 #: koha-tmpl/intranet-tmpl/prog/en/modules/circ/view_holdsqueue.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/members/readingrec.tt:57 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:63 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:74 #: koha-tmpl/intranet-tmpl/prog/en/modules/onboarding/onboardingstep5.tt:86 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:203 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:248 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/acquisitions_stats.tt:263 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/cash_register_stats.tt:111 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/dictionary.tt:116 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:245 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:259 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:887 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/guided_reports_start.tt:1494 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:152 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:156 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:165 #: koha-tmpl/intranet-tmpl/prog/en/modules/reports/itemslost.tt:179 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/checkexpiration.tt:50 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:281 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:396 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/serials-search.tt:415 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:25 #: koha-tmpl/intranet-tmpl/prog/en/modules/serials/subscription-bib-search.tt:37 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/additional-contents.tt:135 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/marc_modification_templates.tt:226 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:217 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:219 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:238 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:240 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:268 #: koha-tmpl/intranet-tmpl/prog/en/modules/tools/viewlog.tt:270 #: koha-tmpl/intranet-tmpl/prog/en/includes/additional-fields-entry.inc:12 #: koha-tmpl/intranet-tmpl/prog/en/includes/av-build-dropbox.inc:16 #: koha-tmpl/intranet-tmpl/prog/en/includes/patron-search.inc:247 #: koha-tmpl/intranet-tmpl/prog/en/includes/subscriptions-search.inc:33 #: koha-tmpl/intranet-tmpl/prog/en/includes/str/tinymce_i18n.inc:2 We should add context so that translators know what that "All" refers to. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 157

[Bug 29236] New: Allow OPAC News / HTML Customization contents to be set for library groups
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29236 Bug ID: 29236 Summary: Allow OPAC News / HTML Customization contents to be set for library groups Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org For the content sent to various OPAC pages/fields from the HTML Customizations interface (OPACNavRight, OPACHeader, etc), it would be helpful to be able to set those values for groups of libraries, rather than just individual libraries. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 28593] New: Add ability to charge lost fee when applying new lost status when resolving a claim
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28593 Bug ID: 28593 Summary: Add ability to charge lost fee when applying new lost status when resolving a claim Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Depends on: 28271 Bug 28271 added the ability to apply a new lost status when resolving a claim. We should also add the ability to charge a replacement fee. Many libraries do not charge a replacement fee when a claim is generated. If the item is not found within the time period allowed by library policy, then the item is assumed lost, the claim is resolved, and the item is set to lost. At that point, the library would like to charge the patron. As things stand, there is not a way to generate a lost fee tied to that issue_id. You'd have to either create a manual invoice or return the item, check it back out to the patron, and mark it lost again. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28271 [Bug 28271] Add the ability to set a new lost status when a claim is resolved -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 13

[Bug 24288] New: Add wording to authorized value interface to indicate valid code length
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24288 Bug ID: 24288 Summary: Add wording to authorized value interface to indicate valid code length Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Several standard authorized values feed into fields that require a single character code (LOST, NOTFORLOAN, DAMAGED, RESTRICTED, WITHDRAWN). It'd be good to have some wording in the authorized value interface that would indicate this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 43

[Bug 33905] New: Username and cardnumber should be unique respectively
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33905 Bug ID: 33905 Summary: Username and cardnumber should be unique respectively Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Currently Koha allows a user to sign in with either their cardnumber or userid Confusion can arise when a user has a username that is another users cardnumber, and vice versa We should check uniqueness across both of these fields. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

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

23 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 30557] New: Add ability to create Item lists
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30557 Bug ID: 30557 Summary: Add ability to create Item lists Change sponsored?: --- Product: Koha Version: 21.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: estherm(a)sodaspringsid.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl This is relevant for multi-branch installations. Lists currently appear to be primarily bibliographic lists. This creates a problem when sorting lists by call number. In this scenario there may be multiple items from different libraries using different call number schema attached to a single bibliographic record. The list cannot be sorted accurately by call number. It would be helpful if there was an option for an item based list. In this scenario items are added to a list for a specific branch. The call number sort will then sort correctly because the call number schema will be consistent for the branch. An item list would display the same information as a bibliographic list with the exception of additional branches which may also have the item. A typical use case would a library creating an item list, sort by call number, and then use that list to go to the shelf to pull the items in order. This is currently not possible in a multi-branch installation without a bit of work. It would require downloading the list and then cleaning up the list to be useful for this kind of work. It may be possible to create a report that will do this, but it would be a nice added functionality in the List tool. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 256

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

23 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 23998] New: Messages REST API
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23998 Bug ID: 23998 Summary: Messages REST API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi Expose messages table via REST API. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 64

[Bug 23649] New: Elasticsearch offer an option to weight search results by type
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '26

23 Oct '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23649 Bug ID: 23649 Summary: Elasticsearch offer an option to weight search results by type 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: nick(a)bywatersolutions.com Some libraries would like to be able to prioritize "books" over "large print" , audios, etc in the search results -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 69