Open Metadata View Services (OMVS)¶
The Open Metadata View Services (OMVS) provide task oriented, domain-specific services for user interfaces to integrate with open metadata. They provide REST APIs.
The view services are as follows:
| OMVS | Summary | Description |
|---|---|---|
| Action Author | Create and maintain governance actions. | The Action Author OMVS is for user interfaces supporting the governance team to set up governance definitions and actions. |
| Asset Catalog | Search for assets. | The Asset Catalog OMVS provides search and query capabilities for tools and applications to support an asset catalog function. It supports search requests for assets with specific characteristics and returns summaries of the matching assets, plus methods to allow drill-down into the details of a specific asset to related metadata. |
| Automated Curation | Discovery, initiate and monitor metadata cataloging and governance actions such as automated surveying. | The Automated Curation OMVS is for user interfaces that allows asset owners and consumers to set up, execute and monitor automated harvesting and governance services. |
| Classification Manager | Manage classifications on open metadata.. | The Classification Manager OMVS enables the caller to add classifications and governance relationships to open metadata elements. |
| Collection Manager | Manage collections of assets and other elements. | The Collection Manager OMVS provides the REST APIs to create collections of asset and other elements such as glossary terms or policies. The collections can be nested (like folders in a file system) and they can be classified to describe the type of collection. For example, one type of classification for a collection is a DigitalProduct that allows the collections of assets and other related material to describe data and or services for a specific consumer or purpose. |
| Data Designer | Create schema definitions to describe the structure of data. | The Data Designer OMVS is a REST API designed to support user interfaces (UIs) for building schemas for new data assets. |
| Data Discovery | Define and search for new data resources. | The Data Discovery OMVS is a REST API designed to support user interfaces (UIs) for locating the data needed for a project. |
| Data Officer | Manage the governance of data. | The Data Officer OMVS is a REST API designed to support user interfaces (UIs) for supporting a Data Officer as they lead the data governance program. This builds on the capabilities of the Governance Officer OMVS. |
| Devops Pipeline | Maintain the metadata about the assets managed by a devops pipeline. | The Devops Pipeline OMVS is a REST API designed to support user interfaces (UIs) for supporting a devops engineer to maintain the metadata about the changing digital resources being deployed through devops pipelines. |
| Feedback Manager | Maintain feedback such as comments, tags, reviews, likes and note logs. | The Feedback Manager OMVS is for user interfaces supporting feedback from users. A registered user is able to add comments, informal tags, notes, reviews and likes to elements such as assets or glossary terms. |
| Glossary Browser | Search and view the contents of specific glossaries and their links to governance definitions and assets. | The Glossary Browser OMVS is for user interfaces that wish to provide search facilities within a single glossary (or glossaries) along with the ability to browse the structure of the glossary and view an element within a glossary along with connected governance classifications, governance definitions, user feedback and attached assets. |
| Glossary Manager | Develop new glossary terms and categories in a controlled workflow process. | The Glossary Manager OMVS is for user interfaces supporting the creation and editing of glossary content, such as glossary terms and categories, in a controlled workflow process. This means that as terms and categories are created, updated and deleted, these changes are invisible to the general user until they are approved. |
| Governance Officer | Maintain governance definitions used to define any governance domain. | The Governance Officer OMVS is for user interfaces supporting the creation and editing of a new governance domain. |
| Metadata Explorer | Provides generic search, query and retrieval operations for open metadata.. | The Metadata Explorer OMVS is for user interfaces supporting the search, query and retrieval of open metadata. It is an advanced API for users that understand the Open Metadata Types. |
| My Profile | Locate, retrieve and update information relating to the calling user's profile. | The My Profile OMVS is for user interfaces supporting a personalized experience. A registered user is able to maintain information about themselves, their roles and their network. |
| Notification Manager | Locate, retrieve and update the types of user notifications that should be produced. | The Notification Manager OMVS is for user interfaces supporting personalized notifications to specific users. A registered user is able to define which types of notification should be produced and who they should be delivered to. |
| People Organizer | Describe teams, roles and organizational structure. | The People Organizer OMVS provides the REST APIs used to maintain information about an organization. This includes the definitions of teams, roles and organization structures. |
| Project Manager | Locate, retrieve and update information relating to projects. | The Project Manager OMVS is for user interfaces supporting projects, either for a group of people or personalized sandboxes for individuals. A registered user is able to maintain information about a project and link it with other projects, users and resources. |
| Privacy Officer | Manage the governance of privacy. | The Privacy Officer OMVS is a REST API designed to support user interfaces (UIs) for supporting a Privacy Officer as they lead the data privacy governance program. This builds on the capabilities of the Governance Officer OMVS. |
| Reference Data | Create and maintain reference data values and their mappings. | The Reference Data OMVS is a REST API designed to support user interfaces (UIs) that maintain reference data values and their mappings. |
| Runtime Manager | Retrieve status information about Egeria's OMAG Server Platform and OMAG Servers. | The Runtime Manager OMVS is a REST API designed to support user interfaces (UIs) that displays operational status about Egeria. |
| Security Officer | Manage the governance of security. | The Security Officer OMVS is a REST API designed to support user interfaces (UIs) for supporting a Security Officer as they lead the security governance program. This builds on the capabilities of the Governance Officer OMVS. |
| Template Manager | Create and maintain templates used to create new metadata elements. | The Template Manager OMVS is a REST API designed to support user interfaces (UIs) that support the management of templates that are used when creating new metadata. |
| Valid Metadata | Create and maintain metadata valid values. | The Valid Metadata OMVS is a REST API designed to support user interfaces (UIs) that query and maintain lists of valid values for open metadata attributes as well as query open metadata type definitions. |
Inside an OMVS¶
The OMVS APIs are deployed together in a View Server. User Interfaces connect to an OMVS through its REST API. The REST API interacts with a remote Metadata Access Server to retrieve and maintain metadata.
Configuring an OMVS¶
The administration services provide the ability to configure a View Server.