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

[Bug 24123] New: bulkmarcimport.pl doesn't support UTF-8 encoded MARCXML records
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '20

05 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24123 Bug ID: 24123 Summary: bulkmarcimport.pl doesn't support UTF-8 encoded MARCXML records Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: koha-bugs(a)lists.koha-community.org Reporter: joonas.kylmala(a)helsinki.fi QA Contact: testopia(a)bugs.koha-community.org CC: jonathan.druart(a)bugs.koha-community.org, robin(a)catalyst.net.nz Importing an UTF-8 encoded MARC21 MARCXML record that has leader value in position 09 equal 'a' (unicode) makes non-ascii characters like 'ä' to be replaced with character '�'. The command being run is > misc/migration_tools/bulkmarcimport.pl -biblios -file record.marcxml -m=MARCXML -v -v I tracked this problem down to the line > $MARC::File::XML::_load_args{BinaryEncoding} = 'utf-8'; If you add that line again as first thing in the RECORD label block further down in the bulkmarcimport.pl the problem is fixed. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 24263] New: borrowers.relationship should not contain an empty string
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '20

05 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24263 Bug ID: 24263 Summary: borrowers.relationship should not contain an empty string Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: ASSIGNED Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: jonathan.druart(a)bugs.koha-community.org Reporter: jonathan.druart(a)bugs.koha-community.org QA Contact: testopia(a)bugs.koha-community.org It should be set to NULL if not relationship exist. Otherwise the about page will display a warning about a missing/wrong relationship in data (that is not in the syspref) -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 24445] New: Add missing Z3950 updates to Makefile.PL
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '20

05 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24445 Bug ID: 24445 Summary: Add missing Z3950 updates to Makefile.PL Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtj(a)kohaaloha.com QA Contact: testopia(a)bugs.koha-community.org Add missing Z3950 updates to Makefile.PL, so tar file will build ok this bug was introduced in BZ 13937 to test... 1/ attempt to build koha tar, observe failure 2/ apply patch 3/ attempt to build koha tar, observe success! -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 18

[Bug 23800] New: Batch modification tool orders items by barcode incremental by default (different behavior than 17.11)
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '20

