- Koha - lists.katipo.co.nz

Re: [Koha] MARC RECORD PROBLEM
by baljkas＠mb.sympatico.ca 29 Jul '03

29 Jul '03

Tuesday, July 29, 2003 15:34 CDT Hi, all, Paul/Rahayu, the record that was given as an example might be a valid MARC record and iso2709 file that's being dumped through an OCLC filter (the structure at the beginning anyway, combining the LEADER, 001, 005, and 008 elements is typical of them). This means you should be able to get it over to Koha. What system are you using, Rahayu? Can you export a raw MARC record? If you view a MARC record outside of an ILS or MARC editor, it will be a string of alphanumerics, with a lot of numbers at the beginning (the matrix for recompiling it into fields and subfields: For an explanation of how a MARC record is structured, surf to URL <http://www.loc.gov/marc/umb/um11to12.html> ). The real (raw) MARC record from Library of Congress record for the book you used as an example looks like this: 01153cam 2200301 a (BTW, no spaces were added or deleted to this example, so if you were to select the above text and dump it back into a text editor file, you would have a valid MARC21 record again.) Anyway, if you can get whatever system you're using to export records so that they look like the above in a simple text editor, you can get them over to Koha. Hope this helps. Don't give up on your data or Koha yet., ;-) Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB CANADA paul POULAIN <paul.poulain(a)free.fr> wrote: >rahayu rms wrote: > >> Hi..... >> >> I have installed koha Koha - V2.0.0pre2. on windows and successfully >> run. But I have problem to import 5000 marc record into koha. I would >> like to test koha using our data. >> Anybody know how to transfer data using marc record.These are sample >> data.Is it in the correct format?.I need some help.I hope somebody >> can explain how to do it & how the format? >> >> Rec stat: n >> Entered: 20021020 Replaced: 20021020 >> Type: a ELvl: 1 Srce: a Audn: Ctrl: >> Lang: eng >> BLvl: m Form: Conf: 0 Biog: MRec: >> Ctry: xxk >> Cont: GPub: Fict: 0 Indx: 0 >> Desc: a Ills: Fest: 0 DtSt: e Dates: 2002, >> ÿ040 ßc KUI >> ÿ020 0471126500 >> ÿ050 HG4751 ßb .C36 2002 >> ÿ090 HG4751 ßb .C36 2002 >> ÿ049 KUIM >> ÿ100 1 Camp, Justin J. >> ÿ245 10 Venture capital due diligence ßb a guide to making smart >> investment >> choices and increasing your portfolio returns ßc Justin J. Camp >> ÿ260 New York : ßb John wiley : ßc 2002 >> ÿ300 xi, 258p. : ßc 24cm >> ÿ504 Includes bibliographical references and index >> ÿ650 0 Venture capital >> Ü650 0 Rate of return >> Ü999 000010424 > >Is it a dump of your imported file ? >If yes, then it's not iso2709 file, so can't work. Koha handles only >iso2709, which is the standard anyway :-) > >-- >Paul POULAIN >Consultant indépendant en logiciels libres >responsable francophone de koha (SIGB libre http://www.koha-fr.org) 450000100090000000500170000900800410002690600450006792500420011295501320015 401000170028601500150030302000150031803500230033304000230035604200140037905 000220039308200190041510000200043424501340045426000300058830000250061844000 2500643504006400668650002100732650002000753856007800773126959312002081720 3133.0020308s2002 nyu b 001 0 eng d a7bcbcccopycatd2encipf20gy-gencatlg0 aacquireb2 shelf copyxpolicy default aps10 2002-03-08 to SSCDise02 2002-03-11; se00 recd copy 2 2002-03-15cse03 2002-03-22ese03 03-22-02 To Deweyaaa19 2002-04-08 a 2002277403 aGBA1-U8291 a0471126500 a(OCoLC)ocm48362961 aUKMcUKMdJBOdDLC alccopycat00aHG4751b.C36 200200a332.67/2532211 aCamp, Justin J.10aVenture capital due diligence :ba guide to making smart investment choices and increasing your portfolio returns /cJustin Camp. aNew York :bWiley,c2002. axi, 258 p. ;c24 cm. 0aWiley finance series aIncludes bibliographical references (p. 227-246) and index. 0aVenture capital. 0aRate of return.413Table of contentsuhttp://www.loc.gov/catdir/toc/wiley022/2002277403.html

1 0

member flag confuse
by rahayu rms 29 Jul '03

29 Jul '03

