This function is complete and can be used. The interfaces will be supported until the function is removed from the project via the deprecation process. There will be ongoing extensions to this function, but it will be done to ensure backward compatibility as far as possible. If there is a need to break backward compatibility, this will be discussed and reviewed in the community, with a documented timeline.
We are still working on this content -- you may find some broken links. Until resolved, You can find additional information in the Egeria repository
Asset Consumer Open Metadata Access Service (OMAS)¶
The Asset Consumer OMAS provides services to an individual who wants to work with assets such as:
- data stores, data sets and data feeds
- functions such as analytical services
- the retrieval of connection objects from the open metadata repositories. A connection object is used to create a connector to an asset.
- the creation of a connector based on the properties in a connection object.
- the retrieval of properties about an asset. These properties are called the connected asset properties.
- the adding of feedback (comments, ratings and likes) to an asset.
- the attachment of informal tags to an asset.
- the adding of an audit log record for an asset.
- the publishing of notifications about assets on Asset Consumer OMAS's out topic.
Adding feedback through the Asset Consumer OMAS results in Karma Points being awarded to the individual. These are maintained in the individual's profile. A karma point is awarded for each contribution of feedback through the API. (The awarding of Karma points is managed by the Community Profile OMAS.)
The connectors returned by the Asset Consumer OMAS are Open Connector Framework (OCF) connectors. The caller can use the connector to access the contents of the asset itself and the properties about the asset it is accessing. This service is provided by the OCF Metadata Management Common Service.
The Asset Consumer OMAS is designed for use by an application that is accessing data sources and services through connectors. These data sources and services are called Assets, hence the name of this OMAS is Asset Consumer.
Typically the first action to take is to create the connector to get access to the asset content and its properties. Connectors are created from Connection objects. Connection objects can be created by the calling application, or stored in one of the open metadata repositories that are accessible to the Asset Consumer OMAS.
Within the asset properties are links to glossary terms. It is possible to look up the full description of a term to further understand the asset.
The Asset Consumer OMAS offers the following types of interface:
Connectors are only available through the Java client.
Details of how to configure the Asset Consumer OMAS can be found here
This is the list of documented scenarios: