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

[Bug 10819] New: Allow for auto filling of holds when items are checked in via SCO
by bugzilla-daemon＠bugs.koha-community.org 24 Jul '15

24 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10819 Bug ID: 10819 Summary: Allow for auto filling of holds when items are checked in via SCO Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Self checkout Assignee: koha-bugs(a)lists.koha-community.org Reporter: cnighswonger(a)foundations.edu QA Contact: testopia(a)bugs.koha-community.org When an item with a hold on it is checked in via the SCO module (web), no further processing is done which results in the hold being overlooked unless the circulation desk workflow includes a regular run of the hold reports. The least fix for this would be to add a system pref allowing for the option of auto-filling the highest priority hold on an item checked in via the SCO module. Perhaps other options allowing for various alternate workflows might be added here as well. I'm listing this as an enhancement because depending on one's workflow, this may not be a bug. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 8950] New: Patron Card Creator_Background Image and barcode
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '15

23 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8950 Priority: P5 - low Change sponsored?: --- Bug ID: 8950 Assignee: gmcharlt(a)gmail.com Summary: Patron Card Creator_Background Image and barcode Severity: enhancement Classification: Unclassified OS: All Reporter: sophina0516(a)gmail.com Hardware: All Status: NEW Version: rel_3_8 Component: Tools Product: Koha Our patron card design has a background image, which is the same size as the plastic card, (2" height * 3.25" width).If we prefer to locate the barcode at the front of the card, the barcode will be covered by the background image. Just wondering that ----Is there a way that we can bring the barcode to front of the background image? http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=patroncards/creat… -- You are receiving this mail because: You are watching all bug changes.

1 4

[Bug 13680] New: Items list on edit items page separates add items form from header and sidebar
by bugzilla-daemon＠bugs.koha-community.org 23 Jul '15

23 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13680 Bug ID: 13680 Summary: Items list on edit items page separates add items form from header and sidebar Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: nick(a)quecheelibrary.org QA Contact: testopia(a)bugs.koha-community.org Created attachment 35720 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=35720&action=edit Proposed layout On records with multiple items attached the add items form can be pushed down the page, separating it from the header and sidebar and requiring a choice between where pages focus should fall and often leading to scrolling depending on your action. See bug 11905 A different solution would be to move the existing items list to the bottom of the page. This is a fairly striking difference, but with the addition of edit item links on the record detail page I don't think it makes selecting an item to edit more onerous. That being said, change is upsetting and I believe this would need some discussion. -- You are receiving this mail because: You are watching all bug changes.

1 16

[Bug 12144] New: Book drop mode mode erasing fine when CalculateFinesOnReturn is enabled
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '15

22 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12144 Bug ID: 12144 Summary: Book drop mode mode erasing fine when CalculateFinesOnReturn is enabled 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com When returning items with Book drop mode mode enabled and CalculateFinesOnReturn set to "calculate", the amountoutstanding for a fine, no matter how large, is reduced to 0.00 To reproduce: 1) Fine a patron with and overdue item that has fines 2) Ensure CalculateFinesOnReturn is enabled 3) Browse to the returns screen, check the "Book drop mode" but *not* the "Forgive overdue charges" box 4) Return the item 5) Check the fine for that item, it should now be reduced to 0.00 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 2

[Bug 13044] New: Deprecate old dropbox mode
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '15

22 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13044 Bug ID: 13044 Summary: Deprecate old dropbox mode 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com We now have two ways to backdate returns, the older "Book drop" mode, and the newer arbitrary backdating of returns feature. We should deprecate the older mode by having the "Book drop" checkbox insert the date the library was last open into the date field. We would also need to remove the system preference to have the returns backdating feature always on. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 14437] New: Refactor C4::Auth::haspermission() to Koha::Object and return errors better.
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '15

22 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14437 Bug ID: 14437 Summary: Refactor C4::Auth::haspermission() to Koha::Object and return errors better. Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Authentication Assignee: gmcharlt(a)gmail.com Reporter: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: dpavlin(a)rot13.org Refactoring haspermission() and improving documentation. Also added a return value unintrusively (in the old context still RETURNS the same result) to tell which permission failed. Modification should have no adverse effects, other than killing the process (by throwing uncaught exceptions) if no valid parameters are given. Depends on Bug 13995 - Proper Exception handling so apply it first. Cannot create unit tests because there is no CRUD interface for permissions. Not even with TestBuilder. TEST PLAN: 1. Find a borrower with only the catalogue-permission. 2. try opening this page cgi-bin/koha/tools/manage-marc-import.pl 3. You get "Permission denied" -- You are receiving this mail because: You are watching all bug changes.

1 13

[Bug 11512] New: Forced holds that violate issuing rules will never be filled
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '15

22 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11512 Bug ID: 11512 Summary: Forced holds that violate issuing rules will never be filled Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Hold requests 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 Currently in Koha, if you choose to force a hold from the staff side that would contravened the current issuing rules, that hold will never be filled, as it is always skipped over by CheckReserves. I think the only way to resolve this is to add a flag to the reserves table to alert the system that despite the fact that this hold should usually be skipped over, in this case, it should not. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 4

[Bug 12160] New: Rename intranetuserjs to IntranetUserJS
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '15

22 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12160 Bug ID: 12160 Summary: Rename intranetuserjs to IntranetUserJS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com ... to match IntranetUserCSS The same should be done with opacuserjs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 14121] New: Silence warnings t/db_dependent/Auth_with_cas.t
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '15

22 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14121 Bug ID: 14121 Summary: Silence warnings t/db_dependent/Auth_with_cas.t 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: mtompset(a)hotmail.com QA Contact: gmcharlt(a)gmail.com C4::Auth_with_case has a $query->param($_) in a context which is not clearly scalar to the interpreter, so it throws a security warning. Introduce a variable, use the variable instead of calling param() twice. Noise disappears. -- You are receiving this mail because: You are watching all bug changes.

1 30

[Bug 13760] New: Authorities merge sometimes create duplicate fields in biblio
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13760 Bug ID: 13760 Summary: Authorities merge sometimes create duplicate fields in biblio 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: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When merging two authorities the biblio records linked to those authorities are updated. It is directly done if syspref "dontmerge" is on "Do". Actually some cases create a duplicate field. For example, a biblio record as : 600 $9 11 $a Son Goku 600 $9 12 $a Vegeta If you merge the authorities id=11 and id=12 into id=11 (creating Gogeta), you actually get : 600 $9 11 $a Son Goku 600 $9 11 $a Son Goku Having two identical fields linked to the same authority is useless. The same problem is even more frequent when merging two authorities of different type. -- You are receiving this mail because: You are watching all bug changes.

1 15