- Koha - lists.katipo.co.nz

Re: [Koha] Apache bandwidth tuning in default config
by MJ Ray 17 Aug '09

17 Aug '09

"Pablo A. Bianchi" <pbianchi(a)fi.uba.ar> > The purpose also was to know if someone think there is not a good idea > to made those changes, because is strange that being so simple nobody > say something about before. > Furthermore, this simples changes seems to be a very interesting > improve with an small effort, I was surprise no one responds (perhaps > it was a good reason). I didn't see it until now because it was sent to the wrong list (should have gone to koha-devel) and two copies soon together may have been misdetected as bulk mail. deflate - I think enabling this would mean that we end support for Apache 1.3. Is that OK? expires - I think this may mess up pre-production testing. PageSpeed - mentioned but I don't know where to get the mentioned files from. I think we should put deflate and expires into the default config file, but commented out with notes that the deflate is only for Apache httpd 2.x and that expires should only be enabled once you're finished messing with CSS and images. Does that sound right? -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op

3 2

Mahalya Havard est absente.
by Mahalya_Havard＠ssss.gouv.qc.ca 17 Aug '09

17 Aug '09

Je serai absent(e) du Lun 17-08-2009 au Mar 18-08-2009. Je répondrai à votre message dès mon retour, mercredi, le 19 août 2009. Merci.

1 0

Another 229 to 30 migration, again - items... a new twist?
by Andrew Séguin 17 Aug '09

17 Aug '09

