Skip
repetitive navigational links
L-Soft  -  Home of  the  LISTSERV  mailing list  manager LISTSERV(R) 14.5
Skip repetitive navigational links
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (May 2003)Back to main MODS pageJoin or leave MODSReplyPost a new messageSearchProportional fontNon-proportional fontLog in
Date:         Mon, 5 May 2003 11:29:03 -0400
Reply-To:     Metadata Object Description Schema List <[log in to unmask]>
Sender:       Metadata Object Description Schema List <[log in to unmask]>
From:         Bruce D'Arcus <[log in to unmask]>
Subject:      Re: Attribute in partNumber?
Comments: To: Metadata Object Description Schema List <[log in to unmask]>
In-Reply-To:  <[log in to unmask]>
Content-Type: text/plain; charset=US-ASCII; format=flowed

On Monday, May 5, 2003, at 10:23 AM, Suzanne Pilsk wrote: > I want to do the following for just the MODS record for that Part 1 of > Volume 2 but feel it isn't quite kosher: > <titleInfo> > <title>My Mulitvolume Book</title> > <partNumber type="volume"> 2</part number> > <partName>Second volume in two parts</partName> > <partNumber type="part">1</part number> > <partName>Part 1 of 2 volumes of my multivolume book</partName> > </titleInfo> Just discussing this elsewhere. I'm not totally sure about how to integrate titles here (parts and chapters of books generally have them), and so will leave that alone, but how about something like this (I've substituted a more generic name for Karen's proposed subDoc)? <partDesc> <detail type="volume"><number>2</number></detail> <detail type="part"><number>1<number></detail> </partDesc> Also, wouldn't your <partName> example really be a description? > This way if I have volumes that are actually Teils or Hefts or > something, I > could use that in the type value and have a style sheet of some sort > be able > to take that value and formulate some sort of citation. Right. There also needs to be a way to map these language-based structural names back to the language specific Schema. In other words, we need a way to separate out the structural information from the (language based) presentation. If, for example, "teil" is just a German word for part, then I think that needs to be accounted for in a MODS record. So rather than simply having: <partDesc> <detail type="teil"><number>1</number></detail> </partDesc> ...maybe it'd be: <partDesc> <detail type="part"><number>1</number></detail> </partDesc> ...and it would be understood to be a transliterated German word by virtue of the fact that the language information was coded somewhere else in the record. This becomes important if you are dealing with documents in a variety of languages, and in turn need to publish in a variety of languages. Say, for example, I download a MODS record at some future date from an online catalog in Germany, but want to cite it in for English audience? Bruce


Back to: Top of message | Previous page | Main MODS page

LISTSERV.LOC.GOV CataList email list search Powered by LISTSERV email list manager