![[GILS Logo]](/Images/gils-logo.gif) |
|
gils: Re: GILS to USMARC mapping. |
gils: Re: GILS to USMARC mapping.
Re: GILS to USMARC mapping.
Rebecca S. Guenther (rgue@loc.gov)
Fri, 11 Oct 1996 15:04:12 -0400 (EDT)
Date: Fri, 11 Oct 1996 15:04:12 -0400 (EDT)
From: "Rebecca S. Guenther" <rgue@loc.gov>
To: "Margaret St. Pierre" <saint@bluangel.com>
Subject: Re: GILS to USMARC mapping.
In-Reply-To: <9610101147.AA00987@bluangel.com>
Message-Id: <Pine.A32.3.93.961011075113.27025E-100000@rs8.loc.gov>
On Thu, 10 Oct 1996, Margaret St. Pierre <saint@bluangel.com> wrote:
>
> At 09:48 AM 10/9/96 -0400, you wrote:
> >
> > There is the element that was added called "Medium". This was mapped to
> > 245$h (Medium, in title field), although some consideration was given to
> > mapping it to the Leader/06 (Type of record).
> >
> > The element you are referring to would be roughly equivalent to ObjectType
> > in the Dublin Core list of elements. There has been a lot of discussion
> > about what should go there, and there are various levels of "object type".
> > As to the "Type of Record" in USMARC, perhaps there should be an element
> > in GILS, since there seems to be nothing now that could generate that,
> > except making an inference from the "Medium". However, since I see the
> > "Medium" element is actually "Availability Medium", this may not always be
> > the same as the type of record. We are having discussions in the USMARC
> > community about how to code Type of record for electronic items; whether
> > using the code that indicates it is a computer file is useful when the
> > content is, for example, a digitized picture (some think it should be
> > coded in Type of record as "graphic" in this case).
> >
> > The Dublin Core ObjectType has been mapped to Leader/06, although that
> > mapping is far from perfect since a mixture of levels of object types
> > will likely be used for that element. However, for GILS, there could be
> > guidelines as to what specific values are used.
>
> It was suggested that if a GILS record contains one or more Available
> Linkage elements, that the USMARC Type of Record mapping should be an
> electronic information resource (code "m"). All other cases would
> result in code "a" (other), until it is determined what is meant by a
> geospatial resource. Does this seem like reasonable guidelines for now?
It would be useful if there were a way to identify a geospatial resource,
which may speak to adding an element for Object Type as you initially
asked. Is there anything else in the GILS record to identify it as
geospatial? Otherwise for now these guidelines are reasonable.
> >> What does it mean when a single GILS element maps to multiple USMARC
> >> tags? Does it mean that the element is replicated once for each
> >> USMARC tag?
> >>
> > Please give an example of where this occurs. I think the original mapping
> > may have had some cases where 2 USMARC tags were used, but since the
> > revision a year or so ago, these had been changed.
>
> For example, the GILS element 'Author' maps to USMARC Tags 100, 110, 111,
> 400, 410, 411, 700, 710, 711, 800, 810, 811. Should I map the Author to
> all these USMARC tags? Date of Publication, Place of Publication, Language
> of Resource, and Cross Reference Relationship also map to multiple USMARC
> tags, according to the GILS Profile.
I'm glad you brought this up. I didn't realize that some of the elements
mapped to multiple MARC tags. A discussion about this with Eliot revealed
that some of these mappings came from the Bib 1 attribute set. I am
revising the mapping and Eliot will change the profile accordingly. Here
are the revised mappings:
Originator: 710
(always a corporate body; can't be in 110 because it isn't repeatable)
Author: 720
(this is a new uncontrolled name field, undistinguished by type of name)
Date of publication: 260$c
260$c=Date of publication, distribution, etc.
Place of publication: 260$a
260$a=Place of publication, distribution, etc.
Language of resource: 041$a
041$a=Language code
Cross reference relationship: 787$g
787$g=Nonspecific relationship entry--Relationship information
Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^ Rebecca S. Guenther ^^
^^ Senior MARC Standards Specialist ^^
^^ Network Development and MARC Standards Office ^^
^^ Library of Congress ^^
^^ Washington, DC 20540-4020 ^^
^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
^^ rgue@loc.gov ^^
^^ ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^