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

[Bug 25366] New: MARC import does not have duplicate record search option for online items
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25366 Bug ID: 25366 Summary: MARC import does not have duplicate record search option for online items Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: jaki.frisina(a)leblibrary.com QA Contact: testopia(a)bugs.koha-community.org When importing Kanopy records, I cannot search and replace duplicate records because Kanopy records do not have an ISBN or ISSN, which are the only items you can match on when searching for duplicates. I do not know if there are other online items that are affected by this. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 25401] New: Backup/Restore Functions
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25401 Bug ID: 25401 Summary: Backup/Restore Functions 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: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com I would love to see backup and restore exports/imports for preferences and tables. For example, if I am monkeying with the transport cost matrix, I would like to export it before I play with it, and have the ability to import it if needed. Or if i am working on jQuery, CSS, circulation rules, or any other settings in Koha, it would be great to be able to export on the fly and restore when needed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 25474] New: Component Description for 'Templates'
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25474 Bug ID: 25474 Summary: Component Description for 'Templates' Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: bugs.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: timothy_alexis.vass(a)ub.lu.se QA Contact: testopia(a)bugs.koha-community.org Bugs / errors in the the koha templates Should be: Bugs / errors in the Koha templates -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 25495] New: members-home.pl should allow search for exact borrowernumber
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25495 Bug ID: 25495 Summary: members-home.pl should allow search for exact borrowernumber 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: andrew(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When searching by borrowernumber in the patrons module, the only search type options are "contains" and "starts with," both of which can be unhelpful when searching by borrowernumber, especially when trying to find a relatively low-numbered patron in a large system. It'd be great to be able to perform an exact match search so "10" wouldn't find 100, 101, 1001, etc. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 25533] New: Perl "not numeric" warning on the "Holds" page
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25533 Bug ID: 25533 Summary: Perl "not numeric" warning on the "Holds" page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Hold requests Assignee: slavashishkin(a)gmail.com Reporter: stalkernoid(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, nugged(a)gmail.com Perl warning on the intranet "Holds" page (/cgi-bin/koha/reserve/request.pl): Argument "" isn't numeric in numeric gt (>) at .../C4/Reserves.pm line 2233. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 25652] New: Holds Daily is not looking at Item Type when Not Allowing Holds
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25652 Bug ID: 25652 Summary: Holds Daily is not looking at Item Type when Not Allowing Holds Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 If a library has a rule that allows 5 holds daily on DVDs and 50 holds daily on the BOOK rule, Koha will count the first 5 holds regardless of item type and not allow any more of that item type (DVD) for a hold, but will allow more BOOK holds. 423 my $today_holds = Koha::Holds->search({ 424 borrowernumber => $borrowernumber, 425 reservedate => dt_from_string->date 426 }); Koha should be looking at Item Type when determining whether a hold can be placed in this today_holds search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 8

[Bug 25688] New: 'All libraries' terminology used on first page of circulation rules is confusing
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25688 Bug ID: 25688 Summary: 'All libraries' terminology used on first page of circulation rules is confusing Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement 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 CC: andrew(a)bywatersolutions.com Our circulation rules page has undergone some terminology changes over the years, but at the moment, it seems quite confusing as discussions on some bugs (example: 25643) have shown. We say "default for all libraries" but actually, it's just "default for each libary" as the default rules page is used, when no library specific rule exists. Counts like 'number of holds' or 'number of checkouts' will not count for 'all libraries' but only for the 'individual library'. We should look for a way to make this more obvious in our wording. Would "default for a library" or "default for each library" work in English? -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 25689] New: Move 'Manage OPAC problem reports' permission into tools
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25689 Bug ID: 25689 Summary: Move 'Manage OPAC problem reports' permission into tools 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: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Depends on: 25627 There is no reason for this permission to be a module level permission - it has no sub permission and as such currently is not set up quite right (compare to others like editauthorities). I propose that we move it to the tools permissions after bug 25627 has been resolved. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25627 [Bug 25627] Move OPAC problem reports from administration to tools -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 25704] New: With ICU chains on, searching by callnumbers does not produce accurate results
by bugzilla-daemon＠bugs.koha-community.org 01 Jan '24

01 Jan '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25704 Bug ID: 25704 Summary: With ICU chains on, searching by callnumbers does not produce accurate results Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Zebra Assignee: koha-bugs(a)lists.koha-community.org Reporter: kelly(a)bywatersolutions.com This seems to be a change in functionality around the 19.05.09 version, with ICU chains turned on, the ability to search using the "Call Number" option from the staff client or the OPAC search, is not working accurately. It will pull results but not all good results and certainly not find all the results for that particular search. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 12

[Bug 24577] New: API schema merging breaks with older versions of JSON module
by bugzilla-daemon＠bugs.koha-community.org 31 Dec '23

31 Dec '23

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24577 Bug ID: 24577 Summary: API schema merging breaks with older versions of JSON module 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: andrew.isherwood(a)ptfs-europe.com I discovered this while deploying a plugin that defines an API route. If the installation is using a version of the JSON module < 2.90, schema merging doesn't work correctly, these are the sort of errors that were being generated during validation of the merged schema: { 'path' => '/paths/~1contrib~1ill_availability_unpaywall~1ill_availability_search_unpaywall/get/parameters/0', 'message' => 'oneOf failed: oneOf failed: Properties not allowed: type. oneOf failed: (Not in enum list: header.. Expected boolean - got JSON::XS::Boolean.) (Not in enum list: formData.. Expected boolean - got JSON::XS::Boolean.) Expected boolean - got JSON::XS::Boolean. (Expected boolean - got JSON::XS::Boolean.. Not in enum list: path.) Properties not allowed: name, required, type, description, in.' } Pretty nonsensical and a nightmare to try and get to the bottom of. I was seeing this using JSON 2.61. I believe the change that was implemented in 2.90 that we're dependent on, is the top one listed here: https://metacpan.org/changes/release/MAKAMAKA/JSON-2.90 Koha is currently specifying 2.07 as the required version. I'm wondering if it is worth moving this to 2.90. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4