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

[Bug 10522] New: Javascript error on acquisition pages: YAHOO is not defined
by bugzilla-daemon＠bugs.koha-community.org 27 Aug '13

27 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10522 Bug ID: 10522 Summary: Javascript error on acquisition pages: YAHOO is not defined Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: major Priority: P5 - low Component: Templates Assignee: oleonard(a)myacpl.org Reporter: jonathan.druart(a)biblibre.com git bisect tells me that bug 9779 introduces a javascript issue in some acquisition pages. To reproduce: - open Firebug - go to acqui/addorderiso2709.pl I don't know if the guilty code in js/acq.js can be removed. -- You are receiving this mail because: You are watching all bug changes.

1 14

[Bug 10719] New: UT GetUpcomingDueIssues
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '13

26 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10719 Bug ID: 10719 Summary: UT GetUpcomingDueIssues Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Test Suite Assignee: gmcharlt(a)gmail.com Reporter: tomascohen(a)gmail.com QA Contact: testopia(a)bugs.koha-community.org C4::Circulation::GetUpcomingDueIssues needs some unit tests. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 2500] Standing enhancement request for adding/updating call number splitting algorithms in C4/Labels.pm
by bugzilla-daemon＠bugs.koha-community.org 26 Aug '13

26 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2500 David Cook <dcook(a)prosentient.com.au> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dcook(a)prosentient.com.au --- Comment #18 from David Cook <dcook(a)prosentient.com.au> --- So I've recently encountered a call number like this: 361.250994 REP NO. 11/10 The section "361.250994" is DDC, I believe. However, "REP NO. 11/10" is entirely local. When printing labels and splitting call numbers, the slash between 11 and 10 gets removed using _split_ddcn. This isn't desirable, so I opted to use a different splitting sub. However, if I use _split_ccn, "REP NO. 11/10" gets turns into "REP NO. 11 /10", which is also undesirable, as that means "11" gets printed on one line and "/10" gets printed on the next. This is due to some regexp found in _split_ccn, which pulls apart the last element in the @parts array. Is there are a reason why the last element in the array is being pulled apart like this? I used git blame but the original 2009 commit message from Chris Nighswonger didn't really tell me much. I'm sure there is a reason, but it might make more sense for this - or another - sub to just split on spaces. -- Another thought...currently there is no way to associate splitting subs with call number classification schemes. The only way I see is to hardcode it into Label.pm. Perhaps it would be an idea to specify the call number splitting rule in the "Classification sources" part of the Administration module. This could be useful in several contexts. For instance, we're currently using the _split_lccn sub for LCC and NLM, but it could also be useful for the KF Modified classification scheme (which is a legal scheme based on LCC) and other schemes. KDC (Korean Decimal Classification) would also probably use DDC. Admittedly, since the behaviours are likely the same, people using KF Modified or KDC should probably just use "LCC" or "DDC" as classification sources rather than making new ones, so perhaps I don't actually have a good point there :p. However...there might be times when a library wants to use the DDC filing rules but have call number splitting just on spaces. Like in the above case where they want to preserve those local slashes. I don't know. Just a thought. I've already set up "z" to use _split_ccn in the past. I might adjust it so that it uses a different sub which just split on spaces... -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 10780] New: Updatedatabase updates permission labels incorrectly
by bugzilla-daemon＠bugs.koha-community.org 25 Aug '13

25 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10780 Bug ID: 10780 Summary: Updatedatabase updates permission labels incorrectly Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Installation and upgrade (web-based installer) Assignee: koha-bugs(a)lists.koha-community.org Reporter: liz(a)catalyst.net.nz QA Contact: testopia(a)bugs.koha-community.org CC: gmcharlt(a)gmail.com The stock descriptions of permissions are correct, but an updatedatabase stanza updates two of them to be identical when they shouldn't be. Patch incoming. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 0

[Bug 10779] New: Keyword Highlighting highlights partial words
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '13

22 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10779 Bug ID: 10779 Summary: Keyword Highlighting highlights partial words Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: OPAC Assignee: oleonard(a)myacpl.org Reporter: martin.renvoize(a)ptfs-europe.com QA Contact: testopia(a)bugs.koha-community.org I'm not 100% sure this is a bug or a 'feature'.. If you do a search on "Chitty on contracts" for example, every instance of 'Chitty' and 'on' is highlighted including the 'on' contained within 'contracts'. Surely the hole word 'contracts' should be highlighted and every occurrence of 'on' inside a word should not..? I've found that if you change the order of the search words to 'chitty contracts on' then you'll get 'contracts' highlighted correctly. but you will also still get 'on' within other words highlighted. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 9453] New: Update records acording to the new UNIMARCField100Language system preference
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '13

22 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=9453 Bug ID: 9453 Summary: Update records acording to the new UNIMARCField100Language system preference Classification: Unclassified Change sponsored?: --- Product: Koha Version: 3.8 Hardware: All OS: All Status: NEW Severity: enhancement Priority: P1 - high Component: Cataloging Assignee: gmcharlt(a)gmail.com Reporter: rolando.isidoro(a)gmail.com CC: m.de.rooy(a)rijksmuseum.nl Depends on: 8347 The solution to bug 8347 introduced a new system preference, UNIMARCField100Language, which allows us to set the value for the mandatory Language of cataloguing field in the UNIMARC field 100 builder form. Before this bug was fixed all values on that field were set to 'fre', so we need to update all the existing records to match the new system preference. -- You are receiving this mail because: You are watching all bug changes.

1 19

[Bug 10460] New: wait to stop a run away report
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '13

22 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=10460 Bug ID: 10460 Summary: wait to stop a run away report Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Reports Assignee: gmcharlt(a)gmail.com Reporter: nengard(a)gmail.com Right now the only way to stop a runaway report is to go in to the command line. It would be great if there were a button that the librarian could hit on the reports page to "kill" a report that's taking too long to run. -- You are receiving this mail because: You are watching all bug changes.

1 3

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '13

22 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 --- Comment #42 from Chris Cormack <chris(a)bigballofwax.co.nz> --- (In reply to Nicholas van Oudtshoorn from comment #40) > Sorry about the noise. Have created the new bug report (10777), and will > upload patch there shortly! A patch more than makes up for it, people can make as much noise as they want, if they also send patches ;) -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '13

22 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 --- Comment #41 from M. de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to Nicholas van Oudtshoorn from comment #40) > Sorry about the noise. Have created the new bug report (10777), and will > upload patch there shortly! Thx -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 1993] Task Scheduler Needs Re-write
by bugzilla-daemon＠bugs.koha-community.org 22 Aug '13

22 Aug '13

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1993 --- Comment #40 from Nicholas van Oudtshoorn <vanoudt(a)gmail.com> --- Sorry about the noise. Have created the new bug report (10777), and will upload patch there shortly! -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0