- Koha - lists.katipo.co.nz

MULTIPLE KOHA ON ONE SERVER
by DEEPTI 16 Dec '10

16 Dec '10

I HAVE INSTALL KOHA ON OPENSUSE 11.1 AND IT IS WORKING PROPERLY BUT NOW I WANT TO CONFIGURE MULTIPLE KOHA ON SINGLE SERVER .I HAVE DONE SOME CONFIGURATION BUT IT IS NOT WORK. WILL ANYONE HELP ME (CONFIGURATION OF MULTIPLE KONA) To use multiple databases: A lot of experimentation went into this. You need to modify the /etc/network/interfaces file to bind multiple ip addresses to the ethernet interface. Here is what I wound up with: -------------------------------------------------------------------------------------------------------- # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo eth1 eth1:0 eth1:1 iface lo inet loopback # The primary network interface allow-hotplug eth1 iface eth1 inet static address 192.168.21.249 netmask 255.255.255.0 gateway 192.168.21.10 ------------------------------------------------------------------------------------------------------ This creates three static addresses on the same interface eth1. Using phpmyadmin or the MySQL command line, login as kohaadmin and create the new databases, ours are image, leisure, main. You need to dump the structure of the koha database and then import it into the new databases. To dump the database use mysqldump . At the command line, create a new directory and cd into it. Then enter: mysqldump –u kohaadmin –p koha > kohaout.sql You enter the password for kohaadmin, and this creates an sql file of the koha database. Create the new databases using phpmyadmin or the mysql command line – example below. Start the mysql command line utility with: mysql –u kohaadmin –p After you enter your password, this gives you a mysql prompt. Then enter: show databases; to see the list of databases. To create one enter: create database <new db name>; Then change to that dataabase: use <new DB name>; This command will import all the koha structure into the new database. source kohaout.sql; quit gets you out of the MySql utility and back to the command line. Next you copy the config files. Change to the /etc/koha directory, and copy the koha-conf.xml and koha-httpd-conf files using the new name of your database. So if your database is named “book”, you now have book-conf.xml and book-httpd.conf. Edit the book-conf.xml file, and change the name of the database. You should find this near the end of the file under the <config> section. Edit the book-httpd.conf file and make the following changes: Edit the VirtualHost entry and change the name to one of the IP addresses you bound to the network interface – using a different address for each configuration/database. So your entry looks like <VirtualHost 192.168.21.139:55180> for the OPAC and <VirtualHost 192.168.21.139:55188> for the staff client. The IP addresses need to be in the interfaces config file, and the ports (after the :) are from the address range 50000 – 63535. These are unassigned ports in the internet scheme, and since they will be used only on the internal network can be whatever you like. The normal koha ports are the standard http port 80 for the OPAC and 8080 for the staff client. Further down in each VirtualHost section find the SetEnv KOHA_CONF declaration. Change the file to the new one, in our example “/etc/koha/book-conf.xml”. You need to change this in two places, one for each VirtualHost section. Change to the /etc/apache2 directory and edit the ports.conf file. Add the new ports you just put into the VirtualHost directives – 55180 and 55188 in our example. If you want to use the default koha database, also add 8080 – the default staff client port. You need to add symbolic links for the httpd.conf file and enable the site, so as above you do: ln -s /etc/koha/book-httpd.conf /etc/apache2/sites-available/book a2ensite book ( NOT ABLE TO THIS PART AS I THERE IS NO DIR IN /ETC/APACHE2 OF SITES-AVAILABLE) Then restart Apache - /etc/init.d/apache2 reload If you have done all your edits correctly, apache will reload without any errors. Browse to the new IP address – i.e. 192.168.21.239:55280 and you should see the koha opac screen. Browse to the staff client – 192.168.21.239:55288 and you should get that screen. Login as kohaadmin. For each new database you should create a new library with the IP address that goes with it entered there. Note: DON’T turn on IndependentBranches, it causes other problems and had to be turned off. It is not needed anyway with the different catalogs running on different virtual servers. That should get you multiple databases, with appropriate defaults when connecting to the staff client or the opac. To use a different background on the top bar of the opac for each database, create a new gif file similar to menu-background.gif found in /usr/share/koha/opac/htdocs/opac-tmpl/prog/images with a different name. We have one called green-background.gif in there now. In the /usr/share/koha/opac/htdocs/opac-tmpl/prog/en/css folder create an new css file - we are using imagelib.css. Edit the opac.css file, find the menu-background.gif line. Copy the entire section (Alt-6 in nano). Open the new css file (iamagelib.css) and past the info in (right or left mouse click). Change the menu-background.gif to green-background.gif. Using the staff client – System Preferences – OPAC page change the opaccolorstylesheet option to point to the new css file, imagelib.css in our case. The default is the colors.css file, which is empty. This file overrides the section that is in the opac.css file. To use a different background for the staff client go to the /usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/css directory. Copy the intranet.css file to a new name – I used imagelib-intranet.css. Edit the file, and change the fourth line in the file from “background-color:white” to background-color:<something else>”. A list of colors can be found by searching for “css color codes” on Google. You can use the name or maybe the code, didn’t try the code. Move the cursor past the end of the body section marked by a brace and hit Alt-t to delete the rest of the text in the file. Save the file. In the Staff Client go to the System Preferences, Staff Client tab and change the “intranetcolorstylesheet” to the new name. This will change just the background of the pages and use the defaults in the intranet.css file for everything else. I made the above color changes to try and give the librarian and the users a color cue about what database they were in. -- View this message in context: http://koha.1045719.n5.nabble.com/MULTIPLE-KOHA-ON-ONE-SERVER-tp3304116p330… Sent from the Koha - Discuss mailing list archive at Nabble.com.

