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

[Bug 22160] New: OMNIBUS: Transfers enhancements
by bugzilla-daemon＠bugs.koha-community.org 27 Jan '25

27 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22160 Bug ID: 22160 Summary: OMNIBUS: Transfers enhancements 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: josef.moravec(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 88

[Bug 35720] New: Add option to require confirmation of hold override when placing hold
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35720 Bug ID: 35720 Summary: Add option to require confirmation of hold override when placing hold Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: lisette.scheer(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com It would be helpful to some libraries to be able to require staff to confirm when they're overriding policy to place a hold. This would help highlight that they are overriding, not just placing a normal hold. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 33137] New: Make sure columns on transactions and 'pay fines' tab are matching up
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33137 Bug ID: 33137 Summary: Make sure columns on transactions and 'pay fines' tab are matching up Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial 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 The information visible on the transactions and 'pay fines' tabs is drifting apart with different columns visible on each. It would be nice to make them consistent again. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 35220] New: Merging patrons can cause lock timeouts
by bugzilla-daemon＠bugs.koha-community.org 24 Jan '25

24 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35220 Bug ID: 35220 Summary: Merging patrons can cause lock timeouts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Patrons 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, kyle.m.hall(a)gmail.com The code to merge patrons uses a transaction to update all of the related patron tables. On systems with a long history (i.e. a big statistics table) this operation can take 30 seconds or more, which begins to cause issues writing to the tables. We need to find a way to speed this up, or to defer the merging of patrons. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 30088] New: Forgotten password
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30088 Bug ID: 30088 Summary: Forgotten password Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Two thoughts: Is there a reason patrons have to be presented with two fields, one for login or one for e-mail address? The prompt says to enter one or the other. Since there is the possibility for more than one account to have the same e-mail address, should we only ask for the username? The second thought is, should Koha e-mail the account user if a request has been made to reset the password? This seems to be common practice these days. -- You are receiving this mail because: You are watching all bug changes.

1 28

[Bug 33654] New: Add more permissions to Item Group Cataloging
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=33654 Bug ID: 33654 Summary: Add more permissions to Item Group Cataloging 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: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, there is only one permission attached to Item Groups: Permission Create, update, and delete item groups, add or remove items from an item group (manage_item_groups) It would be nice to make this functionality more granular within the permissions in Koha. For some catalogers, the permission to add an item to an item group is all they should be able to do in this workflow, but currently, once this overarching item group permission is granted, they can also create groups. Adding permission for only adding items to a group separate from creating groups would be the ultimate goal in this request. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 30070] New: There are performance issues with edifactmsgs when you have a large number of messages
by bugzilla-daemon＠bugs.koha-community.org 23 Jan '25

23 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=30070 Bug ID: 30070 Summary: There are performance issues with edifactmsgs when you have a large number of messages Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Staff Client 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 The edifact messages table can grow to a very large size over time, and the page to display them has issues with this growth as it always loads all messages. We should switch this to an ajax driven datatable. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 136

[Bug 29858] New: Item.pm "Use of uninitialized value" warn when $field var is NULL
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '25

20 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29858 Bug ID: 29858 Summary: Item.pm "Use of uninitialized value" warn when $field var is NULL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: OPAC Assignee: stalkernoid(a)gmail.com Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 6

[Bug 31800] New: REST API: POST endpoint for Biblios
by bugzilla-daemon＠bugs.koha-community.org 20 Jan '25

20 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=31800 Bug ID: 31800 Summary: REST API: POST endpoint for Biblios Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com CC: tomascohen(a)gmail.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 38

[Bug 22013] New: Command line staging: Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202.
by bugzilla-daemon＠bugs.koha-community.org 19 Jan '25

19 Jan '25

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22013 Bug ID: 22013 Summary: Command line staging: Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: MARC Authority data support Assignee: koha-bugs(a)lists.koha-community.org Reporter: simon.hohl(a)dainst.org QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- Created attachment 83307 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=83307&action=ed… MARC File containing geographical authority data When using stage_file.pl to import authority data (see attachment), I get the warning: Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in regexp compilation at /usr/share/perl5/MARC/Record.pm line 206. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 207. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. Use of uninitialized value $tag in hash element at /usr/share/perl5/MARC/Record.pm line 202. That's 28 warnings for 31 records, but I am unable to decide which cause the warning and which do not. Anybody able to find out why a pattern? Cheers -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13