Use this feature to customize the default templates for the core of an EAD finding aid and its components. The prepackaged templates represent a bare-bones XML model with inputs required by the schema or for machine processing purposes (e. g., the id attribute in <ead>). The template editor enables a site administrator or archivist to add more elements or textual values. For example, the default EAD template only requires did/unititle in the Archival Description. An institution's best practices may require further detail in the archdesc, such as did/unitdate, did/container, access or use restriction statements, or an abstract. The template interface is nearly identical in functionality as the forms for editing EAD documents themselves.
In addition to EAD templating, this section offers forms for setting very restrictive controlled vocabulary (drop down menus in the EAD editor as opposed to open-ended autocomplete for subject terms or personal names) that are more likely to vary from institution to institution. This includes institution names/codes and container types.
New Agency Codes can be added to the list. Note that the code itself must be compliant to the agency code data type in the EAD 2002 schema, e.g., US-NNAN. This this will populate the @mainagencycode drop-down menu for the EAD header in the EAD Core web form.
Agency codes may be scraped from finding aids already in the eXist database.
Container types are available as a drop-down menu in the attributes window for the container element. The default list is as follows: