- Koha - lists.katipo.co.nz

Running koha 3.04.01 on Ubuntu 10.04 64 Bit server edition without Zebra Index
by sunil.kumar＠ecoleglobal.com 19 Sep '11

19 Sep '11

Dear All, We have installed Koha 3.04.01 on Ubuntu 10.04 64 bit on a server. Even after migrating book database to koha, I am not able to see the detail on the OPAC or staff client's search interface. The Error is comming. IDZebra 2.0 is not installed, we tried to installed the same but in vain. Once again I like to clarify that we are installing KOHA 3.04.01 on Ubuntu 10.04 Lucid (64 bit server), MySQL 5.1.41, Perl 5.0.001 Apache 2.2.14. Please share your feedback. Thanks and Regards R Sunil Kumar Library Technologist

1 0

Report help needed
by Sue McMillan 19 Sep '11

19 Sep '11

Hello everyone, I need a report that shows the average age of our item collections at specific branches. I've looked at the pre-made sql reports on the Koha-Community pages but nothing there is useful for this report and I've also tried to make my own with no success. I would be grateful if someone could give guide me in the right direction. Regards Susan McMillan Acquisitions and Systems Librarian South Taranaki District Libraries 06 278 0555 or freecall 0800 111 323 ext 8706 ,sue.mcmillan(a)stdc.govt.nz http://www.southtaranaki.com This e-mail and any attachments may contain confidential and privileged information. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Any dissemination or use of this information by a person other than the intended recipient is unauthorised and may be illegal. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002. <p><b>CAN'T OPEN ATTACHMENTS?</b></p> The Council has upgraded to Microsoft office 2007 suite. This may mean you cannot open attachments if you have older versions of office. <a href="http://www.microsoft.com/downloads/details.aspx?familyid=941B3470-3AE9-4AEE…"> Click here to access Microsoft Office 2007's compatibility website.<a/>

1 0

AUTO: Boystown Library is out of the office (returning 03/10/2011)
by Library＠boystown.com.au 17 Sep '11

17 Sep '11

I am out of the office until 03/10/2011. I'm currently on leave until the 3 October. Please refer any urgent queries to John Dalgleish at jdalgleish(a)boystown.com.au. Cheers, Mandy Note: This is an automated response to your message Koha Digest, Vol 71, Issue 44 sent on 17/9/2011 10:00:01 AM. This is the only notification you will receive while this person is away.

1 0

Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/koha/lib/C4/Context.pm line 692.
by Vimal Kumar 16 Sep '11

16 Sep '11

Dear Friends, I got the following error when open Koha today, How to recover it? Software error: Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) at /usr/share/koha/lib/C4/Context.pm line 692. Compilation failed in require at /usr/share/koha/lib/C4/Auth.pm line 33. BEGIN failed--compilation aborted at /usr/share/koha/lib/C4/Auth.pm line 33. Compilation failed in require at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23. BEGIN failed--compilation aborted at /usr/share/koha/intranet/cgi-bin/mainpage.pl line 23. -- Vimal Kumar V. Mahatma Gandhi University Library Kottayam, Kerala- 686 560 Web: www.vimalkumar.org Blog: http://linuxhalwa.blogspot.com --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

2 1

3.4.x String Freeze
by Chris Nighswonger 16 Sep '11

16 Sep '11

Hi all, 3.4.x is presently in a string freeze preparing for the 3.4.5 release. The only string affecting patches that will be accepted at this point are blocker and security related bugs. Other patches will be pushed up to the release date. Kind Regards, Chris

1 0

KohaCon 2012 Survey
by BWS Johnson 15 Sep '11

15 Sep '11

Kia ora! Nengard has been so kind as to set us up a survey. http://survey.web2learning.net/limesurvey/index.php?sid=63529 So go vote and stuff. :) Cheers, Brooke

1 0

Can't call method "subfield" ERROR
by Pomorska škola 15 Sep '11

15 Sep '11

Hi all, I have Koha 3.04.04 installed on Ubuntu 10.04 and I'm getting the error Can't call method "subfield" on an undefined value at /usr/share/koha/lib/C4/Biblio.pm line 2835. on basically anything, Check In, Check Out, adding books and so on but even if there is an error, the operation seemingly completes successively. Now while I'm ready to go into production usage even with this error if despite it operations will be successfully done, but I would like to avoid having to fix at later date something that then turns out is a big problem. Also I have seen other posts detailing this bug. And most of them say that it's a problem with Marc to Koha mapping, and that I should check the mapping of the offending sub field, but how do I know WHICH sub field produces this error. Thanks in advance Maritime School Kotor -- View this message in context: http://koha.1045719.n5.nabble.com/Can-t-call-method-subfield-ERROR-tp480607… Sent from the Koha - Discuss mailing list archive at Nabble.com.

1 0

Barcode label printer not working
by swathi 15 Sep '11

15 Sep '11

Hi We are using koha 3.02 on ubuntu 10. We got a problem with the barcode label printer. We purchased Datamax oneill printer. The Drivers were also installed. When we give the print in quick spine label print, the printer was not printing anything. But the printer is working on the shell with lp command...... Is there anyone using the label printer and working good??? or is there any one got the same problem and solved Help me-Reg or please suggest which printer suits best on our environment. Thanks -- View this message in context: http://koha.1045719.n5.nabble.com/Barcode-label-printer-not-working-tp47970… Sent from the Koha - Discuss mailing list archive at Nabble.com.

2 2

Commentary on Paul's Koha 3.8 Release Manager proposal
by Ian Walls 14 Sep '11

14 Sep '11

Everyone, Enclosed is my response to Paul Poulain's proposal for Koha 3.8 Release Manager. The details of his document can be found here: http://wiki.koha-community.org/wiki/Proposal_paul_p_RM38 I thoroughly agree that the time has come to start thinking beyond the next stable release, and on to Koha 4.0. Those of you who have seen either my presentation at KohaCon 2010's hackfest or KUDOScon 2011 know I'm very excited about the possibilities of where we can take Koha in it's next major iteration. However, I disagree with a couple of the details of Paul's proposal. The major disagreement is with the timeline. The proposal as it stands is to start working on Koha 3.8 and Koha 4.0 in parallel, with Koha 3.8 releasing April 2012, and Koha 4.0 releasing Oct. 2012. I feel that going from Koha 3.8 directly to 4.0 is unwarranted. To my mind, there are many possible releases between 3.8 and 4.0, like 3.10, 3.12, 3.14 and so forth. This is supported by the actual database version numbers in Koha: the current release is actually 3.04.04; the zeros are squashed out for convenience. I would counter that, while we should continue releasing new features every 6 months on the 3.X line, Koha 4.0 should be defined by it's features. Paul's proposal calls several features to be key, including Solr integration, database abstraction, updated online help, improved authentication stack and automated tests. I agree that all these things are important and should be worked towards, but I'm not convinced they should be the sum total of the changes that define Koha 4.0 I would like to see the following in Koha 4.0: - arbitrary metadata formats (beyond MARC) - arbitrary biblio relationships - full support for authority records, including uploading through the GUI, automatic linking, "explode" searching and more - improvements to the borrower data structure (fewer pre-defined data fields, more flexibility) - separation of "receiving" and "payment" in acquisitions - serials import and export (MFHD, prediction patterns, etc) - many, many more things I think that the community should meet and discuss what features are both desirable and reasonably likely to be completed in the next few years (is there interest by libraries to sponsor these developments, or from developers to code it "for fun"?). Once a feature set is agreed on to "define" Koha 4.0, the developers of these features would meet to hash out what underlying structural changes would be required to make them happen. Hopefully commonalities could be found, so that the underlying structure could be developed in a way that accommodates multiple developments at once. Identifying these prerequisite changes early on would reduce the difficulties of rebasing developments, since we'd all be working off a similar set of base assumptions. It would also provide a reasonable basis for excluding or delaying developments that don't fit into the overall plan. Once the features were chosen and a framework for their development agreed upon, it would be time to code. The development and submission process would be the same as it is now (basing patches off master and submitting to the patches listserv and Bugzilla). As new features become ready, they would be incorporated into the time-based 3.X releases by the release manager for that particular cycle. This way, what works is made available, and what needs more time continues to be tested until it's stable for production use. Once all the agreed upon features were ready, it would be time to release Koha 4.0. Hopefully, that would be with 1-2 years, but there would be flexibility here. One of my other issues with the proposal was the "lightening" of Quality Assurance standards for the first 3 months of the 3.8 release cycle. If operating under the 1 year time frame for Koha 4.0 as outlined in Paul's proposal, this would seem necessary in order to get everything included in time. Unfortunately, while the next 3 months would be dedicated to clean up of features rolled in, there is never any guarantee of bug fixes being generated in a timely fashion. You cannot force people to write or sign off on bug fixes; we're all free agents here. So code that has not been rigourously tested could get in and stay in for a long time, long after 4.0 would release, because no one knows how to test it or fix it. However, if we operate under my proposed model, all code could continue to operate under the same quality assurance standards, and nothing that is broken or otherwise incomplete would make it in until it was ready. Releases would still come out every 6 months, even if a major development was inoperable, until that development could be completed. This has been a long email, so let me sum up. I think: - we should continue to release Koha 3.8, 3.10, 3.12 etc on 6 month cycles using the current community practices for feature inclusion - we should, as a community, meet and decide what features we want to define Koha 4.0 - the developers of those features should get together and come up with a unified plan for accomplishing them all, in a way that requires minimal rebasing - as new features become stable and tested, they should be folded into the 3.X line until all the features defined as "Koha 4.0" are ready - Once all the agreed upon features are complete, Koha 4.0 is then released. I've already gotten some feedback on this in today's Koha IRC meeting, but I'd very much like to hear what the rest of the community thinks about this, particular in relation to Paul's proposal for 3.8 Release Manager. Our time is limited for discussion, as the election time draws near, but hopefully I've made my thoughts clear enough for a dialogue to get started. Please let me know if I've been at all unclear. Cheers, -Ian -- Ian Walls Lead Development Specialist ByWater Solutions Phone # (888) 900-8944 http://bywatersolutions.com ian.walls(a)bywatersolutions.com Twitter: @sekjal

3 2

3.4.4 Perl upgrade/rebuilding perl-modules
by Perch 14 Sep '11

14 Sep '11

I upgraded my Perl (compiled a new version from source) from 5.8.8 to 5.14.1, because evidently Koha 3.4.4 needs a newer version of Perl than 5.8.8. Now I'm having problems getting some of the required CPAN modules to install. First of all: HTTP::OAI wants a newer version of XML::SAX::Base. I have version 1.02, while HTTP::OAI wants 1.04. However, when I try to upgrade it using CPAN, all I get is a message saying: "XML::SAX::Base is up to date (1.02)." So, no newer version available on CPAN? Secondly: PDF::Reuse::Barcode wants Barcode::Code128, which it tries to automatically install. However the installation fails (it fails if I try the install Barcode::Code128 manually too): Going to read '/root/.cpan/Metadata' Database was generated on Thu, 08 Sep 2011 09:28:48 GMT Running install for module 'Barcode::Code128' Running make for W/WR/WRW/Barcode-Code128-2.01.tar.gz Checksum for /root/.cpan/sources/authors/id/W/WR/WRW/Barcode-Code128-2.01.tar.gz ok CPAN.pm: Going to build W/WR/WRW/Barcode-Code128-2.01.tar.gz Checking if your kit is complete... Looks good Writing Makefile for Barcode::Code128 Writing MYMETA.yml cp lib/Barcode/Code128.pm blib/lib/Barcode/Code128.pm Manifying blib/man3/Barcode::Code128.3 WRW/Barcode-Code128-2.01.tar.gz /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/lib/perl5/perl-5.14.1/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/barcode.t .. ok t/gif.t ...... skipped: (no reason given) t/png.t ...... skipped: (no reason given) Test Summary Report ------------------- t/gif.t (Wstat: 0 Tests: 1 Failed: 1) Failed test: 1 Parse errors: Bad plan. You planned 0 tests but ran 1. t/png.t (Wstat: 0 Tests: 1 Failed: 1) Failed test: 1 Parse errors: Bad plan. You planned 0 tests but ran 1. Files=3, Tests=4, 0 wallclock secs ( 0.05 usr 0.00 sys + 0.04 cusr 0.01 csys = 0.10 CPU) Result: FAIL Failed 2/3 test programs. 2/4 subtests failed. make: *** [test_dynamic] Error 255 WRW/Barcode-Code128-2.01.tar.gz /usr/bin/make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports WRW/Barcode-Code128-2.01.tar.gz Running make install make test had returned bad status, won't install without force Thirdly, the installtion of Schedule::At fails: Going to read '/root/.cpan/Metadata' Database was generated on Thu, 08 Sep 2011 09:28:48 GMT Running install for module 'Schedule::At' Running make for J/JO/JOSERODR/Schedule-At-1.13.tar.gz Checksum for /root/.cpan/sources/authors/id/J/JO/JOSERODR/Schedule-At-1.13.tar.gz ok CPAN.pm: Going to build J/JO/JOSERODR/Schedule-At-1.13.tar.gz Checking if your kit is complete... Looks good Writing Makefile for Schedule::At Writing MYMETA.yml and MYMETA.json cp At.pm blib/lib/Schedule/At.pm Manifying blib/man3/Schedule::At.3 JOSERODR/Schedule-At-1.13.tar.gz /usr/bin/make -- OK Running make test PERL_DL_NONLAZY=1 /usr/lib/perl5/perl-5.14.1/bin/perl "-MExtUtils::Command::MM" "-e" "test_harness(0, 'blib/lib', 'blib/arch')" t/*.t t/t1.t .. 1/9 # Failed test 2 in t/t1.t at line 45 # t/t1.t line 45 is: ok(!$rv && ((scalar(keys %beforeJobs)+1) == scalar(keys %afterJobs))); # Failed test 3 in t/t1.t at line 48 # t/t1.t line 48 is: ok(%atJobs); # Test 4 got: <UNDEF> (t/t1.t at line 51) # Expected: "/thisIsACommand/" # t/t1.t line 51 is: ok($content, '/thisIsACommand/'); # Test 6 got: "" (t/t1.t at line 73) # Expected: "/^(_TEST_tag1)+$/" # t/t1.t line 73 is: ok(join('', map { $_->{TAG} } values %tag1Jobs), '/^(_TEST_tag1)+$/'); # Test 7 got: <UNDEF> (t/t1.t at line 76) # Expected: "/testCMD2/" # t/t1.t line 76 is: ok($content2, '/testCMD2/'); # Test 8 got: <UNDEF> (t/t1.t at line 77) # Expected: "/testCMD3/" # t/t1.t line 77 is: ok($content2, '/testCMD3/'); t/t1.t .. Failed 6/9 subtests Test Summary Report ------------------- t/t1.t (Wstat: 0 Tests: 9 Failed: 6) Failed tests: 2-4, 6-8 Files=1, Tests=9, 0 wallclock secs ( 0.03 usr 0.01 sys + 0.04 cusr 0.07 csys = 0.15 CPU) Result: FAIL Failed 1/1 test programs. 6/9 subtests failed. make: *** [test_dynamic] Error 255 JOSERODR/Schedule-At-1.13.tar.gz /usr/bin/make test -- NOT OK //hint// to see the cpan-testers results for installing this module, try: reports JOSERODR/Schedule-At-1.13.tar.gz Running make install make test had returned bad status, won't install without force I tried installing ExtUtils::Command::MM, which went ok, but didn't help any. -- View this message in context: http://koha.1045719.n5.nabble.com/3-4-4-Perl-upgrade-rebuilding-perl-module… Sent from the Koha - Discuss mailing list archive at Nabble.com.

4 5