- Koha - lists.katipo.co.nz

Problems...
by gekigan_flare＠hotPOP.com 06 Aug '04

06 Aug '04

Hello. I'm a linux newbie, and I've tried to install koha 2.0.0 on Mandrake 10.0, with apache2 and mysql. The installation seemed to go well, however, I receive a '403 Forbidden' error when I try to access the opac and the librarian modules on my browser (localhost:80 and localhost:8080). It's only a hunch, but I think the User setting in the httpd.conf file (or lack thereof) is somehow related to it (or maybe it's something else, I don't know.) Help and suggestions would be much appreciated. Thanks in advance. -James **Just a student trying this out for the sake of his school**

2 1

Installing koha-2.0.0 trouble installing DBD-mysql-2.9004
by Pradeep P Kavi 06 Aug '04

06 Aug '04

Hello, I just tried to install koha on Linux 7.2 version. I have installed mysql, perl and apache successfully. Also, I could install all perl modules successfully except DBD-mysql-2.9004. I am able to connect to mysql and run sql commands without any problems. I have downloaded the file DBD-mysql-2.9004.tar.gz from CPAN network and when I give the command # perl Makefile.PL make make test I get the message Can't exec "mysql_config": No such file or directory at Makefile.PL line 174. readline() on closed filehandle PIPE at Makefile.PL line 176 Failed to determine directory of mysql.h. Use perl Makefile.PL --cflags=-I<dir> to set this directory. For details see the INSTALL.html file, section "C Compiler flags" or type perl Makefile.PL --help As a novice, I am not able to bug this. Can anybody help me out. Pradeep __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

2 1

Koha Presentation
by Joshua Ferraro 06 Aug '04

06 Aug '04

Hi all, I've got a Koha presentation at the OLC annual conference (http://www.heightslibrary.org/webmaster/olc_showcase/annual.php) and I'd like to put together a list of Koha features that folks are working on. I'll probably write up a brief synopsis of features similar to the one I did last time I presented on Koha (http://kados.org/LibraryScience/koha_at_a_glance.html) So if you're working on something exciting let me know and I'll include it. Other than that I'll be relying on release-notes, etc. Thanks, Joshua

5 7

Re: [Koha] Connection refused
by Marco Antonio Castillo Arreozola 06 Aug '04

06 Aug '04

Thanks! I modified the file /etc/koha-httpd.conf to add the line "Listen 8080" and copy to /etc/httpd/conf.d/koha-httpd.conf. Can somebody recommend to me a manual for user and administrator for koha-2?, thanks. ¿Alguien me puede recomendar un manual para usuario u administrador de Koha-2?, gracias. Marco Antonio Castillo Euroamerican School of Monterrey, Mexico. ----------------------------------------------------------------- From: MJ Ray lt;mjr(a)dsl.pipex.comgt; To: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Connection refused Date: Wed, 28 Jul 2004 18:22:33 +0100 On 2004-07-28 17:08:21 +0100 Marco Antonio Castillo Arreozola <cobi31(a)hotmail.com wrote: But when I want try to connect to http://myserver:8080 the connection was refused. Sounds like your server does not listen on 8080. Look for a line Listen 8080 in the config files, or some line containing 8080 and LISTEN in the output of the command netstat -an. If neither are there, add the Listen line to a config file, perhaps even koha_httpd.conf Hope that helps, -- MJR/slef My Opinion Only and not of any group I know http://www.ttllp.co.uk/ for creative copyleft computing Please email about: BT alternative for line rental+DSL; Education on SMEs+EU FP6; office filing that works fast _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha _________________________________________________________________ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963

4 3

Re: [Koha] losing data during import
by Baljkas Family 06 Aug '04

06 Aug '04