Hi, I am confused on how to determine level for user acess?For example V1000001-member flag ->circulate V1000002-member flag ->borrow When I checked in borrowers table, it shows Cardnumber Flags V1000001 2->what does it mean? V1000002 128->what does it mean? If flags in borrowers table is null, does it mean the person can acess all librarian function? 2. How many books for each person can borrow defend on category of user.Can Koha determine how many book for each borrower can borrow automatically? I am using koha v1.2.3 on windows. Thanks _________________________________________________________________ Using a handphone prepaid card? Reload your credit online! http://www.msn.com.my/reloadredir/default.asp

2 1

MARC RECORD PROBLEM
by rahayu rms 29 Jul '03

29 Jul '03

Hi..... I have installed koha Koha - V2.0.0pre2. on windows and successfully run.But I have problem to import 5000 marc record into koha .I would like to test koha using our data. Anybody know how to transfer data using marc record.These are sample data.Is it in the correct format?.I need some help.I hope somebody can explain how to do it & how the format? Rec stat: n Entered: 20021020 Replaced: 20021020 Type: a ELvl: 1 Srce: a Audn: Ctrl: Lang: eng BLvl: m Form: Conf: 0 Biog: MRec: Ctry: xxk Cont: GPub: Fict: 0 Indx: 0 Desc: a Ills: Fest: 0 DtSt: e Dates: 2002, ÿ040 ßc KUI ÿ020 0471126500 ÿ050 HG4751 ßb .C36 2002 ÿ090 HG4751 ßb .C36 2002 ÿ049 KUIM ÿ100 1 Camp, Justin J. ÿ245 10 Venture capital due diligence ßb a guide to making smart investment choices and increasing your portfolio returns ßc Justin J. Camp ÿ260 New York : ßb John wiley : ßc 2002 ÿ300 xi, 258p. : ßc 24cm ÿ504 Includes bibliographical references and index ÿ650 0 Venture capital Ü650 0 Rate of return Ü999 000010424 OCLC: NEW Rec stat: n Entered: 20021020 Replaced: 20021020 Type: a ELvl: 1 Srce: a Audn: Ctrl: Lang: eng BLvl: m Form: Conf: 0 Biog: MRec: Ctry: xxk Cont: GPub: Fict: 0 Indx: 0 Desc: a Ills: Fest: 0 DtSt: e Dates: 2002, ÿ040 ßc KUI ÿ020 0471126500 ÿ050 HG4751 ßb .C36 2002 ÿ090 HG4751 ßb .C36 2002 ÿ049 KUIM ÿ100 1 Camp, Justin J. ÿ245 10 Venture capital due diligence ßb a guide to making smart investment choices and increasing your portfolio returns ßc Justin J. Camp ÿ260 New York : ßb John wiley : ßc 2002 ÿ300 xi, 258p. : ßc 24cm ÿ504 Includes bibliographical references and index ÿ650 0 Venture capital Ü650 0 Rate of return Ü999 000010424 OCLC: NEW Rec stat: n Entered: 20021020 Replaced: 20021020 Type: a ELvl: 1 Srce: a Audn: Ctrl: Lang: eng BLvl: m Form: Conf: 0 Biog: MRec: Ctry: xxk Cont: GPub: Fict: 0 Indx: 0 Desc: a Ills: Fest: 0 DtSt: e Dates: 2002, ÿ040 ßc KUI ÿ020 0471126500 ÿ050 HG4751 ßb .C36 2002 ÿ090 HG4751 ßb .C36 2002 ÿ049 KUIM ÿ100 1 Camp, Justin J. ÿ245 10 Venture capital due diligence ßb a guide to making smart investment choices and increasing your portfolio returns ßc Justin J. Camp ÿ260 New York : ßb John wiley : ßc 2002 ÿ300 xi, 258p. : ßc 24cm ÿ504 Includes bibliographical references and index ÿ650 0 Venture capital Ü650 0 Rate of return Ü999 000010424 OCLC: NEW Rec stat: n Entered: 20021020 Replaced: 20021020 Type: a ELvl: 1 Srce: a Audn: Ctrl: Lang: eng BLvl: m Form: Conf: 0 Biog: MRec: Ctry: xxk Cont: GPub: Fict: 0 Indx: 0 Desc: a Ills: Fest: 0 DtSt: e Dates: 2002, ÿ040 ßc KUI ÿ020 0471126500 ÿ050 HG4751 ßb .C36 2002 ÿ090 HG4751 ßb .C36 2002 ÿ049 KUIM ÿ100 1 Camp, Justin J. ÿ245 10 Venture capital due diligence ßb a guide to making smart investment choices and increasing your portfolio returns ßc Justin J. Camp ÿ260 New York : ßb John wiley : ßc 2002 ÿ300 xi, 258p. : ßc 24cm ÿ504 Includes bibliographical references and index ÿ650 0 Venture capital Ü650 0 Rate of return Ü999 000010424 OCLC: NEW Rec stat: n Entered: 20021020 Replaced: 20021020 Type: a ELvl: 1 Srce: a Audn: Ctrl: Lang: eng BLvl: m Form: Conf: 0 Biog: MRec: Ctry: xxk Cont: GPub: Fict: 0 Indx: 0 Desc: a Ills: Fest: 0 DtSt: e Dates: 2002, ÿ040 ßc KUI ÿ020 0471126500 ÿ050 HG4751 ßb .C36 2002 ÿ090 HG4751 ßb .C36 2002 ÿ049 KUIM ÿ100 1 Camp, Justin J. ÿ245 10 Venture capital due diligence ßb a guide to making smart investment choices and increasing your portfolio returns ßc Justin J. Camp ÿ260 New York : ßb John wiley : ßc 2002 ÿ300 xi, 258p. : ßc 24cm ÿ504 Includes bibliographical references and index ÿ650 0 Venture capital Ü650 0 Rate of return Ü999 000010424 _________________________________________________________________ _________________________________________________________________ Are you in love? Find a date on MSN Personals http://match.msn.com.my/

