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

[Bug 3462] Link see alsos in authorities
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '12

31 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3462 --- Comment #15 from Paul Poulain <paul.poulain(a)biblibre.com> --- Testing with UNIMARC before pushing, I can't see any difference before and after the patch. In AuthoritiesMarc.pm, there is some code related to that: if (C4::Context->preference('marcflavour') eq 'UNIMARC') { # construct UNIMARC summary, that is quite different from MARC21 one # accepted form foreach my $field ($record->field('2..')) { push @authorized } foreach my $field ($record->field('3..')) { push @notes } foreach my $field ($record->field('4..')) { push @seefrom } foreach my $field ($record->field('5..')) { push @seealso } I have 400 and 500 in my record (just freshly added, and can't see anything appearing :\ -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 8485] New: Make koha_perl_deps.pl batch friendly
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '12

31 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8485 Priority: P5 - low Change sponsored?: --- Bug ID: 8485 Assignee: gmcharlt(a)gmail.com Summary: Make koha_perl_deps.pl batch friendly Severity: enhancement Classification: Unclassified OS: All Reporter: tomascohen(a)gmail.com Hardware: All Status: NEW Version: master Component: Installation and upgrade (command-line installer) Product: Koha I propose adding a switch to the koha_perl_deps.pl script so it is more batch friendly. I propose -B (for batch) and make it output just the library name, preserving the other switches semantics. It could be useful to do things like: for k in $(for i in $(./koha_perl_deps.pl -m -B | perl -pi -e 's/::/-/g' | tr '[A-Z]' '[a-z]') do echo lib$i-perl done) do apt-cache search $k done (fix it) to maintain a list of debian packages needed, and stuff like that. -- You are receiving this mail because: You are watching all bug changes.

1 10

[Bug 8532] New: Old/iffy data causes error checking out
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '12

31 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=8532 Priority: P5 - low Change sponsored?: --- Bug ID: 8532 CC: gmcharlt(a)gmail.com, kyle.m.hall(a)gmail.com Assignee: koha-bugs(a)lists.koha-community.org Summary: Old/iffy data causes error checking out Severity: enhancement Classification: Unclassified OS: All Reporter: robin(a)catalyst.net.nz Hardware: All Status: NEW Version: rel_3_8 Component: Circulation Product: Koha In some cases (I don't really know the cause, but it doesn't matter) the issuedate in the 'old_issues' table ends up with NULL. In the case, there is an error when converting that date to the proper form during circulation (possibly happens elsewhere too, but that's where I saw it.) -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.

1 10

[Bug 4118] Add Collection Code to Statistics Table
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '12

31 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4118 Paul Poulain <paul.poulain(a)biblibre.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Passed QA |Failed QA --- Comment #15 from Paul Poulain <paul.poulain(a)biblibre.com> --- QA comment: I was about to push your patch (after squashing the 2 last follow-up and adding a removal of useless `` in updatedatabase), and, at the end, I won't, because I've found a tiny mistake: The update says: UPDATE statistics SET statistics.ccode = ( SELECT items.ccode FROM items WHERE statistics.itemnumber = items.itemnumber ) which seems OK OTOH you record a ccode only in Circulation.pm, which seems OK (you don't need to record the item ccode when a fine is paid, so nothing changed in C4::Accounts.pm) BUT: when you pay a fine because of a lost item, the itemnumber field *can* be set. In this case, you will have an itemnumber, but no ccode. Your updatedatabase will populate ccode anyway. So, 2 options: * populate ccode in Accounts.pm, when there is an item * UPDATE by discarding statistics.type='payment' or 'writeoff' (maybe there are other values, not 100% sure) Please choose and resubmit. I suggest you squash the 4 current patches, and add a follow-up for this QA question -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2060] Ability to import Authorities from Staff Client
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '12

31 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2060 --- Comment #19 from Kyle M Hall <kyle(a)bywatersolutions.com> --- (In reply to comment #18) > (In reply to comment #16) > > How can you possibly pass QA if you HAVEN'T TESTED IT!!!! > Shouting to volunteers in the QA team will not help you. Your tone is not > acceptable. So I will not even respond. But you did respond ; ) I do apologize if my reply came off as yelling. Tone doesn't really come through well when it comes to plain text. I was only trying to add emphasis. I do stand by what I wrote but I hope there are no hard feelings. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 4266] encumbrance and expenditure not used in code
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '12

31 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=4266 Koha Team Lyon 3 <koha(a)univ-lyon3.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |koha(a)univ-lyon3.fr --- Comment #4 from Koha Team Lyon 3 <koha(a)univ-lyon3.fr> --- I confirm that we except impatiently the budget freeze in the page neworderempty.pl when the amount remaining is lower than encumbrance. -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 1917] Add RSS Feeds for Lists
by bugzilla-daemon＠bugs.koha-community.org 31 Aug '12

31 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1917 Katrin Fischer <katrin.fischer(a)bsz-bw.de> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |katrin.fischer(a)bsz-bw.de -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 1917] Add RSS Feeds for Lists
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '12

30 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1917 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED Hardware|Macintosh |All Assignee|gmcharlt(a)gmail.com |oleonard(a)myacpl.org -- You are receiving this mail because: You are the QA Contact for the bug. You are watching all bug changes.

1 0

[Bug 2060] Ability to import Authorities from Staff Client
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '12

30 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2060 --- Comment #18 from M. de Rooy <m.de.rooy(a)rijksmuseum.nl> --- (In reply to comment #16) > How can you possibly pass QA if you HAVEN'T TESTED IT!!!! Shouting to volunteers in the QA team will not help you. Your tone is not acceptable. So I will not even respond. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2326] Help should be diff for each of the sys pref tabs
by bugzilla-daemon＠bugs.koha-community.org 30 Aug '12

30 Aug '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2326 Owen Leonard <oleonard(a)myacpl.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |gmcharlt(a)gmail.com Component|Documentation |System Administration Hardware|PC |All Assignee|paul.poulain(a)biblibre.com |koha-bugs(a)lists.koha-commun | |ity.org QA Contact|koha-bugs(a)lists.koha-commun | |ity.org | --- Comment #2 from Owen Leonard <oleonard(a)myacpl.org> --- Digging this up again, it seems like it would be simple to implement from the script side of things. We'd have to create a special case for admin/preferences where the query string was processed. After that, create separate preferences help files based on a simple pattern like "help/admin/preferences_staff_client.tt" Is isolating the query string a matter of a good regular expression, or might there be some existing URL-crunching code to use? -- You are receiving this mail because: You are the QA Contact for the bug. You are the assignee for the bug. You are watching all bug changes.

1 0