- Koha - lists.katipo.co.nz

A question
by Laura Ferreyra 07 Jul '04

07 Jul '04

Hi!, I'm a librarian and I work in a university library in Uruguay, South America. We are interested in working with koha. Now we have CDS/ISIS with Cepal format. We have first to change the databases format from Cepal to Marc. Is there anyone who have already done this?. I will really appreciate any previous experience, Best regards, Lic. Laura Ferreyra ORT University Central Library

2 1

isam and innodb usage
by David Everly 07 Jul '04

07 Jul '04

Hello, I'm curious to know what libraries generally use with Koha 2.0.0 MySQL: isam or innodb? (Google search hasn't revealed much) Also, is anyone using Postgres with 2.0.0? Thank you, Dave. -- Encrypted Mail Preferred: Key ID: 8527B9AF Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF Information: http://www.gnupg.org/ ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html

2 1

KOHA IN LANGUAGE ESPANISH
by Christian Calle 06 Jul '04

06 Jul '04

Hello. Excuses my native language is espanol. WE ARE IN a PROJECT TO MIGRATE the KOHA To ESPANOL, FIRST THAT BECAME WAS TO ELIMINATE the DIRECTORIES/koha-2.0.0/intranet/intranet-html/intranet- tmpl/default the DIRECTORIES/fr/pl and /zh-TW. I AM IN THE CORRECT WAY? IT KNOWS SOMEBODY ALGUN SIMILAR PROJECT? THANKS To ALL BEING BRILLIANT... CHRISTIAN CALLE Lapaz-Bolivia

2 2

Koha 2.0.0 Biblio Barcode
by David Everly 06 Jul '04

06 Jul '04

Using Koha 2.0.0, I want to confirm the expected barcode process (using MARC): 1. I should generate barcodes and affix them to all my items 2. After clicking "Add Biblio", I should scan the affixed barcode for adding each item. Is there an alternative process available. For instance, when adding 30 copies, to automatically generate and print the barcodes? -- Encrypted Mail Preferred: Key ID: 8527B9AF Key Fingerprint: E1B6 40B6 B73F 695E 0D3B 644E 6427 DD74 8527 B9AF Information: http://www.gnupg.org/ ASCII ribbon campaign: () against HTML email /\ against Microsoft attachments Information: http://www.expita.com/nomime.html

1 0

internal server error
by François Patte 06 Jul '04

06 Jul '04

Bonjour, I have just installed koha-2.1.0 and I get this error message. In the log files: Can't locate Net/LDAP.pm in @INC (@INC contains: Is an LDAP perl module missing? The installer didn't complain about it... I just want to use koha on this machine for testing and I do not require any LDAP authentification. Thank you. -- François Patte Ecole française d'Extrême-Orient - Pune - Inde Université René Descartes - Paris 5 UFR de mathématiques et informatique http://www.math-info.univ-paris5.fr/~patte

3 3

notes during koha 2.0 install
by Scott Scriven 05 Jul '04

05 Jul '04

Hello. I installed koha 2.0.0 about a month ago, and wrote down some info about my experiences with it afterward. I began the process as a complete koha newbie, though I've been a *nix sysadmin for nearly a decade. Anyway, I'm providing these notes in hopes it will help the koha developers: Installation experiences... I went to koha's main site and found a download link to sourceforge. Continuing, I found a tarball for koha-2.0.0, and grabbed it. After unpacking, I browsed the contents a bit. The README had very little info, and said to run the installer. No INSTALL file was provided. I don't like running downloaded executables on my system; who knows what they might do? Such a script might assume things which are not true about me, or my system. I probably didn't even have its dependencies satisfied, so I decided to get more information first. Suggestion: Create an INSTALL file, and list all dependencies in it. Also, describe what the installer script does, in detail. I looked at the koha site again, for installation info. It had a decent installation guide, here: http://www.koha.org/installation/quick-start.html I read the hints there, the faq, and the install guide. I located the debian packages for listed dependencies, and installed them. I got the rest of the deps from cpan, packaged them into .deb files, and installed them. Then I followed directions, and ended up without a working koha. This was partly because of a typo in apache's config, but mostly because I had tried to do as the install guide said. Suggestion: update the online docs to reflect the current version. Perhaps maintain them along with the koha source, and copy the files to the site whenever there is a new release. Or, at least, add a note to the online docs stating they do not apply to koha 2.0.0 or newer. Eventually, I decided to run the installer, as a throwaway user, to see what it did. It informed me about additional dependencies, so I located and/or built those again, as needed. Continuing on, I learned all about what the installer does, but it failed to set up the database correctly. I got enough errors that I couldn't scroll back to see where they started. ... I have a pretty long scrollback buffer. Anyway, the installer continued merrily along, having noticed nothing wrong. Suggestion: check for errors during installer operations. Other than the database errors, and the expected failure while trying to write to /etc, all went well. I decided to run it as root as soon as I got the database problem fixed. But, as it turns out, running as non-root was the problem. I discovered this after I found the koha IRC channel and chris helped me. (thanks!) It gets DB info from /etc instead of from the installer script, so failing to write /etc/koha.conf is fatal to the install. Suggestion: list the IRC channel somewhere on the main site; it was buried near the last hit on google. Suggestion: notify user that installer must be run as root. Or, add non-root installation capability. Or, abort install when writing to /etc fails, and explain why to the user. Continuing, I ran the installer as root, and it worked. It still printed a bunch of red text during the database portion, but none of it was errors. I then looked at the apache config it generated, merged parts into my apache config, and tested. On the first try, it failed, but then I fixed a typo from earlier, and it worked. :) -- Scott

