The following table explains how each of the metadata elements has been described.
Name of metadata element. To be in "lowerCamelCase" format.
Value(s) that typically appear on the computer screen that a user see. Labels are for display purposes and are not standardized across institutions.
The meaning of the element.
The intention or goal in using the element. Examples include resource discovery and identification, tracking the status of correspondence and reporting on trends in correspondence management.
Identifies where the element applies in the correspondence management domain (i.e., to a folder, to an attachment, to a task or to a correspondent).
Indicates the type of data that can be represented in the value of the term at the record and/or file level.
The described element is qualified by the referenced Value Domain(s). A Value Domain may either control the format or convention used to record the value or control the list of allowable terms (i.e. a controlled vocabulary) for the value. Lists the Value Domain(s) allowed. In many cases, and increasingly, institutional "pick lists" are used to provide the value in the metadata element and this practice creates a more consistent application of values by users and may even provide a foundation for developing more commonly accepted values for use across government.
Conditions of Application
Indicates if the element is mandatory or optional.
When is Element Populated?
Explains at what stage in the use case specification the element is added/updated in the correspondence management system.
How is the Element Populated?
Distinguishes whether the element is system generated or user populated and whether or not is based on a default value.
Indicates the source document and reference number where the element is identified (i.e., Functional Requirements, Use Case Specification).