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

[Bug 10120] New: Fine recalculation on return needs to be a system preference
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10120 Bug ID: 10120 Summary: Fine recalculation on return needs to be a system preference Classification: Unclassified 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: katrin.fischer(a)bsz-bw.de CC: chris(a)bigballofwax.co.nz, gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com As agreed on IRC today, recalculation of fines on return needs to be tied to a system preference as it changes the fines workflow. Ideally the system preference would have 3 settings: - recalculate always - recalculate only for hourly loans - don't recalculate -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 24

[Bug 12488] New: bulkmarcimport.pl -d option should use DELETE instead of TRUNCATE
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12488 Bug ID: 12488 Summary: bulkmarcimport.pl -d option should use DELETE instead of TRUNCATE Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org bulkmarcimport.pl -d ("Delete EVERYTHING related to biblio in koha-DB before import. Tables: biblio, biblioitems, items") use this code if ($delete) { if ($biblios){ print "deleting biblios\n"; $dbh->do("truncate biblio"); $dbh->do("truncate biblioitems"); $dbh->do("truncate items"); } else { print "deleting authorities\n"; $dbh->do("truncate auth_header"); } $dbh->do("truncate zebraqueue"); } But, as Robin Sheat[1] point me this is a deprecated way. Now, with MySQL >~5.5 the way is just to: DELETE FROM biblio; And the constraints will propagate the delete to (ALMOST) all other tables. [1] http://lists.katipo.co.nz/public/koha/2014-June/039701.html Related bug: #12486. -- You are receiving this mail because: You are watching all bug changes.

1 9

[Bug 12486] New: Appendix G (Resetting the Koha Database) using DELETE instead of TRUNCATE
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12486 Bug ID: 12486 Summary: Appendix G (Resetting the Koha Database) using DELETE instead of TRUNCATE Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: trivial Priority: P5 - low Component: Documentation Assignee: nengard(a)gmail.com Reporter: pablo.bianchi(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Manual appendix G, "Resetting the Koha Database"[1] talks about resetting Koha database with TRUNCATE SQL command. As Robin Sheat[2] point me this is a deprecated way. Now, with MySQL >~5.5 the way is just: DELETE FROM biblio; And the constraints will propagate the delete to (ALMOST) all other tables. [1] http://manual.koha-community.org/3.16/en/resetkohadb.html [2] http://lists.katipo.co.nz/public/koha/2014-June/039701.html I'll fill another bug about updating also bulkmarcimport.pl -d option. -- You are receiving this mail because: You are watching all bug changes.

1 5

[Bug 10454] New: Failure to lock could generate duplicate card numbers
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10454 Bug ID: 10454 Summary: Failure to lock could generate duplicate card numbers Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: mtompset(a)hotmail.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com In C4::Members.pm there is a function AddMembers_Opac which calls fixup_cardnumber. The problem is there is no locking to ensure that someone else doesn't add a member at the same time and create a duplicate card number. This patch adds the missing locking in. I've left commented wait code in, so that the person testing this can switch tabs or browsers to test that the locking doesn't catastrophically break things. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 32

[Bug 11780] New: Need to prevent specific fields from being overwritten with z39.50 import
by bugzilla-daemon＠bugs.koha-community.org 27 Oct '15

27 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11780 Bug ID: 11780 Summary: Need to prevent specific fields from being overwritten with z39.50 import Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In our previous LMS we could associate specific marc fields as "local use" in the configuration. If a marc record was overwritten with another via z39.50 these local use files remained in the new record. (if it was in a field that also contained data in the incoming record, then a 2nd instance for that field was created - e.g. multiple 500 notes, etc e.g. we need to keep our own 001 control numbers as Analytics links from other records get broken if this is replaced with the 001 of a new record say from LC or NLM. At the moment I have to note the existing 001 & put that value in again after replacing the record. There are also local notes fields etc that we would want to keep. It would be useful if this setting is also framework specific. (e.g. to keep certain fields for serials but not for monographs etc) -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 5560] New: pagination option for lists
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5560 Summary: pagination option for lists Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Virtual Shelves AssignedTo: gmcharlt(a)gmail.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Right now lists show 20 items per page and this is not changeable. I would like to see an option at list creation that lets me say how many items I want to show per page. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.

1 8

[Bug 11626] New: Cannot receive serial issues after subscription expiry date
by bugzilla-daemon＠bugs.koha-community.org 26 Oct '15

26 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11626 Bug ID: 11626 Summary: Cannot receive serial issues after subscription expiry date Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: Jeremy.evans(a)nibsc.org QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Some of our serials subscriptions were not renewed after 31/12/2013 but I cannot receive any of the outstanding 2013 issues unless I renew the subscription record (a couple of publishers are about 3 months late with their printing/postage schedules compared to the subscription/cover dates). For a couple of these titles we do not have a 2014 subscription so it is not appropriate to renew the subscription record. We should still be able to receive late issues after the subscription expiry date (the date published for these issues would in most cases be on or before the expiry date) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 7789] New: Add translations of item type and authorized value descriptions
by bugzilla-daemon＠bugs.koha-community.org 24 Oct '15

24 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7789 Priority: P5 - low Change sponsored?: --- Bug ID: 7789 Assignee: frederic(a)tamil.fr Summary: Add translations of item type and authorized value descriptions QA Contact: koha.sekjal(a)gmail.com Severity: normal Classification: Unclassified OS: All Reporter: oleonard(a)myacpl.org Hardware: All Status: NEW Version: master Component: I18N/L10N Product: Koha Created attachment 8471 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8471&action=edit Mockup of a possible implementation for Item Types Since descriptions of item types and authorized values are stored in the database, there is no way to translate them. This creates a problem if the descriptions in the database are in one language but your user has switched to another. I propose that we add a language column to the itemtypes and authorised_values tables. For existing installations the existing data would remain with an empty "language" value, and this option would be displayed by default. If a library adds a set of language-specific translations that set will be displayed when that language is chosen. I think the entry form would not require extensive updating, but the display of existing values in Administration might. I'm thinking that each language's values might be displayed in a separate tab. See the attached mockup. The tabs could be displayed based on enabled languages. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 12157] New: Batch delete for serial holdings
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '15

23 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12157 Bug ID: 12157 Summary: Batch delete for serial holdings Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: colin.campbell(a)ptfs-europe.com Request by a library: Currently we have to delete serial holdings one by one, it would be nice to be able to delete several (or many) at one time with a batch delete function for serial holdings. This would not necessarily have to delete the associated holding item, only the serial record. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 1

[Bug 9768] New: Problem with grace period calculation and fine intervals >1
by bugzilla-daemon＠bugs.koha-community.org 23 Oct '15

23 Oct '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9768 Bug ID: 9768 Summary: Problem with grace period calculation and fine intervals >1 Classification: Unclassified 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: m.de.rooy(a)rijksmuseum.nl CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With a fine interval > 1 there is currently no way to avoid a effective grace period. Fines can not start the day after the due date. Configuration: With grace period = 1 fine interval 5 (= weekly, the library is closed Sunday and Saturday) Result: The first fine ist set 7 days after the item was due. Monday, checkout Tuesday, item due Wednesday Thursday Friday Saturday, holiday Sunday, holiday Monday, Tuesday, first fine Grace period for fine intervals > 1 should describe the days between the due date and the day the first fine is set. CalcFines() in Overdues.pm: 266 my $days_minus_grace = $daystocharge - $data->{'firstremind'}; 267 if ($data->{'chargeperiod'} > 0 && $days_minus_grace > 0 ) { 268 $amount = int($daystocharge / $data->{'chargeperiod'}) * $data->{'fine'}; -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10