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 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@amigos.org http://www.amigos.org
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@skemotah.com
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
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 ----- Original Message ----- From: "Greg Lambert/Amigos" <lambert@amigos.org> To: <koha@lists.katipo.co.nz> Sent: Monday, September 08, 2003 4:11 PM Subject: [Koha] 090 Fields the
item number information (at least in the colleges I've worked). Is that not the case with MARC21?
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@amigos.org http://www.amigos.org
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
I all, I've read the mail on this thread rapidly. I just wanted to explain something : To support any MARC flavour, NO MARC TAG/SUBFIELDS ARE HARDCODED into Koha. So, you can move the koha fields that are mapped to 090 in the default configuration to ANYTHING YOU WANT. There is only 2 constraints : * The 2 koha fields MUST be in the same MARC tag. * No other subfield can be defined in this tag. It's only for koha internal use. I hope this is a good news for you, and hope you'll like more and more how Koha was designed :-) (Koha MARC DB design is @ Paul, Steve and Serguey iirc. You can see some benchmarks history in /marc/ directory of cvs) -- Paul POULAIN Consultant indépendant en logiciels libres responsable francophone de koha (SIGB libre http://www.koha-fr.org)
participants (4)
-
Greg Lambert/Amigos -
paul POULAIN -
Stephen Hedges -
Steven F. Baljkas