Optional user friendly business name of the folder. If set, this supplements the harvested display name of the object.
OCID of the user who created the folder.
The list of customized properties along with the values for this object
The key of the associated data asset.
Detailed description of a folder.
A user-friendly display name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
Unique external key of this object in the source system.
Status of the object as updated by the harvest process.
Unique folder key that is immutable.
The key of the last harvest process to update the metadata of this object.
A message describing the current state in more detail. An object not in ACTIVE state may have functional limitations, see service documentation for details.
The current state of the folder.
List of objects and their relationships to this folder.
URL of the folder in the object store.
The unique key of the containing folder or null if there is no parent folder.
Full path of the folder.
A map of maps that contains the properties which are specific to the folder type. Each folder 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 folders have required properties within the "default" category. Example: {@code {"properties": { "default": { "key1": "value1"}}}}
The date and time the folder was created, in the format defined by RFC3339. Example: {@code 2019-03-25T21:10:29.600Z}
Last modified timestamp of this object in the external system.
The date and time the folder was harvested, in the format defined by RFC3339.
The last time that any change was made to the folder. An RFC3339 formatted datetime string.
The type of folder object. Type keys can be found via the '/types' endpoint.
OCID of the user who modified the folder.
URI to the folder instance in the API.
A generic term used in the data catalog for an external organization concept used for a collection of data entities or processes within a data asset. This term is an internal term which models multiple external types of folder, such as file directories, database schemas, and so on. Some data assets, such as Object Store containers, may contain many levels of folders.