Send Koha mailing list submissions to koha@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@lists.katipo.co.nz
You can reach the person managing the list at koha-owner@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. Re: Defaulting to a specific branch and Serhold question (theashik) 2. zebra erro (Cody Hennesy) 3. Re: Defaulting to a specific branch and Serhold question (Joe Atzberger)
----------------------------------------------------------------------
Message: 1 Date: Wed, 22 Apr 2009 23:30:55 -0700 (PDT) From: theashik <theashik@hotmail.com> Subject: Re: [Koha] Defaulting to a specific branch and Serhold question To: koha@lists.katipo.co.nz Message-ID: <23190964.post@talk.nabble.com> Content-Type: text/plain; charset=UTF-8
I have followed the same procedure as mentioned by Doug Dearden, but when i search the catalogue from staff client, it is still showing the record from the old database while it has to be shown from new database at new ip address. Can u help me how i solve it and that u have mentioned to create new library for the newly created database, how to do that?
with regards, Mohan Raj Pradhan HEALTHNET NEPAL
Doug Dearden wrote:
Zachary,
The way I did it was with different virtual hosts listening on different ip address and port combinations, and pointing to the individual databases for each catalog. One set of koha program files, but a different database and config files for each library. I have three databases running this way, I'm not sure how it will expand to 17. My notes on how to do this are pasted below.
Doug
To use multiple databases:
Modify the /etc/network/interfaces file to bind multiple ip addresses to the ethernet interface. After much trial and error 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.1.133 netmask 255.255.255.0 gateway 192.168.1.10
iface eth1:0 inet static address 192.168.1.139 netmask 255.255.255.0 gateway 192.168.21.10
iface eth1:1 inet static address 192.168.1.140 netmask 255.255.255.0 gateway 192.168.1.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 database.
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.1.139:50180> for the OPAC and <VirtualHost 192.168.1.139:50188> 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
Hi Twinamatsiko, Each book in the library has a unique call number. A call number is like an address: it tells us where the book is located in the library. More info here: http://honolulu.hawaii.edu/legacylib/callno.html This library uses the Library of Congress Classification system http://info.library.unsw.edu.au/skills/call-numbers.html This library uses the Dewey Classification system Some libraries create their own classification system for their call numbers. Cheerio, Irma CALYX information essentials -----Original Message----- From: koha-bounces@lists.katipo.co.nz [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Twinamatsiko Smith Sent: Saturday, 25 April 2009 2:20 AM To: koha@lists.katipo.co.nz Subject: [Koha] inquiries hey guys What's a call number? what does t do and help? On 4/24/09, koha-request@lists.katipo.co.nz <koha-request@lists.katipo.co.nz> wrote: this: 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 50180 and 50188 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 koha
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.1.139:50180 and you should see the koha opac screen. Browse to the staff client - 192.168.21.139:50188 and you should get that screen. Login as kohaadmin.
For each new database you should create a new library in the staff client, with the IP address that goes with the library filled in. 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.
Zachary Spalding <spalding@senylrc.org> 4/6/2009 1:51 PM >>> I am just starting out with Koha and was hoping someone on the list may be able to answer these questions?
1. Is there a way to default to a specific branch library, I have about 17 libraries that our separate institutions that need to default to a search for only their stuff. If it could be done via a parameter in the URL that would be perfect. I just don't want to run 17 instances of Koha if I can avoid it.
2. Has anyone tryed to import Serhold data from National Library of Medicine and can you tell me how did you get that process started with NLM?
Thanks
-- Zachary Spalding Systems Manager 21 S. Elting Corners Rd. Highland, NY 12528
Phone: 845-883-9065 Fax: 845-883-9483 Email: spalding@senylrc.org
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- View this message in context: http://www.nabble.com/Re%3A-Defaulting-to-a-specific-branch-and-Serhol d%09question-tp22938535p23190964.html Sent from the Koha - Discuss mailing list archive at Nabble.com.
------------------------------
Message: 2 Date: Thu, 23 Apr 2009 14:11:12 -0700 From: Cody Hennesy <chennesy@cca.edu> Subject: [Koha] zebra erro To: koha@lists.katipo.co.nz Message-ID: <8427A769-8A0F-4353-8927-CFF9FBFBBFCF@cca.edu> Content-Type: text/plain; charset="us-ascii"
Hello all,
I'm trying to get zebra 2 running on a centos 5 machine with Koha 3.00.01, and everything looks good until I run a catalog search and the connection closes with an error 109 message. Tried rebuilding and restarting zebra plenty of times, as both root and koha user. / etc/koha and /var/lock/koha are owned by the koha user now. Have also done these exports: export KOHA_CONF=/etc/koha/koha-conf.xml export PERL5LIB=/usr/share/koha/lib
Not sure what to do next - reinstall zebra??
[root@koha-test migration_tools]# cd /usr/bin [root@koha-test bin]# zebrasrv-2.0 -f /etc/koha/koha-conf.xml 16:10:19-20/04 [log] zebra_start 2.0.8 /etc/koha/zebradb/zebra- biblios.cfg 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-marc.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-alvis.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-xml.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-safari.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-text.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-regx.so 16:10:19-20/04 [log] zebra_start 2.0.8 /etc/koha/zebradb/zebra- authorities.cfg 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-marc.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-alvis.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-xml.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-safari.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-text.so 16:10:19-20/04 [log] Loaded filter module /usr/lib/idzebra-2.0/modules/mod-grs-regx.so 16:10:19-20/04 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/bibliosocket id=1 16:10:19-20/04 [server] Adding dynamic listener on unix:/var/run/koha/zebradb/authoritysocket id=2 16:10:19-20/04 [server] Starting server zebrasrv-2.0 pid=30051 16:10:38-20/04 zebrasrv-2.0(1) [session] Session - OK 1 unix:/var/run/koha/zebradb/bibliosocket 30059 16:10:38-20/04 zebrasrv-2.0(1) [request] Auth idPass kohauser - 16:10:38-20/04 zebrasrv-2.0(1) [request] Init OK - ID:81/81 Name:ZOOM-C/YAZ Version:1.116/2.1.54 16:10:38-20/04 zebrasrv-2.0(1) [request] Search biblios ERROR 109 1 1+0 RPN @attrset Bib-1 @or @or @or @or @or @attr 1=36 @attr 4=1 @attr 6=3 @attr 9=32 @attr 2=102 adorn @attr 1=4 @attr 4=1 @attr 6=3 @attr 9=28 @attr 2=102 adorn @attr 1=4 @attr 4=1 @attr 9=26 @attr 2=102 adorn @attr 4=6 @attr 5=103 @attr 9=16 @attr 2=102 adorn @attr 4=6 @attr 5=1 @attr 9=14 @attr 2=102 "adorn? " @attr 4=6 @attr 9=14 @attr 2=102 adorn 16:10:38-20/04 zebrasrv-2.0(1) [session] Connection closed by client
thanks! Cody ____________________________ Cody Hennesy Librarian, Systems & Services California College of the Arts 510.594.3659 | library.cca.edu
-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20090423/c2470e94 /attachment-0001.htm
------------------------------
Message: 3 Date: Thu, 23 Apr 2009 18:08:43 -0400 From: Joe Atzberger <ohiocore@gmail.com> Subject: Re: [Koha] Defaulting to a specific branch and Serhold question To: theashik <theashik@hotmail.com> Cc: koha@lists.katipo.co.nz Message-ID: <235bf14f0904231508r736873b9uebd957c70ee19f32@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
Make sure you have created different databases and that your Apache VirtualHosts reference two different KOHA_CONF files. Each file should use distinct database name (and login/password).
--Joe
On Thu, Apr 23, 2009 at 2:30 AM, theashik <theashik@hotmail.com> wrote:
I have followed the same procedure as mentioned by Doug Dearden, but when i search the catalogue from staff client, it is still showing the record from the old database while it has to be shown from new database at new ip address. Can u help me how i solve it and that u have mentioned to create new library for the newly created database, how to do that?
with regards, Mohan Raj Pradhan HEALTHNET NEPAL
-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.katipo.co.nz/pipermail/koha/attachments/20090423/36253ac5 /attachment.htm
------------------------------
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
End of Koha Digest, Vol 42, Issue 51 ************************************
-- .............. Smith Matsiko Sparklink systems (u) Ltd Plot 42 Buganda Rd, # 3463 Kampala Uganda mob:0752 690319 _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha