<accessrestrict> Conditions Governing Access

<accessrestrict> is a wrapper element which contains information about conditions that affect the availability of the materials being described. These conditions may be based on location, physical condition, and restrictions imposed by another party. It may also indicate that there are no restrictions on the described materials. It is comparable to ISAD(G) data element 3.4.1 and MARC21 field 506.

This should not be confused with <userestrict>, which designates information about limitations on the use of accessed materials or <legalstatus>, which encodes the statutorily-defined status of the materials.

<accessrestrict> is one of the elements which may be used within <archdesc>, <c>, <c01> … <c12>, and itself.

Attributes

  • @altrender – not required. Use if the content of the element should be displayed or printed differently than the rendering established in a style sheet for other occurrences of the element.
  • @audience – not required. Use to set whether the element’s contents will be visible to external users or to internal ones. Possible values are: “internal” and “external.”
  • @encodinganalog – not required. May contain information to map this tag to a particular element in another schema.
  • @id – not required. Creates an ID for element. Can be used for linking.
  • @lang – not required. Three-letter code that indicates the language in which the element’s contents were written. It should come from ISO 639-2b.
  • @localtype – not required. This attribute may be used within a number of elements. Its use and values are not defined by the schema and may be defined locally.
  • @script – not required. Four-letter code that indicates the script in which the element’s contents were written. It should come from ISO 15924.

Child Elements

<accessrestrict> may contain an optional <head> element. It must contain one or more of the following: <blockquote>, <chronlist>, <list>, <p>, <table>, and further <accessrestrict> elements.

DACS

See DACS Section 4.1, Conditions governing access (Required) and DACS Section 4.2, Physical access (Added value). (DACS 2013, pp.51-54)

Examples

Some examples of how <accessrestrict> may be used:

<accessrestrict>
	<head>Restrictions on Access</head>
	<p>Access to the materials is restricted to the following persons:</p>
	<list listtype="deflist">
		<listhead>
			<head01>Category</head01>
			<head02>Access level</head02>
		</listhead>
		<defitem>
			<label>Students: Year 5 and above</label>
			<item>With permission of a professor, students Year 5 and above may do historical research on letters and journals included in the collection.</item>
		</defitem>
		<defitem>
			<label>Slytherin alumni</label>
			<item>All materials, except spell books. Use of spell books requires approval from the headmaster and archivist.</item>
		</defitem>
		<defitem>
			<label>Hogwarts faculty and administration</label>
			<item>All materials.</item>
		</defitem>
		<defitem>
			<label>Researchers: Hogwarts alumni</label>
			<item>Alumni of other Hogwarts houses must obtain approval from the archivist. Use of spell books requires additional approval from the headmaster.</item>
		</defitem>
		<defitem>
			<label>Researchers: Other</label>
			<item>Researchers who graduated from other magical academies must obtain permission from the Bloody Baron to use Salazar Slytherin's materials. They must then obtain approval for their project's research topics from the archivist. Use of spell books requires additional approval from the headmaster.</item>
		</defitem>
	</list>
</accessrestrict>

Changes from EAD 2002

<accessrestrict> gained @lang and @script. @type changed to @localtype. It lost child elements: <address>,<legalstatus>, and <note>.

EAD3 Tag Library Entry

View the official tag library entry for <accessrestrict>