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

[Bug 20203] New: Add info about contributing to koha-community.org/documentation/
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '24

04 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20203 Bug ID: 20203 Summary: Add info about contributing to koha-community.org/documentation/ Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Websites, Mailing Lists, etc Assignee: wizzyrea(a)gmail.com Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org It might be nice if the page at https://koha-community.org/documentation/ said something about how to contribute to the documentation, or linked to such info published elsewhere. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 23015] New: Create a "GetPickupLocation" endpoint for the ILS-DI Service
by bugzilla-daemon＠bugs.koha-community.org 04 Apr '24

04 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23015 Bug ID: 23015 Summary: Create a "GetPickupLocation" endpoint for the ILS-DI Service Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- That endpoint may take 2 parameters: - a borrowernumber - and a biblio or item number And it would return a list of available pickup location given a user and a biblio or item. On success would return the following example : <?xml version="1.0" encoding="UTF-8"?> <pickup_locations> <pickup_location> <pickup_location_label>First library</pickup_location_label> <pickup_location_id>1</pickup_location_id> </pickup_location> <pickup_location> <pickup_location_label>Second library</pickup_location_label> <pickup_location_id>2</pickup_location_id> </pickup_location> </pickup_locations> On error : - PatronNotFound in case borrowernumber is not found - RecordNotFound in case Biblio doesn't exist - ItemNotFound in case item doesn't exist -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 23

[Bug 23943] New: koha-run-backups --days is misleading
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23943 Bug ID: 23943 Summary: koha-run-backups --days is misleading Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Packaging Assignee: koha-bugs(a)lists.koha-community.org Reporter: magnus(a)libriotech.no QA Contact: testopia(a)bugs.koha-community.org CC: mirko(a)abunchofthings.net The documentation for the --days option to koha-run-backups says: --days: the number of days to keep backups around for (default: 2) Sometimes I do the following: 1. Rename a backupfile, e.g. from instance-2019-10-22.sql.gz to instance-2019-10-22-1230.sql.gz 2. Run koha-dump to create a new instance-2019-10-22.sql.gz This reveals that --days does not really care about days at all, just the number of files in the backup dir. This means that if I have adjusted the cronjob to keep backups for 14 days, after the next time it runs, I actually have backups for 13 days. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 23656] New: Add search box to top of page on cataloguing/editor.pl
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '24

01 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23656 Bug ID: 23656 Summary: Add search box to top of page on cataloguing/editor.pl Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: barbara.johnson(a)bedfordtx.gov QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the Advanced Cataloging editor, both addbooks.pl and additem.pl have a cataloging search box at the top of the page. It would be great to add one to cataloguing/editor.pl so that users don’t have to click away from the page if they need to perform a new search. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 31

[Bug 24422] New: Advanced search shelving locations are restricted to the same restrictions as cataloging
by bugzilla-daemon＠bugs.koha-community.org 01 Apr '24

01 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24422 Bug ID: 24422 Summary: Advanced search shelving locations are restricted to the same restrictions as cataloging Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Shelving locations that are setup in the LOC category allow libraries to include a location or not, based on whether they use the location in cataloging. This makes sense. What cataloger wants to sift through a bunch of shelving locations they are never going to use? However, if you allow advanced searching to use shelving locations as a limiter (AdvancedSearchTypes), if you are on the staff client in advance search, you have the same locations restricted imposed on search.pl, which is not what one would want. Staff will never be able to limit to a shelving location used at another library. I don't think that the library limitations in LOC should apply to search.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 18053] New: Allow to manually link items to serial issues
by bugzilla-daemon＠bugs.koha-community.org 29 Mar '24

29 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18053 Bug ID: 18053 Summary: Allow to manually link items to serial issues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com In some cases, when items for a subscription have been (accidentally) added outside the subscriptions module, it would be nice if it was possible to link the items to their corresponding serial issues manually. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 2

[Bug 21087] New: Patron's password is hashed twice when the object is saved
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '24

28 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21087 Bug ID: 21087 Summary: Patron's password is hashed twice when the object is saved Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org Depends on: 20287 When a patron is edited (reading the code at least using patron batch modification), the password is lost. Prior to bug 20287 ModMember took the $hash of modification, and '****' was a trick to not update the password (when coming from memberentry). The same trick has been reused for the move of ModMember to Koha::Patron->store, but then the following code will modify the password of the patron: my $password = 'password'; $patron->password($password)->store; $patron->surname('xxx')->store; => User is not longer able to login with 'password' Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20287 [Bug 20287] Move AddMember and ModMember to Koha::Patron -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 28

[Bug 18213] New: Add language facets to Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '24

27 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18213 Bug ID: 18213 Summary: Add language facets to Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 48

[Bug 23352] New: Set serial issue default values when creating a subscription in serials/subscription-add.pl
by bugzilla-daemon＠bugs.koha-community.org 27 Mar '24

27 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23352 Bug ID: 23352 Summary: Set serial issue default values when creating a subscription in serials/subscription-add.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: alexbuckley(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com To speed up the process of receiving serial issues libraries should be able to set default serial issue values for the subscription when they create the subscription. Currently, it is possible for librarians to set default values for 952 MARC fields in the bibliographic frameworks but that would set blanket default values for all subscriptions. As different subscriptions are likely to have different 952 MARC field values it would be useful for libraries to set default values which are only applied to the serial issue items created for a specific subscription. The default values they should be able to set when creating the subscription (in serials/subscription-add.pl) are: * Collection code * Subscription full cost Then when a serial issue is received from the two above values the following 952 subfields will be pre-populated: * 952$8 Collection Code - Pulled in from default set in serials/subscription-add.pl * 952$b Current location - Set to the currently logged in library branch * 952$d Date acquired - This will be pre-populated upon page load rather than when you click on the text input field as is the current behaviour * 952$h Serial Enumeration/ chronology - This will be pre-populated from the subscription numbering pattern * 952$v Cost, replacement price - This will be pre-populated from the calculation of the subscription full cost/number of issues This would only leave the librarian to input 952$p (barcode) and 952$a (permanent location), speeding up the cataloguing process of receiving serials. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 82

[Bug 16654] New: The output from reports/cat_issues_top.pl is not proper CSV
by bugzilla-daemon＠bugs.koha-community.org 25 Mar '24

25 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16654 Bug ID: 16654 Summary: The output from reports/cat_issues_top.pl is not proper CSV Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org The output from reports/cat_issues_top.pl is *NOT* csv; it is DSV (delimiter separated values) with the option of using commas as delimiters... and the delimiters aren't properly escaped. To illustrate the point 1/ Check out an item whose title contains a comma. 2/ Go to Home [34m~@� Reports [34m~@� Most-circulated items 3/ Select a date range containing today's date 4/ Select the "To a file" radio button, and use comma (,) as the delimiter. 5/ Click Submit Open the file in the spreadsheet program of your choice. Note that the title containing the comma spans two columns, because it was not properly quoted. If the report is going to use CSV as a file extension, it should be exported using Text::CSV_XS, which properly handles CSV export. -- You are receiving this mail because: You are watching all bug changes.

1 3