2 2

Re: upgrade from 1.3.2 to 2.0
by Philippe Revault 02 Jul '04

02 Jul '04

>Date: Tue, 29 Jun 2004 15:36:31 -0500 >From: Robert Maynord <maynord(a)terracom.net> >To: KOHA <koha(a)lists.katipo.co.nz> >Subject: [Koha] upgrade from 1.3.2 to 2.0 > >Hello Koha Folks! > >It is summer, and time for our school KOHA upgrade from 1.3.2 to 2.0! I >have 2.0 installed and working on a new machine, and I have left the old >1.3.2 library machine in place -untouched- until I complete the >transition - just to be sure the data is safe. My plan is to save the >data on the old machine using mysqldump - then transfer it to the new >machine. > > IMH and not expert opinion I would (because I did so with some personnal datas) install a new 1.2.3 instance (using the sql dump) and run the upgrade with it. > >I have been promising our librarian an upgrade for a year now -- any >suggestions would be greatly appreciated! > > Be really carefull with setting the MARC parameters because the job is very long and some of your datas may be lost if you don't match correctly MARC structure and KOHA structure before you run updatedb2marc.pl. When you finished setting MARC structure you should save it (2 tables : marc_tag_structure and marc_subfield_structure) in order to be able to start again the all process without suffering once again. Regards, Philippe

1 0

MARC TAG STRUCTURE
by kanwaljit Dhindsa 01 Jul '04

01 Jul '04

PLEASE TELL ME WHERE I FIND OUT THE HELP ABOUT MARC TAG STRUCTURE PARAMETERS IN KOHA . HOW TO SET THEM,WHICH TAB IS USED FOR WHICH FIELD. Ms.KANWAL _________________________________________________________________ Transfer home loans now! http://go.msnserver.com/IN/51405.asp Home loans with 7.5% only.

2 1

Migrating from Athena -- Koha-MARC DB links
by Tim McMahon - West Liberty Public Library 01 Jul '04

01 Jul '04

Has anyone switched from Athena to Koha or are in the process? I could use some help with the MARC DB links. The problem I'm having is mapping the items fields. It looks like I should be mapping 852 here. On the item fields test I'm getting ALL items MUST: -be mapped to the same tag -and they must be in the 10 (items) tab Do I need to map all of the items from the drop-down menu? -- Tim McMahon Technical Services West Liberty Public Library http://www.wlpl.org

1 1

upgrade from 1.3.2 to 2.0
by Robert Maynord 01 Jul '04

01 Jul '04

Hello Koha Folks! It is summer, and time for our school KOHA upgrade from 1.3.2 to 2.0! I have 2.0 installed and working on a new machine, and I have left the old 1.3.2 library machine in place -untouched- until I complete the transition - just to be sure the data is safe. My plan is to save the data on the old machine using mysqldump - then transfer it to the new machine. As of my last inquiry about the process of upgrading (August 2003) there was no script that would completely handle the process. At that point, upgrading involved: * run update database * import MARC parameter tables * modify MARC parameter tables * run updatedb2marc.pl Should I still use this process? Would I start by importing my old database into mysql? Are the above commands included with 2.0? Are there documents available to help with the upgrade from 1.2.3 to 2.0? I have been promising our librarian an upgrade for a year now -- any suggestions would be greatly appreciated! Robert Maynord Immaculate Heart of Mary School

4 3