In EAD Version 1.0 <admininfo> is repeatable and is available at every
level of description, so you shouldn't have any problem using
<accessrestrict> in a single record group, subgroup, or series within a
larger body of materials (i.e., within a component at any level in
<dsc>).  So following your <scopecontent> for the record group, you could
open an <admininfo> and <accessrestrict>.

In the soon-to-be-released Version 2002, <accessrestrict> will be available
directly within <archdesc> and <c0x>.


At 12:29 PM 10/14/2002 -0500, you wrote:
>Hello everyone,
>Why is it that the <accessrestrict> tag is only available in the
><admininfo> section of the finding aid?  I have a collection wherein only
>one record group has sensitive material that I need to restrict for 40
>years.  I've included wording in the <admininfo> section, but I'd also like
>to add an <accessrestrict> tag within the finding aid, at the record group
>level.  Right now I've just added a <note> to the <scopecontent> field at
>that level.
>Thanks for any and all <insight>,
>Alison Hinderliter -    [log in to unmask]
>Project Archivist, Illinois Central Railroad Archives
>The Newberry Library
>60 W. Walton St.
>Chicago, IL  60610-7324
>(312) 255-3694

Kris Kiesling
Chair, SAA EAD Working Group
Coordinator, Technical and Digital Services and
Head, Department of Manuscripts and Archives
Harry Ransom Humanities Research Center
University of Texas at Austin
Austin, TX  78713-7219
Voice:  (512) 232-4614
Fax:  512.471.7930
[log in to unmask]