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:
|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 and their network as well as set up and use personalized collections of metadata elements.|
|Glossary Author||Develop new glossary terms and categories.||The Glossary Author OMVS is for user interfaces supporting the creating and editing of glossary content, such as glossary terms and categories. The changes made are immediately visible to all users.|
|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 Workflow||Develop new glossary terms and categories in a controlled workflow process.||The Glossary Workflow 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.|
|Repository Explorer||Explorer interface to inspect instances across a cohort of repositories.||The Repository Explorer (Rex) OMVS is for user interfaces that support enterprise architects who need to inspect, navigate or explore the instance data stored in an open metadata repository or a cohort of repositories. It enables the retrieval of instance data (entities and relationships) and exploration of the graph of instances connected to those entities. This enables the user to construct a graph (as a diagram) to visualize the details and connectivity of a group of instances of interest to the user.|
|Type Explorer||Explorer interface to inspect types across a cohort of repositories.||The Type Explorer (Tex) OMVS is for user interfaces that support enterprise architects who need to inspect, navigate or explore the open metadata types supported by a repository or a cohort of repositories. It enables the retrieval of type data (relating to entities, relationships and classifications) and exploration of the graphs of entity type inheritance and the supported combinations of entity and relationship types.|
|Dynamic Infrastructure and Operations||Admin interface to inspect servers, services, cohorts and platforms.||The Dino OMVS is for user interfaces that support Egeria operators who need to inspect, navigate or explore the open metadata servers, services, cohorts and platforms that are configured or actively running. It is intended for operations and problem-determination.|
|Server Author||An authoring interface for servers.||The Server Author OMVS is for user interfaces that support Egeria Server authors. This user interface allows the author to create, delete or update a server configuration using an intuitive UI, rather than needing to use the low level admin rest calls and associated json payloads.|
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.