- Koha - lists.katipo.co.nz

Re: [Koha] How to get MARC biblio export to work? 2.0.1RC1
by Michael Lake 04 Nov '04

04 Nov '04

Hi all David Bigwood kindly sent me some help.... > Mike, > To view MARC records download MarcEdit http://oregonstate.edu/~reeset/marcedit/html/index.html > It is free. > The MARC format is a compressed format, it is all on one line. > MarcEdit is a wonderful tool and may be useful in cleaning the records before importing. > To get an overview of your MARC records, fields used, > MARC RTP http://www.loungebythelake.com/marcrtp/marc-explained.html is great. Also free. The above is helping enormously. The tutorials on that site are excellent. The reason why I thought the format might have been 7bit and on multiple lines was my cursory reading of: http://www.saas.nsw.edu.au/koha_wiki/index.php?page=WhatIsMarc e.g. 200 1# $a Je craque $b Text imprim� $f Guy Bedos 200 : title zone Of course I should read the full spec http://www.loc.gov/marc/ :-) With the wonderful MarcEdit program I have opened the marc file that Steven Baljkas posted and now I can read and understand each field. Thanks. -- Michael Lake Chemistry, Materials & Forensic Science, UTS Ph: 9514 1725 Fx: 9514 1460 -- UTS CRICOS Provider Code: 00099F DISCLAIMER: This email message and any accompanying attachments may contain confidential information. If you are not the intended recipient, do not read, use, disseminate, distribute or copy this message or attachments. If you have received this message in error, please notify the sender immediately and delete this message. Any views expressed in this message are those of the individual sender, except where the sender expressly, and with authority, states them to be the views the University of Technology Sydney. Before opening any attachments, please check them for viruses and defects.

1 0

Re: Re: [Koha] How to get MARC biblio export to work? 2.0.1RC1
by Baljkas Family 03 Nov '04

03 Nov '04

Wednesday, November 3, 2004 09:38 CST Hi again, Michael, Well, I don't know about how to get it to display -- I thought that it just did 'automagically' (as one Koha'ite put it earlier on) -- but I can answer your query about MARC record structure. > > [snip] > > The record attached is for: > > The hidden encyclical of Pius XI / Georges Passelecq and > > Bernard Suchecky ; translated from the French by Steven > > Rendall ; with an introduction by Garry Wills. -- > > > > Thanks. I have the attachment fine but I'm wondering if there are some > character encoding probs. It appears on a single line in either Windows > or Linux and there are control characters in the text. I was expecting > ASCII or 7 bit stuff. Would that be correct? I take it when you say control characters, you mean the little box-like things (or other symbols). These indicate the beginnings of subfields (well, that, and a few other things). They are supposed to be there. BTW, different systems -- ILS and editors -- will display different symbols to show these delimiters, but all amount to the same thing. As for the single line: MARC records are usually short enough to fit on one line in a text editor. If you take a look at the record, it begins with a set of fixed position-coding data called the Leader, which is immediately followed by a set of numbers called the Directory. If you took a really careful look at the Directory you could see that the different MARC tags you have in your record are encoded there, along with the number of spaces the data in the fields takes up. The Directory essentially encodes the data matrix, allowing for unpacking of the information. For a better explanation than I am giving, please see: <http://www.loc.gov/marc/umb/um11to12.html> In terms of ASCII or 7-bit stuff: as far as I know, the character set has always been ASCII. In one section of the General Introduction to MARC21 Concise Bibliographic Format <http://www.loc.gov/marc/concise/concise.html#general_intro> (i.e. what is used for item records), there is a note stating "ASCII is used for the structure elements of the record, with most coded data also specified within the ASCII range of characters." In fact, in the formal explanations there, one sees references to specific ASCII codes (e.g. "The Directory ends with a field terminator character (ASCII 1E hex)" and, under Variable fields, "The data in a MARC 21 record is organized into variable fields, each identified by a three-character numeric tag that is stored in the Directory entry for the field. Each field ends with a field terminator character. The MARC record ends with a record terminator (ASCII 1D hex)"). Anyway, I hope that helps clarify, Michael. If I am missing what you meant or misunderstanding it, please let me know and I'll try again. > I tried it anyway and received: > Import into Breeding Farm, 2 imported records, 2 records parsed. > This suggests then that its in the "Breeding Farm" and that when I do a > MARC search it will find it. > When I go to the catalog and search on 245a - Title contains 'hidden' or > 100c - Title and other words contains 'hidden' I dont get any biblios. As you stated elsewhere that you are using MARC21, the 100c definitely should NOT have the word 'hidden' in it. That occurs in the 245a. The 'title' in the 100c is not the title of a work but rather a title in the sense of honorific! If you look at the examples for proper coding of the 100 field on the LC site at <http://www.loc.gov/marc/bibliographic/ecbdmain.html#mrcb100> you would find the following 2 illustrations of what is meant: 100 0#$aJohn,$cthe Baptist, Saint. 100 0#$aJohn$bII Comnenus,$cEmperor of the East,$d1088-1143. Hope that helps. > It's a bit hard to see what's what as it's all on one line. True, but then again, MARC communications format is really not meant for us to read, but for computers. ;-) They don't need the spaces our brains like to have. It takes some time, but, if you want to, eventually you could get used to reading raw MARC just as easily as the more user-friendly tagged (matrix) form. In the meantime, continued good luck with your work. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada

