We're still working on the next version of the schema, because we very
recently received some suggested changes from a user that we are
evaluating. Since we want to minimize the frequency with which we revise
the schema, it is a good opportunity to incorporate these now if they are
needed. So, in the meantime, here is what we've come up with for the
elements to support citations under <relatedItem>.

If you have any comments on this, please send them to me or to the
list. We are particularly interested in whether this will work for other
than text (particularly the <extent> element).

Our plan is to resolve the other schema issues by (we hope) early next
week when we will put out a list of what we are planning to change. Then
the XML schema would go out the week of Aug. 6 for a 2-week review. After
that we would finalize everything and publish the new version.

--------------------------------------------------------------------------

MODS changes to accommodate citation elements

1. Summary of elements:
Under relatedItem:
<part>
   <detail>
        Attributes: type, order
        Type: Suggested values include part, volume, issue, chapter,
        section, paragraph, track
        Subelements:
                <number>
                <caption>
                <title>
    <extent>
        Attribute: unit
        Suggested values: page, minute
        Subelements:
                <start>
                <end>
                <total>
                <list>
    <date>
        Attributes: encoding, point
    <text>

2. Descriptions (includes additional information for guidelines)
To be used to give full citation information about the location within a
host item; use with relatedItem type="host".

Under relatedItem:
<part>
    <detail>
        Attributes: type, order
                type: Suggested values include part, volume, issue,
                chapter, section, paragraph, track
                 (Put in MODS guidelines: these values are used regardless
                 of linguistic term)
                order: Hierarchical order of detail elements relative to
                host (i.e. level of enumeration)
        Subelements:
                <number>
                <caption>
                <title>
                Use only if different than main title of resource being
                described in <title>
    <extent>
        Attribute: unit
                unit: suggested values include pages, minutes
                <start>Use for first page or begin minutes
                <end>Use for last page or end minutes
                <total>Use for a total number, rather than specific
                 pages/minutes cited
                <list>Use for an unparsed statement, e.g. p. 5-12. May not
                 be applicable to minutes.

Guidelines should specify: if a single page, give the same page as
<start> and <end>. If no <end> is given, it should be interpreted that the
end page is unknown. If a string, use list. You can decide whether to
parse start and end or not, in which case use list.

    <date> (uses dateType)
        Attributes: encoding, point
Could use dateType to allow for structured and unstructured forms. Use
only if different from date of resource being described in <originInfo>

    <text>Textual form of <part>

Also note in guidelines that this need not be given instead of structural
metadata used within a METS objects. This is primarily for locating a part
within a host.

Examples:

Journal article with details

<relatedItem type="host">
        <title=Journal of the American Medical Association</title>
        <part>
                <detail type="volume" order="1"
                        <caption>v.</caption>
                        <number>5</number>
                </detail>
                <detail type="issue" order="2">
                        <caption>no.</caption>
                        <number>44</number>
                </detail>
                <extent unit="pages">
                        <start>34</start>
                        <end>45</end>
-and/or-
                        <list>34-45</list>
                </extent>
                <date>March 2002</date>
(or)
                <date encoding="iso8601">200203</date>
                <text>v. 5, no. 44, p. 34-56, March 2002
                </text>
        </part>
</relatedItem>

Journal article without details

<relatedItem type="host"
        <title>Journal of Irreproducible Results</title>
        <part>
                <text>v.3, March, 2002</text>
                <extent unit="pages"><list>1, 3-7</list>
                </extent>
        </part>
</relatedItem>

Chapter:

<relatedItem type="host"
        <title>Collected essays</title>
        <name>Smith, John</name>
        <part>
                <detail type="chapter">
                        <number>10</number>
                        <title>Why I Write</title>
                </detail>
                <extent unit="pages">
                        <start>100</start><end>135</end>
                </extent>
                <text>Chapter 10: Why I Write</text>
        </part>
</relatedItem>
Note: if the title "Why I write" is in <title> of the description, do not
include here.


Rebecca
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^ Rebecca S. Guenther ^^
^^ Senior Networking and Standards Specialist ^^
^^ Network Development and MARC Standards Office ^^
^^ 1st and Independence Ave. SE ^^
^^ Library of Congress ^^
^^ Washington, DC 20540-4402 ^^
^^ (202) 707-5092 (voice) (202) 707-0115 (FAX) ^^
^^ [log in to unmask] ^^
^^ ^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^