September 2011 - Koha-bugs - lists.koha-community.org

[Bug 5440] New: improvements on authorities links
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '13

24 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5440 Summary: improvements on authorities links Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All URL: http://wiki.koha-community.org/wiki/Improvements_to_Au thority_Searching OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: henridamien(a)koha-fr.org ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 The way you can search on authorities (authors & sujects) will be improved, and the user will be able to search on more than 1 authority at a time. For example : a book has 3 authors : Victor Hugo, John Travolta, Nicolas Sarkozy. If the user click on one of the 3 authors, a small popup opens, with the 3 authors, the one he has clicked on is selected, and the user can check the other ones if he want, and launch the search on 1, 2, or the 3 authors. For subject search, the idea is the same, except the user can select at subfield level. For example, if a biblio has 3 subject : sports, Europe – France, Soccer –- FIFA world cup 2010, if the user click on one of them, 5 choices can be checked : Sports / Europe / France / Soccer / FIFA world cup 2010 for an example, see here http://cat-bib.nimes.fr/cgi-bin/koha/opac-detail.pl?biblionumber=9 -- 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 1

[Bug 5219] New: Perltidy code
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '13

24 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5219 Summary: Perltidy code Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: cnighswonger(a)foundations.edu QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 This is a standing bug to be used for tidy patches. Be sure to use xt/perltidyrc as the basis for any perl tidying to be done. -- 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 4

[Bug 4985] New: Edit a calendar entry for all branches
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '13

24 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4985 Summary: Edit a calendar entry for all branches Change sponsored?: --- Product: Koha Version: HEAD Platform: All URL: /cgi-bin/koha/tools/holidays.pl OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 It is possible to create a holiday and copy it to all branches but it's not possible to edit a holiday and apply the change to all branches. -- 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 2

[Bug 5256] New: Merge bibs should work from cart
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '13

24 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5256 Summary: Merge bibs should work from cart Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Cataloging AssignedTo: gmcharlt(a)gmail.com ReportedBy: camins(a)numismatics.org QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 It would be really helpful if the Merge feature worked with records in the cart and not just records in lists. That way it would be possible to merge records quickly without needing to create a list every time. -- 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 1

[Bug 5394] New: Fatal error when searching for a non-existant item when receiving an order
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '13

24 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5394 Summary: Fatal error when searching for a non-existant item when receiving an order Change sponsored?: Sponsored Product: Koha Version: rel_3_0 Platform: All URL: http://localhost:8080/cgi-bin/koha/acqui/orderreceive. pl?supplierid=4&freight=0&invoice=2117008&receive=9781 563636783 OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Acquisitions AssignedTo: henridamien(a)koha-fr.org ReportedBy: mjr(a)ttllp.co.uk QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 A book is a new edition of the title in the catalogue, but their records are, and should remain, completely unrelated. I couldn't see a record for it in the acquisition module so I searched for it by ISBN from here: http://localhost:8080/cgi-bin/koha/acqui/parcel.pl?type=intra&supplierid=4&… under "search orders to add to this shipment" to check that the new edition record wasn't tucked away somewhere. I got the error message "Can't use string ("0") as a HASH ref while "strict refs" in use at /usr/local/share/koha/cgi-bin/acqui/orderreceive.pl line 192." This appears to be because the end of acqui/orderreceive.pl doesn't check whether the earlier GetBookSellerFromId actually found anything. I will prepare a simple patch. I think this is 3.0.x only. -- 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 2

[Bug 4906] New: Problem with grace period calculation and fine intervals >1
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '13

24 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4906 Summary: Problem with grace period calculation and fine intervals >1 Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 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'}; -- 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 38

[Bug 6314] New: UNIMARC OPAC XSL improvements
by bugzilla-daemon＠bugs.koha-community.org 24 Mar '13

24 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6314 Bug #: 6314 Summary: UNIMARC OPAC XSL improvements Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: frederic(a)tamil.fr QAContact: koha-bugs(a)lists.koha-community.org - Exclude 'marc' & 'item' prefix from UNIMARC util XSL to slim down result - Add missing NSB/NSE characters striping - 200 fields on result/detail page: show all subfields in order, link to detail page only on $a - 4xx display, more fields and more subfields, respects subfields order which matter - Add missing fields: 205, 500 - Add missing MARC21 syspref: - DisplayOPACiconsXSLT, not implemtable in UNIMARC - OPACURLOpenInNewWindow - URLLinkText - ShowISBD Sidenote: this should have been done by people having introduced those syspref into MARC21 XSL. -- 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 24

[Bug 6209] New: Standardize on one javascript library for client-side form validation
by bugzilla-daemon＠bugs.koha-community.org 23 Mar '13

23 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6209 Bug #: 6209 Summary: Standardize on one javascript library for client-side form validation Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Staff Client AssignedTo: paul.poulain(a)biblibre.com ReportedBy: oleonard(a)myacpl.org QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com We handle client-side validation in a piecemeal fashion. It would simplify things for the user and developers if we standardized on one JavaScript library for handling all client-side form validation. I propose we use this one: http://bassistance.de/jquery-plugins/jquery-plugin-validation/ Syntax is pretty simple: In the JavaScript: $(document).ready(function(){ $("#commentForm").validate(); }); In the markup: <form id="commentForm" method="get" action=""> <input id="cname" name="name" size="25" class="required" minlength="2" /> "class='required'" tells the script to validate that field as required. Other options include email, url, date, number, specific length, etc. -- 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 29

[Bug 5608] New: Tool to move MARC21 series info to 490 tag
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '13

22 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5608 Summary: Tool to move MARC21 series info to 490 tag Change sponsored?: --- Product: Koha Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Command-line Utilities AssignedTo: gmcharlt(a)gmail.com ReportedBy: mdhafen(a)tech.washk12.org QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 With the MARC21 standard moving from the 440 to the 490 it would be nice to have to tool that would move information in the catalogue from the 440 to the 490. I've written a tool that switches the information in the two tags for records found to have series information in the database. -- 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 35

[Bug 5635] New: bulkmarcimport new parameters & features
by bugzilla-daemon＠bugs.koha-community.org 22 Mar '13

22 Mar '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5635 Summary: bulkmarcimport new parameters & features Change sponsored?: Sponsored Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: ASSIGNED Severity: enhancement Priority: PATCH-Sent Component: Command-line Utilities AssignedTo: paul.poulain(a)biblibre.com ReportedBy: paul.poulain(a)biblibre.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 it's sometimes useful to do some changes on the fly on biblios or items. We will add a YAML file to do some mappings when running bulkmarcimport we will also add: * a test parameter * an insert parameter to allow INSERT only * and update parameter to allow biblios to be only updated * a filter on tags/subfields -- 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 40