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

[Bug 9614] New: Fines not assessed after renewing an item
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '15

06 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9614 Bug ID: 9614 Summary: Fines not assessed after renewing an item Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: elliott(a)bywatersolutions.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When an item is overdue and is renewed the fines that were assessed are removed. This is obviously not a desired behavior. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 11

[Bug 10450] New: Editing serials predicts wrong
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '15

06 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10450 Bug ID: 10450 Summary: Editing serials predicts wrong Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Serials Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com CC: colin.campbell(a)ptfs-europe.com I have seen this happen since Koha 3.8 but thought it was just me - now I'm going to report a bug in case someone can track down the problem. Here's an example: ---- I have the July issue of Food & Wine in hand. I am in the Food & Wine serials record and filling in the date of next publication and the '# starts with' for predictions. I put 07/01/2013 for next publication and I put a 7 in the predictions chart (since I am starting these records off now) But when I go to check in the July issue, it gives 2013:8 for the issue and publication date as 08/01/2013. ---- This always happens when you edit an existing serial record's prediction pattern. No matter what you put in it always generates the next one - not the one you entered. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3

[Bug 11496] New: The number of tested records when searching for duplicates during import is too low
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '15

06 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11496 Bug ID: 11496 Summary: The number of tested records when searching for duplicates during import is too low Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: matthias.meusburger(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl Currently, only the first 10 records returned by koha for a given matchpoint are tested. This is not enough in some cases, because a significant matching record can be beyond these 10 first results. Please note that when the checkpoint is about fields with unique identifiers, like ISBN, the problem won't occur. On the other hand, when the checkpoint is about something less precise, like an author name, the matching record can be beyond the 10 first results. When that happens, the matchpoint will fail, the match threshold won't be reached, and a duplicate record will be created. -- You are receiving this mail because: You are watching all bug changes.

1 11

[Bug 13391] New: MARC 008 builder plugin not compatible with browser autocompletion
by bugzilla-daemon＠bugs.koha-community.org 06 Nov '15

06 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13391 Bug ID: 13391 Summary: MARC 008 builder plugin not compatible with browser autocompletion Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: abl(a)biblos.pk.edu.pl QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl In the koha-tmpl/intranet-tmpl/prog/en/js/xmlControlfield.js (line 317) there are two JS events (onkeyup and onfocus) being handled for 008 MARC plugin <input ...> fields (for MARC21 008 plugin, <input> is used e.g. for dates, country codes and language codes). But there is a slight problem with onkeyup event handler: apparently this event does not fire when: - user starts to enter some characters using the keyboard, - and then chooses something from the autocompletion list offered by browser. End result is that in such circumstances only the first character[s] entered in the given field are saved in 008 (only the part that was typed on the keyboard), and the remaining characters are effectively lost / being ignored by 008 plugin (unless the user "returns" to this field, i.e. gives it focus once again, before clicking "OK"). Replacing 'onkeyup' with 'oninput' in line 317 looks like the easiest solution for this issue; it works fine in recent (HTML5 compliant) browsers, but OnInput event handler is relatively new thing - it would not work in old, "legacy" WWW browsers. I guess we can also add autocomplete='off' to the <input> fields generated by renderPositions() function in xmlControlfield.js ;). I'm wondering what would happen if we try to put both oninput=.. and onkeyup= event handlers in those fields (probably both of them would fire when user enters something, but maybe that will be not necessarily such a bad thing ?). However, none of those methods are quite sufficient for older browsers. Reparsing all fields on form submit may help a little bit - so changes in the entered values which may have been previously ignored by the plugin would have a chance to be saved in 008 after all - but that's only a partial solution, the 008 contents being displayed on top may still sometimes get "out of sync" with the individual values below.. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 13435] New: OPAC self registration can't find OPAC_REG_VERIFY notice if it is assigned to a branch
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '15

05 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13435 Bug ID: 13435 Summary: OPAC self registration can't find OPAC_REG_VERIFY notice if it is assigned to a branch Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Email verification can look very broken for multi branch systems - if there is no "all libraries" notice defined for "OPAC_REG_VERIFY," but one defined for a specific branch, the self registration code can't find the notice and thus the verification email is not sent. Additionally, this code will only ever return the "all libraries" version of this notice, as it never passes a branchcode - making this notice useless on a per-branch basis. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 9468] New: Add ability to hide items from purchase suggestions forms
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '15

05 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9468 Bug ID: 9468 Summary: Add ability to hide items from purchase suggestions forms Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: kyle(a)bywatersolutions.com -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 88

[Bug 13409] New: Add ability to purge old special holidays using cleanup_database.pl
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '15

05 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13409 Bug ID: 13409 Summary: Add ability to purge old special holidays using cleanup_database.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org Some libraries have expressed interested in being able to purge old holidays from the database. -- You are receiving this mail because: You are watching all bug changes.

1 29

[Bug 13049] New: Improve self-registration cronjobs
by bugzilla-daemon＠bugs.koha-community.org 05 Nov '15

05 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13049 Bug ID: 13049 Summary: Improve self-registration cronjobs Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Command-line Utilities Assignee: gmcharlt(a)gmail.com Reporter: m.de.rooy(a)rijksmuseum.nl QA Contact: testopia(a)bugs.koha-community.org There are two small cronjobs for self-registration: delete_expired_opac_registrations.pl and delete_unverified_opac_registrations.pl The expired job is meant to delete from borrowers when the patron category is equal to PatronSelfRegistrationDefaultCategory and date enrolled past PatronSelfRegistrationExpireTemporaryAccountsDelay. (See also bug 11945.) It seems to me that this behavior is unexpected since the pref descriptions do not suggest that the default category is temporary. Perhaps, it was meant to add some verification step into the process when you do not use the email verification triggered by pref PatronSelfRegistrationVerifyByEmail. The unverified job is meant to delete from borrower_modifications and uses a time parameter (defaulting to 24 hours) to find unverified entries. It seems to me that it should use the PatronSelfRegistrationExpireTemporaryAccountsDelay preference. (Read its description.) I propose the following changes: [1] Move these actions to cleanupdatabase. Do they really need two separate scripts? [2] Rename the Delay preference. Name and description conflict now. We could make name and description cover both cases: (a) verify is on and still unverified and (b) verify is off and still in the initial category. [3] Trigger the borrowers/category delete only if Verify is off and the renamed delay has been past. -- You are receiving this mail because: You are watching all bug changes.

1 26

[Bug 13995] New: Proper Exception handling
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13995 Bug ID: 13995 Summary: Proper Exception handling Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org We should have a Java-style Exception handling mechanism in place. It will make it easier to handle exception across the board. Try::Tiny and Exception::Class seem to be the most bestest approaches. -- You are receiving this mail because: You are watching all bug changes.

1 39

[Bug 8436] New: Add branch limit on checkexpiration.pl
by bugzilla-daemon＠bugs.koha-community.org 04 Nov '15

04 Nov '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8436 Priority: P5 - low Change sponsored?: --- Bug ID: 8436 CC: colin.campbell(a)ptfs-europe.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Add branch limit on checkexpiration.pl Severity: enhancement Classification: Unclassified OS: All Reporter: claire.hernandez(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Serials Product: Koha This limit is available only if user is superlibrarian or has the permission 'superserials'. Otherwise, only subscriptions that are linked to the working branch are shown. (BibLibre stetienne/ft/MT6725) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 41