EADiva has just migrated to a static site. If you see broken links or behavioral errors, please let me know.

<arrangement> Arrangement

<arrangement> encodes information on how the described materials have been subdivided into smaller units. Can also be used to express the filing sequence of described materials.

<arrangement> is one of the elements which may be used within <archdesc>, <archdescgrp>, <c>, <c01> through <c12>, and <descgrp>. It may also be used within <scopecontent>.


  • 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.”
  • ID – not required. Creates an ID for element. Can be used for linking.
  • ENCODINGANALOG – not required. May contain information to map this tag to a particular element in another schema.
  • TYPE – not required. May be used to designate the type of acquisition info.


<arrangement> may contain further <arrangement> elements, as well as <address>, <blockquote>, <chronlist>, <head>, <list>, <note>, <p>, and <table>. Note, since PCDATA is not used within this element, it serves as a wrapper, at least of a <p> element containing the actual text.


See DACS Section 3.2, System of arrangement. Added value. (DACS 2013, pp.49-50)


Some examples of how <arrangement> may be used:

	<head>Arrangement of the Materials</head>
	<p>The materials have been divided into the following three subseries:
	<p>Correspondence is organized alphabetically by author, then chronologically. Correspondence by [creator's name] is organized by correspondent, then chronologically.</p>

EAD tag library entry for <arrangement>.