January 2013 - Koha-bugs - lists.koha-community.org

[Bug 9354] New: Koha has insufficient MARC validation checks
by bugzilla-daemon＠bugs.koha-community.org 07 Jan '13

07 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9354 Bug ID: 9354 Summary: Koha has insufficient MARC validation checks Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.10 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: dpk(a)randomnotes.org CC: m.de.rooy(a)rijksmuseum.nl I think this is a MAJOR bug because it leads to silent data corruption. You can reclassify as an enhancement if you don't agree with this assessment. The Koha MARC import functions do little if any MARC record validation and some errors in MARC formatting can lead to bad data imports with no warning. Case in point for us was generating records with pymarc (with Python) and not setting the 'force_utf8' flag. We generated records that appeared valid, but tools like MarcEdit clearly complain about the format (length errors, and leader errors). leader[9] should have been an 'a', indicating that the data should be interpreted as UTF8. Since it was missing, the data fields appeared truncated because the MARC offset calculations got screwed up. Koha said nothing. We should incorporate the same validation checks that MarcEdit makes to flag bad import files before the data is accepted. -- You are receiving this mail because: You are watching all bug changes.

1 1

[Bug 3092] Data values storage and use 100 bug meta-bug
by bugzilla-daemon＠bugs.koha-community.org 06 Jan '13

06 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3092 --- Comment #2 from Jared Camins-Esakov <jcamins(a)cpbibliography.com> --- If there are any issues described in this bug still outstanding, please open a separate bug for each issue. If all the issues described have been fixed, please mark the bug as such. Otherwise, people coming across this bug will believe that all the issues still exist when presumably they do not. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 6287] New: No slip for aggregate fine activity for today
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '13

04 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6287 Bug #: 6287 Summary: No slip for aggregate fine activity for today Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Depends on: 2349, 3246 The current fine receipt printing is very nice, but it would also be nice to be able to have today's fine activity reflected on the regular issuing slip. Constructed like: Library Name Date Patron Number (name) Today's Issues Total fines owed: $$ Total paid today: $$ [News and other stuff] ---- Could go under an omnibus "stuff to be able to add to receipts by branch" since only fining libraries would want this on their receipts (important in consortia). -- 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 3

[Bug 3246] Looking for a way to customize the patron slips (receipts)
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '13

04 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3246 Melia Meggs <melia(a)bywatersolutions.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED CC| |melia(a)bywatersolutions.com Resolution|--- |DUPLICATE --- Comment #1 from Melia Meggs <melia(a)bywatersolutions.com> --- Slips are now customizable in version 3.8 and later. *** This bug has been marked as a duplicate of bug 7001 *** -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9325] New: overdue notices sent same messages for all users.
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '13

04 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9325 Bug ID: 9325 Summary: overdue notices sent same messages for all users. Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: jonathan.druart(a)biblibre.com In overdue_notices.pl, letter template must not be passed to parse_letter because this sub modifies it, so the first overdue letter is ok but following letters have exactly the same content. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 9279] New: Problem with quick slip templates
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '13

04 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9279 Bug ID: 9279 Summary: Problem with quick slip templates Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Notices Assignee: koha-bugs(a)lists.koha-community.org Reporter: vfernandes(a)keep.pt Yesterday I was trying the using of quick slip templates in Koha 3.8.7. I've modified the template and then I've done one check out to one patron. Then I tried to print the quick slip, and two thing happened: - If I was in circulation tab of the patron, when printing the quick slip the template was used (printslip.pl was called) - If I was in details tab of the patron, when printing the quick slip the templates wasn't used (moremember.pl was called) Should be the template always be used besides being on circulation or details tab? -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 12

[Bug 6535] New: Dates in notices should be syspref formatted
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '13

04 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6535 Bug #: 6535 Summary: Dates in notices should be syspref formatted Classification: Unclassified Change sponsored?: Sponsored Product: Koha Version: rel_3_6 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Notices AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org Any date field being parsed into the notice should be formatted accounting to dateformat system preference. A change made to C4::Letters::parseletter would handle this for every letter coming though. -- 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 9347] New: save button at the top of screen when editing or adding patron
by bugzilla-daemon＠bugs.koha-community.org 04 Jan '13

04 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9347 Bug ID: 9347 Summary: save button at the top of screen when editing or adding patron Classification: Unclassified 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: melia(a)bywatersolutions.com CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com With the next version of Koha, would you please put a save button at the top of the page (as well as the bottom) for Patron edits and adding a new patron. It sure would save some time if we did not have to scroll down to the bottom of the page to save our changes or add a new patron. Thanks. Janet Lyon -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 5172] New: Use other name rather than first name when referring to the user
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '13

03 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5172 Summary: Use other name rather than first name when referring to the user Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: OPAC AssignedTo: oleonard(a)myacpl.org ReportedBy: robin(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 In the OPAC, the 'Other Name' field should be used when referring to the user, if it's been supplied. For example, "Mr Firstname Surname" should be "Mr Othername Surname" if there is a defined Othername. -- 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 16

[Bug 9340] New: Server Error while downloading translation files
by bugzilla-daemon＠bugs.koha-community.org 03 Jan '13

03 Jan '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9340 Bug ID: 9340 Summary: Server Error while downloading translation files Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: critical Priority: P5 - low Component: translate.koha-community.org Assignee: koha-bugs(a)lists.koha-community.org Reporter: rolando.isidoro(a)gmail.com CC: frederic(a)tamil.fr Created attachment 14386 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=14386&action=edit Server Error while downloading translation files When trying to download a translation file, in my case some pt-PT files for Koha 3.8, I get the following Server Error message (also as seen in the attached image): "An error has occurred. Thank you for your patience. Error accessing /var/www/Pootle/po/38/pt/pt-PT-pref.po, Filesystem sent error: Permission denied" This can be replicated by accessing the following URL: http://translate.koha-community.org/pt/38/pt-PT-pref.po/download/. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 3