2 1

Koha z39.50 client (2.0.0-pre1)
by Thien Ho 29 Jul '03

29 Jul '03

Hello, I've just installed Koha 2.0.0-pre1 to try z39.50 search. I did not find any place to specify a search term as well as z39.50 server. I did the following for a z39.50 search: - Run z3950-daemon-launch.sh - Go to Intranet site - Go to Acquisition page - Click the link "Add biblio without ISBN/ISSN" - Click the link "z3950 search" Now a window poppep up with the message 'Still ?? requests to go'... It does not seem to search any z39.50 server, even Library of Congress z39.50 server (the one listed in tables z3950servers). Am I missing something? What does the current z39.50 client do? Does it actually search a z39.50 server? Thien ctho(a)freeshell.org SDF Public Access UNIX System - http://sdf.lonestar.org

2 5

can koha calculate fines?
by rahayu rms 28 Jul '03

28 Jul '03

Hi.. 1. I am using koha v1.2.3 on windows.The problem is can Koha calculate fines if items on issue are overdue?When I return the borrower item which are overdue there is no fines or charges. As you said before, fines are worked out on the basis of borrower type and item type and it is like a matrix. I don't understand..What do you mean 'like a matrix'.Can you explain more on that? 2. Can I change cardnumber default using our own member number which have 7 characters for student and 4 characters for staff? _________________________________________________________________ Using a handphone prepaid card? Reload your credit online! http://www.msn.com.my/reloadredir/default.asp

2 1

Automatically adding a large number of books
by Kamuran Chabuk 27 Jul '03

27 Jul '03

I have a list of thousands of ISBN numbers. Is there a way to run these through a script or something so I can quickly download a MARC record via z39.50 and then add the book to the database? Kamuran Chabuk

1 0

RE: [Koha] Record doesn't exists on V2.0.0
by Lucia Phillip 26 Jul '03

26 Jul '03

I am experimenting with version 2 on Windows and I have tried to upload the same MARC files that I was able to upload using the earlier versions and when I check for the record in the breeding farm it says it does not exist. Lucia Phillip -----Original Message----- From: rahayu rms [mailto:ayunnisa82@hotmail.com] Sent: Saturday, July 26, 2003 2:04 AM To: koha(a)lists.katipo.co.nz Subject: [Koha] Record doesn't exists on V2.0.0 Hi.. I have try upload marc record using data from OCLC using extension file .dat and .bib. Statement shows that the records are imported.When I checked the record in biblio table, the record does not exists.Am I wrong or maybe something to do? Anybody can tell me and explain how to upload the record? I am using koha v2.0.0 on windows.. _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

2 1

Record doesn't exists on V2.0.0
by rahayu rms 26 Jul '03

26 Jul '03

Hi.. I have try upload marc record using data from OCLC using extension file .dat and .bib. Statement shows that the records are imported.When I checked the record in biblio table, the record does not exists.Am I wrong or maybe something to do? Anybody can tell me and explain how to upload the record? I am using koha v2.0.0 on windows.. _________________________________________________________________ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail

1 0

RE: [Koha] data import question - a few more thoughts
by baljkas＠mb.sympatico.ca 25 Jul '03

25 Jul '03

