RE: [Koha-devel] request bulkmarcimport assistance -- an answer, I think
I believe I have at least part of the answer. Because I am using conf files named something other than /etc/koha.conf, the file context.pm needs to know the exact conf filename in line 97. Setting this parameter _appears_ to be sufficient to get the db files in the correct directory. Now I'll have to see if I can get the data stored where I want it by using a symbolic link for each data directory. Don't know if mysql will be too happy about that, but i will try it and report success or failure. Thanks again for all pointers. Mark
-----Original Message----- From: koha-devel-admin@lists.sourceforge.net [mailto:koha-devel-admin@lists.sourceforge.net] On Behalf Of Bruffey, Mark Sent: Wednesday, February 02, 2005 1:47 PM To: Joshua Ferraro Cc: Joshua Ferraro; koha-devel@lists.sourceforge.net Subject: RE: [Koha-devel] request bulkmarcimport assistance
I did not choose to enable SELinux when I installed FC3, so I think I can get around that issue. However, I suppose I could make a soft link from /var/lib/mysql/csl and /var/lib/mysql/cslr to the spot where I actually want the data (for the curious, I want it on a different physical drive--space issues). This still leaves me hoping bulkmarcimport.pl will actually put the data in the correct place. I'll try Stephen's suggestions. Mark
[Apologies for my previous email reply syntax deviations.]
-----Original Message----- From: Joshua Ferraro [mailto:jferraro@athenscounty.lib.oh.us] Sent: Wednesday, February 02, 2005 1:27 PM To: Bruffey, Mark Cc: Joshua Ferraro; koha-devel@lists.sourceforge.net Subject: Re: [Koha-devel] request bulkmarcimport assistance
On Wed, Feb 02, 2005 at 01:00:37PM -0600, Bruffey, Mark wrote:
Hi Joshua! I have tried to respond below so that you may be able to figure out where I am in the process. I have tried to be somewhat detailed; I hope this is appropriate. Sure is ... the more detail the better ... one note though, standard reply syntax is to use > for the message you're replying to and nothing for your new comments fyi. This makes it a bit easier to parse through. See my comments below.
### I understand. [I have /var/lib/mysql/csl and /var/lib/mysql/cslr and wish to relocate them to /csl/anydir1 and /csl/anydir2 ; see below]
### I have done this. [/etc/koha-csl.conf and /etc/koha-cslr.conf as well as /etc/koha-httpd-csl.conf and /etc/httpd-cslr.conf, pointing properly, I think, since I can call up both user interfaces and both admin interfaces on the net at the designated ip adddresses.
### I think I have gotten the initial dual setup done "properly" but, as you say, some customization remains. For me this appears to entail getting koha to import marc records to a dir specified by me [/csl/anydir1 or /csl/anydir2] and getting and koha and/or mysql (maybe just mysql?) to look for the data in the that location specified by me, not in /var/lib/mysql/csl or /var/lib/mysql/cslr as the case may be. There MUST be a config file with these paths or variable to them somewhere; I'm just not sure where to look. Especially since you're running FC3 this is a bad idea (it will really annoy SElinux). In general, I'd recommend keeping the standard database directory that mysql uses.
### There's one other issue that I think is important. When
bulkmarcimport.pl from the /csl/koha/_"csl"_ directory, the data ended up in the /var/lib/mysql/_"cslr"_ directory. "cslr" was the _second_ of the two install routines I did, so this leads me to believe that bulkmarcimport.pl, no matter the dir in which it is executed, is running in the same "context" [?]. What files does bulkmarcimport.pl look at? I suspect that your second install overwrote or appended the
I ran the path variables so a command like the one Stephen suggested might work. You should also make sure that your installation is actually using the right koha.conf file and not another one (check for /etc/koha.conf for instance).
Joshua
### Sincere thanks for your assistance. Mark ###
For instance, afaik Koha will always put the koha.conf file
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
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
(Although that usually produces a different error.) Try this:
Before you run "./bulkmarcimport.pl", export the
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
in /etc. path you directory? directory where 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
------------------------------------------------------- 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
------------------------------------------------------- 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
------------------------------------------------------- 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
Bruffey, Mark a écrit :
I believe I have at least part of the answer. Because I am using conf files named something other than /etc/koha.conf, the file context.pm needs to know the exact conf filename in line 97. Setting this parameter _appears_ to be sufficient to get the db files in the correct directory. Now I'll have to see if I can get the data stored where I want it by using a symbolic link for each data directory. Don't know if mysql will be too happy about that, but i will try it and report success or failure. Thanks again for all pointers. Mark
"setvenv/export KOHA_CONF=/path/to/koha.conf" before launching the script is your friend, you're right. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (2)
-
Bruffey, Mark -
Paul POULAIN