1 0

Re: Re: [Koha] How to get MARC biblio export to work? 2.0.1RC1
by Baljkas Family 03 Nov '04

03 Nov '04

Tuesday, November 2, 2004 23:43 CDT Hi, Michael, I am attaching a single MARC record as you requested. If you want more, let me know. # From past experience trying to discuss them on the listserv and elsewhere, it'll probably be split into 2 parts, one part appearing somewhere in the body of this text I am typing, with the remainder (usually after the Directory part) continuing below. Hopefully, you'll still be able to recover it. I don't remember what extension Koha needs for its MARC records, so you may need to change the .mrc to something else. The record attached is for: The hidden encyclical of Pius XI / Georges Passelecq and Bernard Suchecky ; translated from the French by Steven Rendall ; with an introduction by Garry Wills. -- Let me know how it works out. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB, Canada > From: Michael Lake <Mike.Lake(a)uts.edu.au> > Date: 2004/11/02 Tue PM 10:58:47 CST > To: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] How to get MARC biblio export to work? 2.0.1RC1 > > Michael Lake wrote: > >>> loaded the sample data and so I have biblio info in there - I can > >>> search for and find it. But when I click Export it just saves an > >>> empty 'marc.pl' file. I expected lots of MARC stuff. > > Still trying to get this working. I have reinstalled just in case. > Running from command line: > perl -I /home/rsnsw/koha/intranet/modules -file marc.dat > just produces a page of HTML to screen now and at least no errors but no > file marc.dat > > I see that it needs to set a cookie. Cookies are allowed in my browser > and I can see the sessionID cookie from localhost there. > Im still getting a zero length file from running marc.pl > > What should I use from the command line to test it? What do people get? > > I prob also need to try a marc import but I dont have a example of a > single marc record. Can one be posted here as an example? I looked at > the archives but didnt find an 'example'. > > Thanks > > Mike > -- > Michael Lake > Chemistry, Materials & Forensic Science, UTS > Ph: 9514 1725 Fx: 9514 1460 > > > > -- > UTS CRICOS Provider Code: 00099F > DISCLAIMER: This email message and any accompanying attachments may contain > confidential information. If you are not the intended recipient, do not > read, use, disseminate, distribute or copy this message or attachments. If > you have received this message in error, please notify the sender immediately > and delete this message. Any views expressed in this message are those of the > individual sender, except where the sender expressly, and with authority, > states them to be the views the University of Technology Sydney. Before > opening any attachments, please check them for viruses and defects. > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha >

2 2

2.0.0 release date
by Paul POULAIN 02 Nov '04

02 Nov '04

Hi, My goal here is to ask for a 2.0.0 release date. It may sound strange to have the Release Manager asking users for a release date, but let me explain : The 2.1.3 works fine since some weeks in EMN, in France. My opinion is that the 2.1.3 can be used in production. Not 100% bug free with a UNIMARC DB, but works. The question is : how works 2.1.3 with a MARC21 installation ? Important question, but I don't know it's answer yet. Nelsonville or Katipo, did you do some tests ? So, when do you think I could publish a 2.2.0RC1 in the stable tree ? My opinion is ASAP : I don't want to wait for months like I did for 2.0.0. As I said previously, I realize delaying the 2.0.0 version had a very bad effect on french libraries, that didn't want to install 2.0.0RCx, thinking it was too unstable. The DB schema didn't change from 2.1.2 to 2.1.3 and still has no change. I think this is the most important point : the DB IS stable, so Koha is on the road to be stable. Feel free to argue if you don't agree & have any other opinion/idea. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

3 2

Koha future
by Paul POULAIN 02 Nov '04

02 Nov '04

Hi all, I tried to put all suggestions for Koha future into a wiki page. It's on : http://www.saas.nsw.edu.au/koha_wiki/index.php?page=KohaRoadmap2.2.x I merged 2.2.x and 2.4.0 features. But the table shows in which version it should be done. Feel free to complete this page, I will add features myself if you post only on this list. -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)

1 0

Koha - copyright date
by Bernadette Cassidy 02 Nov '04

02 Nov '04

Hi, Since the upgrade of Koha to version 2.0, I've noticed when adding new items that Koha doesn't display the publication date - see attached catalogue record. Does anyone know why?! Kind regards, Bernadette Bernadette Cassidy Library & Learning Coordinator Allan Bean Centre for Research and Learning in Rehabilitation Private Bag 4708 Christchurch Tel: (03) 383 9492 Fax (03) 383 7500 Email: bernadettec(a)burwood.org.nz <mailto:bernadettec@burwood.org.nz>

