LISTSERV mailing list manager LISTSERV 16.0

Help for MODS Archives


MODS Archives

MODS Archives


MODS@LISTSERV.LOC.GOV


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

MODS Home

MODS Home

MODS  July 2008

MODS July 2008

Subject:

Fwd: Re: [MODS] uniform titles in mods

From:

Stephen Hearn <[log in to unmask]>

Reply-To:

Metadata Object Description Schema List <[log in to unmask]>

Date:

Thu, 3 Jul 2008 12:33:40 -0500

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (128 lines)

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] 

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

October 2019
September 2019
August 2019
June 2019
May 2019
March 2019
February 2019
January 2019
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011
February 2011
January 2011
December 2010
November 2010
October 2010
September 2010
August 2010
July 2010
June 2010
May 2010
April 2010
March 2010
February 2010
January 2010
December 2009
November 2009
October 2009
September 2009
August 2009
July 2009
June 2009
May 2009
April 2009
March 2009
February 2009
January 2009
November 2008
October 2008
September 2008
August 2008
July 2008
June 2008
May 2008
April 2008
February 2008
January 2008
December 2007
November 2007
October 2007
August 2007
July 2007
June 2007
May 2007
April 2007
March 2007
February 2007
January 2007
December 2006
November 2006
October 2006
September 2006
August 2006
July 2006
June 2006
May 2006
April 2006
March 2006
February 2006
January 2006
December 2005
November 2005
October 2005
September 2005
August 2005
July 2005
June 2005
May 2005
April 2005
March 2005
February 2005
January 2005
December 2004
November 2004
October 2004
September 2004
August 2004
July 2004
June 2004
May 2004
April 2004
March 2004
February 2004
January 2004
December 2003
November 2003
October 2003
September 2003
August 2003
July 2003
June 2003
May 2003
April 2003
March 2003
February 2003
January 2003
December 2002
November 2002
October 2002
September 2002
August 2002
July 2002
June 2002
May 2002
April 2002
March 2002
February 2002

ATOM RSS1 RSS2



LISTSERV.LOC.GOV

CataList Email List Search Powered by the LISTSERV Email List Manager