Metadata Families
Each metadata field or definition belongs to a metadata family. MediaHaven fields are those fields whose family is different from Dynamic.
Family | Ownership | Fields Modifiable? | Fields can be inherited? | Description | Since |
|---|---|---|---|---|---|
Descriptive | MediaHaven | Yes | Yes | Descriptive fields are modifiable fields that describe files for purposes such as discovery. |
|
Administrative | MediaHaven | No | No | Administrative Fields are human readable read-only fields which are used for managing and preserving files in MediaHaven. |
|
Technical | MediaHaven | No | No | Technical fields are read-only fields whose values are inherent to data file itself. (Re)-ingesting the file, possibly in a different MediaHaven, will result in exactly the same values. |
|
Internal | MediaHaven | No | No | Internal fields are read-only metadata fields proper to MediaHaven and often not a human readable format opposed to the administrative fields. |
|
Structural | MediaHaven | Mixed | Yes | Structural fields provide how compound files such as collections are put together or how files are related between each other. |
|
RightsManagement | MediaHaven | Mixed | Yes | Rights management fields provide information about who can access, edit or export files. |
|
RecordInformation | MediaHaven | Mixed | No | Additional metadata fields for non Archive Information Package records. |
|
Dynamic | Customer | Yes | Yes | Customer specific fields. Customers can only add fields belonging to this family. If a field has no matching field definition, it is always in the family Dynamic. |
|
Timers | MediaHaven | Yes | Yes | Used to store timer fields for https://mediahaven.atlassian.net/wiki/spaces/CS/pages/3949297684. |
|
Governance | Mediahaven | Yes | Yes | Used to store record governance information like destruction |
|