I'm trying to do the migration from Koha 229 to Koha 30, and haven't yet experienced full success. First, upgrading in place didn't work out so well for some reason - I had copied the virtual machine's disk, so was able to revert quickly. After looking through the mailing lis, I then tried just running a Koha 30 system; imported the database of the 229 system and ran the upgrade scripts... this also didn't work out so well, "lazy me" just moved on once again. Finally, I took a koha 30 prebuilt virtual machine (time constraints, surely not because I'm a "lazy" system admin, right?) and imported the bibliographic entries. Through the web interface, it worked so-so, rejecting some "slices" (read: independent files with 1000 exported records from the 229 system) of the exported data... tried the bulkimport.pl script which rejected certain records as bad marc ... which I took (combined with some combing of the mail-group archives) as the reason behind the failure of the web interface. In the end, imported by the web interface or bulkimport.pl, I would end up with some biblios with the items all proper, some with the items not showing up properly (without call number). The Koha 30 system I'm using is the pre-built virtualbox machine 3.0 release -- version "Koha 3.0001005". Before running bulkimport, I recreated the same item-types and branches. Both systems are set to MARC21. I'm turning to the community here for some advice how to proceed / what to consider (I'm not afraid of research, scripting, or SQL... but a bit lost at the moment): * My first question would be, is there any trick, quick way, of knowing which biblios were rejected by bulkimport.pl ? I tried with "-v", "-v 2" without success to get more details. (sample/full command: nohup /home/koha/kohaclone/misc/migration_tools/bulkmarcimport.pl -d -v 2 -file ~/Koha20090811_02.mrc -commit 1 | tee ~/bulkimport_KOP20090811_2.log after having set PERL5LIB and KOHA_CONF) * My second question, is - are there any pointers/ideas concerning the import of items? Items that I consider properly imported have the call number displayed; where not, the call number is missing. In either case at least the barcode is correctly imported. Maybe somebody has a quick moment to look at the difference between the two and sees something obvious I don't? * Imported correctly: http://161.53.212.104/cgi-bin/koha/opac-detail.pl?biblionumber=820 * Not imported correctly: http://161.53.212.104/cgi-bin/koha/opac-detail.pl?biblionumber=9880 (was biblio 11874) I just (while writing this mail) found a difference looking at the records from Koha 229 and Koha 30: bibid 820 had under Koha 229 the "call number prefix" set to the same value as "call number" where 9880 doesn't. Maybe somebody has a comment about this (did I ignore something basic with the frameworks)? - I'll test the call number / call number prefix issue (either with marc-edit or directly in 229's database, for each item, copying the call-number to the call-number-prefix subfield value ...) within a day or two... Many thanks for all those in general who take the time work on Koha, even more to those who patiently read this entire email! Andrew

1 1

Re: [Koha] Difficulties encountered as a newbie in KOHA
by MJ Ray 17 Aug '09

17 Aug '09

Nadel Catura <caturan(a)canlubang.dlsu.edu.ph> > #1 On adding records, which we understand as the items in the library > itself such as books, Yes, we can add thru the module Cataloguing > Add > MARC Record, then Save and Add Item. However, when we try to access this > newly added item using the Search bar, we always get this message, > > No results found > Biblios in reservoir > None > > Is the item really not added in the Biblios Reservoir? > If so, how can we add this item to the Biblios Reservoir? > We are confused. Why would they be in the Reservoir? The Reservoir is a pool of records that you've uploaded into Koha in order to link those records to materials that you own. It is not the catalogue. If items appear to be adding OK, but can't be found in search, are you using the indexing server (zebra) and is it running and updating OK? This has to be configured separately from MySQL and Koha configuration. Look for zebrasrv in the process list and look for a cron job or scheduled task that runs a zebra pl script. To be more help, I suspect we'd need version numbers and a fuller description of the steps taken. > #2 On displaying all the records, which is we call here in our libraries > the "Accession Record", where can we view this? In "Reports" I think. Some Acquisitions reports are wizarded, but others can be created as custom reports. If you write a good custom report, please add it to http://wiki.koha.org/doku.php?id=sql_library Hope that helps, -- MJ Ray (slef) LMS developer and webmaster at | software www.software.coop http://mjr.towers.org.uk | .... co IMO only: see http://mjr.towers.org.uk/email.html | .... op

1 0

Difficulties encountered as a newbie in KOHA
by Nadel Catura 17 Aug '09

17 Aug '09

Good day! I am Nadel Catura from De La Salle Canlubang Philippines. We have installed our KOHA ILS for a several months now. After installation, up until this very moment, we are still on exploration stage. We have discovered the features are so useful to us. However, We haven't use it for official transactions in our Libraries because of some difficulties we are experiencing. #1 On adding records, which we understand as the items in the library itself such as books, Yes, we can add thru the module Cataloguing > Add MARC Record, then Save and Add Item. However, when we try to access this newly added item using the Search bar, we always get this message, No results found Biblios in reservoir None Is the item really not added in the Biblios Reservoir? If so, how can we add this item to the Biblios Reservoir? We are confused. #2 On displaying all the records, which is we call here in our libraries the "Accession Record", where can we view this? We are really looking forward on using it as our official Library system. So, your help is greatly appreciated. Thank you very much.

1 0

Apache bandwidth tuning in default config
by Tomás 17 Aug '09

17 Aug '09

I've been playing recently with some firefox extensions for web developers: FireBug: https://addons.mozilla.org/es-ES/firefox/addon/1843 PageSpeed: http://code.google.com/intl/es-ES/speed/page-speed/index.html YSlow: http://developer.yahoo.com/yslow/ and found that enabling certain options in the koha's apache VirtualHosts configuration would improve a lot koha's performance in bandwidth use. Only the opac startup page bandwidht usage goes from 368.5K to 118.3K. Enable http compression using mod_deflate --------------------------------------------------------------- Document this command for enabling this in Debian/Ubuntu # a2enmod deflate and add this lines to koha-http.conf in both VirtualHost definitions SetOutputFilter DEFLATE SetEnvIfNoCase Request_URI \.(?:gif|jpe?g|png)$ no-gzip I specify not to apply useless compression to compresed images. Further options could be used. See http://httpd.apache.org/docs/2.0/mod/mod_deflate.html Enable better caching features by setting explicit expiration far in the future for static content using mod_deflate ---------------------------------------------------------------------------------------------------------------------------------------------------------------- Document this command for enabling this in Debian/Ubuntu # a2enmod expires and add this lines to koha-http.conf in both VirtualHost definitions ExpiresActive On ExpiresDefault "modification plus 1 year" as mod_expires only applies to files in the filesystem it is safe to rely on modification date. This could be fine-tuned, for example on a per filetype basis (see http://httpd.apache.org/docs/2.0/mod/mod_expires.html) ----- PageSpeed in particular offers some recommendation on image sizes and provides an optimal image file for substitution. This could be analised. To+. -- Aparición con vida de Jorge Julio López.

3 3

CDS/ISIS records to MARC-21 for Koha
by Vimal Kumar 16 Aug '09

16 Aug '09

Dear Friends, I just prepared a documentation for the migration of bibliographic records in CDS/ISIS to MARC-21 using MarcEdit software. Many libraries are still using CDS/ISIS for record management and would like to convert their records to open source ILS like Koha. This document focuses on the conversion of CDS/ISIS data to MARC-21 for Koha. Migration from CDS/ISIS to MARC was not easy before. Certain useful scripts are now available for data migration between CDS/ISIS and Koha. Such processes are highly technical and not affordable for the library professionals who are not tech savvy. I hope that, this documentation will be helpful to convert your records from CDS/ISIS to Koha (ver. 3) open source ILS. I extent my thanks to Mr. Sandeep Bhavsar, Librarian, Dr.V.N.Bedekar Institute of Management Studies, Mumbai, who inspired me to write this documentation. I also extent my thanks to Mr. Amit Gupta, OSS Labs for editing this document. I expect your valuable feed back to enhance the usability of this document. You can access the document from the following link, http://isistomarc.pbworks.com -- Vimal Kumar V. Asst. Librarian Asian School of Business Technopark, Trivandrum-695 581 Web: www.vimalkumar.co.nr Blog: http://vimalkumar.oksociety.in OK Society Volunteer. http://oksociety.in --------------------------------------------------------------------------- "I forget what I was taught. I only remember what I have learnt" -Patrick White

2 1

Koha Training/Tutorials
by Nicole Engard 16 Aug '09

16 Aug '09

Per our August meeting, I set up the following page: http://wiki.koha.org/doku.php?id=en:documentation:tutorials Any suggestions on when to start? Or if you have a tutorial you want to add please go right ahead - the more the merrier. Nicole

1 0

Re: [Koha] Strange SAX error when searching
by Sophat Sam 16 Aug '09

16 Aug '09

Thanks! Problem solved! Running the script with --fix didn't do anything. I ran the script but it would escape every time it came across an error resembling the one I got before, but at least this time I knew which files and which lines were causing it, so I went through and made modifications to each file manually. Seems like it was a character issue. Once the script was able to run through without coming across any errors, I rebuilt with rebuild_zebra.pl -b -r -x and no more error! Thanks again for your suggestion. Best On Sat, Aug 15, 2009 at 8:26 AM, Galen Charlton<gmcharlt(a)gmail.com> wrote: > Hi, > > On Fri, Aug 14, 2009 at 7:41 PM, Sophat Sam<sophat.sam(a)gmail.com> wrote: >> Error: >> Field 500 must have at least one subfield at >> /usr/local/lib/perl5/site_perl/5.8.9/MARC/File/SAX.pm line 60 > > This probably indicates a glitch in one of your bib records - the > MARCXML from biblioitems.marcxml contain something like: > > <datafield tag="500" ind1=" " ind2=" "> > </datafield> > > To identify records with parsing errors, you can run the script > misc/cronjobs/MARC21_parse_test.pl. After checking the results, > running the sample script with the --fix option, then reindexing, may > correct the problem. > > Regards, > > Galen > -- > Galen Charlton > gmcharlt(a)gmail.com >

1 0

Strange SAX error when searching
by Sophat Sam 15 Aug '09

15 Aug '09

Hi, Recently I have been getting this error when I search with certain terms from the staff client as well as the OPAC. Don't know why. Any ideas? Error: Field 500 must have at least one subfield at /usr/local/lib/perl5/site_perl/5.8.9/MARC/File/SAX.pm line 60 Running Koha 3.01.00.037 with Perl version 5.008009. Other related modules and version numbers: MARC::Charset 0.98 MARC::Crosswalk::DublinCore 0.02 MARC::File::XML 0.88 MARC::Record 2.0.0 XML::Dumper 0.81 XML::LibXML 1.59 XML::LibXSLT 1.59 XML::RSS 1.32 I've installed most of these modules manually, without CPAN and made sure they all installed correctly. Everything had been working perfectly until I upgraded Koha (from 3.0 to below) and Perl (from 5.8.8 to 5.8.9). Best

2 1