4 5

excel to iso convertion
by Yatheesh Y 16 Dec '10

16 Dec '10

please help me I have data in excel format I want convert and load data into koha please help me in this reg thank you

5 4

Re: [Koha] Crontab appearing to not run
by Randall Rowe 16 Dec '10

16 Dec '10

Check the mail for the koha user (type "mail" at the command prompt. If the cronjob isn't executing properly you should be getting an email that might contain the needed clue to the reason it's not. Randy Rowe Lincoln City Libraries I.T. (402) 441-8523 r.rowe(a)lincolnlibraries.org -----Original Message----- From: "Fogg, Shawn (DPH)" <Shawn.Fogg(a)state.ma.us> Sent 12/16/2010 9:58:29 AM To: "koha(a)lists.katipo.co.nz" <koha(a)lists.katipo.co.nz> Subject: [Koha] Crontab appearing to not run Hi, I need a little basic help with crontab and re-indexing the database. I am using one of the pre-build virtual machines with v3.03.00.004. I SSH into the system using the koha user. When in that user I can run: /home/koha/kohaclone/misc/migration_tools/rebuild_zebra.pl -b -a -z and it will properly reindex the database so that new catalog entries will show up. If I do: crontab -l in the list I have an entry of: */10 * * * * /home/koha/kohaclone/misc/migration_tools/rebuild_zebra.pl -b -a -z >/dev/null Which I believe should re-index the database every 10 minutes. This isn't occurring though and I have not been able to figure out why. I don't know if it means anything but the rebuild_zebra is a little funny. If I move into the migration_tools directory I can't simply run rebuild_zebra.pl -b -a -z. It comes back with command not found. The only way I can run it is using the fully qualified path. Any thoughts as to what I am doing wrong? Thanks, Shawn _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha ��

2 1

Crontab appearing to not run
by Fogg, Shawn (DPH) 16 Dec '10

16 Dec '10

Hi, I need a little basic help with crontab and re-indexing the database. I am using one of the pre-build virtual machines with v3.03.00.004. I SSH into the system using the koha user. When in that user I can run: /home/koha/kohaclone/misc/migration_tools/rebuild_zebra.pl -b -a -z and it will properly reindex the database so that new catalog entries will show up. If I do: crontab -l in the list I have an entry of: */10 * * * * /home/koha/kohaclone/misc/migration_tools/rebuild_zebra.pl -b -a -z >/dev/null Which I believe should re-index the database every 10 minutes. This isn't occurring though and I have not been able to figure out why. I don't know if it means anything but the rebuild_zebra is a little funny. If I move into the migration_tools directory I can't simply run rebuild_zebra.pl -b -a -z. It comes back with command not found. The only way I can run it is using the fully qualified path. Any thoughts as to what I am doing wrong? Thanks, Shawn

2 1

Koha 3.2 searching words with diacritics
by Linda Culberson 16 Dec '10

16 Dec '10

Can anyone give me any clues about how to use diacritics correctly in Koha? I need help with how to get them into Koha using cataloging and how to get the searches to work in both the opac and and staff interfaces. Thanks! -- Linda Culberson lculber(a)mdah.state.ms.us Archives and Records Services Division Ms. Dept. of Archives& History P. O. Box 571 Jackson, MS 39205-0571 Telephone: 601/576-6873 Facsimile: 601/576-6824

1 1

Re: [Koha] Curious searching problem with zebra
by Bob Ewart 16 Dec '10

16 Dec '10

I've tried 'Ignore' and 'Don't Ignore' on the QueryRemoveStopwords entry in the searching preferences. It works the same both ways. And it is not supposed to matter when you are using zebra. I can't find any other preference for stop words. I tried to search 'and the' with no hits either way. I'm wondering if it's a 64-bit system problem. I did have to change the modulePath in the.cfg files in /etc/koha/zebradb to: /usr/lib64/idzebra-2.0/modules. My main system is openSUSE 11.3 and my test system is squeeze/sid Debian. Both are 64-bit. Both work the same way. I'm going to try a 32-bit system to see if that makes a difference. On 12/16/2010 06:19 AM, Elaine Bradtke wrote: > Just ran a test on our system (3.02.00.007); Apache/2.2.9 (Debian), zebra > Searched 'and the' > Got 924 hits (out of 1471 biblios) which sounds about right. > We don't have stop words turned on. > > On Thu, Dec 16, 2010 at 11:14 AM, Elaine Bradtke <eb(a)efdss.org> wrote: >> ??? do you have stop words turned on by any chance? >> Seems odd that it would just give up after and even if it were turned on. >> >> On Thu, Dec 16, 2010 at 1:31 AM, Bob Ewart <bob-ewart(a)bobsown.com> wrote: >>> I'm running koha 3.02.01 on a 64-bit openSUSE 11.3 system with zebra. I >>> have 3 biblios for 'And the band played on', a book, a tape and a DVD. >>> >>> When I search for 'and the band played on', it finds nothing. >>> When I search for 'the band played on', it finds all three. >>> >>> I've done a complete rebuild of the zebra index. >>> >>> Any ideas? >>> >>> -- >>> Bob >>> >>> _______________________________________________ >>> Koha mailing list http://koha-community.org >>> Koha(a)lists.katipo.co.nz >>> http://lists.katipo.co.nz/mailman/listinfo/koha >>> >> >> >> >> -- >> Elaine Bradtke >> Data Wrangler >> VWML >> English Folk Dance and Song Society | http://www.efdss.org >> Cecil Sharp House, 2 Regent's Park Road, London NW1 7AY >> Tel +44 (0) 20 7485 2206 ext 36 >> -------------------------------------------------------------------------- >> Registered Company No. 297142 >> Charity Registered in England and Wales No. 305999 >> --------------------------------------------------------------------------- >> "Writing about music is like dancing about architecture" >> --Elvis Costello (Musician magazine No. 60 (October 1983), p. 52) >> > > > -- Bob

1 0

Re: [Koha] koha for windows
by Chris Cormack 16 Dec '10

16 Dec '10

On 16 December 2010 16:19, Bagus Ramdan <bagusramdan(a)yahoo.com> wrote: > > Hi Chris, > Tks for your reply :-) What kind of linux server is the best for koha? > Hi Bagus I would recommend Debian squeeze, or Ubuntu Lucid (or Maverick) there the developers mostly work on these and consequently Koha is tested most heavily on them. There is also debian.koha-community.org which as packages to make installing Koha on Debian or Ubuntu a lot easier Chris

