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

[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 25990] New: `WhenLostChargeReplacementFee` and `WhenLostForgiveFine` preferences should be moved into circulation rules to be consistent with `RefundLostOnReturn` rules
by bugzilla-daemon＠bugs.koha-community.org 03 Apr '24

03 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25990 Bug ID: 25990 Summary: `WhenLostChargeReplacementFee` and `WhenLostForgiveFine` preferences should be moved into circulation rules to be consistent with `RefundLostOnReturn` rules 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: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Currently there is an inconsistency with the level at which `WhenLostChargeReplacementFee` and `WhenLostForgiveFine` can be set when compared to the complimentary `RefundLostOnReturn` rule. For consortial installations, all these rules should apply at the same level, be that system or branch level.. I propose to move the two 'system' level preferences into 'branch' level by migrating them into the circulation rules area. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 9

[Bug 25439] New: [Omnibus] Prepare Koha to ElasticSearch 7 - ES7
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25439 Bug ID: 25439 Summary: [Omnibus] Prepare Koha to ElasticSearch 7 - ES7 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: victor(a)tuxayo.net ES6 will be end of life when the version 8 will come out[1]. there is no alpha of version 8 so we have at least half a year[2] before that happens. [1] https://www.elastic.co/support/eol [2] https://discuss.elastic.co/t/elasticsearch-8-release-date/202759/2 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 26274] New: Expose cash register cashup summaries via an API route.
by bugzilla-daemon＠bugs.koha-community.org 02 Apr '24

02 Apr '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26274 Bug ID: 26274 Summary: Expose cash register cashup summaries via an API route. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST API Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com Depends on: 26172 Blocks: 26272, 26273 It would be useful to expose cashup summaries via an API endpoint to allow for displaying this data in various area's around Koha on demand. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26172 [Bug 26172] Add a cashup summary view https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26272 [Bug 26272] Allow cashup summaries to be displayed from the library summary page https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=26273 [Bug 26273] Expose cashup summary historyfor a cash register -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 49

[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 28854] New: [ALTERNATIVE] Add ability to create bundles of items
by bugzilla-daemon＠bugs.koha-community.org 28 Mar '24

28 Mar '24

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28854 Bug ID: 28854 Summary: [ALTERNATIVE] Add ability to create bundles of items Change sponsored?: Sponsored Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: andrew(a)bywatersolutions.com, bwsdonna(a)gmail.com, cecile.joyet(a)biblibre.com, dcook(a)prosentient.com.au, e.betemps(a)gmail.com, fiona.borthwick(a)ptfs-europe.com, george(a)nekls.org, jonathan.field(a)ptfs-europe.com, julian.maurice(a)biblibre.com, m.de.rooy(a)rijksmuseum.nl, martin.renvoize(a)ptfs-europe.com, severine.queune(a)bulac.fr, testopia(a)bugs.koha-community.org, tomascohen(a)gmail.com +++ This bug was initially created as a clone of Bug #24023 +++ This bug started as a rebase of bug 24023, but as time went on and I tested that bug I found bits of it lacking and felt enough time had passed that we could try a more modern approach. To keep the work distinct, I created this bug to encompass my alternative approach. This new feature will add the ability to bundle existing items together into loanable sets linked to a new collection bibliographic record. Items will be withdrawn from their original bib and take on the circulation rules of the collection record. We update the display for items attached to a collection to show what collection they are linked to and we added the ability to expand a collection item to list it's content items. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 611

[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