- Koha - lists.katipo.co.nz

Marc and LC call number import
by Zeki Celikbas 11 Sep '03

11 Sep '03

hi all I'm working a branch library of the university. We are cataloging our library records to the main library's database. But they are not let us to use the circulation systems. Because of this I want to use the koha to make my library's circulation. Our records are usmarc format and we use LC call numbers at 050 fields first and second indicators are 0. It will be welcome for us to resolve LC call number problem at Koha. By the way I'm using a little book called "Understanding MARC Bibliographic: Machine-Readable Catatoging" which can be downloadable from LC's web sites. http://www.loc.gov/marc/umb/ The book is explain most using marc tags with examples. You can download the chapters and print out them to use hard copy. Zeki Celikbas Librarian ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Istanbul Technical University e:mailto:celikbas@itu.edu.tr Faculty of Aero. & Astro. w:http://www2.itu.edu.tr/~celikbas 80626 Maslak Istanbul Turkey t:(212)2853108 f: (212)2853139 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

1 0

RE: [Koha] 090 Fields
by Bigwood, David 11 Sep '03

11 Sep '03

Steven, The call number in 050 and 090 are for the manifestation of the work not the individual copy. 852, is for copy information, so that would not be a good choice to map the info to. Greg's records should have a field with copy info including a call number, location within his institution, cost, fund info and whatever his institution needs to attach to that copy. That is good for 852. 050 and 090 classification information is not copy related. The Functional Requirements for Bibliographic Records (FRBR) clear up some of the confusing aspects of our bib records. I never knew that LC used 090 for local call numbers, interesting bit of history. That explains why it is so common to see that field used. Sincerely, David Bigwood bigwood(a)lpi.usra.edu Lunar & Planetary Institute cataloging news: http://www.catalogablog.blogspot.com -----Original Message----- From: Steven F. Baljkas [mailto:baljkas@mb.sympatico.ca] Sent: Tuesday, September 09, 2003 12:58 AM To: Greg Lambert/Amigos; koha(a)lists.katipo.co.nz Cc: baljkas(a)mb.sympatico.ca Subject: Re: [Koha] 090 Fields Tuesday, September 9, 2003 00:50 CDT Hi, Greg, It's not unusual for ILS to use 090 for the call number used by the library. This is, in part, because LC used it for both Local Call Number and Shelf Location at different times in the past (I actually have a print-off of an old-enough USMARC Concise Format that lists the 090 that way with the notation obsolete) and when it was cleared for system developpers use, many remembered its past and kept it going. Unless you've dumped your database in migrating/upgrading the Koha, the info should still be there. Did the call numbers not end up in Koha somehow? How did you go about mapping your 090 into Koha? If it didn't work and you still have the original data, you might want to: · attempt mapping the 090 data into a properly formatted 852 field; or, as a stop-gap · select a 9xx number field that wasn't used in your data and isn't used in Koha and move the call numbers there with a global MARC editor (see the MARC tools pages at LC for MARCEdit) Or if Koha currently supports global edits of its MARC data (does it? I don't remember reading so) I suppose you could do it within the system. As for issues, I would guess that if the data did map, you'd now have items types of all the LC classes. That oughta be a neat wake-up call to patrons! ;-) As for the 001 field, yes, you're mostly right. Its formal definition is Control Number, that is, the number the ILS knows the item by, acting as a primary key for the database structure holding all the bibliographic records (i.e. it must be unique within the whole mass). Hope this helps. If you want some help with the 852 write me back off-list and I'll be glad to assist. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB CANADA

3 2

Re: [Koha] support for LC call numbers, authority cross-references?
by baljkas＠mb.sympatico.ca 09 Sep '03

09 Sep '03

Tuesday, September 9, 2003 16:15 CDT Hi, Robert, Welcome to the list. I'm sure you'll find, as I have, that this is a great little community of helpful folk. I'll attempt a quick answer to your questions. 1) LC -- no, not *yet*. Ed Sharpe and many of the rest of this would like to see it, and it is probably being worked on since the Koha cognoscenti realise that it is in demand. Maybe Paul Poulain will be able to tell us what stage LC-readiness is at. 2) Cross-reference authorities - this question was asked a while ago and I think the answer was still no. There is an authority table, though, I haven't had to use because I'm working with Koha on a family library collection. I know it breaks the rules, but -- for those of us who've had to work with systems that had no authorities, this was the only choice --there is a way to 'rig' dummy bibliographic records that redirect patrons to other headings. 3) Farsi (Persian) script support - I am sure that the answer to this would be, 'Would you like to do the coding?' ;-) Seriously, I don't think Koha's close to that level yet. Only a few costly ILS are capable of it, as far as I've learned. Wouldn't it be serviceable to use the ALA-LC transliteration tables for the mean time, though? There was someone asking about Arabic a while ago now so perhaps there is some work being done on that. Pat Eyler would probably now. Best wishes to your librarian as she heads off to Afghanistan. What a great project for your university to attempt, official or not! A friend of a friend of mine was there last year with the UN helping set up their government's economics stuff and he had a good experience (despite the lack of running water at the time). All the best to her. Cheers, Steven F. Baljkas library tech at large Koha neophyte Winnipeg, MB CANADA

1 0

Re: [Koha] support for LC call numbers, authority cross-references?
by COURYHOUSE＠aol.com 09 Sep '03

09 Sep '03

Ah! Welcome yet another LC person! Ed Sharpe > Subj: [Koha] support for LC call numbers, authority cross-references? > Date: 9/9/2003 10:43:14 AM US Mountain Standard Time > From: <A HREF="mailto:rgrunloh@s4.library.arizona.edu">rgrunloh(a)s4.library.arizona.edu</A> > To: <A HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A> > Sent from the Internet > > > > Hi all, > > I'm very happy to see that a project like this exists. Here at the > University of Arizona Library, we have a librarian who is going to Kabul, > Afghanistan, to try to help them reopen (I think) their University > Library. She needs a small economical system to 'bootstrap' their > operation on no funds, and Koha looks like a wonderful contribution. > > My role in this has only been to do a test install for her, and provide > some opensource software she can take with her on cd. We believe they have > some sort of PC that can run Linux, and an internet connection, and > someone who can install it. > > But of course she has questions I've been unable to answer. The 2 most > pressing for her are, does Koha support using LC call numbers for the > collection, and does it support cross-references, ie some sort of > authority control? I haven't been able to find evidence of them. > > Has this been discussed before? > > The third thing she would like to add, which would be in the distant > future, is farsi (Persian) language support. We have some programming > staff here but her Afghanistan trip is not an official University project > at this point. Sometimes things like this can grow, of course ... > > Thanks very much, > > Robert Grunloh > Support Systems Analyst Sr. > University of Arizona Library > Tucson AZ >

1 0

C4 @INC
by Greg Lambert/Amigos 09 Sep '03

09 Sep '03

I'm doing a "fresh install" with Pre3 and am having a brainlock: Would someone please remind me how to update the C4 directory in @INC? I'm running the bulkmarcimport.pl file and am getting the "can't locate C4 /Context.pm in @INC..." error. I remember updating the @INC file to include the C4 directory, but can't remember exactly what I did.... Thanks! -Greg Greg Lambert, JD, MLIS Project Manager Amigos Library Services, Inc. 5000 Gulf FWY Building 9 - Univ. Business Park Houston, Texas 77023-4600 713/923-2373 x225 office 877/707-1577 toll-free 713/923-2192 fax 281/433-9145 cell lambert(a)amigos.org http://www.amigos.org

3 2

Re: [Koha] 090 Fields
by COURYHOUSE＠aol.com 09 Sep '03

09 Sep '03

Then Koha should be changed to make things compliant one should not expect people to have to move data around if ... that is where the data would be normally found. Ed Sharpe > > > Fields 090 and 092 are very often used by institution to store their locally > created LC class number and Dewey class number. It is very common to see > that information there. It was not a safe field. > > Picking those fields to store other information was not the best choice. > Something in the 9XX would have been better. > > However, if someone has info in 090, they could move it to 050, with a > second indicator of 4. 050 can repeat, so the record could have an 050 with > a second indicator of 0 for LC and another with a second indicator of 4 for > the locally created number. > > MarcEdit or MARC::pm may be able to make the change. > > Field 001 is used for the bibliographic record number. It can be different > for each institution. An institution receiving a record from OCLC, for > example, will move the current record number to 035 and then place their > number in 001 and their institutional code in 003. > > Each bibliographic record can have several items attached to that one > record. For instance, an encyclopedia will only have the one record for the > work but each volume must have their individual barcodes, and other copy > information recorded. > > The copy and work information should be kept separate and not confused. > > Sincerely, > David Bigwood > bigwood(a)lpi.usra.edu > Lunar &Planetary Institute > Cataloging news: http://www.catalogablog.blogspot.com >

1 0

RE: [Koha] 090 Fields
by Bigwood, David 09 Sep '03

09 Sep '03

Fields 090 and 092 are very often used by institution to store their locally created LC class number and Dewey class number. It is very common to see that information there. It was not a safe field. Picking those fields to store other information was not the best choice. Something in the 9XX would have been better. However, if someone has info in 090, they could move it to 050, with a second indicator of 4. 050 can repeat, so the record could have an 050 with a second indicator of 0 for LC and another with a second indicator of 4 for the locally created number. MarcEdit or MARC::pm may be able to make the change. Field 001 is used for the bibliographic record number. It can be different for each institution. An institution receiving a record from OCLC, for example, will move the current record number to 035 and then place their number in 001 and their institutional code in 003. Each bibliographic record can have several items attached to that one record. For instance, an encyclopedia will only have the one record for the work but each volume must have their individual barcodes, and other copy information recorded. The copy and work information should be kept separate and not confused. Sincerely, David Bigwood bigwood(a)lpi.usra.edu Lunar & Planetary Institute Cataloging news: http://www.catalogablog.blogspot.com -----Original Message----- From: Stephen Hedges [mailto:shedges@skemotah.com] Sent: Monday, September 08, 2003 7:23 PM To: Greg Lambert/Amigos Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] 090 Fields Greg Lambert/Amigos said: > As I was reviewing the bulkmarcimport I noticed that the 090 MARC field is > used by Koha as the ITEMTYPE fields. > > In the MARC data I am importing, the 090 "a" and "b" subfields are > assigned > local LC call numbers. > > Since Koha assigns "a" as Koha Itemtype (NR) > "b" as Koha Dewey Subclass (NR) > "c" as Koha biblionumber (NR) > "d" as Koha biblioitemnumber (NR) > > What will happen to my original 090a and 090b fields? Will they still be > in the database? If so, will this cause item "issues"? > > My limited cataloging knowledge tells me that the 001 field is used for > the > item number information (at least in the colleges I've worked). Is that > not the case with MARC21? > > > Thanks! > -Greg Hmmm. Do you mean your existing MARC records use an 090 field? Koha has to store some important non-MARC information, primarily the biblionumber, biblioitemnumber and the itemtype, in the MARC record in order to interface with the "old" Koha databases. The 090 tag was chosen because neither MARC21 nor Unimarc define any use for this tag, so it was considered to be "safe." If you have existing MARC records that have data in an 090 tag, then you have a problem. You could move the data to a new tag using MARC::Record. -- Stephen Hedges Skemotah Solutions, USA www.skemotah.com -- shedges(a)skemotah.com _______________________________________________ Koha mailing list Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

1 0

Re: [Koha] 090 Fields
by COURYHOUSE＠aol.com 09 Sep '03

09 Sep '03

I guess what we have to analyze ... "is Koha doing something non standard that impacts the integrity of the MARC record? " if so perhaps the non standard information needs to be at the end of the record past where the MARC data is kept? if there is no area present perhaps one needs to be created as a 'stash' Just a thought.... Ed Sharpe archivist for SMECC > Subj:Re: [Koha] 090 Fields > Date:9/8/2003 5:24:04 PM US Mountain Standard Time > From:<A HREF="mailto:shedges@skemotah.com">shedges(a)skemotah.com</A> > To:<A HREF="mailto:lambert@amigos.org">lambert(a)amigos.org</A> > CC:<A HREF="mailto:koha@lists.katipo.co.nz">koha(a)lists.katipo.co.nz</A> > Sent from the Internet > > > > > Greg Lambert/Amigos said: > > As I was reviewing the bulkmarcimport I noticed that the 090 MARC field is > > used by Koha as the ITEMTYPE fields. > > > > In the MARC data I am importing, the 090 "a" and "b" subfields are > > assigned > > local LC call numbers. > > > > Since Koha assigns "a" as Koha Itemtype (NR) > > "b" as Koha Dewey Subclass (NR) > > "c" as Koha biblionumber (NR) > > "d" as Koha biblioitemnumber (NR) > > > > What will happen to my original 090a and 090b fields? Will they still be > > in the database? If so, will this cause item "issues"? > > > > My limited cataloging knowledge tells me that the 001 field is used for > > the > > item number information (at least in the colleges I've worked). Is that > > not the case with MARC21? > > > > > > Thanks! > > -Greg > > Hmmm. Do you mean your existing MARC records use an 090 field? Koha has > to store some important non-MARC information, primarily the biblionumber, > biblioitemnumber and the itemtype, in the MARC record in order to > interface with the "old" Koha databases. The 090 tag was chosen because > neither MARC21 nor Unimarc define any use for this tag, so it was > considered to be "safe." If you have existing MARC records that have data > in an 090 tag, then you have a problem. You could move the data to a new > tag using MARC::Record. > > -- > Stephen Hedges > Skemotah Solutions, USA > www.skemotah.com -- shedges(a)skemotah.com > _______________________________________________ > Koha mailing list > Koha(a)lists.katipo.co.nz > http://lists.katipo.co.nz/mailman/listinfo/koha Thanks Ed Sharpe, Archivist for SMECC See the Museum's Web Site at www.smecc.org We are always looking for items to add to the museum's display and ref. library please advise if you have anything we can use. mail: Coury House / SMECC 5802 W. Palmaire Ave. Glendale Az 85301 USA 623-435-1522 CONFIDENZIALE: Questo messaggio e gli eventuali allegati sono confidenziali e riservati. Se vi è stato recapitato per errore e non siete fra i destinatari elencati, siete pregati di darne immediatamente avviso al mittente. Le informazioni contenute non devono essere mostrate ad altri, né utilizzate, memorizzate o copiate in qualsiasi forma. CONFIDENTIAL: This e-mail and any attachments are confidential and may contain reserved information. If you are not one of the named recipients, please notify the sender immediately. Moreover, you should not disclose the contents to any other persons, nor should the information contained be used for any purpose or stored or copied in any form.

2 1

Re: [Koha] C4 @INC
by Greg Lambert/Amigos 08 Sep '03

08 Sep '03

Thanks MJ, The "export PERLLIB=/path/to/directory" did it for me!! -Greg Greg Lambert, JD, MLIS Project Manager Amigos Library Services, Inc. 5000 Gulf FWY Building 9 - Univ. Business Park Houston, Texas 77023-4600 713/923-2373 x225 office 877/707-1577 toll-free 713/923-2192 fax 281/433-9145 cell lambert(a)amigos.org http://www.amigos.org

1 0

Re: [Koha] C4 @INC
by Greg Lambert/Amigos 08 Sep '03

08 Sep '03

Okay.... I remember what I did.... Let me know if this is a bad way to do it. I copied the C4 directory into the PERL directory (one that was already listed in the @INC file).... It worked, but it may not be the most efficient way to do it. -Greg Greg Lambert, JD, MLIS Project Manager Amigos Library Services, Inc. 5000 Gulf FWY Building 9 - Univ. Business Park Houston, Texas 77023-4600 713/923-2373 x225 office 877/707-1577 toll-free 713/923-2192 fax 281/433-9145 cell lambert(a)amigos.org http://www.amigos.org

2 1