Object metadata

Content Platform Tenant Management Help

File Size
4269 KB
Part Number

HCP automatically generates metadata for each object. Some of this metadata is specific to HCP. Examples of this type of metadata are the retention setting, object creation date, and cryptographic hash value.

Objects also have POSIX metadata. POSIX is a set of standards that defines an application programming interface (API) for software designed to run under heterogeneous operating systems. These standards include specific types of metadata, such as permissions and ownership.

Users and applications can override the defaults for some HCP-specific and POSIX metadata when they add an object to a namespace. They can also change certain metadata values for existing objects.

Users can create their own custom metadata to associate additional descriptive information with an object. Custom metadata is specified as annotations, where each annotation is a discrete unit of information about the object.

Custom metadata enables the creation of self-describing objects. Future users and applications can use this metadata to understand and repurpose object content.

When added to a namespace, custom metadata becomes part of the target object. Custom metadata is typically but not necessarily formatted as XML.

Users can also associate access control lists (ACLs) with objects. An ACL grants permissions for an individual object to specified users or groups of users.

When added to a namespace, an ACL becomes part of the target object. When viewed or specified in the Console, ACLs are formatted as XML.

ACLs are enabled on a per-namespace basis. In namespaces where ACLs are enabled, the namespace can be configured to either enforce or ignore the permissions granted by ACLs.