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

[Bug 20626] New: Fines are recalculated and removed on SIP checkin
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=20626 Bug ID: 20626 Summary: Fines are recalculated and removed on SIP checkin 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: stefan.berndtsson(a)ub.gu.se QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com When a patron has an accruing fine (code FU) for an item, and that item is returned, there are some parts of the logic that causes unexpected consequences. All of the following assumes CalculateFinesOnReturn is not active. The following happens when the issuing rule fine value is set to 0. If the return is made via the staff interface, and no explicit return date is set, the item is returned, and the fine is changed to code F, but amount remains. If the return is made via the staff interface, with an explicit return date, the item is returned, and the fine is changed to code F, but the amount is cleared. This is documented in a comment in the code as the expected behaviour. If the return is made via the SIP2 protocol, it will always have an explicit return date, because the date is set from the SIP reply. Therefor the amount will be cleared. This is unexpected since the SIP checkins aren't backdated returns. When the issuing rule fine value is set to higher than 0, similar things happen, except it will change the fine instead of clearing it. Again, this is unexpected for SIP checkin. With no expected backdating, and CalculateFinesOnReturn disabled, I'd expect fine amounts to remain untouched. A very simple fix is of course to change C4/SIP/ILS/Transaction/Checkin.pm and simply not send $return_date to AddReturn(). I don't know if this is a proper solution or not. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 3

[Bug 16972] New: ./misc/ sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section.
by bugzilla-daemon＠bugs.koha-community.org 06 Feb '20

06 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=16972 Bug ID: 16972 Summary: ./misc/sip_cli_emulator.pl should list mandatory vs. optional command line options in its usage section. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: robin(a)catalyst.net.nz As far as I can tell, the following options are mandatory: -a (address) -p (port) -su (sip user) -sp (sip password) -l (sip location/institution) The sip terminator (-t) is not mandatory, but getting it wrong hangs the script without warning. The usage would look like this, more or less: Usage: $0 -a <address> -p <port> -su <sip user> -sp <sip port> -l <location> [--patron <patron barcode>] [--password <patron password>] [-i <item barcode>] [-fa] [-m <message>] [-h] -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 23274] New: t/db_dependent/XISBN.t fails with Elasticsearch
by bugzilla-daemon＠bugs.koha-community.org 05 Feb '20

05 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23274 Bug ID: 23274 Summary: t/db_dependent/XISBN.t fails with Elasticsearch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Test Suite Assignee: chris(a)bigballofwax.co.nz Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org What is says in the title: - Run t/db_dependent/XISBN.t - tests pass - Activate Elasticsearch - t/db_dependent/XISBN.t fails -- You are receiving this mail because: You are watching all bug changes.

1 14

[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 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 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 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

[Bug 23425] New: Search explodes with "invalid data, cannot decode object"
by bugzilla-daemon＠bugs.koha-community.org 04 Feb '20

04 Feb '20

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=23425 Bug ID: 23425 Summary: Search explodes with "invalid data, cannot decode object" Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Searching 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: 22144 If the MARCXML data is wrong for some reasons and so MARC::Record::new_from_xml fails, a search will explodes with "invalid data, cannot decode object" We should: - Understand why the data is wrong - Provide a maintenance script to catch problematic data - Skip the record instead of exploding (or maybe not, it will hide a data problem) It has been highlighted by bug 22144, was silently failing before those patches. Referenced Bugs: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=22144 [Bug 22144] Add method metadata() to Koha::Biblio -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 23