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

[Bug 24134] New: improve 008 framework flexibility (autogenerate date)
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24134 Bug ID: 24134 Summary: improve 008 framework flexibility (autogenerate date) 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: philip.bertling(a)rbg.vic.gov.au QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When creating a framework for a form type other than book, it does not seem possible to autogenerate the date correctly. The 00-05 ‘date entered on file’ in the 008 field, can almost be auto-filled by using the code <<YYYY>><<MM>><<DD>>. However it doesn’t quite work because the 008 field expects a 6 digit date [YYMMDD] – this code inserts an 8 digit date [YYYYMMDD]. e.g. <<YY>><<MM>><<DD>> b at |||p |||||00| eng d = entered on the date <<29>><<11>><<25>> This creates the following data in a record: <<YY>>1125 b at |||p |||||00| eng d Is it possible to make this date code work to insert a date comprising 6 digits? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 26

[Bug 21504] New: enumchron shows as 0 in pdf
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '20

30 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21504 Bug ID: 21504 Summary: enumchron shows as 0 in pdf Change sponsored?: --- Product: Koha Version: 17.11 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Label/patron card printing Assignee: cnighswonger(a)foundations.edu Reporter: bwsdonna(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Created attachment 80141 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=80141&action=ed… bibrecord for testing enumchron issue When printing a spine label with itemcallnumber and enumchron, the pdf shows the one or two digit enumchron value as 0, but the CSV and XML formats show the correct enumchron value. Have replicated in 18.05. Changing item type, bib record, enumchron value, etc all result in same scenario. To replicate, create a template and layout: Template: US inches Page height 11 Page width 8.5 Label width 1.625 Label height 1 Top page margin .5 Left page margin .25 Top text margin .3 Left text margin 1.25 Number of columns 5 Number of rows 10 Gap col 0 Gap row 0 No profile Layout: Biblio 1 itemcallnumber 2 enumchron Split call numbers Text: center Font: Times-Bold Font size 12 Create a label batch with an enumchron, marc file for the record I was using is attached. View the pdf and see the enumchron shows 0. View the CSV and XML and see the correct enumchron shows. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 22939] New: Hard due date should block renewals when it wouldn't extend the due date
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '20

28 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22939 Bug ID: 22939 Summary: Hard due date should block renewals when it wouldn't extend the due date 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: lisetteslatah(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Target Milestone: --- It seems like it would make sense for renewals to be blocked if there is a hard due date set equal to or before the time the renewal would normally allow it would block renewing. aka: School branch (branch a) is closing for the summer. They set their hard due date to be 5/17/19. Their checkout period is 14 days, they allow 1 renewal, and the renewal is 14 days. Patron at branch b (not closing for the summer) gets a book from branch a on hold and checks it out 5/3/19. Due date is 5/17/19 and it says they have 1 renewal on the item. There is no warning about a hard due date and it looks like they should be able to renew it. On 5/16/19 they come in and want to renew the item, as their account says there is a renewal available. When the item is renewed it only gains 1 day. The patron has no indication why it is renewing differently than before. If the renewal was blocked (box grayed out or changed to zero) staff could preserve the previous renewal information without as much confusion for patrons. Lisette -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 22269] New: Pay amount - modal confirmation of amount to return to patron should be suppressed if attempting to pay (not collect) more than owed
by bugzilla-daemon＠bugs.koha-community.org 28 Aug '20

28 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22269 Bug ID: 22269 Summary: Pay amount - modal confirmation of amount to return to patron should be suppressed if attempting to pay (not collect) more than owed Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Fines and fees Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Target Milestone: --- To recreate: 1 - Add a fine or find a patron owing money 2 - Go to pay fines, pay amount 3 - Set amount to be paid higher than amount owed 4 - Set amount collected higher than amount paid 5 - Note you get a confirmation modal, confirm 6 - payment fails Expected action would be that modal is prevented or notifies user that they are trying to pay more than owed. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 10

