Print

Print


Thank you very much for your assistance, Bill!  I still have so much to learn.
-Alison

At 11:20 AM 10/14/02 -0700, you wrote:
>Alison;
>
>In the soon-to-be-released EAD 2002, <admininfo> has been unbundled and
you will be able to use <accessrestrict> (and other former <admininfo>
subelements) anywhere you can now use <did>, <scopecontent>, etc.
>
>In EAD 1.0, though, it seems to me that you *can* do what you seem to want
to do, which if I read your message correctly is to get an <accessrestrict>
statement in your
><archdesc level="recordgrp">, you just have to wrap <accessrestrict> as
follows:
>
><admininfo>
>  <accessrestrict>
>    <head>Restrictions on Access</head>
>    <p>Blah, blah, blah.</p>
>  </accessrestrict>
></admininfo>
>
><admininfo> is repeatable, so you can put this access restriction statment
anywhere you want it after you close the </did> and before you open the
<dsc>. Download Michael Fox's fonds.xml (Appendix A), in the section
labelled "Download special sections of the EAD Cookbook" at
<http://jefferson.village.virginia.edu/ead/cookbookhelp.html>. You'll see
how Michael has repeated <admininfo> several times within <archdesc> to
allow flexibility in where the varous <admininfo> subelements are placed
within the encoding.
>
>Bill
>--
>| Bill Landis
>| Manuscripts Librarian, Special Collections and Archives
>| The UCI Libraries, University of California
>| P.O. Box 19557, Irvine, CA 92623-9557
>| 949 824.3113 Voice | 949 824.2472 Fax
>| [log in to unmask]
>