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

[Bug 5927] New: Show series information in OPAC search results
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '15

06 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5927 Bug #: 5927 Summary: Show series information in OPAC search results Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: shelley(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Currently, in the staff client, if you search a book in a series, and the series information is included in the 490 fields, it displays at the end of the title in the search results. However, in the OPAC, the search screen does not display what series or volume in the series the book is. Show the series and volume info on a separate line in OPAC search results Edit the staff search results to do so, as well (currently only volume). -- 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 5

[Bug 4502] Perl error in acq budget planning
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '15

06 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4502 M. Tompsett <mtompset(a)hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Failed QA |In Discussion --- Comment #8 from M. Tompsett <mtompset(a)hotmail.com> --- (In reply to Katrin Fischer from comment #7) [ISSUE SNIPPED] > > I know this is a messy script - but can we catch this easily maybe? That's beyond the scope of this patch, as far as I can tell. I wouldn't fail this patch for the failing of the whole larger mess. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 10848] New: Allow configuration of mandatory/required fields on the suggestion form in OPAC
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '15

06 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10848 Bug ID: 10848 Summary: Allow configuration of mandatory/required fields on the suggestion form in OPAC Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org Several libraries have been suggesting that ISBN should also be mandatory on the suggestion form in OPAC. As some libraries might disagree but prefer other fields it would be nice to have a configuration option for mandatory/required fields. -- You are receiving this mail because: You are watching all bug changes.

1 43

[Bug 9846] New: system preference for required purchase suggestion fields
by bugzilla-daemon＠bugs.koha-community.org 06 Apr '15

06 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9846 Bug ID: 9846 Summary: system preference for required purchase suggestion fields Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Acquisitions Assignee: koha-bugs(a)lists.koha-community.org Reporter: nengard(a)gmail.com Right now the title is the only required field on the purchase suggestions form. There should be a system preference like borrowermandatoryfields that lets you choose what fields are required on your purchase suggestion form. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 5

[Bug 2542] Manual invoice fails on superfluous characters ( e.g. '$' )
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '15

05 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2542 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #11 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Some thoughts on this: 1) I think displaying the 0 is not good for ergonomy. I can type 03.00, but I feel libraries will think they need to delete the 0 first, before typing in the correct amount. 2) Also: with the 0 in the field, you can still accidentally save 0 value credits and fines easily and the 'required' attribute on the field doesn't kick in. 3) The message is very unspecific. For example, when I enter 'agahgag' it will just ask me to 'fill out the field' Can we have the field empty and have a better error message? Maybe something like: 'The entered amount is not valid'? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4502] Perl error in acq budget planning
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '15

05 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4502 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Signed Off |Failed QA --- Comment #7 from Katrin Fischer <katrin.fischer(a)bsz-bw.de> --- Hm, something is not looking quite right in my test. I marked all existing budgets as inactive. I created a new one without any fund and also marked it inactive. I click on the inactive budget, select Planning and the perl error occurs without the patch. With the patch, I do the same, example URL: http://localhost:8080/cgi-bin/koha/admin/aqplan.pl?budget_period_id=8&authc… Message displayed: No funds to display for this search criteria When I know submit the filters, the budget selection seems to be forgotten: http://localhost:8080/cgi-bin/koha/admin/aqplan.pl And instead of displaying the new error message I see some fund values that maybe belong to one of the other budgets? I know this is a messy script - but can we catch this easily maybe? -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 13955] New: 'Processing...' message out of place
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '15

05 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13955 Bug ID: 13955 Summary: 'Processing...' message out of place Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Circulation Assignee: koha-bugs(a)lists.koha-community.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com To test: - create a hold for your patron - go to the patron account - go to the details (not checkouts!) tab - load the holds tab - notice the 'Processing...' message appears at the very top left instead of close to the table -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 13857] New: Email input field for sharing lists is too small
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '15

05 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13857 Bug ID: 13857 Summary: Email input field for sharing lists is too small Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The input field for the email address of the patron you want to share your list with is a bit too short. -- You are receiving this mail because: You are watching all bug changes.

1 8

[Bug 13869] New: Wrong capitalization on guided reports page
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '15

05 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13869 Bug ID: 13869 Summary: Wrong capitalization on guided reports page Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: katrin.fischer(a)bsz-bw.de Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org On the last step of saving a new guided report to the database, the button is labelled "Save Report", but should be "Save report". -- You are receiving this mail because: You are watching all bug changes.

1 12

[Bug 10993] New: Transfer limits should be checked when placing a hold/reservation.
by bugzilla-daemon＠bugs.koha-community.org 05 Apr '15

05 Apr '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10993 Bug ID: 10993 Summary: Transfer limits should be checked when placing a hold/reservation. 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: olli-antti.kivilahti(a)jns.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com If a Borrower cannot get an Item transfered to his pickup location of choice, the Borrower needs to know that before he places a hold. This is especially true when placing Item-level holds. If a patron can place a hold on an item, he expects the item to be available at his pickup location of choice. Currently there is no warning or hold block for holds that violate the UseBranchTransferLimits-setting. Solution. Create or use an existing centralized CheckBranchTransferLimits-function inside the C4::Reserves::CanItemBeReserved(), to see if an item can be reserved for the desired pickup location. When the borrower changes his pickup location in koha/opac-reserve.pl?biblionumber=xxx, the BranchTransferLimits need to be recalculated. UseBranchTransferLimits should also affect placing holds via the Restful API's. $pickuplocation is not always available in the Restful API -requests so we can use the Borrowers homebranch as the default pickup location. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 26