[Bug 18251] New: SCO alerts - need a trigger for successful checkouts
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '20

26 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18251 Bug ID: 18251 Summary: SCO alerts - need a trigger for successful checkouts Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: nick(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Failed checkouts on the sco can be triggered by presence of alert, however, we have no feedback for a successful checkout. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 63

[Bug 19287] New: Add ability to mark an item ‘Lost’ from ‘Holds awaiting pickup’ list
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '20

25 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=19287 Bug ID: 19287 Summary: Add ability to mark an item ‘Lost’ from ‘Holds awaiting pickup’ list Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Hold requests Assignee: koha-bugs(a)lists.koha-community.org Reporter: severine.queune(a)bulac.fr QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The BULAC (http://www.bulac.fr/) would like to mark items not found on shelves after patrons’ holds as ‘Lost’ directly from the “Circulation > Holds awaiting pickup” list. We could have a new button on the “Action” columns of the 2 tabs, producing 3 automatic actions : - cancel the hold - notify the patron if the hold was supposed to be available (the notice should be set on the “Tools > Notices and Slips” menu) - set the field “items.notforloan” or “items.itemlost” (define in a system preference) from “0” to a value from the same ‘authorized values list’ and set in another system preference As long as “Change sponsored?” is set on “Seeking developer”, anyone wanting to quote us for the development of such a feature or just ask for more information is welcome to write to us: <sigb(a)bulac.fr>. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 108

[Bug 23788] New: Writing off multiple fees allows 'overpayment' of those fees
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '20

24 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23788 Bug ID: 23788 Summary: Writing off multiple fees allows 'overpayment' of those fees Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 Individual fees cannot be overpaid of over-written off, but it's possible to 'overpay' a writeoff of selected fees. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26

[Bug 22594] New: Validate SMS messaging numbers using the E.164 format
by bugzilla-daemon＠bugs.koha-community.org 24 Aug '20

24 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22594 Bug ID: 22594 Summary: Validate SMS messaging numbers using the E.164 format Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons 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 Target Milestone: --- Many SMS messaging services reject numbers that do not conform to the E.164 international public telecommunication numbering plan. On the OPAC we already We already tell patrons on the OPAC "Please enter numbers only. (123) 456-7890 would be entered as 1234567890." but we do not enforce this. We should be validating the patron's SMS number on both the staff side and the patron self-service for updating the SMS number. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 21

[Bug 21189] New: GDPR: Log all CRUD actions on patron data
by bugzilla-daemon＠bugs.koha-community.org 23 Aug '20

23 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=21189 Bug ID: 21189 Summary: GDPR: Log all CRUD actions on patron data Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: vfernandes(a)keep.pt QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Under the auspices of the recently issued European legislation regarding data privacy (GDPR), the Portuguese government has issued a series of mandatory requirements, as well as general recommendations, for software applications that are implemented under the umbrella of public bodies (RCM 41/2018). Since Koha is mostly used by municipalities and universities in Portugal, some of these mandatory requirements need to be address by Koha implementers in Portugal. We believe that this requirement is also useful for the community at large. Here’s a description of the requirement. *** Requirement description *** Every operation that has to do with creating, updating, deleting and changing permissions of user personal data should be logged. One should know who, when, on who and from the operation has been performed. *** Scope *** Applies in all cases. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 6

[Bug 25521] New: NewItemsDefaultLocation description should not mention cart_to_shelf.pl
by bugzilla-daemon＠bugs.koha-community.org 21 Aug '20

21 Aug '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25521 Bug ID: 25521 Summary: NewItemsDefaultLocation description should not mention cart_to_shelf.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Staff Client 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 This system preference says "NOTE: This system preference requires the misc/cronjobs/cart_to_shelf.pl cronjob. Ask your system administrator to schedule it." But this isn't true, you don't need cart_to_shelf running to use the PROC shelving location. If you you want to go from PROC to CART to permanent location then you need cart_to_shelf for that last part, but not for the PROC part. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 13