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

[Bug 14064] New: Implement language overlay for item types
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14064 Bug ID: 14064 Summary: Implement language overlay for item types Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: I18N/L10N Assignee: koha-bugs(a)lists.koha-community.org Reporter: veron(a)veron.ch QA Contact: testopia(a)bugs.koha-community.org CC: frederic(a)tamil.fr Implementation of language overlays for item types similar to Bug 14063. -- You are receiving this mail because: You are watching all bug changes. You are the assignee for the bug.

1 4

[Bug 7041] New: Sort >1000 search results with sortmax parameter in zebra config file
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7041 Bug #: 7041 Summary: Sort >1000 search results with sortmax parameter in zebra config file Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Searching AssignedTo: gmcharlt(a)gmail.com ReportedBy: m.de.rooy(a)rijksmuseum.nl QAContact: koha-bugs(a)lists.koha-community.org By default, zebra does not sort more than 1000 records (search results). You can increase this number by adding the sortmax parameter in zebra-biblios.cfg. Putting this value in Koha's zebra config file will make this default value visible and make it easier to increase it if one prefers that. This patch therefore adds the default of 1000 to zebra-biblios.cfg. Does not change any Koha/Zebra behavior. If you want to test it, look for a search in your catalog with >1000 results. Look at the order of the records. Now apply the patch and copy the zebra-biblios.cfg to your zebra directory. Increase sortmax, reindex and search again. If you increased sortmax above the number of hits, you should see a difference in sort order now. -- 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 11

[Bug 14324] New: "Add Child" button missing on moremember.pl
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14324 Bug ID: 14324 Summary: "Add Child" button missing on moremember.pl Change sponsored?: --- Product: Koha Version: unspecified Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Patrons Assignee: koha-bugs(a)lists.koha-community.org Reporter: barton(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com The code which adds the "Add child" button is in koha-tmpl/intranet-tmpl/prog/en/includes/members-toolbar.inc at line 151: 149 [% IF ( CAN_user_borrowers ) %] 150 [% IF ( adultborrower AND activeBorrowerRelationship ) %] 151 <a id="addchild" class="btn btn-small" href="/cgi-bin/koha/members/memberentry.pl?op=add&guarantorid=[% borrowernumber %]&category_type=C"> Add child</a> 152 [% END %] 153 [% IF ( CAN_user_borrowers ) %] 154 <a id="changepassword" class="btn btn-small" href="/cgi-bin/koha/members/member-password.pl?member=[% borrowernumber %]"> Change password</a> 155 [% END %] 156 <a id="duplicate" class="btn btn-small" href="/cgi-bin/koha/members/memberentry.pl?op=duplicate&borrowernumber=[% borrowernumber %]&category_type=[% category_type %]">Duplicate</a> 157 [% END %] I added code to dump CAN_user_borrowers, adultborrower and activeBorrowerRelationship, and found that adultborrower was not set, even for a borrower whose borrower's category type is 'A'. 'adultborrower' is set in moremember.pl at line 192, but *only if $count returned by GetGuarantees is not 0*. 172 my ( $count, $guarantees ) = GetGuarantees( $data->{'borrowernumber'} ); 173 if ( $count ) { 174 $template->param( isguarantee => 1 ); 175 176 # FIXME 177 # It looks like the $i is only being returned to handle walking through 178 # the array, which is probably better done as a foreach loop. 179 # 180 my @guaranteedata; 181 for ( my $i = 0 ; $i < $count ; $i++ ) { 182 push(@guaranteedata, 183 { 184 borrowernumber => $guarantees->[$i]->{'borrowernumber'}, 185 cardnumber => $guarantees->[$i]->{'cardnumber'}, 186 name => $guarantees->[$i]->{'firstname'} . " " 187 . $guarantees->[$i]->{'surname'} 188 } 189 ); 190 } 191 $template->param( guaranteeloop => \@guaranteedata ); 192 ( $template->param( adultborrower => 1 ) ) if ( $category_type eq 'A' || $category_type eq 'I' ); 193 } In other words, you can't add children unless you already have children. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 13851] New: Replace waiting holds logic in circulation.pl with Koha Objects
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13851 Bug ID: 13851 Summary: Replace waiting holds logic in circulation.pl with Koha Objects 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 This is the original patch for bug 12892 and replaces the older style of fetching the holds data with Koha Objects. -- You are receiving this mail because: You are watching all bug changes.

