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

[Bug 6821] New: no results found message when searching serials
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6821 Bug #: 6821 Summary: no results found message when searching serials Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: nengard(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org When you search subscriptions from the serials page, if you don't get any results it should say 'no results found' instead of just showing the form headings with no results listed. -- 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 5561] New: Help on summary field in authority type editor
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5561 Summary: Help on summary field in authority type editor Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: Online Help AssignedTo: nengard(a)gmail.com ReportedBy: januszop(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 I have dug through C4::AuthoritiesMarc::BuildSummary and, if I understand well, what on-line help says on summary: >> The summary contains an "ISBD" like description to explain how the entry must be shown in the result list. The syntax is : * [xxxFFFSyyy] where are up to 3 digits BEFORE the field, FFF the field number, S the subfield code, yyy up to 3 digits AFTER the field. * things outside [] are kept as is (including HTML) * repeatable fields are managed. << is relevant for UNIMARC authorities *ONLY*. For MARC21 the content of the summary field, taken as string, will just precede the summary constructed by the function. Am I right? If so then I think this remark should be in the help file not to confuse users. Regards, Janusz -- 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 5891] New: Budgeting for Serials
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5891 Bug #: 5891 Summary: Budgeting for Serials Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Serials AssignedTo: colin.campbell(a)ptfs-europe.com ReportedBy: vimal0212(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Budgeting of serials not possible with current version of Koha. Cash management of Serial is not available. We want to manage amount of subscription in serial module and deduction in Serials fund in budget. -- 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 5906] New: Notices: formating of notices
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5906 Bug #: 5906 Summary: Notices: formating of notices Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: shelley(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Is it possible to apply any kind of formatting to notices created in the koha > tools > notices area? Specifically: make text bold make text italic make font size smaller insert a page break -- 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 5400] New: add test case to detect merge conflict markers in the code
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5400 Summary: add test case to detect merge conflict markers in the code Change sponsored?: --- Product: Koha Version: HEAD Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: gmcharlt(a)gmail.com QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Merge conflict markers don't belong in the code, of course, but occasionally can creep in during a moment of inattention. A test case can catch them. -- 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 5103] New: Dates in MARC details not formatted correctly
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5103 Summary: Dates in MARC details not formatted correctly Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All URL: /cgi-bin/koha/catalogue/MARCdetail.pl?biblionumber=xx OS/Version: All Status: NEW Severity: minor Priority: P5 Component: Templates AssignedTo: oleonard(a)myacpl.org ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2483 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2483 Screenshot shows acq date in MARC details. Date formats in catalogue > MARC > items are not formatted according to sys pref dateformat. Tested with Koha version 3.01.00.145 and different settings for dateformat. -- 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 5012] New: bulkmarcimport.pl throws uninitialized value error if no ISBN
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5012 Summary: bulkmarcimport.pl throws uninitialized value error if no ISBN Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: MARC Bibliographic record staging/import AssignedTo: gmcharlt(a)gmail.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: koha-bugs(a)lists.koha-community.org CC: ian.walls(a)bywatersolutions.com Estimated Hours: 0.0 When importing records with bulkmarcimport.pl -b, records that have a ISBN field, but not a value in subfield 'a', return an uninitialized value error on line 209. This occurs when there is a 020, but not a subfield 'a' (or 010 in UNIMARC). This occurs during the '-' scrubbing section of the script, and may or may not block the import of the record (further testing required). Since not having a 020a (or 010a in UNIMARC) does not invalidate the record, import should succeed, and the import status display should not be interrupted with this error message. -- 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 5087] New: Option to not show CSV profiles in OPAC
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=5087 Summary: Option to not show CSV profiles in OPAC Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Tools AssignedTo: gmcharlt(a)gmail.com ReportedBy: katrin.fischer(a)bsz-bw.de QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 Created attachment 2450 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=2450 download option in opac's cart Currently CSV profiles defined in staff are shown in the pull down of download options in opac's cart. I would like an option to only show those CSV profiles in staff. More complex but even better would be a system where I can define for each CSV profile wether it will be shown in OPAC or only in staff. -- 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 4974] New: process_koc.pl fails to display date and time of return
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4974 Summary: process_koc.pl fails to display date and time of return Change sponsored?: --- Product: Koha Version: rel_3_4 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Circulation AssignedTo: kyle.m.hall(a)gmail.com ReportedBy: magnus(a)enger.priv.no QAContact: koha-bugs(a)lists.koha-community.org CC: gmcharlt(a)gmail.com Estimated Hours: 0.0 On a successful return, process_koc.pl displays something like this: Checked in TITLE (BARCODE) from PERSON (PATRONBARCODE): The date and time is supposed to be displayed after the trailing colon. On lines 276, 297, 318 and 344 the script tries to assign datetime to @output: datetime => $circ->{ 'datetime' } but in the function parse_command_line on line 189 the timestamp from the .koc-file is split into $date, $time and $id, and date and time are returned seperately. A couple of solutions spring to mind: - Returning the timestamp from parse_command_line and assigning that to datetime in @output - Concatenating date and time in the assignment to datetime. Not sure which makes most sense... -- 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 4871] New: Debian packaging should use start-stop-daemon, not daemon
by bugzilla-daemon＠bugs.koha-community.org 13 Apr '13

13 Apr '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4871 Summary: Debian packaging should use start-stop-daemon, not daemon Change sponsored?: --- Product: Koha Version: rel_3_2 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: Packaging AssignedTo: lars(a)catalyst.net.nz ReportedBy: lars(a)catalyst.net.nz QAContact: koha-bugs(a)lists.koha-community.org Estimated Hours: 0.0 start-stop-daemon is the canonical tool in Debian for init.d scripts to start and stop server processes. daemon is used less. It would be good for Koha packaging to follow mainstream here. -- 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