Friday, July 25, 2003 14:22 CDT David, Thank you for the very helpful rejoinder. I plead guilty to going with what was familiar to me. In all honesty, working with the few systems that I have, I'd never seen the holdings fields used and so hadn't looked into the 876. Of course, you are right. Very neat. Thank you for pointing all of us in a better direction! The FRBR stuff is also something I've yet to get into as keeping up with MARC has always seemed enough of a challenge. ;-) Thanks again, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB CANADA see P.S. below "Bigwood, David" <Bigwood(a)lpi.usra.edu> wrote: >Steven, > >Most of this I agree with 100%. Well said, it deserves better >distribution. > >However putting copy information into 037 is not the way I'd go. It is >not easy to distinguish the different information for different copies >there. Also, if we take a FRBR approach 037 seems to apply to the >expression but acquisition information belongs at the item level. P.S. when I'd used it that way, David, I'd taken advantage of its repeatability and the note fields to clarify the relationship of the price to the item level; nevertheless, you are right in what you say in recommending the 876. >Field 876 seems a better choice. That would tie the donated copy from >1999 to one item and the 1998 copy costing 45.00 from a particular fund >with another copy. > >Sincerely, >David Bigwood >bigwood(a)lpi.usra.edu >Lunar & Planetary Institute > >-----Original Message----- >From: baljkas(a)mb.sympatico.ca [mailto:baljkas@mb.sympatico.ca] >Sent: Thursday, July 24, 2003 7:51 PM >To: larry(a)larrystamm.com; koha >Cc: baljkas(a)mb.sympatico.ca >Subject: Re:[Koha] data import question - a few more thoughts > >Thursday, July 24, 2003 18:46 CDT > >Hi, Larry, > >Glad that some of what I wrote was useful. I know that the MARC stuff >isn't easy for those who haven't been 'initiated' into its mysteries. > >[major snip] Personally, I would have preferred the data to be placed >in a good old 037 tag. To my mind, its subfields provide for all of the >above, plus it can be entered at the time one creates a temporary >minimal record (to indicate to patrons searching that an item is >on-order for example) without the need to muck about with the 852 or >other call number field until the work is received in cataloguing. > >The map for the 037, is simple > $a Stock number - possibly useful for re-ordering/replacement > $b Source of stock number/acquisition ** > $c Terms of availability = (in almost all cases) price ** > $f Form of issue - easily adaptable to be an institution's needs > with a ltd. institution-specific set of terms or more ones > more generally recognised > $n Note - where you could easily enter acquisition fund (usually > coded in most institutions anyway), order date and received-in > date > >ex. 037 _ _ $bBook Barn $c$22.50 $c$5.00 (sale price) $fTrade pbk. > $nGenBkFund; ordered 20021209; received 20030108.

1 0

RE: [Koha] data import question - a few more thoughts
by Bigwood, David 25 Jul '03

25 Jul '03

