- Koha - lists.katipo.co.nz

Patron/Member management using npl theme/templates
by Adam Thick 16 Jan '06

16 Jan '06

Hi everyone, before I begin hacking my npl theme templates to fix a few problems I'm experiencing in the patron management section I was wondering if anyone else had come up against the following items or had fixed them, or am I missing something about the function of the patron management section? Adding a new institution takes me to the patron screen with a few missing items ( First Name, Second Name, etc... ) which are replaced with Institution Name. I enter the required info and then hit 'Add This Patron', I'm then taken to a screen which is for adding new institutions. So I fill in the information there too... What I'm wondering is which one is the right one to enter info into? is this a bug? The default templates do not reflect this functionality so I'm inclined to think it is. Does anyone else use the npl templates? They look nice, and I'm happy to edit the patron templates if something is a miss here, but if someone else has a fix already I'm also happy to remain lazy. It is also a bit confusing because institutional membership is reliant on creating the category 'Institution' and uses 'I' on creation of a member to figure out if it's a new member or institution... now wierd things happen if I create a borrower category called 'Individual' ;o). Cheers for any assistance, Adam Thick. -- Adam Thick Strategic Data Pty Ltd Ph : +61 (3) 9348-2013 Fax: +61 (3) 9348-2015 Mob: 0404 032 763 Email: Adam.Thick(a)StrategicData.com.au Web: http://www.StrategicData.com.au/ Post: P.O. Box 4262 Melbourne University, VIC 3052 Australia

1 0

z3950 YAZ Toolkit with debian sarge installation
by Amzari Abu Bakar 14 Jan '06

14 Jan '06

Haven't read email recently due to Hajj fiest. Additional info that might help, For debian woody installation, you might add the following lines in apt-get source files. > # for Yaz Toolkit > deb http://www.indexdata.dk/debian indexdata/woody released > deb-src http://www.indexdata.dk/debian indexdata/woody but for sarge installation, I change to deb http://www.indexdata.dk/debian indexdata/sarge deb-src http://www.indexdata.dk/debian indexdata/sarge It work find for me as z3950 seem to be working with the right version of YAZ Toolkit.(I have noticed that YAZ Toolkit version for sarge is different from woody). For UBUNTU installation, I haven't try it yet, since haven't have much time. In my opinion, UBUNTU origin from debian. Thus, it will not very much difference: i.e:you may try using Debian installation guidelines, install PERL, mysql, apache and YAZ Toolkit for debian distro. Hope this info can assist you. __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com

1 0

Error at Install.pm line 661 during install
by Mike D. 14 Jan '06

14 Jan '06

