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

[Bug 26820] New: "Important" flag enforced only at subfield level
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26820 Bug ID: 26820 Summary: "Important" flag enforced only at subfield level Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 To recreate: - edit your framework so the 001 is set to Important at the tag level but not at the subfield level - create a new record in that framework, note that the 001 is not marked Important - edit framework, set it to Important on the @ subfield in the 001 - reload new record, see the 001 is now marked Important We're not doing anything with Important at the tag level, so let's not ask for it. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 34924] New: Add ability to send 'final auto renewal notice'
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34924 Bug ID: 34924 Summary: Add ability to send 'final auto renewal notice' 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com See bugs 19014 and 31427 - users can end up receiving an auto renewal failure immediately after a success. 31427 updates to send this notice at the end of a circ period, but then the user doesn't know the book won't renew until it is nearly due We should have a way to mark that an issue has reached the end of the allowed renewals and warn the user that the item won't be renewed when it becomes due. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 50

[Bug 35017] New: If creating items when ordering, an alert should appear if the item type is not filled out
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35017 Bug ID: 35017 Summary: If creating items when ordering, an alert should appear if the item type is not filled out Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Step to reproduce 1. Create a basket 2. Choose to create items upon ordering 3. Use either a new file or a staged file 4. When adding records to the basket, the required fields seem to only be fund and price. Fill out the required fields. 5. Close the basket 6. Go to receive from that vendor, - add invoice number, then see a 500 error instead of being able to receive anything from that vendor. When a basket is created in Acquisitions with the "create items on ordering", but the item type is not filled in, a 500 error will appear when attempting to receive. Although the item type is not required, thus allowing a user to go through the whole process only to receive a 500 error when receiving. This error will appear regardless of what the user is receiving if an order within that vendor has an order without an item type. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 36902] New: Blank year fields should not be indexed.
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36902 Bug ID: 36902 Summary: Blank year fields should not be indexed. 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: andreas.jonsson(a)kreablo.se The comment says 'Only accept years containing digits and "u"' but proceeds to also accept fields with blanks: # Only accept years containing digits and "u" push @{$default_options->{value_callbacks}}, sub { my ($value) = @_; # Replace "u" with "0" for sorting return map { s/[u\s]/0/gr } ( $value =~ /[0-9u\s]{4}/g ); }; If the field contains blanks it is either because it is invalid or because the year is missing, so the field should not be indexed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 36483] New: Calling $object->to_api directly should be avoided
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36483 Bug ID: 36483 Summary: Calling $object->to_api directly should be avoided Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: tomascohen(a)gmail.com CC: tomascohen(a)gmail.com Highlighted on bug 36482, calling $object->to_api directly on our API controllers makes several parameters ineffective. Notably, x-koha-embed. We should call instead: ```perl $c->objects->to_api( $object ) ``` A follow-up bug replacing all existing calls should've been filled but we somehow missed it. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 32183] New: Purchase suggestions for logged in patron - doesn't display suggestions made by everyone
by bugzilla-daemon＠bugs.koha-community.org 16 Oct '24

16 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32183 Bug ID: 32183 Summary: Purchase suggestions for logged in patron - doesn't display suggestions made by everyone Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: david(a)davidnind.com QA Contact: testopia(a)bugs.koha-community.org If OPACViewOthersSuggestions is set to 'Show', for a logged in patron they can only see their own suggestions - not all suggestions as expected. This is working correctly on 22.05.x, but is not working on the current master. To replicate on the current master: 1. Set AnonSuggestions to 'Allow'. 2. Set OPACViewOthersSuggestions to 'Show'. 3. On the OPAC, when not logged in, add a purchase suggestion. 4. On the OPAC, log in as a patron and make a purchase suggestion. 5. Change OPACViewOthersSuggestions to "Don't show". 6. Under Your account > Purchase suggestions, you can only see your own suggestions (as expected). 6. Change OPACViewOthersSuggestions set to "Show". 7. Under Your account > Purchase suggestions, after the "Search for" input field there is a dropdown list with options: 7.1 Select "Suggested by me" and press "Go": the patron's own suggestion(s) are correctly shown. 7.2 Select "Suggested by anyone" and press 'Go': it DOESN'T show all suggestions. Identified when testing bug 20207. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 32256] New: self-checkout batch mode
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=32256 Bug ID: 32256 Summary: self-checkout batch mode Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: ddaghita(a)mckinneytexas.org QA Contact: testopia(a)bugs.koha-community.org Please enable batch checkouts on self-checkout machines using koha self-checkout module (/cgi-bin/koha/sco/sco-main.pl?). We have patrons place one book at time on the RFID pad to self-checkout. We would ideally like patrons to stack five or more materials at a time so they checkout more efficiently all at once as it does on the koha staff side. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 105

[Bug 35465] New: Ability to select multiple funds for a single order
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=35465 Bug ID: 35465 Summary: Ability to select multiple funds for a single order Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: cguenther(a)coloradocollege.edu QA Contact: testopia(a)bugs.koha-community.org Allow multiple funds to be selected for tracking payment on a single order. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 7

[Bug 36319] New: Splitting a single item between multiple funds
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36319 Bug ID: 36319 Summary: Splitting a single item between multiple funds Change sponsored?: --- Product: Koha Version: 23.05 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: liberm(a)uhv.edu QA Contact: testopia(a)bugs.koha-community.org Periodically we run into instances where we need to split the cost of a book or database between two funds. Currently this is not possible in Koha and so we add and subtract money from funds to get the money to match, but it doesn't allow us to track the actuality of how the money was spent for reporting purposes. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 25375] New: Elasticsearch: Limit on available items does not work
by bugzilla-daemon＠bugs.koha-community.org 15 Oct '24

15 Oct '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25375 Bug ID: 25375 Summary: Elasticsearch: Limit on available items does not work Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Searching - Elasticsearch Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com Currently what this limit does is a filter on onloan:false This means that: - Any biblio with at least one checked out item will be hidden from the results, even if it has other available items - A biblio whose items are all lost, damaged, withdrawn or "notforloan" will not be hidden, but the results will show "X items, none available" -- You are receiving this mail because: You are watching all bug changes.

1 70