1 35

[Bug 13029] New: Allow to pass additional parameters to SMS::Send drivers
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13029 Bug ID: 13029 Summary: Allow to pass additional parameters to SMS::Send drivers Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: ASSIGNED Severity: enhancement Priority: P5 - low Component: Notices Assignee: julian.maurice(a)biblibre.com Reporter: julian.maurice(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 13376] New: Include a user-editable area/page for terms and conditions of use in the opac
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13376 Bug ID: 13376 Summary: Include a user-editable area/page for terms and conditions of use in the opac Change sponsored?: --- Product: Koha Version: 3.16 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Since Koha collects user data, we should have a place for libraries to include their website terms and conditions (and/or cookie policy information). I am thinking a link that appears in the footer area of every page if there is text in a system preference (along the lines of OpacMainUserBlock - free text area that accepts html). The contents of the syspref would be displayed in a page that has the same layout as the home page. I realise that libraries can use a page on their website to do that, but as Koha sometimes stands in for a website for libraries, I think it's important to at least offer a place to put the terms and conditions of use. We could also offer a standardised set of terms and conditions for the syspref (default value) - but a problem here is that people might not edit it, and getting one general enough might be problematic. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 12802] New: Sent notices using several email addresses
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12802 Bug ID: 12802 Summary: Sent notices using several email addresses Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org At the moment, the only place where a library can sent several emails to 1 patron is the overdue_notices.pl script. The mechanism will be extended to all notices. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 66

[Bug 9163] New: Cataloguing validation workflow
by bugzilla-daemon＠bugs.koha-community.org 08 Dec '15

08 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9163 Bug ID: 9163 Summary: Cataloguing validation workflow Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: new feature Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: vfernandes(a)keep.pt CC: m.de.rooy(a)rijksmuseum.nl New feature to have cataloguing validation workflow (some user validates the cataloguing of others and put the record online in OPAC). The idea is the following: - all framework needs to have suppress subfield hidden - the normal cataloguers uses this frameworks to catalogue the record - the record will not have suppress subfield filled (I don't know what happens when the record has no suppress - if it appears there is the need of set suppress = 1 automatically) - there is special framework with suppress subfield visible - only some users have access to the special framework - those users uses the special framework to validate the cataloguing and set suppress = 0 if everything is OK (after indexation the record appears online in OPAC) To have this working there is the need of a multi system preference with 3 options: 1 - Turn on/off the validation workflow (controll the appearing of the special framework in the dropdown list in addbook.pl and addbiblio.pl, set suppress = 1 if needed, etc) 2 - Set which will be the special framework (text box to set the framework code) 3 - List of users with access to this functionallity separated by comma (can be a permission but if the validation is off the permission has no sense, can be a file in the Koha structure with each username in one line, etc...) -- You are receiving this mail because: You are watching all bug changes.

1 40

[Bug 14393] New: Add collection code filter to inventory
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '15

07 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14393 Bug ID: 14393 Summary: Add collection code filter to inventory Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Tools Assignee: gmcharlt(a)gmail.com Reporter: dcook(a)prosentient.com.au QA Contact: testopia(a)bugs.koha-community.org Add the ability to do inventory by collection code as well. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 14364] New: Allow automatically canceled expired waiting holds to fill the next hold
by bugzilla-daemon＠bugs.koha-community.org 07 Dec '15

07 Dec '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=14364 Bug ID: 14364 Summary: Allow automatically canceled expired waiting holds to fill the next hold 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: kyle(a)bywatersolutions.com QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com Right now, if a library automatically cancels expired waiting holds, a librarian must still re-checkin an item to trap the next available hold for that item. It would be better if the next hold was automatically trapped and the librarians receive an email notification so they can make any changes to the item if need be ( hold area, hold slip in item, etc ). -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 30