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 (January 2005)Back to main MODS pageJoin or leave MODSReplyPost a new messageSearchProportional fontNon-proportional fontLog in
Date:         Thu, 27 Jan 2005 10:52:46 -0500
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: MODS part
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 Jan 27, 2005, at 10:26 AM, Rebecca S. Guenther wrote: > There is a need to include information about the > enumeration (volume, issue, etc.) about the particular issue being > digitized which is what is being described. It seems more intuitive in > this instance to do this at the MODS level rather than the related item > level. There's an argument to be made that the part content is more about a relation between a work and its host, than something intrinsic to the relatedItem (as it is now). So how are you planning to code these records in MODS (if you make part global, that is)? I'm curious about it myself. For example, I may want store a hundred journal articles from a single journal. So, that journal really ought to have a single MODS record it seems. But then how to code the individual articles and link to that record? Bruce


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

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