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

[Bug 12160] New: Rename intranetuserjs to IntranetUserJS
by bugzilla-daemon＠bugs.koha-community.org 22 Jul '15

22 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12160 Bug ID: 12160 Summary: Rename intranetuserjs to IntranetUserJS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: minor Priority: P5 - low Component: System Administration Assignee: koha-bugs(a)lists.koha-community.org Reporter: pasi.kallinen(a)pttk.fi QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com ... to match IntranetUserCSS The same should be done with opacuserjs. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 19

[Bug 13760] New: Authorities merge sometimes create duplicate fields in biblio
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13760 Bug ID: 13760 Summary: Authorities merge sometimes create duplicate fields in biblio Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: fridolyn.somers(a)biblibre.com QA Contact: testopia(a)bugs.koha-community.org CC: m.de.rooy(a)rijksmuseum.nl When merging two authorities the biblio records linked to those authorities are updated. It is directly done if syspref "dontmerge" is on "Do". Actually some cases create a duplicate field. For example, a biblio record as : 600 $9 11 $a Son Goku 600 $9 12 $a Vegeta If you merge the authorities id=11 and id=12 into id=11 (creating Gogeta), you actually get : 600 $9 11 $a Son Goku 600 $9 11 $a Son Goku Having two identical fields linked to the same authority is useless. The same problem is even more frequent when merging two authorities of different type. -- You are receiving this mail because: You are watching all bug changes.

1 15

[Bug 8190] New: Koha does not have a logging module
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8190 Priority: P5 - low Change sponsored?: --- Bug ID: 8190 Assignee: gmcharlt(a)gmail.com Summary: Koha does not have a logging module Severity: enhancement Classification: Unclassified OS: All Reporter: jonathan.druart(a)biblibre.com Hardware: All Status: NEW Version: unspecified Component: Architecture, internals, and plumbing Product: Koha I would be great to specify a log level (to differentiate production and development environment for example). -- You are receiving this mail because: You are watching all bug changes.

1 144

[Bug 13413] New: Koha::Log - an attempt to have sane logging in Koha
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=13413 Bug ID: 13413 Summary: Koha::Log - an attempt to have sane logging in Koha Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: srdjan(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org Koha is painfully lacking logging infrastructure. This is an attempt to retrofit one. It is based on Log::Contextual rather than Log::Log4Perl for the sake of simplicity and efficiency. This is a discussion bite. -- You are receiving this mail because: You are watching all bug changes.

1 27

[Bug 10998] New: code duplication introduced by Z39.50 authority search
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10998 Bug ID: 10998 Summary: code duplication introduced by Z39.50 authority search Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: P5 - low Component: Architecture, internals, and plumbing Assignee: gmcharlt(a)gmail.com Reporter: gmcharlt(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org Bug 10096, which introduces a feature to import authority records via Z39.50, also introduces some code duplication. To summarize the differences: - z3950_search.pl and z3950_auth_search.pl differ only in the input search attributes they accept - C4::Breeding::ImportBreeding() and C4::Breeding::ImportAuth() do mostly the same thing - the actual search logic in C4::Breeding::Z3950SearchAuth() and C4::Breeding::Z3950Search() is the same; the two routines differ only in the specific Z39.50 attributes they handle and in some details of post-retrieval record processing. Also, Z3950SearchAuth() does not reflect the work that was done for bug 10462. Consequently, there is plenty of opportunity for code consolidation, as well as adding unit tests. -- You are receiving this mail because: You are watching all bug changes.

1 2

[Bug 8582] New: NULL issuedates with offline circ
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8582 Priority: P5 - low Change sponsored?: --- Bug ID: 8582 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: NULL issuedates with offline circ Severity: enhancement Classification: Unclassified OS: All Reporter: melia(a)bywatersolutions.com Hardware: All Status: NEW Version: rel_3_8 Component: Circulation Product: Koha We don't think offline circ works quite right with 3.8. It may be a date vs. datetime problem, perhaps? After processing offline circ files in 3.8, we have seen some NULL issues.issuedate. We discovered these after seeing the following error occur when going to the check-out screen. Software error: Can't call method "strftime" on an undefined value at /home/koha/kohaclone/Koha/DateUtils.pm line 117 -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 6

[Bug 11629] New: Add ability to update not for loan status on checkin
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=11629 Bug ID: 11629 Summary: Add ability to update not for loan status on checkin Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Circulation 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, kyle.m.hall(a)gmail.com Some libraries would like to streamline the cataloging process my automatically updating notforloan values on checkin. For example, an item is set to notforloan of -1 ( ordered ). The item, is received, processed, and checked in for the first time before being shelved. The checkin automatically changes the nfl value from -1 to 0. The same workflow could be used for damaged items as well. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 50

[Bug 7372] New: RoadTypes should be folded into Authorised Values
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7372 Bug #: 7372 Summary: RoadTypes should be folded into Authorised Values Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: ian.walls(a)bywatersolutions.com ReportedBy: ian.walls(a)bywatersolutions.com QAContact: jonathan.druart(a)biblibre.com The current data structure for Road Types is essentially the same as for Authorised Values, but it gets it's own admin page and database table. In an effort to simply both the Koha data structure, and the admin main page, I suggest moving this into Authorised Values. This development is marked as "(OUEST-PROVENCE)". Is there a reason for the separate table and admin page that I don't understand, (not being in a European library)? -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching all bug changes.

1 29

[Bug 12616] New: Locale in subscriptions should not default to English when empty
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=12616 Bug ID: 12616 Summary: Locale in subscriptions should not default to English when empty Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: katrin.fischer(a)bsz-bw.de QA Contact: testopia(a)bugs.koha-community.org The locale field in subscriptions currently defaults to empty, with a note that in this case English will be used automatically. If it really defaults to English, then it would make sense to offer an option to preselect it to the currently selected template language or to a language chosen in configuration. -- You are receiving this mail because: You are watching all bug changes.

1 24

[Bug 10866] New: Books entered in malayalam language cannot to search
by bugzilla-daemon＠bugs.koha-community.org 21 Jul '15

21 Jul '15

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10866 Bug ID: 10866 Summary: Books entered in malayalam language cannot to search Change sponsored?: --- Product: Koha Version: 3.12 Hardware: PC OS: Linux Status: NEW Severity: critical Priority: P5 - low Component: Searching Assignee: gmcharlt(a)gmail.com Reporter: sameer(a)kvasu.ac.in QA Contact: testopia(a)bugs.koha-community.org Sir, Prior to install 3.12, i was using 3.2 and i could search the terms in malayalam language. Now in 3.12 I cannot search the titles in malayalam, but it is ok in English. is there any solution -- You are receiving this mail because: You are watching all bug changes.

1 5