The data catalog's OCID.
Detailed description of the data asset.
A user-friendly display name. Does not have to be unique, and it's changeable. Avoid entering confidential information.
External URI that can be used to reference the object. Format will differ based on the type of object.
Unique data asset key that is immutable.
A message describing the current state in more detail. An object not in ACTIVE state may have functional limitations, see service documentation for details.
State of the data asset.
The date and time the data asset was created, in the format defined by RFC3339. Example: {@code 2019-03-25T21:10:29.600Z}
The key of the object type. Type keys's can be found via the '/types' endpoint.
URI to the data asset instance in the API.
Summary of a data asset. A physical store, or stream, of data known to the data catalog and containing one or many data entities, possibly in an organized structure of folders. A data asset is often synonymous with a 'System', such as a database, or may be a file container or a message stream.