What are Metadata Attributes
In the platform, metadata attributes define how existing objects like PDDs can be augmented with additional fields. A metadata attribute is created to describe a value that can be added. Metadata attributes can be used to map the fields of a third-party application, like a data catalog, onto a platform object.
Metadata Attribute Mapping
Certain metadata attributes have special meaning to the platform. To express this, when creating a metadata attribute in the platform user interface, it is possible to specify a mapping from the metadata attribute onto the special fields that the platform provides. They can be used to map to metadata read from third-party data catalog applications or can also be used to map to other platform objects that have metadata associated with them.
The following list shows the available mapping options. At the moment, the only object in the platform to support this feature is a PDD.
Mapping | Description | Type |
|---|---|---|
Description | The metadata attribute contains the platform object description. | String |
Expiration date | The metadata attribute contains the Privitar Object Expiration Date. | Date |
When the mapping is enabled, then its type replaces the current type of the metadata attribute.
The mappings are unique.
The mapped metadata connects metadata attribute values to the platform. Once such an association is set, additional actions become allowed (for example, see Managing PDD Lifecycle).
The unmapped metadata contains arbitrary data chosen by the organization to represent data usage information on PDDs. Examples are Approver, Restrictions, etc.