Wednesday, August 4, 2004 23:28 CDT Hi again, Scott, I took a look at the records in detail. Sorry, they weren't missing the 2 blocks at the end of each as they seemed to be in Word Pad. MARCBreaker can't break it down properly, though, so despite first appearances, they still aren't valid MARC. Something is screwing up the Directory. I think you must be right in that the non-ASCII characters definitely need to be replaced. Is there any other way you can replace the non-ASCII characters first? If you could send a sample of the same (or other) records in their original format off listserv, I can see if another method might work. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada P.S. You really shouldn't use the $g in 100 in the way that you did. That's not what it was intended for. > From: Scott Scriven <koha-main(a)toykeeper.net> > Date: 2004/08/04 Wed PM 08:41:18 CDT > To: koha(a)lists.katipo.co.nz > Subject: [Koha] losing data during import > > Hello. > > I'm having some difficulty keeping data intact when I import with > the bulkmarcimport.pl script. Specifically, it seems that fields > are getting the last 5 bytes chopped off. It seems to be related > to character encodings, but I'm not really sure what to do about > it. Converting from utf-8 to iso8859-1 seems to change the > results, but not correct the problem. Manually replacing all > non-ascii characters with safer equivalents seems to cure the > problem, but is not feasible for the amount of data I have. > > I have a data sample which exhibits this problem; it is a > collection of 15 Douglas Adams books: > > http://toykeeper.net/tmp/koha/dna.mrc > > It was generated from: > > http://toykeeper.net/tmp/koha/dna.marcxml > http://toykeeper.net/tmp/koha/dna.mods > > My conversion process goes from custom data to MODS, then MODS to > MARC (xml) using the LoC stylesheets for doing so. It then > converts to binary MARC using perl's MARC::Record and > MARC::File::XML. Somewhere in the bulkmarcimport.pl script, data > is getting lost. It's either MARC::Record failing to read its > own files, or in Koha's code somewhere, but I don't know where. > > Any hints? I'm hoping I can simply sidestep the conversion > to/from binary marc, to avoid the problem; I'll let people know > if this is effective. > > > -- Scott > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha

2 2

Re: Re: [Koha] losing data during import
by Baljkas Family 06 Aug '04

06 Aug '04

Thursday, August 5, 2004 19:13 CDT Hi, Scott, Sorry, I didn't get your message until just now. I think our ISP must be slow today. Anyway, I spent some time last night and today with your records. I cleaned out the error-causing characters manually last night as a test: for 15 records, it took me 90 minutes (although I did correct a few little MARC errors in the process). As part 2 of my self-imposed testing, I then tried downloading what I'll call (and you'll have to forgive me this jingoism) good MARC records from the NLC database: it took 15 minutes. A much better time ratio. When I've done editing them later tonight, I send you the sets off listserv (as real MARC, they wouldn't display properly anyway: for reasons I've never figured out, sending them as attachments somehow integrates them into the message). Anyway, you'll have: 1. your original set reconverted; and, 2. edited records with the text you wanted integrated into each record (not what I would recommend); and then, 3. edited records with a hyperlink to the same text (what I would and did recommend: I think one of my messages to you might have got lost in the ether). I think that will demonstrate why it is preferable to make a hyperlink. I am sure that with your skill you could even make the link appear like an extension to the Koha page so that users wouldn't even be aware they had left the catalogue. Incidentally, 2 of the NLC records that I used as base copy had hyperlinks already in them to (essentially) PURLs at the Library of Congress. They even have pictures of the book copies, which is kind of neat, too. > The majority of the data I've converted seems to import > correctly. I don't know if it was valid MARC, but that > has not prevented the rest from importing, which is what > I'm concerned about. No, and I certainly can understand that. If the examples I'm sending back to you seem too pedantically over-corrective, please forgive me: it is just that once one learns the description standards of the International Standard for Bibliographic Description [ISBD], it is very hard to ignore the training and do things otherwise (when I write down book references for friends I am constantly having to correct the perfect ISBD that comes naturally to me but looks weird to non-cataloguers). If you wouldn't mind terribly indulging my curiosity, I would like to see what kind of 'MARC' the records were in originally. Broadening my own horizons if nothing else. TIA. > > P.S. You really shouldn't use the $g in 100 in the way > > that you did. That's not what it was intended for. > > I'm a bit new to this; is there a better place to put it? > Ideally, I'd like to include as much information as > possible, and keep the data normalized, but I get the > impression that MARC and Koha weren't designed for that. Yep, as I wrote in the message that apparently went missing, no ILS was ever really intended to offer as much info as you want, you little keener you! ;-) Again, the records that I'll send later tonight (my time) will show you 2 different ways of including all that info you've compiled with patience and effort: as integrated and as hyperlinked information. I think the latter is preferable, but then again I am biased by training and experience following rules that basically outlaw what you want to do. (In fact, I can remember my cataloguing mentor criticizing a piece of my work once because I offered a one sentence evaluation of the argument of the book in a 520. Even though she appreciated it and didn't argue with my assessment, it wasn't description, as she rightly pointed out, it was commentary.) Anyway, I admire your intentions and if you aren't happy with the suggestions that I made, we can confab some more and find something that fits within the rules and still pleases you. Until later tonight then, Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada

1 0

Koha VS Home-grown software/database
by Bill Benedetto 06 Aug '04

06 Aug '04

Good day. I have what I think is a somewhat unusual question about Koha. A couple of years ago my daughter and I created a Library Database for our grade school library (Kindergarten through 8th grade). Since I'm fairly well-versed in the land of Linux, here's the infrastructure that we came up with: Debian (Woody) MySQL Perl The librarian just wanted something to catalog the books. She didn't want to do check-in/check-out. Nor did she want anything more than Title, Author, Keywords, Section (of the library). She also just wanted to do the Fiction part of the library so CallNumber was pretty basic (something like "TWA 3"). During this library-system creation, I stumbled across Koha. I thought that Koha would be a much better choice than rolling my own. Consequently, I spent a fair amount of time trying to figure out how to convert my MySQL DB into Koha's. Unfortunately, I couldn't figure out how to map from my table layout to Koha's table layout. Now, time has passed, the Library DB is all created and in use. (And the librarian really likes it!) Now, of course, the librarian wants a check-in/checkout system. I may be up to the task of modifying my DB and scripts to do this but it seems kind of silly to roll my own when a great system like Koha already exists. So, here's my question, finally..... Is it possible for me to take my data and map it to the Koha layout? That is, if I start with a mysqldump of my data, can I use Perl to mangle it into a mysqldump of data suitable for importing into Koha? Yeah, yeah. I know. *ANYTHING'S* possible. But could someone possibly provide me with enough guidance (or documentation) so that I could do the job? Here's my table layout: CREATE TABLE catalog ( bookidnum smallint(6) NOT NULL auto_increment, title varchar(75) NOT NULL default '', author varchar(30) NOT NULL default '', keywords varchar(50) NOT NULL default '', numcopies tinyint(4) NOT NULL default '1', callnumber varchar(10) NOT NULL default '', hard_paperback char(1) NOT NULL default 'H', section varchar(30) NOT NULL default '', PRIMARY KEY (bookidnum), UNIQUE KEY bookidnum (bookidnum) ) TYPE=MyISAM; Notes: o The bookidnum has nothing to do with the physical book. It's just basically the record number in the DB. o keywords consists of a string that looks something like "cats christmas" or "mississippi" or "berenstain bears" or "dinosaurs holidays". We would really like to keep these keywords because that's one of the ways that the librarian/user can search for books. o numcopies is misnamed and is actually the copy number. The first book is copy #1. The second is copy #2. And so on. o hard_paperback is just "H" or "P". o section looks like one of these: Fiction Easy Fiction Intermediate Fiction Non-Fiction Easy Non-Fiction Intermediate Non-Fiction Biography Easy Holidays YA Caldecott Newbery I realize that I'm asking a lot here. What I'm really looking for is some kind of one-to-one mapping that says something like this: "Your 'bookidnum' field is really field 'bookno' in table 'booktable'" so that I might be able to mangle the data from my output to a new input for Koha (rather than have to re-enter all of this data). FWIW, we have around 6000 books in this DB. I appreciate any guidance that I can get! Thanks! - Bill Benedetto

3 2

Koha's call number vs. our library's call number
by Hans Henderson 05 Aug '04

05 Aug '04

