Asset Catalog Open Metadata Access Service (OMAS)¶

The Asset Catalog OMAS provides services to search for data assets including:

• data stores
• event feeds
• APIs
• data sets

The search locates assets based on the content of the Asset metadata itself and the metadata that links to it. This includes:

• glossary terms
• schema elements
• assets

The Asset Catalog REST API supports: * the retrieval of assets based on unique identifiers * the retrieval of asset's relationships and classifications * to query for related assets * the retrieval of assets based on their type

The module structure for the Asset Catalog OMAS is as follows: * asset-catalog-client supports the client library. * asset-catalog-api supports the common Java classes that are used both by the client and the server. * asset-catalog-server supports the server side implementation of the access service. This includes the * interaction with the administration services for registration, configuration, initialization and termination of the access service. * interaction with the repository services to work with open metadata from the cohort. * support for the access service's API and its related event management. * asset-catalog-spring supports the REST API using the Spring libraries. * asset-catalog-topic-connector supports asynchronous messaging through a connector and connector provider class

Using the Asset Catalog OMAS¶

Below is the list of tasks supported by Asset Catalog OMAS.

Get Asset Classifications¶

Get Asset Context¶

Get Asset Details¶

Get Asset Relationships¶

Get Asset Universe¶

Get Supported Types¶

Search¶

Search Solution¶

The search will return Assets, Glossary Terms and Schema Elements that match the search criteria. As the asset search is to be performed against on one or more repositories a search engine will be used. The search will be performed using the existing properties of the asset, glossary terms and/or schema elements. Indexing will be performed by the Asset Catalog OMAS according to supported zones. The search result will contain: guid, name (name or displayName), description, qualifiedName, classifications, zoneMembership (the basic properties of the element).

In order to get the full context of the element, a second call is performed. At this step, the specific relationships are traverse for getting the connection to the asset and to get the schema type that is behind the given asset. This call is using the asset global identifier and the asset type.

Figure 1: Integration of search engine

Raise an issue or comment below