05 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23800 Bug ID: 23800 Summary: Batch modification tool orders items by barcode incremental by default (different behavior than 17.11) Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Cataloging Assignee: koha-bugs(a)lists.koha-community.org Reporter: arthur.suzuki(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Created attachment 93987 --> https://bugs.koha-community.org/bugzilla3/attachment.cgi?id=93987&action=ed… Screen capture When using the batch modification tool and entering barcodes in a list, the screen which shows the different items matched is sorted by barcode ordered incrementally. It's quite inconvenient for a librarian who have a pile of book on his desk with a different order (which was just scanned). -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 33

[Bug 24508] New: Perl version stops upgrade
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '20

05 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24508 Bug ID: 24508 Summary: Perl version stops upgrade Change sponsored?: --- Product: Koha Version: 19.11 Hardware: All OS: Linux Status: NEW Severity: normal Priority: P5 - low Component: Installation and upgrade (command-line installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: hans.palsson(a)hkr.se QA Contact: testopia(a)bugs.koha-community.org In reference to bug 20808, when trying to upgrade 19.05.06 to 19.11.01 the installation fails due to dependencies. It seems Perl version 5.20.0 is required, on our server 5.28.1 is installed. Server is Debian Jessie; PRETTY_NAME="Debian GNU/Linux 8 (jessie)" NAME="Debian GNU/Linux" VERSION_ID="8" VERSION="8 (jessie)" ID=debian Error message is The following packages have unmet dependencies: koha-common : Depends: libnet-z3950-simpleserver-perl but it is not going to be installed ...when searching for solutions it leads to wrong version of perl installed. The server has previously installed and upgraded Koha up to 19.05.06 without errors. Is it a dependence that has come with 19.11? -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 8

[Bug 18155] New: Add useful classes to the rows of checkouts table
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=18155 Bug ID: 18155 Summary: Add useful classes to the rows of checkouts table 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: rbit(a)rbit.cz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Libraries sometimes ask to have different styling in checkouts table according to the item status such as awaiting reservation. Sometimes they need to highlight special document types. So I would propose to add another CSS classes to those already existing, something like: <tr class="odd group-item -group-item-strong.... itype-book hold-awaiting"> The itype class would be concatenated with an item type code. Maybe a class for item's location and overdue item would be useful as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 24558] New: Catching old holds on check in
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=24558 Bug ID: 24558 Summary: Catching old holds on check in Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 Many libraries have public hold shelves, where holds that are waiting are on a publicly accessible shelf where patrons can pick them up and check them out. Sometimes these libraries have patrons that 'mistakenly' pick up the hold and 'forget' to check them out. These items are then returned and the library checks them in, not know the previous status. The same hold is triggered, and the hold goes back out on the shelf. While we print the expiration date of the hold on the slip, not all staff notice the date. I would propose that if an expired hold, or a hold with an expiration shorter than that assigned to ReservesMaxPickUpDelay is checked in, a message or alert displays, to alert staff that this is an old hold. They would still have all the usual options with that hold, but would be alerted to its old status. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 1

[Bug 23620] New: Improve checkin message when suspensions are accrued at check into include number of 'days' overdue and the resulting no. of suspension days.
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23620 Bug ID: 23620 Summary: Improve checkin message when suspensions are accrued at check into include number of 'days' overdue and the resulting no. of suspension days. Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In a library using suspensions only, not fines and not restrictions, when an overdue item is returned there is no visibility for staff on the length of time is it overdue and staff sometimes end up manually calculating the days to answer queries as to why a suspension / fine is a particular length. Staff want to be able to say that book was 2 days / 20 days overdue and your account is suspended for X days until X date. Please improve messaging on circulation so that when an overdue item is returned, the number of days overdue is communicated to staff in addition to any suspension / restriction / fine. Failing this, on checkin of overdue items, it would be very useful to be able to click on a link to view suspensions and see detail about which item is overdue (barcode?) and how many days that item is overdue so that the staff member can explain to a patron why the suspension is X amount of days. This change will save staff time dealing with queries (more efficient use of time), make the process more transparent which in turn provides a better customer service. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 22021] New: Item status not shown accurately on request.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22021 Bug ID: 22021 Summary: Item status not shown accurately on request.pl Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Hold requests 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 Target Milestone: --- Damaged and Lost statuses are showing the generic category of Lost or Damaged instead of the specific status. We've been fixing this issue in other places. This page should also be corrected. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 21

[Bug 23618] New: Make addition SIP2 fields available to self service to add cost of items checked out to check out slip
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23618 Bug ID: 23618 Summary: Make addition SIP2 fields available to self service to add cost of items checked out to check out slip Change sponsored?: --- Product: Koha Version: 18.11 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: SIP2 Assignee: koha-bugs(a)lists.koha-community.org Reporter: niamh.walker-headon(a)it-tallaght.ie QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com We can’t include the total cost of items checked out in a session on the selfcheck out receipt, like we can on the check out digest e-mail. Describe in detail. We would like the SIP2 checkout string to include some enhanced fields. Specifically the item’s 952$g and 952$v. This would involving modification to the SIP2 specification allowing for extra fields. For example, $v => CM , $g => CX field. So a checkout string might look something similar to: 11NN20190401 175709 AOTA|AAX1234567|AB123456789|BON|CM15.99|CX24.99|AC So the idea is to include a note at the bottom of the slip that goes: By using the library today you saved [total replacement cost of items borrowed today] By using the library this year you saved [total replacement cost of items borrowed year] By using the library have you saved [total replacement cost of items borrowed total ever] The alternative is to possibly use the item replacement price [ checkout.item.replacementprice] and total it for a time period, and for all time. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5