Optional user friendly business name of the data entity. If set, this supplements the harvested display name of the object.
The list of customized properties along with the values for this object
Detailed description of a data entity.
A user-friendly display name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Key of the associated folder.
Status of the object as updated by the harvest process. When an entity object is created , it's harvest status will indicate if the entity's metadata has been fully harvested or not. The harvest process can perform shallow harvesting to allow users to browse the metadata and can on-demand deep harvest on any object This requires a harvest status indicator for catalog objects.
Property to indicate if the object is a physical materialized object or virtual. For example, View.
Property to indicate if the object is a sub object of a parent physical object.
Key of the last harvest process to update this object.
Key of the associated pattern if this is a logical entity.
A map of maps that contains the properties which are specific to the entity type. Each entity type definition defines it's set of required and optional properties. The map keys are category names and the values are maps of property name to property value. Every property is contained inside of a category. Most entities have required properties within the "default" category. To determine the set of required and optional properties for an entity type, a query can be done on '/types?type=dataEntity' that returns a collection of all entity types. The appropriate entity type, which includes definitions of all of it's properties, can be identified from this collection. Example: {@code {"properties": { "default": { "key1": "value1"}}}}
The expression realized after resolving qualifiers . Used in deriving this logical entity
Last modified timestamp of the object in the external system.
The type of data entity object. Type key's can be found via the '/types' endpoint.
Properties used in data entity create operations.