[Koha] 090 Fields

[Bigwood, David]

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 at lpi.usra.edu
Lunar & Planetary Institute
cataloging news: http://www.catalogablog.blogspot.com

-----Original Message-----
From: Steven F. Baljkas [mailto:baljkas at mb.sympatico.ca]
Sent: Tuesday, September 09, 2003 12:58 AM
To: Greg Lambert/Amigos; koha at lists.katipo.co.nz
Cc: baljkas at 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