Understanding returned metadata

The Search Results page shows metadata for each listed object. You can see some metadata initially. You can view the remaining metadata by showing result details.

The metadata shown varies depending on namespace type and object type. The Search Results page shows as much of this metadata as is available:

For all objects:

oSize — The object size, in bytes.

oVersion ID — The version ID of the object.

oRetention — The retention setting for the object, shown as one of these:

A specific date and time in the future.

Deletion Prohibited.

Initial Unspecified.

A retention class.

Expired — This includes objects whose retention setting is either a specific date and time in the past or Deletion Allowed.

For more information about retention settings, see Retention settings.

Note: HCP cannot represent dates later than February 18, 2038, at 22:14:07. Later dates appear as 2/18/2038 22:14:07 (overflow).

oHold — An indication of whether the object is on hold. While an object is on hold, it cannot be deleted under any circumstances until it is explicitly released, nor can its retention setting be changed.

While the metadata query engine is active, for an object that’s on hold, the retention setting is followed by | HOLD.

While the HDDS search facility is active, this setting is shown as either Held or Not Held.

oCustom metadata annotation(s) (metadata query engine only) If the object has one or more custom metadata annotations, a list of the annotation names. You can click any annotation name to view the content of that annotation. You can right-click the link to copy the URL for the annotation.

oAccess control list URL (metadata query engine only) — If the object has an ACL, the URL for that ACL. You can click this URL to view the content.

The access control list URL consists of the object path followed by a type=acl query parameter. For example, this URL specifies the ACL for an object named Q1_2012.ppt:

https://finance.europe.hcp.example.com/rest/presentations/
Q1_2012.ppt?type=acl

For information about the content of ACLs, see Access control lists.

oIngest time — The date and time the object was created (that is, when the data was added to the namespace).

oAccess time — The POSIX atime for the object. Users and applications can change this metadata.

While the metadata query engine is active, this metadata is shown for all objects. While the HDDS search facility is active, this metadata is shown only for objects in the default namespace.

oModify time — The POSIX mtime for the object. Users and applications can change this metadata.

While the metadata query engine is active, this metadata is shown for all objects. While the HDDS search facility is active, this metadata is shown only for objects in the default namespace.

oChange time — The POSIX ctime for the object. This is the last time the object metadata changed.

While the metadata query engine is active, this metadata is shown for all objects. While the HDDS search facility is active, this metadata is shown only for objects in the default namespace.

oHash value — The cryptographic hash value for the object. The label for this value is the name of the cryptographic hash algorithm used to calculate the value.

oDPL — The number of copies of the object data HCP must maintain, as dictated by the service plan that applies to the namespace. DPL stands for data protection level.

oShredding — The shred setting for the object, which indicates whether the object will be shredded when it’s deleted. Shredding is the process of deleting an object and overwriting the place where it was stored in such a way that none of its data or metadata can be reconstructed.

oReplication — An indication of whether the object has been replicated to another HCP system.

oMIME type (HDDS search facility only) — The MIME type of the object content. For a list of the MIME types that the HDDS search facility recognizes for search operations, see the applicable HDDS documentation.

oFormat (HDDS facility only) — The format of the object content. For a list of the content formats that the HDDS search facility recognizes for search operations, see the applicable HDDS documentation.

oLanguage (HDDS search facility only) — The language of the object content.

oUser ID — The POSIX user ID of the object owner.

While the metadata query engine is active, this metadata is shown for all objects. While the HDDS search facility is active, this metadata is shown only for objects in the default namespace.

oGroup ID — The POSIX ID of the owning group.

While the metadata query engine is active, this metadata is shown for all objects. While the HDDS search facility is active, this metadata is shown only for objects in the default namespace.

oPermissions — The object permissions in POSIX format and as an octal value.

While the metadata query engine is active, this metadata is shown for all objects. While the HDDS search facility is active, this metadata is shown only for objects in the default namespace.

oOwner (metadata query engine only) — For objects in HCP namespaces, the user that owns the object. The owner is an HCP-specific metadata property and does not correspond to the POSIX UID of an object. This value has this format:

USER,location,username

For objects with no owner, this value has this format:

GROUP,location,all_users

In these formats:

location is the location in which the user account of the object owner is defined. For objects with no owner, this is the tenant that owns the namespace that contains the object.

This value can be the name of an HCP tenant or the name of an Active Directory domain preceded by an at sign (@).

username is the username of the object owner. This value can be the username of a user account that’s defined in HCP or the username of an Active Directory user account. The username for an AD user account can be either the user principal name or the Security Accounts Manager (SAM) account name.

For objects in the default namespace, the value for owner is an empty string.

For objects in HCP namespaces that existed before the HCP system was upgraded from a pre-5.0 release and that have not subsequently had their owner changed, the value for owner is nobody. These objects effectively have no owner.

With the HDDS search facility, for many document formats, such as Word documents and PDFs:

oAuthor — The author of the object content

oTitle — The title of the object content

oSubject — The subject of the object content

oCategory — The category of the object content

With the HDDS search facility, for email objects:

oThe text in the email subject field

oThe message ID

oFrom — The email address of the sender

oTo — The email addresses of the recipients

oAttachments ( ) — The names of any files attached to the email

oCC — The exposed email addresses of additional recipients

oBCC — The hidden email addresses of additional recipients

oSend date — The date and time the email was sent

POSIX permissions

POSIX permissions are represented by three 3-character strings — one for the user identified by the POSIX user ID, one for the group identified by the POSIX group ID, and one for all others. From left to write, the positions in each string represent read (r), write (w), and execute (x). Each position has either the character that identifies the applicable permission, meaning the permission is allowed, or a hyphen (-), meaning the permission is denied. Each string is preceded by a hyphen (-).

For example, the string below means that the user identified by the POSIX user ID has all permissions for the object, the group identified by the POSIX group ID has read and execute permissions, and others have only read permission:

-rwxr-xr--

Octal permission values

Permissions are also represented by octal values. Each object has an octal permission value that’s the sum of the octal permission values specified for the object owner, the owning group, and all other users not in that group. The table below shows the value that corresponds to each permission.

  Read Write Execute
Owner 400 200 100
Group 040 020 010
Other 004 002 001

For example, given the permissions below, the octal value is 755:

POSIX owner has read, write, and execute permissions (700).
POSIX group has read and execute permissions (050).
Other has read and execute permissions (005).

© 2015, 2020 Hitachi Vantara LLC. All rights reserved.