Metadata overview
Metadata is often referred to as the data that describes other data or information. Records management and information systems rely on metadata to manage information.
Records metadata is broadly categorised into a number of different categories and may include:
Structural metadata used to describe the relationship between records, such as a file or container, or the format of the record. Structural metadata includes:
- administrative metadata – used to manage a resource, such as access permissions, and
- descriptive metadata.
Descriptive metadata is deliberate, structured data which provides information about the content or context of the record which may not otherwise be recognised by full text searching.
Descriptive metadata includes:
- author/creator
- date/s
- document type
- description
- subjects/keyword
- title
- unique identifier.
There is a direct relationship between the metadata assigned to a record and the discoverability of that record.
Metadata is generally defined in a schema and encoding scheme or controlled vocabulary.
- A metadata schema shows the relationship between metadata elements and establishes rules for use, for instance, is the element optional or mandatory, which element takes precedence.
- An encoding scheme is the controlled list of terms used and includes rules for how the terms should be entered, for instance, Surname, First name, date formats.
Required metadata
Requirements for the use of metadata depends on the needs of the users and the functionality of the system being used. Does the system:
- allow for full text searching?
- use containers?
- automatically generate metadata through the capture process?
- use templates that have specific metadata embedded, such as, a leave application or accident report form?
- use artificial intelligence or have machine learning functionality?
Automating the capture of metadata where possible reduces the need for manually entering information and enables more consistent classification. When deciding what metadata to capture you should also consider the value of the records. Are they:
- of long-term value to the organisation?
- of archival value?
- vital for the continuation of business functions?
The volume of metadata kept will also depend on the level at which you document the information. For example, low value or low risk information may be documented at the box or series level, whereas high value or high-risk information may be documented at the file or folder level.
Setting minimum metadata
The State Records Office's minimum metadata requirement for information is shown in Table 1.
Table 1
| Name | Obligation | Description |
|---|---|---|
| Author / Creator | All Information | Creator and modifier of information (individual name, business unit or agency name for transfer). |
| Date/s | All Information | All relevant dates of action upon information (creation, modification, transfer). |
| Description | Long term/Vital/Archival | Description of the information and/or its content. May be as simple as a title. |
| Disposal | Long term/Vital/Archival | Information about the disposal action that relates to the information. Whether the information is archival. |
| Format | Long term/Vital/Archival | Description of the information's format. |
| Information classification* | All Information | A classification label to denote the sensitivity of the information. |
| Unique identifier | All Information | A unique value that identifies the information. |
*Information classification is only mandatory for WA public sector agencies.
Managing metadata
Metadata should never be created on an ad-hoc basis, it should be managed. Properly managed metadata promotes the entry of meaningful, standardised, and consistent metadata by users. This contributes to record quality, discoverability, assists in record sharing and reuse, and increases the efficiency of machine learning where available.
Like all information management functions, metadata and its use should be documented. This information is critical for ongoing systems management and for facilitating system migration in the future. The more information you have in a collection the more critical the metadata becomes. As an organisation’s business activities change, the metadata schemas and encoding schemes should be reviewed to make sure they still meet the organisation’s needs.
Retention and disposal of metadata
If organisations kept all metadata indefinitely, they could end up maintaining more metadata for destroyed records than they do for existing records. Metadata should be treated like a record and retained alongside its associated record for the minimum retention period specified in the relevant retention and disposal authority (RDA). An organisation must assess the risks associated with their functions and determine if there are records of temporary value for which metadata should be kept for longer.
Organisations must ensure they retain sufficient evidence of records that have been disposed of including:
- record/file number if applicable
- title/description
- date range
- disposal authority number
- destruction due date.
Metadata for permanent value records, including State archives, must be kept indefinitely with that record, and migrated across systems where necessary.
Sources
The SRO acknowledges the following sources used in the development of this records management advice:
National Archives of Australia, Metadata, https://www.naa.gov.au/information-management/describing-information/metadata (accessed 14 January 2021).
Public Record Office Victoria, Metadata, https://prov.vic.gov.au/recordkeeping-government/a-z-topics/metadata (accessed 14 January 2021).