On second thought, but continuing with the idea of separate data
elements--the 1XX/240 usually contains a uniform entry NOT for the
object, but for the most substantial component of the object. One
could make a case for putting 1XX/240 data in a relatedItem
type:constituent element. What's missing is the ability to specify an
authority attribute for the relatedItem element (i.e., not just for
the subelements Name and titleInfo). Since there are MADS records
with "authority" elements for name/title combinations, which is what
would be contained here, maybe the "authority" attribute for
relatedItem is what's needed?
Stephen
>Date: Thu, 03 Jul 2008 11:02:08 -0500
>To: Metadata Object Description Schema List <[log in to unmask]>
>From: Stephen Hearn <[log in to unmask]>
>Subject: Re: [MODS] uniform titles in mods
>
>In MARC21, the 100 is one field with two uses. It is a name in its
>own right, figuring as a data element in relation to the bib record;
>and it is a lead element in the 1XX/240 "uniform title" data
>structure. These are separable functions, and we'd have been better
>served if they'd been separated in MARC. Maybe MODS could recognize
>this difference by defining "object uniform entry" (or some such) as
>a distinct data element containing Name and Title subelements, like
>"subject" and "relatedItem". Then the name element could be entered
>in two places to fulfill these two distinct functions. Our
>experience with MARC should teach us that trying to finesse these
>kinds of divergent functions with a single data element generally fails.
>
>Stephen
>
>At 06:47 PM 7/2/2008, you wrote:
>>Jenn,
>>
>>How far can you go using <role>? In the example your role term would be
>>"composer" and that would seem to fit -- but there might also be 700s that
>>are also going into a <name> tag, for example, for the conductor and
>>soloist, causing confusion? Could you think about it with respect to the
>>many complex situations that you encounter in the music and performance
>>material? Does one always know what role relates in a primary way to the
>>resource title? MODS does not preserve the "main" distinction but the role
>>can designate "author" and if there are joint authors can allow both to
>>support the title.
>>
>>If there are other a/t in the MARC record they go in either subject or
>>related item, of course, so they do not get in the way, but in some cases
>>could have the same issue.
>>
>>Sally
>>
>>
>>At 08:09 PM 6/29/2008 -0400, you wrote:
>> >Hello all,
>> >
>> >I'm having trouble figuring out how to encode a Uniform Title in a MODS
>>record. While some Uniform Titles (e.g., for the Bible) only have a title
>>component, most have both a name and title components, with the title not
>>making sense without the name. This is common for music.
>> >
>> >This is what a sample MARC name-title authority record would show:
>> >
>> >100 10 |a Beethoven, Ludwig van, |d 1770-1827. |t Symphonies, |n no.
>>5, op. 67, |r C minor
>> >
>> >And this is how the UT would appear in a MARC bibliographic record:
>> >
>> >100 1_ |a Beethoven, Ludwig van, |d 1770-1827.
>> >240 10 |a Symphonies, |n no. 5, op. 67, |r C minor
>> >
>> >The full UT is split across the 100/240 pair. For a MODS record, one would
>>think Beethoven would go in <name> and Symphonies... in <titleInfo
>>type="uniform">. But how is the connection between the name and the title
>>parts of the full UT made in the MODS record? In MODS, lists all the
>>contributors in <name> elements, whereas in MARC you only have one 100
>>field - other names are in 7xx fields.
>> >
>> >I'm not advocating MODS adopt the concept of main entry, but to use the UT
>>effectively (which presumably is a goal of MODS since type="uniform" is
>>defined for <titleInfo>) there needs to be *some* way to connect the right
>>name with the UT. I'm very uncomfortable with the idea of including the
>>name as part of the <titleInfo type="uniform"> - is that what is intended?
>>The MARC to MODS mapping seems to support this not being the right thing to
>>do. At <http://www.loc.gov/standards/mods/mods-mapping.html>, it just pulls
>>in 240 data into <titleInfo> - it doesn't include data from the 100. But
>>what other options are there?
>> >
>> >Thanks,
>> >
>> >Jenn
>> >
>> >========================
>> >Jenn Riley
>> >Metadata Librarian
>> >Digital Library Program
>> >Indiana University - Bloomington
>> >Wells Library W501
>> >(812) 856-5759
>> >www.dlib.indiana.edu
>> >
>> >Inquiring Librarian blog: www.inquiringlibrarian.blogspot.com
>> >
>>
>>********************************************************
>>Sally H. McCallum, Chief, Network Development and
>>MARC Standards Office, Library of Congress
>>Washington, DC 20540 USA
>>[log in to unmask] (Fax: 1-202-707 0115) (Voice: 1-202-707 5119)
>>********************************************************
>
>****************************************************
>Stephen Hearn
>Authority Control Coord./Database Mgmt. Section Head
>Technical Services Dept.
>University of Minnesota
>160 Wilson Library Voice: 612-625-2328
>309 19th Avenue South Fax: 612-625-3428
>Minneapolis, MN 55455 E-mail: [log in to unmask]
****************************************************
Stephen Hearn
Authority Control Coord./Database Mgmt. Section Head
Technical Services Dept.
University of Minnesota
160 Wilson Library Voice: 612-625-2328
309 19th Avenue South Fax: 612-625-3428
Minneapolis, MN 55455 E-mail: [log in to unmask]
|