As I mentioned in my "hierarchical question" posting, the shelf ordering system for one of our book item types (graded readers) is by reading difficulty level. To accommodate this, I've created an alphanumeric local call number unique to each item (copy of a title) I'm also using this as a barcode number. the first part of the number shows the level, then the set, then the titles, and then the individual copies. So Q010A04 means "the fourth copy of title A in set 010 at reading difficulty level Q". I plan to put this local call number into Koha's barcode field in the items table, and link that field to MARC 852c - please confirm I got at least that right, or should I use a 9xx? But I see that the *Koha* call number field is numeric. Can we just leave the Koha call number field empty? I saw Chris Cormack's tip on changing the dewey column's data type to varchar within SQL, but messing with the internals at my current newbie level makes me a bit nervous. Plus, I will be pulling in deweys from many of my MARC records, so where this is so, I'd rather store them where they're supposed to go in Koha in case we need that data later. So more to the point, how do we ignore this data in the meantime, and use the barcode field everywhere in Koha as a local call number field? I'd really appreciate some details as to how to do this, as pertains to both the opac and the intranet. Or alternatively, I'd also appreciate feedback on how I'm totally off-base regarding normal library practices <g>, along with suggestions on how to accomplish what I'm trying to do. Thanks, Hans

4 6

koha error:member cant be added!!
by nadia muzaffar 05 Aug '04

05 Aug '04

hi i m in real trouble cuz i have configured koha-2.0.0 on Redhat but when i try to use the software its not adding the members . i checked the log file for it and here iz the error log generated: [Thu Aug 05 11:33:54 2004] [error] [client 192.168.1.200] Premature end of script headers: newmember.pl, referer: http://192.168.1.50:8080/cgi-bin/koha/memberentry.pl?type=Add [Thu Aug 05 11:33:54 2004] [error] [client 192.168.1.200] ERROR: Date::Manip unable to determine TimeZone., referer: http://192.168.1.50:8080/cgi-bin/koha/memberentry.pl?type=Add [Thu Aug 05 11:33:54 2004] [error] [client 192.168.1.200] !Date::Manip::Date_TimeZone called at /usr/lib/perl5/site_perl/5.8.0/Date/Manip.pm line 661, referer: http://192.168.1.50:8080/cgi-bin/koha/memberentry.pl?type=Add [Thu Aug 05 11:33:54 2004] [error] [client 192.168.1.200] !Date::Manip::Date_Init() called at /usr/lib/perl5/site_perl/5.8.0/Date/Manip.pm line 1395, referer: http://192.168.1.50:8080/cgi-bin/koha/memberentry.pl?type=Add [Thu Aug 05 11:33:54 2004] [error] [client 192.168.1.200] !Date::Manip::ParseDate('today') called at /usr/local/koha/intranet/cgi-bin/newmember.pl line 134, referer: http://192.168.1.50:8080/cgi-bin/koha/memberentry.pl?type=Add ~ ~ i dunno what exactly to do, altough i did checked this date::manip module of perl n it exits in my perl modules, i mean its installed thr properly, perl-DateManip-5.40-30 is there.. so but still when i try to connect through browser by giving: http://mymachine:8000 or http://mymachine:8080 it do connects nad do all stuff but when i try to add member this abbove mentioned log iz generated with messege internal server error.. so plzzzzz help me out of this!! _________________________________________________________________ STOP MORE SPAM with the new MSN 8 and get 2 months FREE* http://join.msn.com/?page=features/junkmail

1 0

Koha Windows version - Server error
by Pradeep P Kavi 05 Aug '04

05 Aug '04

Hello, I have installed Koha successfully on windows 98 machine. The installation was successful. However, when I point my browser to http://localhost the get the following error : Server error! The server encountered an internal error and was unable to complete your request. Error message: Premature end of script headers: opac-main.pl If you think this is a server error, please contact the webmaster. Error 500 172.31.9.20 08/05/02 13:29:27 Apache/2.0.50 (Win32) I believe this is a problem with server settings. kindly help me out. Pradeep __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - 100MB free storage! http://promotions.yahoo.com/new_mail

1 0