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

[Bug 33092] New: Add ability to search within a list
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33092 Bug ID: 33092 Summary: Add ability to search within a list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Lists Assignee: koha-bugs(a)lists.koha-community.org Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl It would be really helpful to be able to search within a list in both the OPAC and the staff interface. For instance, in both the staff interface, if you are viewing a public list with a lot of items on it, you do not have the ability to see if a specific item appears on the list. This is a needed functionality with larger lists. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 16

[Bug 18062] New: Damaged Status shows unavilable in results
by bugzilla-daemon＠bugs.koha-community.org 02 Sep '26

02 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18062 Bug ID: 18062 Summary: Damaged Status shows unavilable in results Change sponsored?: --- Product: Koha Version: 3.22 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org When performing a search in the OPAC or staff client and the results include an item that is marked "Damaged" the status shows unavailable on the results page. When you view the detailed view of the record, the item appears as available. Although the item can still be checked out, it is confusing for the patron when they see the unavailable status. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 26866] New: Items table on additem should sort by cn_sort
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26866 Bug ID: 26866 Summary: Items table on additem should sort by cn_sort Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Staff Client 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 To recreate: - create a bib - add three items with source of classification LCC, call numbers: -- JC43 .G6 1890 -- JC330 .F74 2000 -- JC480 .R63 2006 - on additem.pl, sort the items table by "Full call number" - notice items are order incorrectly, going 330, 43, 480 - use a report to pull the cn_sort values for your 3 items, confirm that ordering by cn_sort in your report correctly orders them 43, 330, 480 We should use cn_sort here to get them in the correct order. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 31487] New: Add emails to message queue by longoverdue script options
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31487 Bug ID: 31487 Summary: Add emails to message queue by longoverdue script options Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: thibaud.guillot(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz Some customers request the possibility of sending an additional reminder when processing longoverdues. I think this may be useful for some and given that it remains an option, it does not handicap those who do not want to use it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 27

[Bug 33557] New: Add a system preference to disable/enable thesaurus checking during authority linking
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33557 Bug ID: 33557 Summary: Add a system preference to disable/enable thesaurus checking during authority linking Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Bug 30280 added support for multiple thesauri, however, this is a major change in behavior. Prior to this patch, heading from different sources would all link to the same authority, and auto generated authorities would link to any source. After this patch, however, a library will need to reindex their authorities after upgrade or face linking issues. For libraries who auto create authorities, there is the potential for generating a new set of authorities for any record from a differing source. In order to minimize disruption, we should provide a system preference, disabled by default, to allow libraries to opt in to thesaurus checking -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 27603] New: Add API for lists management
by bugzilla-daemon＠bugs.koha-community.org 01 Sep '26

01 Sep '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=27603 Bug ID: 27603 Summary: Add API for lists management Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: oleonard(a)myacpl.org Created attachment 116256 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=116256&action=e… Screenshot of the list modal idea I was playing around with making the list add form a modal instead of a popup, and while it can be hacked together as things are now it really would be better to have an API to work with. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 5

[Bug 32122] New: Wrong permissions check on item circulation alerts
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '26

31 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32122 Bug ID: 32122 Summary: Wrong permissions check on item circulation alerts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Bug 14391 added granular permissions for the administration module, however, there was a mismatch in the check on item circulation alerts and the new permission -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 21173] New: Run auto item modifications by age every hour and set the item age unit to hours
by bugzilla-daemon＠bugs.koha-community.org 29 Aug '26

29 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21173 Bug ID: 21173 Summary: Run auto item modifications by age every hour and set the item age unit to hours 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: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Make auto item modification by age cronjob run more often than once daily. Setting this cronjob to run every hour will be set in the /etc/cron.hourly/koha-common. However 2 further changes to the automatic item modification tool to make an hourly running cronjob useful. 1. Be able to set the age of the item in hours not just days. This is so an hourly cronjob has items to alter because items will exceed the age limit more frequently than if the item age is in hours. 2. Give the user the choice of what the age starting point (time from which the age of the item is calculated) used in the cronjob is. The two possible age starting points that users have to choose between are: * Item creation (this is the age starting point in master currently) * Item last altered This is so items whic have been in the catalogue for a while can still be affected by the automatic item modification by age cronjob. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 86

[Bug 23111] New: Setting a custom framework as the default for cataloguing is not possible
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23111 Bug ID: 23111 Summary: Setting a custom framework as the default for cataloguing is not possible 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: hayleymapley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Target Milestone: --- Currently, it is not possible to select a custom framework as the default, in situations where editing a record with no framework mapped, or importing a staged MARC file with no mapping. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 87

[Bug 31268] New: Clearly indicate reason for failed item creation when receiving expired subscription
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '26

28 Aug '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31268 Bug ID: 31268 Summary: Clearly indicate reason for failed item creation when receiving expired subscription Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrewfh(a)dubcolib.org QA Contact: testopia(a)bugs.koha-community.org Bug 29188 points out that while the manual says one cannot receive issues in an expired subscription, Koha is currently allowing one to do so. However, Koha *is* refusing to create an item when receiving an issue on an expired subscription. To recreate: 1 - create a subscription set to *not* create items, subscription end date in the past 2 - save subscription, confirm it shows as expired, confirm you can receive an issue anyway 3 - create a subscription set *to* create items, subscription end date in the past 4- save subscription, confirm it shows as expired, confirm you can get to the receiving page but setting the dropdown for the expected issue to "Arrived" does not cause an item edit box to appear 5- create a subscription set *to* create items, subscription end date in the future, number of issues set to 1 6- save subscription, receive 1 issue, confirm it works as intended 7- confirm subscription now shows a confusing "Subscription will expire on [subscription end date]" message even though the date isn't the problem 8- Attempt to receive another issue, confirm that now the item edit box won't pop up, as in step 4 In steps 4 and 8, the item edit box will appear if one attempts to receive a supplemental issue, but the item will refuse to save, giving an erroneous "missing required field" message. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6