I'm hoping someone might be able to help me out with a curious installation problem. My first Koha setup was such a success (thanks to all the developers) I have another group that has asked me to do a setup for them. I wanted to do this install on OpenBSD so I gave 2.2.3 a try on OpenBSD 3.7. Other than compiling Yaz from source and a couple additional perl modules to install it's very similar to a RedHat setup. I got it working and then didn't have time to work on it for a while. When I got back to it OpenBSD 3.8 and Koha 2.2.4 was out so I repeated the same procedure and it worked again. I then decided to try and get it working in OpenBSD's Apache chroot jail so I reinstalled the OS and Koha to /var/www/koha. I found that getting Koha to run in the chroot was a difficult problem that didn't fit in my time frame so I decide I would just run Apache with the chroot disabled. I reinstalled OpenBSD again and started doing the production install and ran into the problem I mention below. I have since done a basic install again a number of times using the same procedure as before and also varying the order to see if makes a difference but with no success. The Problem: I run "perl installer.pl" and koha asks if I want to begin. I answer "enter", "Y", or "y". After this prompt it no longer asks for input and it's as if I've hit enter at every prompt and I get this error: Use of uninitialized value in scalar chomp at Install.pm line 661, <STDIN> line 1. It ends up in an endless loop in the following steps: DATABASE PASSWORD Please provide a good password for the user kohaadmin. IMPORTANT: You can log in using this user and password at any time. Password for database user kohaadmin: Use of uninitialized value in scalar chomp at Install.pm line 661, <STDIN> line 1. BLANK PASSWORD You must not use a blank password for your MySQL user. Press <ENTER> to try again: My Basic Installation steps (obvious to see I'm using an internal ftp server so you can't copy/paste all lines): Setup Packages/Ports export PKG_PATH=ftp://mirror.arcticnetwork.ca/pub/OpenBSD/3.8/packages/`machine - a`/:ftp://ftp.ca.openbsd.org/pub/OpenBSD/3.8/packages/`machine -a`/ Download, Compile, Install Yaz http://www.indexdata.dk/yaz/ cd /tmp && ftp ftp://192.168.0.10/pub/yaz/yaz-2.1.10.tar.gz tar xvzf yaz-2.1.10.tar.gz && cd /tmp/yaz-2.1.10 ./configure make && make install Install Perl Modules DO NOT INSTALL PDF::API2…… requires ver 0.3r77 perl -MCPAN -e 'install "MARC::Record"' perl -MCPAN -e 'install Event' perl -MCPAN -e 'install Net::Z3950' perl -MCPAN -e 'install Digest::MD5' perl -MCPAN -e 'install "HTML::Template"' perl -MCPAN -e 'install "Mail::Sendmail"' perl -MCPAN -e 'install "Date::Manip"' perl -MCPAN -e 'install "Convert::ASN1"' perl -MCPAN -e 'install "Compress::Zlib"' perl -MCPAN -e 'install "Net::LDAP"' have to install Net::LDAP twice unless Convert::ASN1 is installed first…don’t know if any of the optional components are needed Install PDF::API2 Ver 0.3r77 cd /tmp && ftp ftp://192.168.0.10/pub/perl/PDF-API2-0.3r77.tar.gz tar xvzf PDF-API2-0.3r77.tar.gz && cd /tmp/PDF-API2-0.3r77 perl Makefile.PL make && make install Install MySQL pkg_add -v mysql-server-4.0.24p1 /usr/local/bin/mysqld_safe & /usr/local/bin/mysqladmin -u root password 'newpassword' Koha Install cd /tmp && ftp ftp://192.168.0.10/pub/koha/koha-2.2.4.tar.gz tar xvzf koha-2.2.4.tar.gz && cd /tmp/koha-2.2.4 perl installer.pl /var/www/koha/opac /var/www/koha/intranet /var/www/koha/log Setup apache Add following to /var/www/conf/httpd.conf /etc/koha-httpd.conf To run apache without chroot httpd -u Summary: I've had Koha installed and working (without Apache chroot) several times. I've installed both from the console and via ssh and have the same problem. I've installed on two different computers. I get the error: Use of uninitialized value in scalar chomp at Install.pm line 661, <STDIN> line 1. Any help appreciated. Thanks!

1 1

modifying httpd.conf+500 Internal Server Error
by Wahyu Wijaya H. 13 Jan '06

13 Jan '06

I try again using apache2, and the password hashing problem amazingly "gone" and I don't know what have I done that made the problem solved.. :( (previously I have a password hashing problem) Then, I wrote a line on the bottom of httpd.conf: Include /etc/koha-httpd.conf and perl -I/usr/local/koha/intranet/scripts/misc/fines2.pl on crontab file, and added Listen 8080 on the ports.conf Then I run my firefox browser, and write http://yps-013:8080/ --my hostname is yps-013-- click "Go", and I got the old same apache2 page... :( With little desperate, I try http://localhost:8080/ and I got a Koha welcome... :) then I got a 500 Internal Server Error... :( (http://localhost:80/ give same result) ---------------------------------------------------------------------------------------------- Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator, koha(a)lists.katipo.co.nz and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. --------------------------------------------------------------------------------------------- What has happen? Do I made mistake when I edit the httpd.conf and crontab file? Please tell me what should I do to solve: 1. the confusion of "localhost" and hostname, because when I use http://yps-013:8080 the page comes up is the default apache2 page, and when I use http://localhost:8080/ I got a koha welcome message and the problem number 2. I check the koha-httpd.conf, the servername and virtual host is still yps-013. 2. the 500 Internal Server Error I also attach the error logs generated by apache2 and koha. Thanks. Best Regards, Wahyu W. H. --------------------------------- Yahoo! Messenger NEW - crystal clear PC to PC calling worldwide with voicemail

1 0

New french website... pre-release
by Henri-Damien LAURENT 13 Jan '06

13 Jan '06

Hi, A new version of the french website will be soon issued (next week). It is based on the international design. (Thanks, shaun, Russel, and all) And here is a comment I got from a french librarian : "Bravo pour l'esthétique, c'est beaucoup mieux !" Congratulations, it is far more beautiful ! So, Congratulations folks ;) If you have time to test it http://www.koha-fr.org/nversion/ Feel free to comment. Happy New Year. -- Henri-Damien LAURENT

1 0

Changing the user inteface of KOHA
by mohammed ihsan ps 11 Jan '06

11 Jan '06