2 1

Considering Open Source Software ( for lib. article smecc got a mention)
by COURYHOUSE＠aol.com 01 Nov '04

01 Nov '04

http://www.infotoday.com/cilmag/sep04/balas.shtml dated nov 1, 2004

1 0

Re: Thanks :)
by Olwen 29 Oct '04

29 Oct '04

1 0

Server Error: opac-main.pl, path problem
by Library 29 Oct '04

29 Oct '04

I tried to install koha-2.0.1. After installtion, the home page cgi-bin/koha/opac-main.pl, in browser gave following error. > The server encountered an internal error and was unable to complete > your request. Error message: Premature end of script headers: opac-main.pl On manual running it gave following error: > [root@glide cgi-bin]# ./opac-main.pl > Can't locate C4/Auth.pm in @INC (@INC contains: > /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 > /usr/lib/perl5/site_perl/5.8.0/i386-linux-thread-multi > /usr/lib/perl5/site_perl/5.8.0 /usr/lib/perl5/site_perl > /usr/lib/perl5/vendor_perl/5.8.0/i386-linux-thread-multi > /usr/lib/perl5/vendor_perl/5.8.0 /usr/lib/perl5/vendor_perl > /usr/lib/perl5/5.8.0/i386-linux-thread-multi /usr/lib/perl5/5.8.0 .) at > ./opac-main.pl line 7. > BEGIN failed--compilation aborted at ./opac-main.pl line 7. > [root@glide cgi-bin]# If I include path like perl -I /usr/local/koha/intranet/modules/ opac-main.pl , then it executed fine. On using: export PERL5LIB="/usr/local/koha/intranet/modules" it runs fine, when used as ./opac-main.pl and [root@glide cgi-bin]# export shows following: declare -x PERL5LIB="/usr/local/koha/intranet/modules" But through browser, it gave same error of "Premature end of script headers: opac-main.pl". What will be solution? -- H.S.Rai

3 2

Authorization problems between Koha and Mysql
by csg7142＠students.kennesaw.edu 29 Oct '04

29 Oct '04

My apologies if this issue has been addressed previously, I didnt find it in the archives. After logging into Koha the login screen keeps appearing again after clicking on a new link. We where able to add a branch but no books or new users. The Mysql Koha tables are empty. Any help would be beneficial. We are running: http://localhost:8080/cgi-bin/koha/about.pl Koha version: 2.0.1RC1 OS version (from 'uname -a'): OpenBSD 3.4 GENERIC#18 i386 Perl version: 5.008 MySQL version: 3.23.58 Apache version: Apache/1.3.28 (Unix) mod_ssl/2.8.15 OpenSSL/0.9.7b bash-2.05b# less /usr/local/koha/log/koha-error_log [Thu Oct 28 00:08:20 2004] [error] [client ###.###.###.###] File does not exist: /usr/local/koha/intranet/htdocs/favicon.ico DBD::mysql::st execute failed: Unknown column 'password' in 'field list' at /usr/local/koha/intranet/modules/C4/Auth.pm line 351. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 353. DBD::mysql::st execute failed: Unknown column 'password' in 'field list' at /usr/local/koha/intranet/modules/C4/Auth.pm line 359. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 361. DBD::mysql::db selectrow_array failed: Table 'Koha.sessions' doesn't exist at /usr/local/koha/intranet/modules/C4/Auth.pm line 224. DBD::mysql::st execute failed: Unknown column 'password' in 'field list' at /usr/local/koha/intranet/modules/C4/Auth.pm line 351. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 353. DBD::mysql::st execute failed: Unknown column 'password' in 'field list' at /usr/local/koha/intranet/modules/C4/Auth.pm line 359. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 361. DBD::mysql::db do failed: Table 'Koha.sessions' doesn't exist at /usr/local/koha/intranet/modules/C4/Auth.pm line 281. DBD::mysql::db do failed: Table 'Koha.sessions' doesn't exist at /usr/local/koha/intranet/modules/C4/Auth.pm line 283. DBD::mysql::st execute failed: Unknown column 'userid' in 'where clause' at /usr/local/koha/intranet/modules/C4/Auth.pm line 400. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 401. DBD::mysql::st execute failed: Unknown column 'flags' in 'field list' at /usr/local/koha/intranet/modules/C4/Auth.pm line 385. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 386. DBD::mysql::st execute failed: Table 'Koha.userflags' doesn't exist at /usr/local/koha/intranet/modules/C4/Auth.pm line 388. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 389. DBD::mysql::st execute failed: Unknown column 'userid' in 'where clause' at /usr/local/koha/intranet/modules/C4/Auth.pm line 426. DBD::mysql::st fetchrow failed: fetch() without execute() at /usr/local/koha/intranet/modules/C4/Auth.pm line 428. =-=-=-=-=-=-= Chris Gilbert Kennesaw State University -------------------------------------------------

2 1