1 0

koha for windows
by Bagus Ramdan 16 Dec '10

16 Dec '10

What is the minimum requirement system for windows if we want to install koha Salam, Bagus Ramdan

3 3

Re: [Koha] Error: gzip: stdin: unexpected end of file tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now
by Chris Cormack 16 Dec '10

16 Dec '10

The problem is you are fetching the files from a non official source, or official mirror. You should be getting the files from download.koha-community.org and reading about koha at www.koha-community.org. The liblime/ptfs controlled site is hideously out of date and contains links to not only old releases (3.2.1 is the latest stable) but to corrupt ones. I wish they would either turn the site off or redirect it to the official one so they stop causing these kind of problems. But for your purposes getting the file from download.koha-community.org and reading the documentation on www.koha-community.org should see you right. Chris On 14 Dec 2010 17:30, "Abdullah Al-Modabber" <modabber(a)yahoo.com> wrote: Hi I am trying install KOHA on Ubuntu 10.10. When I tried to extracted koha file the following error occurred after extracted some files gzip: stdin: unexpected end of file tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Can you suggest me any possible solution! The full command line texts are as follows: root@librarian:/build# wget http://files.ptfs.com/koha/koha-3.02.00.tar.gz --2010-12-14 09:56:38-- http://files.ptfs.com/koha/koha-3.02.00.tar.gz Resolving files.ptfs.com... 65.120.65.62 Connecting to files.ptfs.com|65.120.65.62|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 5299490 (5.1M) [application/x-gzip] Saving to: `koha-3.02.00.tar.gz.2' 100%[======================================>] 5,299,490 5.76K/s in 6m 59s 2010-12-14 10:03:41 (12.3 KB/s) - `koha-3.02.00.tar.gz.2' saved [5299490/5299490] root@librarian:/build# sudo tar -xvf koha-3.02.00.tar.gz.2 koha-3.02.00/ koha-3.02.00/opac/ koha-3.02.00/opac/opac-changelanguage.pl koha-3.02.00/opac/opac-MARCdetail.pl koha-3.02.00/opac/opac-readingrecord.pl koha-3.02.00/opac/errors/ koha-3.02.00/opac/errors/500.pl koha-3.02.00/opac/errors/401.pl koha-3.02.00/opac/errors/403.pl koha-3.02.00/opac/errors/404.pl koha-3.02.00/opac/errors/402.pl koha-3.02.00/opac/errors/400.pl koha-3.02.00/opac/opac-passwd.pl koha-3.02.00/opac/unapi koha-3.02.00/opac/opac-addbybiblionumber.pl koha-3.02.00/opac/opac-mymessages.pl koha-3.02.00/opac/opac-suggestions.pl koha-3.02.00/opac/opac-serial-issues.pl koha-3.02.00/opac/opac-tags_subject.pl koha-3.02.00/opac/opac-messaging.pl koha-3.02.00/opac/opac-account.pl koha-3.02.00/opac/opac-downloadcart.pl koha-3.02.00/opac/opac-alert-subscribe.pl koha-3.02.00/opac/sco/ koha-3.02.00/opac/sco/help.pl koha-3.02.00/opac/sco/sco-patron-image.pl koha-3.02.00/opac/sco/sco-main.pl koha-3.02.00/opac/opac-search.pl koha-3.02.00/opac/opac-shelves.pl koha-3.02.00/opac/opac-sendshelf.pl koha-3.02.00/opac/opac-review.pl koha-3.02.00/opac/opac-tags.pl koha-3.02.00/opac/opac-userdetails.pl koha-3.02.00/opac/opac-sendbasket.pl koha-3.02.00/opac/opac-user.pl koha-3.02.00/opac/opac-browser.pl koha-3.02.00/opac/opac-topissues.pl koha-3.02.00/opac/ilsdi.pl koha-3.02.00/opac/opac-authorities-home.pl koha-3.02.00/opac/opac-downloadshelf.pl koha-3.02.00/opac/opac-userupdate.pl koha-3.02.00/opac/opac-authoritiesdetail.pl koha-3.02.00/opac/opac-main.pl koha-3.02.00/opac/opac-basket.pl koha-3.02.00/opac/opac-modrequest.pl koha-3.02.00/opac/opac-export.pl koha-3.02.00/opac/rss/ koha-3.02.00/opac/rss/DO_NOT_REMOVE koha-3.02.00/opac/maintenance.pl koha-3.02.00/opac/opac-detail.pl koha-3.02.00/opac/opac-showreviews.pl koha-3.02.00/opac/opac-reserve.pl koha-3.02.00/opac/opac-showmarc.pl koha-3.02.00/opac/opac-ISBDdetail.pl koha-3.02.00/opac/opac-ics.pl koha-3.02.00/opac/opac-renew.pl koha-3.02.00/opac/opac-search-history.pl koha-3.02.00/opac/changelanguage.pl koha-3.02.00/opac/oai.pl koha-3.02.00/misc/ koha-3.02.00/misc/translator/ koha-3.02.00/misc/translator/po/ koha-3.02.00/misc/translator/po/zh-Hans-CN-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/tet-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/en-GB-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/lo-Laoo-pref.po koha-3.02.00/misc/translator/po/pt-BR-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/bg-Cyrl-pref.po koha-3.02.00/misc/translator/po/el-GR-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/sk-SK-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/lo-Laoo-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/am-Ethi-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/mr-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/lo-Laoo-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/ru-RU-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/ur-Arab-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/zh-Hans-TW-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/zh-Hans-CN-pref.po koha-3.02.00/misc/translator/po/ro-RO-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/sl-SI-pref.po koha-3.02.00/misc/translator/po/mr-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/prs-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/vi-VN-pref.po koha-3.02.00/misc/translator/po/bg-Cyrl-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/mi-NZ-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/ro-RO-pref.po koha-3.02.00/misc/translator/po/ja-Jpan-JP-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/ne-NE-pref.po koha-3.02.00/misc/translator/po/pl-PL-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/hr-HR-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/nn-NO-pref.po koha-3.02.00/misc/translator/po/pbr-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/hi-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/prs-pref.po koha-3.02.00/misc/translator/po/ja-Jpan-JP-pref.po koha-3.02.00/misc/translator/po/tl-PH-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/tet-pref.po koha-3.02.00/misc/translator/po/nl-BE-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/hu-HU-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/hr-HR-i-opac-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/tr-TR-i-staff-t-prog-v-3002000.po koha-3.02.00/misc/translator/po/nl-BE-pref.po koha-3.02.00/misc/translator/po/de-DE-pref.po koha-3.02.00/misc/translator/po/ms-MY-i-staff-t-prog-v-3002000.po gzip: stdin: unexpected end of file tar: Unexpected EOF in archive tar: Unexpected EOF in archive tar: Error is not recoverable: exiting now Kind regards, Abdullah-Al-Modabber Deputy Librarian Southeast University Dhaka, Bangladesh Tel. +88028838013, ext. 101 Mobile: +8801819695123 http://www.seu.ac.bd _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

2 2

Re: [Koha] MULTIPLE KOHA ON ONE SERVER
by Robin Sheat 15 Dec '10

15 Dec '10

DEEPTI AHLAWAT schreef op wo 15-12-2010 om 13:49 [+0530]: > thanks for the reply Robin > it will help me alot please can u send me a proper configuration or > example of this. it's really imp for me i have to setup a mutiple koha > as soon as possible my deadline is near.please i hope u'll help me Please post to the list so others can weigh in if they want. It depends completely on your environment, so I can't send you a configuration. But if you start by creating a new koha_conf.xml (by copying your existing one) with updated database and zebra access details, create a new zebra setup (I can't help there, I don't know enough about zebra yet), set up an apache virtual host that uses the new one, and set up the new database for it to use, that's most of what you need. This does require a moderate amount of sysadmin knowledge, which this email window is too small to contain, but I'd say less than duplicating everything behind a second IP address. Or use the packages on Debian Squeeze, they do 95% of this for you automatically. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5957 6D23 8B16 EFAB FEF8 7175 14D3 6485 A99C EB6D

1 0