Steven, Most of this I agree with 100%. Well said, it diserves better distribution. However putting copy information into 037 is not the way I'd go. It is not easy to distinguish the different information for different copies there. Also, if we take a FRBR approach 037 seems to apply to the expression but acquisition information belongs at the item level. Field 876 seems a better choice. That would tie the donated copy from 1999 to one item and the 1998 copy costing 45.00 from a particular fund with another copy. Sincerely, David Bigwood bigwood(a)lpi.usra.edu Lunar & Planetary Institute -----Original Message----- From: baljkas(a)mb.sympatico.ca [mailto:baljkas@mb.sympatico.ca] Sent: Thursday, July 24, 2003 7:51 PM To: larry(a)larrystamm.com; koha Cc: baljkas(a)mb.sympatico.ca Subject: Re:[Koha] data import question - a few more thoughts Thursday, July 24, 2003 18:46 CDT Hi, Larry, Glad that some of what I wrote was useful. I know that the MARC stuff isn't easy for those who haven't been 'initiated' into its mysteries. I snipped back some of my verbiage to make the more important parts a little more identifiable. Yes, your understanding is correct, Larry, in that 852 is "mainly" for use within an organization. However (you knew this was coming, didn't you? ;-) ) ... Part of the whole purpose of creating MARC records was the sharing of cataloguing data. LC proves this daily by giving us all free access to its records (well, one has to have the Internet, etc., etc., but that's not their fault). Part of what we're supposed to be doing, as cataloguers, is obey the conventions (AACR2R, ISBD, etc.) and the standards for use of the MARC21 system (this is why we are given examples, and for those lucky enough to work in libraries that can afford such, access to the Library of Congress Rule Interpretations, LCRIs). If sharing is going to be possible, we do have to look at how things are set up. Yes, it was arbitrary (small groups of people working mainly at LC), but it is thorough. It isn't really a good idea to start switching things around. I remember Athena very well. Especially the arguments I had with my so-called assistant over the useless entry of data like source of acquisition date, fund, price, all of which can be entered in other MARC fields properly kept out of patron's prying eyes anyway (no, I know that data isn't useless, but it can be very frustrating to try explaining to a patron why you're charging them $25 to replace a book they lost when your own catalogue says it only cost $5 [way back in 1979, of course] and I would still rather spend cataloguing time on Authority Records or at least on augmenting the collection with good 520s, genre labels and keywords to improve search results). While I admire the ingenuity of the computer-savvy in creating these wonderful systems -- and Athena is a very neat system that I quite like -- the problems it runs into are largely of its creators own making in deliberating deciding they know better than the sages of LC. When I was in grad school for history, my advisor constantly warned us students of the dangers of present-ism: 'If it's this way now, that's how it will always be, how it always was.' So, while I completely sympathise, Larry, LC-NLC have determined the usage of the field and subfields therein and it really isn't a good idea not to follow form. Who knows what developments in the future will bring? It makes it easier if we're all playing the game with the same rule book, even just for the present, let alone the future. The idea that all cataloguing is isolated from affecting others really belongs to the pre-MARC/online era. If we all follow the rules, we can all help each other out now and in the future. In the alternate mapping I suggested (and keep in mind, that's only my off-the-cuff attempt; it has no particular authority), I assumed you wanted to use the one field 852, so I just chose subfields that would allow you to do what you wanted within that one field. (BTW if the tab thing you were writing about to Derek would allow keeping the data in allowed subfields only, that would be preferable to what I suggested viz. a $d or $w.) When I was first confronted with this, I was mighty perturbed. I understand that Athena's programmers wanted to collect the data in one field: all they needed to do though was use multiple 852 $x fields! There is no reason at all for their creativity!! Following the rules would actually simplify matters. Personally, I would have preferred the data to be placed in a good old 037 tag. To my mind, its subfields provide for all of the above, plus it can be entered at the time one creates a temporary minimal record (to indicate to patrons searching that an item is on-order for example) without the need to muck about with the 852 or other call number field until the work is received in cataloguing. The map for the 037, is simple $a Stock number - possibly useful for re-ordering/replacement $b Source of stock number/acquisition ** $c Terms of availability = (in almost all cases) price ** $f Form of issue - easily adaptable to be an institution's needs with a ltd. institution-specific set of terms or more ones more generally recognised $n Note - where you could easily enter acquisition fund (usually coded in most institutions anyway), order date and received-in date ex. 037 _ _ $bBook Barn $c$22.50 $c$5.00 (sale price) $fTrade pbk. $nGenBkFund; ordered 20021209; received 20030108. Not very standardised, as you rightly hint. Or at least, not so much in the details. Core fields like the 008, 100, 245, 250, 260, 300 tend to be pretty good. But that doesn't mean we should stop trying. If it makes you feel any the better, I keep running across records in the NLC database where contributing cataloguers still aren't even following ISBD description rules for newer records (ca. 1985) and the ISBD rules, IIRC, are older than me! As a cautionary tale, let me warn you about what happened to one school division in Winnipeg. For years that division (and the one I reside and have worked in) used TKM Microcat, a decent system for when it was first created. They were told not to bother coding the 008 -- a core required field -- because that system didn't really use it (can't sort results by date, e.g. because of this). That minor reduction in labour over the years came as little comfort to the division's cheque book a few years back when all the schools had to send ALL their records for RECON because the new system they migrated to was MARC-compliant and viewed the records it was fed as the garbage they were! I kinda think LC should start gathering up a page of horror stories like this to remind folks why it is important to follow those nagging standards, even when it doesn't seem to have any purpose at the time. ;-) In any case, LC sets the structure (and it isn't completely autocratic BTW: someone at your level of authority in a library can make suggestions; my former supervisor did) and if you think it's difficult now, think what might happen if they designate something your system was using for a different purpose and many others go along with the change. Either 'welcome back to the age of splendid isolation' or See above for 'The moral of the story is ...' I would've brought you a thank-you card and cake! ;-) I agree. Plus making the patrons feel more at ease and part of the positive change, and this is of no inconsiderable value! Anyway, I hope some of what I've said this time makes sense, too, and that it may be useful to you and others. Cheers from Winnipeg, Steven F. Baljkas library tech at large Koha neophyte _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0