Dear All, I mange to indtall the koha already. i am trying to change the koha interface so i found that a lot of templates inside.But i am trying to open that in dreamwaeaver but i can not open the user interface properly.can any one give me some usefull information to change the user interface of KOHA?. Thanks in Advance, Regards Ihsan On Wed, 11 Jan 2006 Alfred Vahau wrote : >Check out the Mysql manual at http://dev.mysql.com/doc/refman/5.0/en/ > >The link is for version 5 but links to other versions are also listed. > >The default username is root without a password. The manual shows how to enable a root password as well as create users with password access to the database. > >Alf, > >mohammed ihsan ps wrote: > >> dear all, >> >>my installing koha is successfull but i dont know the default username and password of mysql.can any one give me this information or some usefull websites where i can find this information >> >>Regards >>Ihsan >> >>On Wed, 11 Jan 2006 Wahyu Wijaya H. wrote : >> >Hi, you said you are now have installing koha on several linux distro. have you try to install koha on ubuntu linux? if you have, please share your experience with me. Thanks >> > >> > Regards, >> > Wahyu Wijaya H. >> > >> >Amzari Abu Bakar <amzari79(a)yahoo.com> wrote: hello to all, >> > >> >I have struggel past 3 month to install Koha. Now, my >> >effort seems to be fruitful. From an obidience Windows >> >user, I have become a Linux fans.. thanks to Koha for >> >opening my eyes to Open Source Solutions. Now I am >> >enjoying installing Koha on several Linux Distro. >> > >> >I have eventually faced a similar problems mentioned >> >by many of mailing list User before. I am not a goo >> >programmer or an experience System Analyst. But, maybe >> >the following guidelines can help you out there: >> > >> >1. Try to upgrade Apache version 1.3.33 to 2.0.xx (.54 >> >If I am not mistaken), as this will help you running >> >Perl Modules and Environment Variables without >> >problems.(It is working for me) You can use dpkg or >> >aptitude to do this. >> > >> >2. You need CLEAN installation of PERL modules >> >required by KOHA (using CPAN) without any disruption >> >or error message. Also for the YAZ toolkit, which can >> >be obtained from indexdata.dk. If you are using Sarge >> >installation, make sure, you downloads YAZ Toolkit ofr >> >Sarge package*. >> > >> >*Currently, I am using debian SARGE, while current >> >guidelines installing Koha in debian is for woody. So, >> >you need several adjustment for finding right package >> >for Debian Sarge, If you are using Sarge Installation. >> > >> >Thank you and enjoy Koha! >> > >> >--- koha-request(a)lists.katipo.co.nz wrote: >> > >> > > Send Koha mailing list submissions to >> > > koha(a)lists.katipo.co.nz >> > > >> > > To subscribe or unsubscribe via the World Wide Web, >> > > visit >> > > http://lists.katipo.co.nz/mailman/listinfo/koha >> > > or, via email, send a message with subject or body >> > > 'help' to >> > > koha-request(a)lists.katipo.co.nz >> > > >> > > You can reach the person managing the list at >> > > koha-owner(a)lists.katipo.co.nz >> > > >> > > When replying, please edit your Subject line so it >> > > is more specific >> > > than "Re: Contents of Koha digest..." >> > > >> > > >> > > Today's Topics: >> > > >> > > 1. To implement koha (javier(a)ayto-daganzo.org) >> > > 2. Re: I need to add a path to @INC for KOHA, >> > > how? (Stephen Hedges) >> > > 3. Re: I need to add a path to @INC for KOHA, >> > > how? (Andro Gagne) >> > > 4. Thanks all, but I am no closer to getting KOHA >> > > working.... >> > > (Marty Jongepier) >> > > 5. Z39.50 (javier(a)ayto-daganzo.org) >> > > 6. Shelflist report (David Miner) >> > > >> > > >> > > >> >---------------------------------------------------------------------- >> > > >> > > Message: 1 >> > > Date: Wed, 04 Jan 2006 00:48:10 +0100 >> > > From: "javier(a)ayto-daganzo.org" >> > > >> > > Subject: [Koha] To implement koha >> > > To: koha(a)lists.katipo.co.nz >> > > Message-ID: >> > > <20060103234810.6141.qmail(a)correo2.acens.net> >> > > Content-Type: text/plain; format=flowed; >> > > charset="iso-8859-1" >> > > >> > > Hello to all: >> > > We are implanting koha in a library in Daganzo, a >> > > town of España.This >> > > project we want it integramente to translate >> > > Spanish. We are having problem >> > > with script to pass the files tmpl to po in the part >> > > of opac. Can you pass >> > > somebody the file in format po of >> > > opac-tmpl/default/en to be able to >> > > translate it? >> > > Another problem that we are having is with Z39.50 >> > > and at the time of >> > > concerning registry marc of other libraries. Me >> > > podeis on the matter to >> > > pass information of like forming it? >> > > >> > > Happy 2006 >> > > >> > > >> > > ------------------------------ >> > > >> > > Message: 2 >> > > Date: Tue, 3 Jan 2006 18:58:24 -0500 (EST) >> > > From: "Stephen Hedges" >> > > Subject: Re: [Koha] I need to add a path to @INC for >> > > KOHA, how? >> > > To: "Andro Gagne" >> > > Cc: koha(a)lists.katipo.co.nz >> > > Message-ID: >> > > >> > > >> ><32802.65.24.138.126.1136332704.squirrel(a)webmail.skemotah.com> >> > > Content-Type: text/plain;charset=iso-8859-1 >> > > >> > > You don't normally need to worry about these >> > > environment variables, unless >> > > you are running one of the exceptional command-line >> > > scripts like >> > > bulkmarcimport.pl. The routine Koha functions >> > > should be no problem. >> > > >> > > When you do have some reason to run a special-use >> > > script like >> > > bulkmarcimport.pl, you somehow need to tell the >> > > script where you installed >> > > Koha. My Koha (and koha.conf and modules) may have >> > > been installed in a >> > > completely different location than yours. >> > > >> > > Stephen >> > > >> > > Andro Gagne said: >> > > > Mr. Laurent, >> > > > >> > > > At 09:32 AM 1/3/06 +0100, Henri-Damien >> > > Laurent wrote: >> > > > >> > > >>Normally, >> > > >>when using a koha script, you need to set two >> > > environment variables. >> > > >>PERL5LIB and KOHA_CONF >> > > >>KOHA_CONF contains the path to your koha.conf >> > > >>PERL5LIB the path to your koha >> > > directories/intranet/modules on a >> > > >>standard install. >> > > >> >> > > >>You can set them with export command as such : >> > > >>export KOHA_CONF=/path/to/koha.conf >> > > >>export PERL5LIB=/path/to/koha/intranet/modules >> > > >>And then you can launch your scripts. >> > > > >> > > > Thank you for your helpful reply. I >> > > understand that the setting >> > > > of these environment variables is necessary. That >> > > makes sense to me, and >> > > > I >> > > > don't have any problem with it. What I don't >> > > understand is why Mr. >> > > > Jongepier and I are having this problem in the >> > > first place. Either Koha >> > > > is >> > > > programmed to set these variables on its own when >> > > it is started up, or it >> > > > isn't. If it is supposed to set these variables >> > > when being started, why >> > > > is >> > > > it not doing so? I believe I followed the >> > > installation instructions very >> > > > faithfully, so I have reason to expect that Koha >> > > will start up properly >> > > > and >> > > > set the variables it needs to be set. If Koha is >> > > not programmed to set >> > > > these variables on its own when it is started up, >> > > clearly it is my >> > > > responsibility to set these variables. But if the >> > > latter is the case, why >> > > > didn't the installation instructions tell me this >> > > and tell me how the >> > > > variable setting needs to be done so that Koha's >> > > environment variables are >> > > > set up properly when Koha is started up? (I am >> > > referring to the >> > > > installation instructions that were available at >> > > www.kohadocs.org last >> > > > June.) All I'm trying to do is to understand >> > > where the real problem lies >> > > > so that, hopefully, I can fix the real >> > > problem--especially if I am the one >> > > > who caused the problem in some way--rather than >> > > applying what seems like a >> > > > Band-Aid and not understanding where things went >> > > wrong. The Band-Aid >> > > > approach probably will work for a while, but it is >> > > likely not to be as >> > > > good >> > > > a fix as fixing the underlying problem, especially >> > > as Koha gets upgraded >> > > > over time. >> > > > >> > > > I really want to show the museum--and >> > > other organizations that >> > > > cannot afford integrated library systems that have >> > > prices in the 5- or >> > > > 6-figure range--that Koha can do the job they need >> > > to be done. If you can >> > > > help me understand where the underlying problem is >> > > in regard to setting >> > > > environment variables for Koha, I will appreciate >> > > it very much. I would >> > > > be >> > > > glad to send any information needed about how I >> > > installed Koha to solve >> > > > this issue. Thank you for your patience and >> > > understanding. >> > > > >> > > > Andro P. Gagné >> > > > P.O. Box 715 >> > > > Canandaigua, NY 14424 >> > > > >> > > > >> > > > >> > > > _______________________________________________ >> > > > Koha mailing list >> > > > Koha(a)lists.katipo.co.nz >> > > > http://lists.katipo.co.nz/mailman/listinfo/koha >> > > > >> > > >> > > >> > > -- >> > > Stephen Hedges >> > > Skemotah Solutions, USA >> > > www.skemotah.com -- shedges(a)skemotah.com >> > > >> > > >> > > >> > > ------------------------------ >> > > >> >=== message truncated === >> > >> > >> > >> > >> >__________________________________________ >> >Yahoo! DSL - Something to write home about. >> >Just $16.99/mo. or less. >> >dsl.yahoo.com >> > >> >_______________________________________________ >> >Koha mailing list >> >Koha(a)lists.katipo.co.nz >> >http://lists.katipo.co.nz/mailman/listinfo/koha >> > >> > >> > >> > >> >--------------------------------- >> >To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. >> >_______________________________________________ >> >Koha mailing list >> >Koha(a)lists.katipo.co.nz >> >http://lists.katipo.co.nz/mailman/listinfo/koha >> >> >> >><http://adworks.rediff.com/cgi-bin/AdWorks/sigclick.cgi/www.rediff.com/signa…> >> >>------------------------------------------------------------------------ >> >>_______________________________________________ >>Koha mailing list >>Koha(a)lists.katipo.co.nz >>http://lists.katipo.co.nz/mailman/listinfo/koha >> >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha

