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

[Bug 26166] New: Patron verification through SMS one time code
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '26

14 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26166 Bug ID: 26166 Summary: Patron verification through SMS one time code 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Often we have a patron that will call to do something with their account and cannot because they don't have their card on them or they have lost their card. It would be FANTASTIC if there was a button on the account, for those that have SMS messaging setup, to send them a one-time code that they could read back to us to verify that it is them. I could also see this as a validation process for setting up SMS messaging on the patron (OPAC) side. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 38703] New: Merged patrons should keep the most recent lastseen date
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '26

14 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38703 Bug ID: 38703 Summary: Merged patrons should keep the most recent lastseen date Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: emily.lamancusa(a)montgomerycountymd.gov QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Let's say a patron has duplicate accounts, account #1 and account #2, with the following data: lastseen Account #1 2024-05-01 Account #2 2024-11-15 Let's say a staff member merges the duplicate accounts and chooses to keep account #1 based on whatever criteria they use to decide. Currently, account #1 would keep its lastseen date of 2024-05-01. Since the lastseen date may be used to determine account retention and automatic renewal, it would make more sense to keep the more recent lastseen date in this case, especially for patrons who use the library relatively infrequently. (As an extreme example, I recently found a patron account in our system that has a lastseen date from 5 years ago yet also still has current checkouts from earlier this year!) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 38301] New: Add option to show holding table filters bu default
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '26

14 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38301 Bug ID: 38301 Summary: Add option to show holding table filters bu default Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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 After Bug 33568 one must click 'Show filters' after the holdings table loads to see the various filters. I would be nice if there was an option to have those filters expanded by default. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 11

[Bug 23010] New: If an item is checked out or in transit it should not be able to be marked withdrawn
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '26

14 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23010 Bug ID: 23010 Summary: If an item is checked out or in transit it should not be able to be marked withdrawn Change sponsored?: --- Product: Koha Version: 18.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: jzairo(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Currently an item can be marked withdrawn if it is checked out to a patron or in transit from one branch to another. This causes confusion for staff checking an item back in or receiving the transfer. If an item is checked out or in transit it should not be able to be marked withdrawn. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 107

[Bug 37569] New: Serials without history cannot be edited
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '26

14 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37569 Bug ID: 37569 Summary: Serials without history cannot be edited Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: baptiste.wojtkowski(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Serials cannot be edited if there is no history associated to the serial. Fetching a subscription matching a given serialnumber results in an hashref containing two fields named serial number. One of them is undef and is used by the form and is therefore not submitted at the end. This is not supposed to happen since creating an exemplary automatically creates a new exemplary, but if serials are created through DB, they are not editable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 14

[Bug 38600] New: NoticeBCC needs granularity
by bugzilla-daemon＠bugs.koha-community.org 14 Apr '26

14 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38600 Bug ID: 38600 Summary: NoticeBCC needs granularity Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: hebah(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com As Koha adds more notices for new functionality, libraries should be able to customize what notices to have delivered as bcc notices so that they are receiving only the pertinent ones. When the system preference was only overdues, it made sense for it to be all or nothing. Now, NoticeBCC includes notices that libraries may not want to receive - like CART and LIST notices, for example. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 36656] New: Add ability to see (limited) error logs from within the Koha inteface
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '26

13 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36656 Bug ID: 36656 Summary: Add ability to see (limited) error logs from within the Koha inteface Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff interface Assignee: koha-bugs(a)lists.koha-community.org Reporter: wizzyrea(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com We should expose the error messages we collect in the plack-*-error.log and plack-error.log to superlibrarians by flag in the Koha Conf or by syspref enabling. This could help librarians solve their own problems with items that don't have item types or identifying bad dates. Nagios does this fairly well, if an example is required. Aspen Discovery as well. It might mean we tidy up our error handling, but I think the trade is worth it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 37334] New: Cannot order/sort holdings table by status
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '26

13 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=37334 Bug ID: 37334 Summary: Cannot order/sort holdings table by status Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation 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 Currently one is not able to sort the holdings table by status. IN catalogue_detail.inc I see the following: 451 data: "me.lost_status", 452 className: "status", 453 searchable: false, // FIXME We are losing the ability to search on the status 454 orderable: false, 455 render: function (data, type, row, meta) { Setting orderable to true brings back the icons, but I am assuming since this wasn't fixed initially that it is not trivial. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 388

[Bug 36920] New: Greater/less than search option on item search page to Barcode-drop-down menu
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '26

13 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36920 Bug ID: 36920 Summary: Greater/less than search option on item search page to Barcode-drop-down menu Change sponsored?: --- Product: Koha Version: Main Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: tuomas.kunttu(a)kouvola.fi QA Contact: testopia(a)bugs.koha-community.org Created attachment 167017 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=167017&action=e… Barcode search section on item search page In the search section on the item search page, where the drop-down menu has a barcode search by default (see attachment image), it would be useful to have the option to do greater/less than searches as well. Now there are only is/is not options. When searching publication year in this menu, this functionality would be useful. This way you could search for works that have been published before/after a certain year. In addition, custom search fields can be added to the menu. These can be, for example, acquisition date or lastseen date. Also with these fields greater/less than searches would be useful. In fields containing letters, greater/less than searches are not necessarily very useful, but not harmful either. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 29

[Bug 28528] New: bulkmarcimport delete option doesn't delete biblio_metadata
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '26

13 Apr '26

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28528 Bug ID: 28528 Summary: bulkmarcimport delete option doesn't delete biblio_metadata Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz When using bulkmarcimport with the -d switch should not only delete biblio, biblioitems and items, but also biblio_metadata. I haven't checked if a FK takes care of the data, but if it does, we should still also reset the AUTO_INCREMENT: https://git.koha-community.org/Koha-community/Koha/src/branch/master/misc/m… -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 20