I would go slightly further than Stephen and propose an
option element to contain all sub-elements relating to a
given level. This would make the processing of a file,
including the separation of information on a given series,
sub-series etc, from its lower level sub-elements, much
easier. I envisage something like this:-
<C01 LEVEL="SERIES">
<levelinfo>
<DID>
<UNITLOC LOCTYPE="CONTAINER" CONTAINERTYPE="BOX">1</UNITLOC>
<UNITTITLE>Correspondence, <UNITDATE TYPE="INCLUSIVE">1935-62</UNITDATE>
</UNITTITLE>
<PHYSDESC><EXTENT>(10 Folders)</EXTENT></PHYSDESC>
</DID>
<SCOPECONTENT><P>blah, blah</P></SCOPECONTENT>
<ADMININFO>...</ADMININFO>
</levelinfo>
<C02>...
At the moment to separate out this information, we need to
look for either a closing </C01> tag or a <C02> tag - at
some points we may have a sequence such as
</C03></C02></C01> which can add to the confusion.
The optional DSC element at present serves a similar
function, but more clumsily, and is certainly more
difficult to use when designing stylesheets etc.
Any thoughts/comments?
Richard Gartner
Bodleian Library
Oxford UK
On Wed, 30 Jul 1997 14:31:23 -0400 Stephen
<[log in to unmask]> wrote:
> When designing methods to translate EAD to HTML, Dynaweb stylesheets for
> example, I find the did wrapper element to be useful.
>
> Say we have this:
> <C01 LEVEL="SERIES"><DID>
> <UNITLOC LOCTYPE="CONTAINER" CONTAINERTYPE="BOX">1</UNITLOC>
> <UNITTITLE>Correspondence, <UNITDATE TYPE="INCLUSIVE">1935-62</UNITDATE>
> </UNITTITLE>
> <PHYSDESC><EXTENT>(10 Folders)</EXTENT></PHYSDESC>
> </DID>
> <C02>...
>
> And want it to display as ("bold" indicates display only, not tags):
>
> Box 1
> <bold>Correspondence, 1935-62 (10 Folders)</bold>
>
> The eaisest way to do this when translating to html is to replace
> <UNITTITLE> with <H2> (or B or whatever you want) and replace </DID> with
> </H2>. This always incorporates the physdesc, which may or may not be
> included with each unittitle. The did is really convienent in this
> situation - it makes the conversion a simple replace operation and avoids
> the programming steps which would be needed to achive the same result
> without it (i.e. IF physdesc exists THEN close H2 after it ELSE close after
> unittitle).
> For this reason I'd be in favor of continuing to use it if it was made
> optional.
>
> Stephen Miller
> Duke University Special Collections
> [log in to unmask]
|