<localcontrol> is a new element in EAD3 and an optional child element of <control> used to specify information necessary to accommodate local practices. It may be used multiple times. Examples below show how <localcontrol> may be very useful to provide administrative data that can be used in sorting, search results, etc.
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 – strongly suggested. Designate a @localtype value to be associated with the relevant terms.
- @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
<localcontrol> should contain a <term> element to designate the local term followed by any associated <datesingle> or <daterange>, if desired.
Another way to look at it:
- <term>
- <datesingle>** (optional but only one of the pair may be used)
- <daterange>** (optional but only one of the pair may be used)
Adjacent Elements
<localcontrol> may be preceded by the optional <localtypedeclaration>. It is followed by the required <maintenancehistory>.
Examples
<localcontrol localtype="descriptionlevel"> <term>subseries</term> </localcontrol> <localcontrol localtype="processinglevel"> <term>folder</term> </localcontrol> |