November 2019 - Koha-bugs - lists.koha-community.org

[Bug 18330] New: REST API: Date-time handling
by bugzilla-daemon＠bugs.koha-community.org 29 May '20

29 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18330 Bug ID: 18330 Summary: REST API: Date-time handling 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 Swagger2 wants dates and date-times as defined in RFC3339, https://xml2rfc.tools.ietf.org/public/rfc/html/rfc3339.html#anchor14 Make sure each object property has a format date or date-time defined where needed. We should include information on time zone and use an appropriate separator "T" between date and time, e.g.: 2017-03-24T14:00:00+02:00 2017-03-24T12:00:00Z -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30

[Bug 18674] New: Show timezone for Perl and MySQL on the About Koha page
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18674 Bug ID: 18674 Summary: Show timezone for Perl and MySQL on the About Koha page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: About Assignee: nengard(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org With the pushing of Bug 18299, we no longer have a quick way of checking the timezone of the Perl and MySQL connection. We should add some code to the About Koha page to show this info. -- You are receiving this mail because: You are watching all bug changes.

1 33

[Bug 19197] New: Lower case "or" results in broken ElasticSearch queries
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19197 Bug ID: 19197 Summary: Lower case "or" results in broken ElasticSearch queries 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: glasklas(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org In some places a literal "or" is used to build search queries which probably works with Zebra, but not with ElasticSearch. Replacing theses occurrences fixes the problem in those cases. This is just a band aid, not addressing the real issue which is (I guess) that a query abstraction interface is needed, and zebra-specific syntax should not be used directly in search queries, but this will at least solve this particular issue. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 16

[Bug 23322] New: Elasticsearch - Record matching fails when multiple keys exist
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23322 Bug ID: 23322 Summary: Elasticsearch - Record matching fails when multiple keys exist Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching - Elasticsearch Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com For a record with multipel matchpoints C4/Matcher.pm combines terms using 'or' however, ES expects 'OR' so the search fails To test: 0 - Set SearchEngine to ElasticSearch 1 - Import the example record (a version is included in sample data in devbox/testing docker so you can skip) 2 - Stage the attached example record 3 - Match using 'ISBN' rule 4 - No matches found -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 17

[Bug 22536] New: Display problem in Holds to Pull report
by bugzilla-daemon＠bugs.koha-community.org 28 May '20

28 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22536 Bug ID: 22536 Summary: Display problem in Holds to Pull report Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: david.roberts(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- Created attachment 86732 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=86732&action=ed… Screenshot In 18.11, the holds to pull screen displays in the table when an bibliographic record has more than one copy (see attached screenshot). This seems to be related to the template: </td> <td>[% reserveloo.itemcallnumber | html %]</td> <td>[% reserveloo.copyno | html %]</td> <td>[% reserveloo.enumchron | html %]</td> <td> Removing the html part of the line fixes the problem, but isn't a very secure long-term solution. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 17

[Bug 23223] New: Allow requested items to be checked out
by bugzilla-daemon＠bugs.koha-community.org 27 May '20

27 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23223 Bug ID: 23223 Summary: Allow requested items to be checked out Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: joy(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Target Milestone: --- Currently patrons are being blocked at self-check when they find an item on the shelf that they want and that item could also fill a hold. If the item is brought to the circ desk, the staff can override the 'hold' and check it out to the patron. The SIP2 devices do not allow for the override. We propose: 1) Add new SIP2 option or system preference ( or 2nd option to AllowItemsOnHoldCheckout ) to allow allow non-waiting items on hold to be checked out 2) Implement business logic in ILS::Transaction::Checkout or C4::Circulation 3) Add unit tests -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 23233] New: AllowItemsOnHoldCheckout is misnamed and does not indicate it is for SIP communication only
by bugzilla-daemon＠bugs.koha-community.org 27 May '20

27 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23233 Bug ID: 23233 Summary: AllowItemsOnHoldCheckout is misnamed and does not indicate it is for SIP communication only Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The system preference AllowItemsOnHoldCheckout only affects SIP based checkouts. I believe we should rename it AllowItemsOnHoldCheckoutSIP so it matches AllowItemsOnHoldCheckoutSCO. We should also update the description as well. As far as I know AllowItemsOnHoldCheckout has never affected anything except SIP traffic. That does not preclude the addition of another AllowItemsOnHoldCheckout syspref that would affect the staff interface, but that would be an enhancement and is outside the scope of this bug report. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 55

[Bug 21446] New: Permanent location should show with cart location - course-details.pl
by bugzilla-daemon＠bugs.koha-community.org 27 May '20

27 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21446 Bug ID: 21446 Summary: Permanent location should show with cart location - course-details.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Course reserves Assignee: koha-bugs(a)lists.koha-community.org Reporter: cbrannon(a)cdalibrary.org QA Contact: testopia(a)bugs.koha-community.org Continuing location fixes in modules. Adding permanent location in course-details.pl. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 27

[Bug 20211] New: Guarantor/Guarantee and PayPal development ideas
by bugzilla-daemon＠bugs.koha-community.org 26 May '20

26 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20211 Bug ID: 20211 Summary: Guarantor/Guarantee and PayPal development ideas Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jesse(a)bywatersolutions.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org 1. Add ability for a guarantor to see fines on their guarantee's accounts in the OPAC 2. Add ability for a guarantor to pay fines on their guarantee's accounts via PayPal in the OPAc (once #1 is complete) 3. Add ability to set a mimimum payment threshold when using PayPal - i.e. the "Make payment" button is not active until the "Amount to pay:" amount is greater than the amount specified in the threshold 4. Add the ability for the PayPal threshold to be set on a branch-by-branch basis (i.e. put it on the Circulation and fines rules rules page for the patron's home library) 5. Add the ability to turn off PayPal if a single branch doesn't want their patrons to use it (i.e. put something on a library's Circulation and fines rules rules that allows that library to prevent patrons with that library's home branch from using PayPal) -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 23779] New: Importing authority records should look for $1xx field matches
by bugzilla-daemon＠bugs.koha-community.org 25 May '20

25 May '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23779 Bug ID: 23779 Summary: Importing authority records should look for $1xx field matches Change sponsored?: --- Product: Koha Version: 19.05 Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Tools Assignee: koha-bugs(a)lists.koha-community.org Reporter: carnold(a)dgiinc.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 93886 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=93886&action=ed… Importing Auth Record Match options When you import authority records using Tools->Stage MARC records for import the options for checking duplicates are for ISBN , ISSN and KohaBiblio. However, those fields make no sense for checking auth duplications. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 9