RE: [Koha-devel] request bulkmarcimport assistance
Thanks for your assistance Stephen. The routine ran fine, but, since I have two installs I am trying to keep separate, I need a way to designate where the data will go. It appears that the data path defaults to /var/lib/mysql/variablename. I need to designate two separate data paths, preferably not as a subdir of /var/lib/mysql, and have my two instances of KOHA be able to find the right set of data. Is this possible? If so, what do I need to do to implement this change? Sincere thanks, Mark -----Original Message----- From: Stephen Hedges [mailto:shedges@skemotah.com] Sent: Saturday, January 29, 2005 8:08 AM To: Bruffey, Mark Cc: koha-devel@lists.sourceforge.net Subject: Re: [Koha-devel] request bulkmarcimport assistance Mark, could it be that your perl can't find the Koha C4 directory? (Although that usually produces a different error.) Try this: Before you run "./bulkmarcimport.pl", export the directory where C4 resides: # export PERL5LIB=/usr/local/koha/intranet/modules (that's the normal directory for most installs, change it if yours is different.) Or if you use bulkmarcimport a lot, add this line to the list of "use" statements at the beginning of the script: use lib "/usr/local/koha/intranet/modules"; Stephen Bruffey, Mark said:
I'm getting the following error when attempting to run bulkmarcimport.pl:
BEGIN failed--compilation aborted at ./bulkmarcimport.pl line 10.
It seems like I had a similar problem when I imported records some months ago, but, of course, I do not appear to have documented the solution to it . . . .
Sincere thanks for any assistance.
Mark
L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264
mbruffey@centralseminary.edu <mailto:mbruffey@centralseminary.edu>
Central Seminary www.centralseminary.edu <http://www.centralseminary.edu> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts <http://www.centralseminary.edu/wcts>
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
Mark, I could be wrong about this (and if I am, I hope someone corrects me quickly!), but if you have two installs, I assume you have two different paths to Koha: something like /usr/local/koha and /usr/local/koha2. So if you change the PERL5LIB environment variable accordingly, you should be able to control where the data goes, because Koha will grab the appropriate "context" from the path you specify. You might do: # export PERL5LIB=/usr/local/koha/intranet/modules to load records in one install, and # export PERL5LIB=/usr/local/koha2/intranet/modules to load records into the other install. You'd need to take out any "use lib "/usr/local/koha/intranet/modules";" statement that you might have added to bulkmarcimport.pl Stephen Bruffey, Mark said:
Thanks for your assistance Stephen. The routine ran fine, but, since I have two installs I am trying to keep separate, I need a way to designate where the data will go. It appears that the data path defaults to /var/lib/mysql/variablename. I need to designate two separate data paths, preferably not as a subdir of /var/lib/mysql, and have my two instances of KOHA be able to find the right set of data. Is this possible? If so, what do I need to do to implement this change? Sincere thanks, Mark
-----Original Message----- From: Stephen Hedges [mailto:shedges@skemotah.com] Sent: Saturday, January 29, 2005 8:08 AM To: Bruffey, Mark Cc: koha-devel@lists.sourceforge.net Subject: Re: [Koha-devel] request bulkmarcimport assistance
Mark, could it be that your perl can't find the Koha C4 directory? (Although that usually produces a different error.) Try this:
Before you run "./bulkmarcimport.pl", export the directory where C4 resides: # export PERL5LIB=/usr/local/koha/intranet/modules (that's the normal directory for most installs, change it if yours is different.)
Or if you use bulkmarcimport a lot, add this line to the list of "use" statements at the beginning of the script: use lib "/usr/local/koha/intranet/modules";
Stephen
Bruffey, Mark said:
I'm getting the following error when attempting to run bulkmarcimport.pl:
BEGIN failed--compilation aborted at ./bulkmarcimport.pl line 10.
It seems like I had a similar problem when I imported records some months ago, but, of course, I do not appear to have documented the solution to it . . . .
Sincere thanks for any assistance.
Mark
L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264
mbruffey@centralseminary.edu <mailto:mbruffey@centralseminary.edu>
Central Seminary www.centralseminary.edu <http://www.centralseminary.edu> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts <http://www.centralseminary.edu/wcts>
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
Mark, The path /var/lib/mysql/"anything" refers to the database itself. The way to distinguish between two koha installs (provided that you want the database to be different for them) is to specify a different database name for each of them (for instance, koha1 and koha2). You'll also probably want to use a different admin account for ease of administration (e.g., kohaadmin1, kohaadmin2). You will also want to keep the koha paths different for those two installs (e.g., /usr/local/koha1, /usr/local/koha2), as well as have a seperate koha.conf file for each of them (e.g., /usr/local/koha1/etc/koha.conf, /usr/local/koha2/etc/koha.conf). The fastest way to do this is during the initial installation of Koha, when it asks you those specific questions, though it would be possible to set it up later on. Of course, the install is not really setup to handle multiple installations so you'll still need to customize some things once you have run both installations. For instance, afaik Koha will always put the koha.conf file in /etc. Just copy that file to wherever you want to store it and update your koha-httpd.conf accordingly. Hope that helps, Joshua On Wed, Feb 02, 2005 at 12:34:14PM -0500, Stephen Hedges wrote:
Mark, I could be wrong about this (and if I am, I hope someone corrects me quickly!), but if you have two installs, I assume you have two different paths to Koha: something like /usr/local/koha and /usr/local/koha2. So if you change the PERL5LIB environment variable accordingly, you should be able to control where the data goes, because Koha will grab the appropriate "context" from the path you specify. You might do: # export PERL5LIB=/usr/local/koha/intranet/modules to load records in one install, and # export PERL5LIB=/usr/local/koha2/intranet/modules to load records into the other install. You'd need to take out any "use lib "/usr/local/koha/intranet/modules";" statement that you might have added to bulkmarcimport.pl
Stephen
Bruffey, Mark said:
Thanks for your assistance Stephen. The routine ran fine, but, since I have two installs I am trying to keep separate, I need a way to designate where the data will go. It appears that the data path defaults to /var/lib/mysql/variablename. I need to designate two separate data paths, preferably not as a subdir of /var/lib/mysql, and have my two instances of KOHA be able to find the right set of data. Is this possible? If so, what do I need to do to implement this change? Sincere thanks, Mark
-----Original Message----- From: Stephen Hedges [mailto:shedges@skemotah.com] Sent: Saturday, January 29, 2005 8:08 AM To: Bruffey, Mark Cc: koha-devel@lists.sourceforge.net Subject: Re: [Koha-devel] request bulkmarcimport assistance
Mark, could it be that your perl can't find the Koha C4 directory? (Although that usually produces a different error.) Try this:
Before you run "./bulkmarcimport.pl", export the directory where C4 resides: # export PERL5LIB=/usr/local/koha/intranet/modules (that's the normal directory for most installs, change it if yours is different.)
Or if you use bulkmarcimport a lot, add this line to the list of "use" statements at the beginning of the script: use lib "/usr/local/koha/intranet/modules";
Stephen
Bruffey, Mark said:
I'm getting the following error when attempting to run bulkmarcimport.pl:
BEGIN failed--compilation aborted at ./bulkmarcimport.pl line 10.
It seems like I had a similar problem when I imported records some months ago, but, of course, I do not appear to have documented the solution to it . . . .
Sincere thanks for any assistance.
Mark
L. Mark Bruffey Director Library Services Central Baptist Theological Seminary 900 Forestview Lane N Plymouth MN 55441 763 417 8264
mbruffey@centralseminary.edu <mailto:mbruffey@centralseminary.edu>
Central Seminary www.centralseminary.edu <http://www.centralseminary.edu> Fourth Baptist Church www.fourthbaptist.org <http://www.fourthbaptist.org> WCTS Radio AM 1030 Online www.centralseminary.edu/wcts <http://www.centralseminary.edu/wcts>
-- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges@skemotah.com
------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Koha-devel mailing list Koha-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/koha-devel
Joshua Ferraro a écrit :
Mark,
The path /var/lib/mysql/"anything" refers to the database itself. The way to distinguish between two koha installs (provided that you want the database to be different for them) is to specify a different database name for each of them (for instance, koha1 and koha2). You'll also probably want to use a different admin account for ease of administration (e.g., kohaadmin1, kohaadmin2). You will also want to keep the koha paths different for those two installs (e.g., /usr/local/koha1, /usr/local/koha2), as well as have a seperate koha.conf file for each of them (e.g., /usr/local/koha1/etc/koha.conf, /usr/local/koha2/etc/koha.conf).
The fastest way to do this is during the initial installation of Koha, when it asks you those specific questions, though it would be possible to set it up later on. Of course, the install is not really setup to handle multiple installations so you'll still need to customize some things once you have run both installations.
For instance, afaik Koha will always put the koha.conf file in /etc. Just copy that file to wherever you want to store it and update your koha-httpd.conf accordingly.
you're right. Just define KOHA_CONF to use one or the other DB setup. For example : the test install is in /etc/koha_test.conf the prod setup is in /etc/kohaprod.conf Do a export/SetEnv KOHA_CONF=/etc/kohaXXX.conf before running what you want. You can have the same cgi/templates for many installs, having just the DB setup different. The DB contains template, language, MARC,... so that will work really fine. HTH. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (4)
-
Bruffey, Mark -
Joshua Ferraro -
Paul POULAIN -
Stephen Hedges