While there are several possible solutions, the most obvious to me is
that what you have is a collection with three high level components,
each of the "parts" being a <c01>.   All the necessary elements,
bioghist, scopecontent, etc., are available under the c01 just as they
are available directly under <archdesc>.

This is a good example of multi-level description within EAD.

Please don't go the different <dsc> route.  That's not what <dsc> was
meant to do.  It exists primarily to handle what I personally hope will
be a rapidly disappearing legacy practice of creating separate series
lists.   Not that I don't think that separate listings of series are
valuable in printed versions of finding aids but that with a stylesheet
language like XSL, one can produce a separate series listing in print
form without actually having to type everything a second time in the
inventory.

Enough misunderstanding has already arise around the use <dsc>.  It is
tricky to understand without an example that helps visual the situation
in which it is applied.  However, it is NOT a method for expressing
hierarchy.  That's what the component model does.

Good luck.

Michael
Michael Fox
Head of Processing
Minnesota Historical Society
345 Kellogg Blvd West
St. Paul MN 55102-1906
phone: 651-296-1014
fax:  651-296-9961
[log in to unmask]
**NOTE NEW AREA CODE EFFECTIVE JULY 12, 1998**

> ----------
> From:         Katherine Hayes[SMTP:[log in to unmask]]
> Sent:         Wednesday, September 09, 1998 1:32 PM
> To:   Multiple recipients of list EAD
> Subject:      Using nested <dsc> tags
>
> We are going to mark up a rather unusual (legacy) finding aid in EAD,
> and
> I'm working on how to apply the tags appropriately. The originator is
> a
> single organization, and the collection (at this point) has been
> processed,
> as received, in three sizable chunks. We can't reprocess the three
> "parts"
> together.
>
> The intellectual content has been restructured to contain a general
> institutional history, arrangement, provenance and scope/content note.
> Then
> each "part" has its own provenance, scope/content, arrangement, series
> descriptions, and folder list.
>
> At this point I'm thinking of using a <dsc type="othertype"
> othertype="part"> as the wrapper for each part's individual series
> descriptions (<dsc type="analyticover">) and folder list (<dsc
> type="in-depth">). However, I don't know quite where to put and how to
> tag
> the scope/content, provenance and arrangement information for each
> part. Is
> <eadgrp> applicable here?
>
> I'd welcome ideas, suggestions or examples of solutions to this
> problem.
> Thanks!
>
> <><><><><><><><><><><><><><><><><><><><><><><><><><>
> Katherine A. Hayes, Assistant Archivist
> Niels Bohr Library, American Institute of Physics
> One Physics Ellipse, College Park, MD 20740
> (301) 209-3179  [log in to unmask]
> <><><><><><><><><><><><><><><><><><><><><><><><><><>
>