4 3

Invalid command 'SetEnv'
by Ian Piper 11 Jan '06

11 Jan '06

Hi all, This is my first posting on this list, so apologies if this question is a FAQ. I am installing Koha on Mac OS X Server. All seems to have gone well, but on trying to start apache after "including" the koha- httpd.conf file I am seeing the following error: morse:~ admin$ apachectl start Processing config directory: /etc/httpd/sites/*.conf Processing config file: /etc/httpd/sites/0000_any_80_.conf Processing config file: /etc/httpd/sites/virtual_host_global.conf Syntax error on line 30 of /etc/koha-httpd.conf: Invalid command 'SetEnv', perhaps mis-spelled or defined by a module not included in the server configuration /usr/sbin/apachectl start: httpd could not be started The syntax looks OK, and I believe that I have an appropriate version of apache (1.3). Any guidance much appreciated. Thanks, Ian. -- Ian Piper Tellura Information Services - the web, document and information people http://www.tellura.co.uk/ 01926 811574 | 07973 156616 skype: ianmpiper --

1 1

Re: Re: [Koha] Guidelines for Koha Installation (Debian)
by mohammed ihsan ps 11 Jan '06

11 Jan '06

dear all, my installing koha is successfull but i dont know the default username and password of mysql.can any one give me this information or some usefull websites where i can find this information Regards Ihsan On Wed, 11 Jan 2006 Wahyu Wijaya H. wrote : >Hi, you said you are now have installing koha on several linux distro. have you try to install koha on ubuntu linux? if you have, please share your experience with me. Thanks > > Regards, > Wahyu Wijaya H. > >Amzari Abu Bakar <amzari79(a)yahoo.com> wrote: hello to all, > >I have struggel past 3 month to install Koha. Now, my >effort seems to be fruitful. From an obidience Windows >user, I have become a Linux fans.. thanks to Koha for >opening my eyes to Open Source Solutions. Now I am >enjoying installing Koha on several Linux Distro. > >I have eventually faced a similar problems mentioned >by many of mailing list User before. I am not a goo >programmer or an experience System Analyst. But, maybe >the following guidelines can help you out there: > >1. Try to upgrade Apache version 1.3.33 to 2.0.xx (.54 >If I am not mistaken), as this will help you running >Perl Modules and Environment Variables without >problems.(It is working for me) You can use dpkg or >aptitude to do this. > >2. You need CLEAN installation of PERL modules >required by KOHA (using CPAN) without any disruption >or error message. Also for the YAZ toolkit, which can >be obtained from indexdata.dk. If you are using Sarge >installation, make sure, you downloads YAZ Toolkit ofr >Sarge package*. > >*Currently, I am using debian SARGE, while current >guidelines installing Koha in debian is for woody. So, >you need several adjustment for finding right package >for Debian Sarge, If you are using Sarge Installation. > >Thank you and enjoy Koha! > >--- koha-request(a)lists.katipo.co.nz wrote: > > > Send Koha mailing list submissions to > > koha(a)lists.katipo.co.nz > > > > To subscribe or unsubscribe via the World Wide Web, > > visit > > http://lists.katipo.co.nz/mailman/listinfo/koha > > or, via email, send a message with subject or body > > 'help' to > > koha-request(a)lists.katipo.co.nz > > > > You can reach the person managing the list at > > koha-owner(a)lists.katipo.co.nz > > > > When replying, please edit your Subject line so it > > is more specific > > than "Re: Contents of Koha digest..." > > > > > > Today's Topics: > > > > 1. To implement koha (javier(a)ayto-daganzo.org) > > 2. Re: I need to add a path to @INC for KOHA, > > how? (Stephen Hedges) > > 3. Re: I need to add a path to @INC for KOHA, > > how? (Andro Gagne) > > 4. Thanks all, but I am no closer to getting KOHA > > working.... > > (Marty Jongepier) > > 5. Z39.50 (javier(a)ayto-daganzo.org) > > 6. Shelflist report (David Miner) > > > > > > >---------------------------------------------------------------------- > > > > Message: 1 > > Date: Wed, 04 Jan 2006 00:48:10 +0100 > > From: "javier(a)ayto-daganzo.org" > > > > Subject: [Koha] To implement koha > > To: koha(a)lists.katipo.co.nz > > Message-ID: > > <20060103234810.6141.qmail(a)correo2.acens.net> > > Content-Type: text/plain; format=flowed; > > charset="iso-8859-1" > > > > Hello to all: > > We are implanting koha in a library in Daganzo, a > > town of España.This > > project we want it integramente to translate > > Spanish. We are having problem > > with script to pass the files tmpl to po in the part > > of opac. Can you pass > > somebody the file in format po of > > opac-tmpl/default/en to be able to > > translate it? > > Another problem that we are having is with Z39.50 > > and at the time of > > concerning registry marc of other libraries. Me > > podeis on the matter to > > pass information of like forming it? > > > > Happy 2006 > > > > > > ------------------------------ > > > > Message: 2 > > Date: Tue, 3 Jan 2006 18:58:24 -0500 (EST) > > From: "Stephen Hedges" > > Subject: Re: [Koha] I need to add a path to @INC for > > KOHA, how? > > To: "Andro Gagne" > > Cc: koha(a)lists.katipo.co.nz > > Message-ID: > > > > ><32802.65.24.138.126.1136332704.squirrel(a)webmail.skemotah.com> > > Content-Type: text/plain;charset=iso-8859-1 > > > > You don't normally need to worry about these > > environment variables, unless > > you are running one of the exceptional command-line > > scripts like > > bulkmarcimport.pl. The routine Koha functions > > should be no problem. > > > > When you do have some reason to run a special-use > > script like > > bulkmarcimport.pl, you somehow need to tell the > > script where you installed > > Koha. My Koha (and koha.conf and modules) may have > > been installed in a > > completely different location than yours. > > > > Stephen > > > > Andro Gagne said: > > > Mr. Laurent, > > > > > > At 09:32 AM 1/3/06 +0100, Henri-Damien > > Laurent wrote: > > > > > >>Normally, > > >>when using a koha script, you need to set two > > environment variables. > > >>PERL5LIB and KOHA_CONF > > >>KOHA_CONF contains the path to your koha.conf > > >>PERL5LIB the path to your koha > > directories/intranet/modules on a > > >>standard install. > > >> > > >>You can set them with export command as such : > > >>export KOHA_CONF=/path/to/koha.conf > > >>export PERL5LIB=/path/to/koha/intranet/modules > > >>And then you can launch your scripts. > > > > > > Thank you for your helpful reply. I > > understand that the setting > > > of these environment variables is necessary. That > > makes sense to me, and > > > I > > > don't have any problem with it. What I don't > > understand is why Mr. > > > Jongepier and I are having this problem in the > > first place. Either Koha > > > is > > > programmed to set these variables on its own when > > it is started up, or it > > > isn't. If it is supposed to set these variables > > when being started, why > > > is > > > it not doing so? I believe I followed the > > installation instructions very > > > faithfully, so I have reason to expect that Koha > > will start up properly > > > and > > > set the variables it needs to be set. If Koha is > > not programmed to set > > > these variables on its own when it is started up, > > clearly it is my > > > responsibility to set these variables. But if the > > latter is the case, why > > > didn't the installation instructions tell me this > > and tell me how the > > > variable setting needs to be done so that Koha's > > environment variables are > > > set up properly when Koha is started up? (I am > > referring to the > > > installation instructions that were available at > > www.kohadocs.org last > > > June.) All I'm trying to do is to understand > > where the real problem lies > > > so that, hopefully, I can fix the real > > problem--especially if I am the one > > > who caused the problem in some way--rather than > > applying what seems like a > > > Band-Aid and not understanding where things went > > wrong. The Band-Aid > > > approach probably will work for a while, but it is > > likely not to be as > > > good > > > a fix as fixing the underlying problem, especially > > as Koha gets upgraded > > > over time. > > > > > > I really want to show the museum--and > > other organizations that > > > cannot afford integrated library systems that have > > prices in the 5- or > > > 6-figure range--that Koha can do the job they need > > to be done. If you can > > > help me understand where the underlying problem is > > in regard to setting > > > environment variables for Koha, I will appreciate > > it very much. I would > > > be > > > glad to send any information needed about how I > > installed Koha to solve > > > this issue. Thank you for your patience and > > understanding. > > > > > > Andro P. Gagné > > > P.O. Box 715 > > > Canandaigua, NY 14424 > > > > > > > > > > > > _______________________________________________ > > > Koha mailing list > > > Koha(a)lists.katipo.co.nz > > > http://lists.katipo.co.nz/mailman/listinfo/koha > > > > > > > > > -- > > Stephen Hedges > > Skemotah Solutions, USA > > www.skemotah.com -- shedges(a)skemotah.com > > > > > > > > ------------------------------ > > >=== message truncated === > > > > >__________________________________________ >Yahoo! DSL Something to write home about. >Just $16.99/mo. or less. >dsl.yahoo.com > >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha > > > > >--------------------------------- >To help you stay safe and secure online, we've developed the all new Yahoo! Security Centre. >_______________________________________________ >Koha mailing list >Koha(a)lists.katipo.co.nz >http://lists.katipo.co.nz/mailman/listinfo/koha

2 1

Z39.50
by javier＠ayto-daganzo.org 11 Jan '06

11 Jan '06

Hello to all: We are implanting koha in a library in Daganzo, a town of España.This project we want it integramente to translate Spanish. We are having problem with script to pass the files tmpl to po in the part of opac. Can you pass somebody the file in format po of opac-tmpl/default/en to be able to translate it? Another problem that we are having is with Z39.50 and at the time of concerning registry marc of other libraries. Can you on the matter to pass information of like forming it? Happy 2006

3 5

Guidelines for Koha Installation (Debian)
by Amzari Abu Bakar 10 Jan '06

10 Jan '06

hello to all, I have struggel past 3 month to install Koha. Now, my effort seems to be fruitful. From an obidience Windows user, I have become a Linux fans.. thanks to Koha for opening my eyes to Open Source Solutions. Now I am enjoying installing Koha on several Linux Distro. I have eventually faced a similar problems mentioned by many of mailing list User before. I am not a goo programmer or an experience System Analyst. But, maybe the following guidelines can help you out there: 1. Try to upgrade Apache version 1.3.33 to 2.0.xx (.54 If I am not mistaken), as this will help you running Perl Modules and Environment Variables without problems.(It is working for me) You can use dpkg or aptitude to do this. 2. You need CLEAN installation of PERL modules required by KOHA (using CPAN) without any disruption or error message. Also for the YAZ toolkit, which can be obtained from indexdata.dk. If you are using Sarge installation, make sure, you downloads YAZ Toolkit ofr Sarge package*. *Currently, I am using debian SARGE, while current guidelines installing Koha in debian is for woody. So, you need several adjustment for finding right package for Debian Sarge, If you are using Sarge Installation. Thank you and enjoy Koha! --- koha-request(a)lists.katipo.co.nz wrote: > Send Koha mailing list submissions to > koha(a)lists.katipo.co.nz > > To subscribe or unsubscribe via the World Wide Web, > visit > http://lists.katipo.co.nz/mailman/listinfo/koha > or, via email, send a message with subject or body > 'help' to > koha-request(a)lists.katipo.co.nz > > You can reach the person managing the list at > koha-owner(a)lists.katipo.co.nz > > When replying, please edit your Subject line so it > is more specific > than "Re: Contents of Koha digest..." > > > Today's Topics: > > 1. To implement koha (javier(a)ayto-daganzo.org) > 2. Re: I need to add a path to @INC for KOHA, > how? (Stephen Hedges) > 3. Re: I need to add a path to @INC for KOHA, > how? (Andro Gagne) > 4. Thanks all, but I am no closer to getting KOHA > working.... > (Marty Jongepier) > 5. Z39.50 (javier(a)ayto-daganzo.org) > 6. Shelflist report (David Miner) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 04 Jan 2006 00:48:10 +0100 > From: "javier(a)ayto-daganzo.org" > <javier(a)ayto-daganzo.org> > Subject: [Koha] To implement koha > To: koha(a)lists.katipo.co.nz > Message-ID: > <20060103234810.6141.qmail(a)correo2.acens.net> > Content-Type: text/plain; format=flowed; > charset="iso-8859-1" > > Hello to all: > We are implanting koha in a library in Daganzo, a > town of España.This > project we want it integramente to translate > Spanish. We are having problem > with script to pass the files tmpl to po in the part > of opac. Can you pass > somebody the file in format po of > opac-tmpl/default/en to be able to > translate it? > Another problem that we are having is with Z39.50 > and at the time of > concerning registry marc of other libraries. Me > podeis on the matter to > pass information of like forming it? > > Happy 2006 > > > ------------------------------ > > Message: 2 > Date: Tue, 3 Jan 2006 18:58:24 -0500 (EST) > From: "Stephen Hedges" <shedges(a)skemotah.com> > Subject: Re: [Koha] I need to add a path to @INC for > KOHA, how? > To: "Andro Gagne" <apgagne(a)frontiernet.net> > Cc: koha(a)lists.katipo.co.nz > Message-ID: > > <32802.65.24.138.126.1136332704.squirrel(a)webmail.skemotah.com> > Content-Type: text/plain;charset=iso-8859-1 > > You don't normally need to worry about these > environment variables, unless > you are running one of the exceptional command-line > scripts like > bulkmarcimport.pl. The routine Koha functions > should be no problem. > > When you do have some reason to run a special-use > script like > bulkmarcimport.pl, you somehow need to tell the > script where you installed > Koha. My Koha (and koha.conf and modules) may have > been installed in a > completely different location than yours. > > Stephen > > Andro Gagne said: > > Mr. Laurent, > > > > At 09:32 AM 1/3/06 +0100, Henri-Damien > Laurent wrote: > > > >>Normally, > >>when using a koha script, you need to set two > environment variables. > >>PERL5LIB and KOHA_CONF > >>KOHA_CONF contains the path to your koha.conf > >>PERL5LIB the path to your koha > directories/intranet/modules on a > >>standard install. > >> > >>You can set them with export command as such : > >>export KOHA_CONF=/path/to/koha.conf > >>export PERL5LIB=/path/to/koha/intranet/modules > >>And then you can launch your scripts. > > > > Thank you for your helpful reply. I > understand that the setting > > of these environment variables is necessary. That > makes sense to me, and > > I > > don't have any problem with it. What I don't > understand is why Mr. > > Jongepier and I are having this problem in the > first place. Either Koha > > is > > programmed to set these variables on its own when > it is started up, or it > > isn't. If it is supposed to set these variables > when being started, why > > is > > it not doing so? I believe I followed the > installation instructions very > > faithfully, so I have reason to expect that Koha > will start up properly > > and > > set the variables it needs to be set. If Koha is > not programmed to set > > these variables on its own when it is started up, > clearly it is my > > responsibility to set these variables. But if the > latter is the case, why > > didn't the installation instructions tell me this > and tell me how the > > variable setting needs to be done so that Koha's > environment variables are > > set up properly when Koha is started up? (I am > referring to the > > installation instructions that were available at > www.kohadocs.org last > > June.) All I'm trying to do is to understand > where the real problem lies > > so that, hopefully, I can fix the real > problem--especially if I am the one > > who caused the problem in some way--rather than > applying what seems like a > > Band-Aid and not understanding where things went > wrong. The Band-Aid > > approach probably will work for a while, but it is > likely not to be as > > good > > a fix as fixing the underlying problem, especially > as Koha gets upgraded > > over time. > > > > I really want to show the museum--and > other organizations that > > cannot afford integrated library systems that have > prices in the 5- or > > 6-figure range--that Koha can do the job they need > to be done. If you can > > help me understand where the underlying problem is > in regard to setting > > environment variables for Koha, I will appreciate > it very much. I would > > be > > glad to send any information needed about how I > installed Koha to solve > > this issue. Thank you for your patience and > understanding. > > > > Andro P. Gagné > > P.O. Box 715 > > Canandaigua, NY 14424 > > > > > > > > _______________________________________________ > > Koha mailing list > > Koha(a)lists.katipo.co.nz > > http://lists.katipo.co.nz/mailman/listinfo/koha > > > > > -- > Stephen Hedges > Skemotah Solutions, USA > www.skemotah.com -- shedges(a)skemotah.com > > > > ------------------------------ > === message truncated === __________________________________________ Yahoo! DSL Something to write home about. Just $16.99/mo. or less. dsl.yahoo.com

2 1