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

[Bug 929] See details of a budget
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '12

17 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=929 Status|Pushed to Master |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7359] New: Begin migration to a new "Koha" namespace from the old "C4" namespace
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '12

17 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7359 Bug #: 7359 Summary: Begin migration to a new "Koha" namespace from the old "C4" namespace Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Architecture, internals, and plumbing AssignedTo: gmcharlt(a)gmail.com ReportedBy: cnighswonger(a)foundations.edu QAContact: ian.walls(a)bywatersolutions.com 2011/3/30 Ian Walls <ian.walls at bywatersolutions.com>: > All this indicate to me that we REALLY need to start thinking about imposing > some kind of structure on C4. I'm thinking something with two-levels: > > Level 1 : Calls to the database, other direct interaction with stored data > Level 2: Calls to Level 1 functions to manipulate data Thanks for doing the analysis. Regarding the overall project of restructuring C4, I suggest a slightly different way of looking at it: *not* restructuring C4 as such, but using it as a springboard for its successor. In other words, we'd still be creating a better structure, just in a different namespace. Let's pick a name randomly for that namespace. I reach into my hat and pull out ... "Koha". Fancy that. :) The Koha namespace would be for Perl modules that meet the following mandatory conditions: - usable by mod_perl (or its equivalent) - export the minimum number of routines necessary - follow stricture, warnings, documentation, and test case standards - separating data access methods from business logic and preferably the following optional conditions: - purely OO Obviously, the conditions and whether they would be mandatory or optional is a topic for discussion. Modules in C4 could use (and would be encouraged to use) routines in the Koha namespace. Modules in Koha could not in general use C4 modules; any C4 module that was safe to be depended on by a Koha module would be a candidate for being renamed to Koha. The advantage of carving out a new namespace is that it doesn't require that we refactor the entirety of C4 to support persistance or to untangle the dependency tree. Instead, the only C4 code we would have to reimplement for the Koha namespace right away would be authentication, basic session management, and basic output. That, along with data access using DBIx::Class, would allow us to start using mod_perl right away for specific functions. One example of something that would then be easy to transform to a service running under mod_perl would be the unapi and OAI-PMH services. As functionality gets detangled from C4 and moved into Koha, we can increase the number of services running under mod_perl while still keeping the CGI scripts that still depend on C4. Regards, Galen -- 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 21

[Bug 7546] New: Cannot view subscription detail - bareword error
by bugzilla-daemon＠bugs.koha-community.org 17 Mar '12

17 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7546 Bug #: 7546 Summary: Cannot view subscription detail - bareword error Classification: Unclassified Change sponsored?: --- Product: Koha Version: rel_3_8 Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P1 - high Component: Serials AssignedTo: paul.poulain(a)biblibre.com ReportedBy: wizzyrea(a)gmail.com QAContact: koha.sekjal(a)gmail.com Bareword "C4::Search::enabled_staff_search_views" not allowed while "strict subs" in use at /home/wizzyrea/kohaclone/serials/subscription-detail.pl line 146. Execution of /home/wizzyrea/kohaclone/serials/subscription-detail.pl aborted due to compilation errors. -- 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 22

[Bug 1817] pagination links disrupt display on large result sets
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '12

15 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=1817 --- Comment #1 from delaye <stephane.delaye(a)biblibre.com> --- Created attachment 8211 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8211&action=edit file iso unimarc with notices bib for test (block 10%) -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2505] enable Perl warnings in all modules and scripts
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '12

15 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2505 --- Comment #10 from Mason James <mtj(a)kohaaloha.com> --- (In reply to comment #8) > The following .pl and .pm files are still missing the use warnings directive: > C4/SIP/xmlparse.pl > acqui/check_budget_total.pl > acqui/fetch_sort_dropbox.pl ... heya Jared, out of curiosity - whats the command or script used to generate this list? -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2505] enable Perl warnings in all modules and scripts
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '12

15 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2505 Mason James <mtj(a)kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |Needs Signoff -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2505] enable Perl warnings in all modules and scripts
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '12

15 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2505 Mason James <mtj(a)kohaaloha.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|Pushed to Master |ASSIGNED CC| |mtj(a)kohaaloha.com -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 2505] enable Perl warnings in all modules and scripts
by bugzilla-daemon＠bugs.koha-community.org 15 Mar '12

15 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=2505 --- Comment #9 from Mason James <mtj(a)kohaaloha.com> --- Created attachment 8209 --> http://bugs.koha-community.org/bugzilla3/attachment.cgi?id=8209&action=edit Bug 2505 - enable Perl warnings in all modules and scripts enable warnings, and correct perlcritic's 'Loop iterator is not lexical' errors in C4/Ris.pm modified: C4/Ris.pm mason@xen1:~/g/head$ perlcritic ./C4/Ris.pm ./C4/Ris.pm source OK applied to 49c387cddf6de083343fe6c88ad9f167844521b4 -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 3216] UNIMARC author facets
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '12

13 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=3216 --- Comment #18 from Frédéric Demians <frederic(a)tamil.fr> --- Thanks for pushing this patch and the ICU one. > However = wouldn't it be better to add 710a, 711a and 712a to authors ? Yes. I purposely haven't introduced facets building modification, except 700$b subfield (and 606$x). It's possible to easily improve facets (and also in MARC21). We may have another bug entry for that. UNIMARC: For 710, 711, and 712, with subfields abcdef, another solution is to create for them a separate Corporate author facet. Another improvement is for 6xx tags, that have important subfields. For example 606ajxyz. Librarians should decide. -- You are receiving this mail because: You are watching all bug changes.

1 0

[Bug 7638] New: one page notice for printing per student?
by bugzilla-daemon＠bugs.koha-community.org 13 Mar '12

13 Mar '12

http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=7638 Bug #: 7638 Summary: one page notice for printing per student? Classification: Unclassified Change sponsored?: --- Product: Koha Version: master Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 - low Component: Notices AssignedTo: henridamien(a)koha-fr.org ReportedBy: melia(a)bywatersolutions.com QAContact: koha.sekjal(a)gmail.com Our schools want a paper notice to send to students. They want it to print one 8 1/2 x 11 page per student. They want all fines, fees, and lost to be on one report. I did create a SQL report that is working, but the schools want to be able to print this out on one piece of paper per student. Below is the SQL statement I made: SELECT b.cardnumber, b.surname, b.firstname, g.attribute AS 'Grade', h.attribute AS 'Homeroom', a.date, a.description, a.accounttype, a.amount, a.amountoutstanding FROM borrowers b JOIN borrower_attributes g on (b.borrowernumber=g.borrowernumber) JOIN borrower_attributes as h ON (h.borrowernumber=b.borrowernumber) JOIN accountlines a ON (b.borrowernumber=a.borrowernumber) WHERE b.branchcode =<<Pick your library|branches>> AND a.date between <<Date Between (yyyy-mm-dd)>> and <<and (yyyy-mm-dd)>> AND g.code='GRADE' AND h.code='Homeroom' ORDER BY a.accounttype ASC Name (Last, First) or in 2 separate fields Student ID number Grade Homeroom (even if the homeroom field is blank) Item Title Date Checked Out Due Date Item Status Amount Due -- 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 5