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

[Bug 22614] New: Request migration from one backend to another should not create new request
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22614 Bug ID: 22614 Summary: Request migration from one backend to another should not create new request Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: ILL Assignee: koha-bugs(a)lists.koha-community.org Reporter: andrew.isherwood(a)ptfs-europe.com Target Milestone: --- Currently, when requests are migrated from one backend to another, a new request is created containing the attributes of the existing one but with the backend set to the migration destination backend and the metadata is derived from the migration destination backend. The existing request is then marked as reverted and a record is made of where the request was migrated to. The downside of this approach is that two requests now exist in the system, whereas in actual fact, it's still the same request. This can be problematic for statistics etc. This bug proposes that request migration should preserve the original request and, instead, change its backend and replace the metadata from the original backend to that of the migration destination backend. Also, we should log where the request has been migrated from and to. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 25173] New: Create list of parameters to choose from via a query
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25173 Bug ID: 25173 Summary: Create list of parameters to choose from via a query Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Currently, you can use something like <<Library|branches>> to have a parameter prepopulate with choices from predetermined tables (in this case, from branches), or you can point to a authorised list. But, if you want to prepopulate from other tables, you are out of luck. I would love to be able to do something like <<List|(SELECT shelfname FROM virtualshelves)>> and have it prepopulate with the results. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 23531] New: ILS-DI doesn't implement needed_before_date and pickup_expiry_date parameters.
by bugzilla-daemon＠bugs.koha-community.org 21 Oct '21

21 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23531 Bug ID: 23531 Summary: ILS-DI doesn't implement needed_before_date and pickup_expiry_date parameters. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal 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 tried to send the following request : GET /cgi-bin/koha/ilsdi.pl?service=HoldItem&patron_id=196&bib_id=96629&item_id=112194&needed_before_date=2020-08-18&pickup_expiry_date=2020-10-18&pickup_location=BDY the reservation which is placed doesn't take the "needed_before_date" and pickup_expiry_date" parameter, although those are documented. Arthur -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 46

[Bug 22061] New: Add a /public namespace that can be switched on/off
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '21

19 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22061 Bug ID: 22061 Summary: Add a /public namespace that can be switched on/off 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: tomascohen(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 43

[Bug 25707] New: Mappings update in bug 11529 causes data loss
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '21

19 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25707 Bug ID: 25707 Summary: Mappings update in bug 11529 causes data loss Change sponsored?: --- Product: Koha Version: master 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: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Turns out the database update for this change causes unexpected changes to the "Koha to MARC mapping" (via the MARC frameworks) -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 18501] New: Automatic refunds need protection from failure
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '21

19 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18501 Bug ID: 18501 Summary: Automatic refunds need protection from failure Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com I am told that the auto refund feature can fail if the status is edited in the item edit screen. There should be some protection in place to keep this from failing so easily and quietly. Possible solutions might be: 1) Prevent status from being edited if a fee has been charged for that item. 2) A warning and confirmation of action when the status is being edited and there is a fee involved. 3) An authorized override for such a change. 4) A note in the patron account lines indicating status was change and an auto refund will not be possible. 5) The ability to auto refund, even after the status has been altered. I am marking this as a bug, because I cannot see how the current behavior could be a desired function. Failure is not an option. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 138

[Bug 17328] New: Koha fixes for Mysql 5.7
by bugzilla-daemon＠bugs.koha-community.org 19 Oct '21

19 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=17328 Bug ID: 17328 Summary: Koha fixes for Mysql 5.7 Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: MARC Bibliographic record staging/import Assignee: gmcharlt(a)gmail.com Reporter: philippe.blouin(a)inlibro.com QA Contact: testopia(a)bugs.koha-community.org I'm accruing many little issues. while running the code. I'll put the patches in, at least to document them. If the powers-that-be decide to fix in differently, all the same to me. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 18191] New: REST API: Add endpoint to list valid pickup locations
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '21

18 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18191 Bug ID: 18191 Summary: REST API: Add endpoint to list valid pickup locations Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Web services Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org Bug 7534, Bug 7614 and Bug 18072 let us limit the choices of pickup location when placing a hold. Add a REST API endpoint that uses this functionality. GET /biblios/{biblionumber}/pickuplocations GET /item/{itemnumber}/pickuplocations Returns an array of library-objects that represent a set of libraries that can be used as pickup locations for hold of the given biblio/item. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 14

[Bug 23449] New: Get available pickup locations from REST API
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '21

18 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23449 Bug ID: 23449 Summary: Get available pickup locations from REST API Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: REST api Assignee: koha-bugs(a)lists.koha-community.org Reporter: lari.taskula(a)hypernova.fi We need a way to tell if we can use library as a hold pickup location via rest api. Patches attached in this Bug number aim to extend Bug 16826. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 21997] New: SIP patron information requests can lock patron out of account
by bugzilla-daemon＠bugs.koha-community.org 18 Oct '21

18 Oct '21

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21997 Bug ID: 21997 Summary: SIP patron information requests can lock patron out of account Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Many SIP services send an empty password field (AD). Even if allow_empty_passwords is enabled for the given SIP account, this empty password is run though Koha's password checker which increments the number of login attempts for a patron. Thus repeated patron information requests can lock a patron out! Empty password fields in SIP should not call for a password check if allow_empty_passwords is enabled. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 22