diff --git a/site/docs/concepts/anchor.md b/site/docs/concepts/anchor.md index 137f67c08c..71348c5b29 100644 --- a/site/docs/concepts/anchor.md +++ b/site/docs/concepts/anchor.md @@ -8,18 +8,20 @@ hide: # Anchor -An *anchor* is a [Referenceable](/concepts/referenceable) metadata entity that -groups other entities together as if they were logically a part of the anchor. -This means, for example, if the anchor entity is deleted then -the entities anchored to this entity are also deleted. +An *anchor* is a metadata element that is the root of a group of linked elements that should be processed as if they were logically a part of the same "object". -The value of establishing this grouping is to ensure that entities that have little meaning without their -anchor entity are cleaned up properly and are not left to uselessly clutter the repository. +For example, an [asset](/concepts/asset) may be linked to its [schema](/concepts/schema), a [connection](/concepts/connection) and a [glossary term](/practices/common-data-definitions/anatomy-of-a-glossary). The schema and connection would typically be anchored to the asset since they only have meaning in the context of the asset. The glossary term is independent of the asset, since it can be used in many other contexts. Therefore the glossary term would not be part of the asset's anchor grouping. +The value of establishing this *anchor grouping* is to ensure that elements that have little meaning without their anchor are managed consistently. There are four main use cases for the anchor grouping: +* *Security* - when elements within the anchor group are created, updated, deleted or accessed, the security check is whether the user has access to the anchor element. +* *Deleting* - when the anchor element is deleted, all of the other elements in the anchor grouping are deleted as well. This ensures anchored elements are cleaned up properly and are not left to uselessly clutter the repository. +* *Templated cataloguing* - when a new element is created from a [template](/concepts/template), all the linked elements anchored to the template are copied. Other elements linked to the template are also linked to the equivalent newly created element(s). +* *Searching and retrieval* - the [Asset Catalog OMVS](/services/omvs/asset-catalog/overview) uses the anchor information in its search API to enable searches to include all elements anchored to assets. !!! education "Further information" - + - [Anchor Management](/features/anchor-management/overview) provide support for the Anchors and LatestChange classifications. + - [Anchor Classification](/types/0/0010-Base-Model) is used to implement the anchor grouping. --8<-- "snippets/abbr.md" diff --git a/site/docs/concepts/catalog-template.md b/site/docs/concepts/catalog-template.md new file mode 100644 index 0000000000..0cc927787c --- /dev/null +++ b/site/docs/concepts/catalog-template.md @@ -0,0 +1,17 @@ +--- +hide: +- toc +--- + + + + +# Catalog Template + +A *catalog template* identifies a template designed to catalog a particular type of open metadata element. For example in the [Automated Curation OMVS](/services/omvs/automated-curation/overview) API, it links a particular *technology type* to relevant [templates](/concepts/template) for that ype of technology. + +The catalog template is implemented using the [CatalogTemplate](/types/0/0011-Managing-Referenceables) relationship. + + + +--8<-- "snippets/abbr.md" diff --git a/site/docs/concepts/governance-action-processes.drawio b/site/docs/concepts/governance-action-processes.drawio index 44a06ff98c..e7cf18e51f 100644 --- a/site/docs/concepts/governance-action-processes.drawio +++ b/site/docs/concepts/governance-action-processes.drawio @@ -1,4 +1,4 @@ - + @@ -120,7 +120,7 @@ - + @@ -1521,7 +1521,7 @@ - + @@ -1671,13 +1671,13 @@ - + - + diff --git a/site/docs/concepts/index.md b/site/docs/concepts/index.md index 1ff0efe376..06364fa6ec 100644 --- a/site/docs/concepts/index.md +++ b/site/docs/concepts/index.md @@ -9,6 +9,8 @@ - [Action Target](/concepts/action-target) - [Analytics Integrator OMIS](/services/omis/analytics-integrator/overview) - [Anchor](/concepts/anchor) +- [Anchor Grouping](/concepts/anchor) +- [Anchor Domain](/concepts/anchor) - [API Integrator OMIS](/services/omis/api-integrator/overview) - [Application Programming Interface (API)](/concepts/basic-concepts) - [Archives for Open Metadata](/concepts/open-metadata-archive) @@ -40,6 +42,7 @@ - [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview) - [Catalog Target](/concepts/catalog-target) - [Catalog Target Type](/concepts/catalog-target) +- [Catalog Template](/concepts/catalog-template) - [Cohort](/concepts/cohort-member) - [Cohort Event](/concepts/cohort-events) - [Cohort Member](/concepts/cohort-member) @@ -147,7 +150,7 @@ - [Glossary Browser OMVS](/services/omvs/glossary-browser/overview) - [Glossary Category](/practices/common-data-definitions/anatomy-of-a-glossary/#glossary-categories) - [Glossary Term](/practices/common-data-definitions/anatomy-of-a-glossary/#inside-a-glossary-term) -- [Glossary Workflow OMVS](/services/omvs/glossary-workflow/overview) +- [Glossary Manager OMVS](/services/omvs/glossary-manager/overview) - [Governance Action](/concepts/governance-action) - [Governance Action Engine](/concepts/governance-action-engine) - [Governance Action OMES](/service/omes/governance-action/overview) @@ -295,6 +298,7 @@ - [Personal Note](/concepts/personal-notes) - [Personal Profile](/concepts/personal-profile) - [Personal Roles](/concepts/personal-roles) +- [Placeholder](/concepts/placeholder) - [Platform Chassis](/services/platform-chassis) - [Platform Metadata Security Connector](/concepts/platform-metadata-security-connector) - [Platform Security](/features/metadata-security/overview) @@ -364,6 +368,7 @@ - [Software Capability](/concepts/software-capability) - [Software Server Capability](/concepts/software-capability) - [Star Ratings](/concepts/review) +- [Specification](/concepts/specification) - [Stewardship](/features/discovery-and-stewardship/overview) - [Stewardship Action OMAS](/services/omas/stewardship-action/overview) - [Stewardship Engine](/concepts/governance-engine) @@ -384,7 +389,7 @@ - [Tagging](/concepts/informal-tag) - [Team](/concepts/team) -- [Templates](/features/templated-cataloguing/overview) +- [Templates](/concepts/template) - [Template Manager OMVS](/services/omvs/template-manager/overview) - [Tool](/concepts/software-capability/#tool) - Tombstone - see [Memento](#m) diff --git a/site/docs/concepts/presentation-server.md b/site/docs/concepts/presentation-server.md index 905bb409d5..6122f3774b 100644 --- a/site/docs/concepts/presentation-server.md +++ b/site/docs/concepts/presentation-server.md @@ -8,24 +8,11 @@ hide: # Presentation server -The **presentation server** hosts the JavaScript applications that provide an interactive browser-based -user interface for Egeria. - -The JavaScript applications call REST API services running in a [view server](/concepts/view-server) -to retrieve information and perform operations relating to open metadata. +The **presentation server** is the reverse proxy that protects the open metadata ecosystem from the vagaries of external user traffic and hosts the static JavaScript that provides the [interactive browser-based user interface for Egeria](/user-interfaces/general/overview). It also routes calls to the REST API services running in a [view server](/concepts/view-server) to retrieve information and perform operations relating to open metadata. ![A presentation server in the open metadata ecosystem](view-server.svg) -The presentation server supports multi-tenant operation. -Each presentation server tenant is designed to support an organization. -These may be independent organizations or divisions/departments within an organization. - -The tenant is configured with the appropriate view server to use, which in turn routes requests -to its [governance servers](/concepts/governance-server) and [metadata access servers](/concepts/metadata-access-server). -Therefore, each tenant sees a different collection of metadata and operates in isolation to the other tenants. - !!! education "Further information" - The [setup and user guide for the presentation server :material-github:](https://github.com/odpi/egeria-react-ui){ target=gh } - is held in a separate repository. + [Setting up the presentation server](/guides/admin/user-interfaces/configuring-the-presentation-server) --8<-- "snippets/abbr.md" diff --git a/site/docs/concepts/specification.md b/site/docs/concepts/specification.md new file mode 100644 index 0000000000..8954744515 --- /dev/null +++ b/site/docs/concepts/specification.md @@ -0,0 +1,31 @@ + + + +# Specification + +Specifications provide the information required to understand the behaviour of a function, to call it and to interpret its results. This is particularly important for functions that are available as a library for people to browse, select and run. + +Egeria's templates, connectors and governance actions fit into this category. They can provide their own specification which can be queried through the [Automated Curation OMVS](/services/omvs/automated-curation/overview). + +## Template specifications + +[Templates](/concepts/template) are used to create consistent catalog entries. They include [placeholders](/concepts/placeholder) to allow specific values to be inserted into the resulting elements during the templating process. The names, types and descriptions are found in a template specification. + +## Integration Connector Specifications + +An integration connector implementation synchronizes (exchanges) metadata with particular types of third party technology. It often picks up details of which instance of this technology it is to synchronize with through its [catalog targets](/concepts/catalog-target). The specification for an integration connector describes the types of catalog targets it supports. + +## Governance Service Specifications + +[Governance Services](/concept/governance-service) provide the implementation of [governance actions](/concepts/governance-action). They are highly configurable and tis reflects in their specification which includes: + +* *Supported Request Parameters* - these are the different types of request parameters that can be used to affect the behaviour of the governance service. +* *Supported Action Targets* - these list the types of [action targets](/concepts/action-target) that the governance service can process. +* *Supported Analysis Steps* ([Survey Action Service](/concepts/survey-action-service) only) - these list the analysis steps supported by the survey action service. They provide a description of the types of analysis performed. Some survey action services allow you to specify which analysis steps to skip through its request parameters. +* *Produced Request Parameters* - these list the types of any new request parameters produced by the governance service. These new request parameters will be added to (and may override) the request parameters supplied to the governance service. If the governance service is running as a step in a [governance action process](/concepts/governance-action-process), the combined request parameters are passed on to the next step(s) in the process. +* *Produced Action Targets* - these list the types of any new [action targets](/concepts/action-target) produced by the governance service. These new action targets will be added to (and may override) the action targets supplied to the governance service. If the governance service is running as a step in a [governance action process](/concepts/governance-action-process), the combined action targets are passed on to the next step(s) in the process. +* *Produced Guards* - these list the possible [guards](/concepts/guard) produced by the governance service when it completes. It also identifies the completion status that accompanies the guard that indicates whether the governance service succeeded or failed. +* *Produced Annotation Types* ([Survey Action Service](/concepts/survey-action-service) only) - these list the different types of annotations produced by the survey action service, the data values they include and which analysis step they are produced by. + + + diff --git a/site/docs/concepts/template.md b/site/docs/concepts/template.md new file mode 100644 index 0000000000..97cbf658b8 --- /dev/null +++ b/site/docs/concepts/template.md @@ -0,0 +1,11 @@ +--- +hide: +- toc +--- + + + + +# Template + +A *template* is a collection of linked metadata elements that can be used to provide values and structure to a newly created element. \ No newline at end of file diff --git a/site/docs/education/egeria-dojo/developer/different-types-of-apis-platform-deployment.md b/site/docs/education/egeria-dojo/developer/different-types-of-apis-platform-deployment.md index dbb0e19341..1af9753e0f 100644 --- a/site/docs/education/egeria-dojo/developer/different-types-of-apis-platform-deployment.md +++ b/site/docs/education/egeria-dojo/developer/different-types-of-apis-platform-deployment.md @@ -128,7 +128,7 @@ In the `omag-server-platform` assembly, there is a jar file called `egeria-platf Glossary Author OMVS: View Service for glossary authoring. Dynamic Infrastructure and Operations OMVS: Explore and operate an open metadata ecosystem. Repository Explorer OMVS: Explore open metadata instances. - Glossary Workflow OMVS: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. + Glossary MAnager OMVS: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. My Profile OMVS: Manage information about the logged on user as well as their preferences. Type Explorer OMVS: Explore the open metadata types in a repository or cohort. Server Author OMVS: Author servers. diff --git a/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-no-servers.md b/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-no-servers.md index c910f4d23a..fc340dc6e4 100644 --- a/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-no-servers.md +++ b/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-no-servers.md @@ -51,7 +51,7 @@ * **Glossary Author OMVS**: View Service for glossary authoring. * **Dynamic Infrastructure and Operations OMVS**: Explore and operate an open metadata ecosystem. * **Repository Explorer OMVS**: Explore open metadata instances. -* **Glossary Workflow OMVS**: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. +* **Glossary Manager OMVS**: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. * **My Profile OMVS**: Manage information about the logged on user as well as their preferences. * **Type Explorer OMVS**: Explore the open metadata types in a repository or cohort. * **Server Author OMVS**: Author servers. diff --git a/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-config.md b/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-config.md index b4f5b70035..2203fd2c07 100644 --- a/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-config.md +++ b/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-config.md @@ -51,7 +51,7 @@ * **Glossary Author OMVS**: View Service for glossary authoring. * **Dynamic Infrastructure and Operations OMVS**: Explore and operate an open metadata ecosystem. * **Repository Explorer OMVS**: Explore open metadata instances. -* **Glossary Workflow OMVS**: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. +* **Glossary Manager OMVS**: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. * **My Profile OMVS**: Manage information about the logged on user as well as their preferences. * **Type Explorer OMVS**: Explore the open metadata types in a repository or cohort. * **Server Author OMVS**: Author servers. diff --git a/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-running.md b/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-running.md index bc97b4f35f..a6650b3ed8 100644 --- a/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-running.md +++ b/site/docs/education/tutorials/developer-intellij-tutorial/egeria-platform-report-server-running.md @@ -51,7 +51,7 @@ * **Glossary Author OMVS**: View Service for glossary authoring. * **Dynamic Infrastructure and Operations OMVS**: Explore and operate an open metadata ecosystem. * **Repository Explorer OMVS**: Explore open metadata instances. -* **Glossary Workflow OMVS**: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. +* **Glossary Manager OMVS**: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. * **My Profile OMVS**: Manage information about the logged on user as well as their preferences. * **Type Explorer OMVS**: Explore the open metadata types in a repository or cohort. * **Server Author OMVS**: Author servers. diff --git a/site/docs/education/tutorials/running-from-assembly-tutorial/different-types-of-apis-platform-deployment.md b/site/docs/education/tutorials/running-from-assembly-tutorial/different-types-of-apis-platform-deployment.md index dbb0e19341..8e8074b4af 100644 --- a/site/docs/education/tutorials/running-from-assembly-tutorial/different-types-of-apis-platform-deployment.md +++ b/site/docs/education/tutorials/running-from-assembly-tutorial/different-types-of-apis-platform-deployment.md @@ -128,7 +128,7 @@ In the `omag-server-platform` assembly, there is a jar file called `egeria-platf Glossary Author OMVS: View Service for glossary authoring. Dynamic Infrastructure and Operations OMVS: Explore and operate an open metadata ecosystem. Repository Explorer OMVS: Explore open metadata instances. - Glossary Workflow OMVS: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. + Glossary Manager OMVS: Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states. My Profile OMVS: Manage information about the logged on user as well as their preferences. Type Explorer OMVS: Explore the open metadata types in a repository or cohort. Server Author OMVS: Author servers. diff --git a/site/docs/guides/admin/egeria-admin.drawio b/site/docs/guides/admin/egeria-admin.drawio index c947399083..a6104a6d30 100644 --- a/site/docs/guides/admin/egeria-admin.drawio +++ b/site/docs/guides/admin/egeria-admin.drawio @@ -1,4 +1,4 @@ - + @@ -3624,6 +3624,71 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/site/docs/guides/admin/user-interfaces/configuring-the-presentation-server.md b/site/docs/guides/admin/user-interfaces/configuring-the-presentation-server.md new file mode 100644 index 0000000000..e5fcaad2b2 --- /dev/null +++ b/site/docs/guides/admin/user-interfaces/configuring-the-presentation-server.md @@ -0,0 +1,46 @@ + + + +# Configuring the presentation server + +The [presentation server](/concepts/presentation-server) can be implemented with any webserver technology that is able to act as a reverse proxy and host the Javascript static content needed gor Egeria's [General User UI](/user-interfaces/general/overview). In these instructions we are using [NGINX](https://nginx.org/en/). + +??? tip "Installing nginx" + On macOS, nginx can be installed using [Homebrew](https://brew.sh/) with the following command: `brew install nginx` + + +## Managing the Javascript static content + +### Downloading + +Egeria's UI static content is located in [https://github.com/odpi/egeria-ui](https://github.com/odpi/egeria-ui). + +```shell +git clone https://github.com/odpi/egeria-ui.git +``` +This creates a new directory called `egeria-ui` +```shell +cd egeria-ui +``` +### Building + +The content is built using the Node Package Manager (NPM) version 16.13.0. + +??? tip "Installing NPM" + On macOS, npm can be installed using [Homebrew](https://brew.sh/) with the following command: `brew install npm`. + You also need to install the Node Version Manager (NVM) to move NPM back to version 16.13.0. (Use `brew install nvm` and follow the instructions to complete the install). + +First, ensure all of your packages are up to date on your local machine: + +```shell + npm install npm@8.1.0 + +``` +Then run the following command and the static content is built in `build` +```shell +npm run build +``` +You can then copy the contents of `build` to where you want nginx to retrieve it from + + +--8<-- "snippets/abbr.md" \ No newline at end of file diff --git a/site/docs/release-notes/4-1.md b/site/docs/release-notes/4-1.md index 8de027737c..12d11f85f5 100644 --- a/site/docs/release-notes/4-1.md +++ b/site/docs/release-notes/4-1.md @@ -19,7 +19,7 @@ In this release we have added the following view services to aid organizations writing user interfaces (UIs): * [Glossary Browser OMVS](/services/omvs/glossary-browser/overview) - * [Glossary Workflow OMVS](/services/omvs/glossary-workflow/overview) + * [Glossary Manager OMVS](/services/omvs/glossary-manager/overview) ??? functional "Glossary specific security" The [Server Metadata Security Connector](/concepts/server-metadata-security-connector) has been extended with a new optional interface that allows the connector to control authorization requests to glossaries. See the [Metadata Security](/features/metadata-security/overview) feature for more details. diff --git a/site/docs/release-notes/5-0.md b/site/docs/release-notes/5-0.md index 6a783e632b..439dfbba8a 100644 --- a/site/docs/release-notes/5-0.md +++ b/site/docs/release-notes/5-0.md @@ -120,8 +120,8 @@ Release 5.0 is a major functional release focused on usability, both from the po ??? functional "Extended support for file system monitoring" The context for all the [Open Metadata Integration Services (OMIS)](/services/omis) has been updated to support a file system listener. This means that [integration connectors](/concepts/integraiton-connector) can easily monitor changing files and directories. This can be useful for situations where new information is being exchanged with open metadata using files such as CSV files and spreadsheets. -??? functional "New View Service: Governance Author OMVS" - [Governance Author OMVS](/services/omvs/governance-author/overview) is a new view service for managing the definitions of governance action types and and governance action processes. +??? functional "New View Service: Action Author OMVS" + [Action Author OMVS](/services/omvs/action-author/overview) is a new view service for managing the definitions of governance action types and and governance action processes. ??? functional "New View Service: Automated Curation OMVS" [Automated Curation OMVS](/services/omvs/automated-curation/overview) is a new view service that enable the user to set up integration connectors in an integration daemon, run engine actions and governance action processes. @@ -168,7 +168,7 @@ Release 5.0 is a major functional release focused on usability, both from the po * [Automated Curation OMVS](/services/omvs/automated-curation/overview) * [Collection Manager OMVS](/services/omvs/automated-curation/overview) * [Glossary Browser OMVS](/services/omvs/glossary-browser/overview) - * [Glossary Workflow OMVS](/services/omvs/glossary-workflow/overview) + * [Glossary Manager OMVS](/services/omvs/glossary-manager/overview) * [My Profile OMVS](/services/omvs/my-profile/overview) * [Notification Manager OMVS](/services/omvs/notification-manager/overview) diff --git a/site/docs/release-notes/april-2023.md b/site/docs/release-notes/april-2023.md index 9b29ddf441..e1becb21ce 100644 --- a/site/docs/release-notes/april-2023.md +++ b/site/docs/release-notes/april-2023.md @@ -42,14 +42,14 @@ The [Server Metadata Security Connector](/concepts/server-metadata-security-conn In this release we have added the following view services to aid organizations writing user interfaces (UIs): * [Glossary Browser OMVS](#glossary-browser-omvs) -* [Glossary Workflow OMVS](#glossary-workflow-omvs) +* [Glossary Manager OMVS](#glossary-manager-omvs) These view services are supported by enhancements to the [Asset Manager OMAS](/services/omas/asset-manager/overivew){target=blank} -### Glossary Workflow OMVS +### Glossary Manager OMVS -Glossary Workflow OMVS supports the development of glossaries using a controlled workflow process -[... more information](/services/omvs/glossary-workflow/overview){target=blank}. +Glossary Manager OMVS supports the development of glossaries using a controlled workflow process +[... more information](/services/omvs/glossary-manager/overview){target=blank}. ### Glossary Browser OMVS diff --git a/site/docs/release-notes/august-2023.md b/site/docs/release-notes/august-2023.md index 40691812f9..e7f13f808e 100644 --- a/site/docs/release-notes/august-2023.md +++ b/site/docs/release-notes/august-2023.md @@ -62,7 +62,7 @@ Each directory in the assembly includes a README.md file to explain its contents ## Controlled glossary development (glossary workflows) -[Glossary terms](/practices/common-data-definitions/anatomy-of-a-glossary) provide important definitions within an organization's governance programs. They help to clarify the terminology being used and identify where data with a certain meaning is located. As a result, organizations often want to operate a collaborative process for updating their glossary terms. Anticipating this, Egeria's original type system included the [ControlledGlossaryTerm](/types/3/0385-Controlled-Glossary-Development#controlledglossaryterm-entity) that had additional statuses beyond ACTIVE to support a complex development lifecycle. In release 4.1 this was extended with [new types](/types/3/0385-Controlled-Glossary-Development) and [services](/services/omvs/glossary-workflow/overview) to control the visibility of glossary terms as they are developed. +[Glossary terms](/practices/common-data-definitions/anatomy-of-a-glossary) provide important definitions within an organization's governance programs. They help to clarify the terminology being used and identify where data with a certain meaning is located. As a result, organizations often want to operate a collaborative process for updating their glossary terms. Anticipating this, Egeria's original type system included the [ControlledGlossaryTerm](/types/3/0385-Controlled-Glossary-Development#controlledglossaryterm-entity) that had additional statuses beyond ACTIVE to support a complex development lifecycle. In release 4.1 this was extended with [new types](/types/3/0385-Controlled-Glossary-Development) and [services](/services/omvs/glossary-manager/overview) to control the visibility of glossary terms as they are developed. ## Extended integration connector function (4.3) @@ -112,16 +112,16 @@ The [Server Metadata Security Connector](/concepts/server-metadata-security-conn View services are designed to provide REST APIs to UIs. In release 4.1 we added the following view services to aid organizations writing user interfaces (UIs): * [Glossary Browser OMVS](#glossary-browser-omvs) -* [Glossary Workflow OMVS](#glossary-workflow-omvs) +* [Glossary Manager OMVS](#glossary-manager-omvs) These view services are supported by enhancements to the [Asset Manager OMAS](/services/omas/asset-manager/overview){target=blank}. In release 4.2 we added another view service called [My Profile OMVS](#my-profile-omvs). -### Glossary Workflow OMVS +### Glossary Manager OMVS -Glossary Workflow OMVS supports the development of glossaries using a controlled workflow process -[... more information](/services/omvs/glossary-workflow/overview){target=blank}. +Glossary Manager OMVS supports the development of glossaries using a controlled workflow process +[... more information](/services/omvs/glossary-manager/overview){target=blank}. ### Glossary Browser OMVS diff --git a/site/docs/services/omas/index.md b/site/docs/services/omas/index.md index 202884da80..3fca1cd6c3 100644 --- a/site/docs/services/omas/index.md +++ b/site/docs/services/omas/index.md @@ -12,31 +12,31 @@ The Open Metadata Access Services (OMAS) provide domain-specific services for da The access services are as follows: -| OMAS | Description | Supplies APIs and events to | -|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Asset Consumer](/services/omas/asset-consumer/overview) | The Asset Consumer OMAS is designed for applications that are using [OCF](/frameworks/ocf/overview) connectors to access data stores, APIs and functions such as analytics. The Asset Consumer OMAS provides a factory function for the connectors, the ability to retrieve all of the metadata about the asset and the ability to add feedback on the asset. | [Search Integrator OMIS](/services/omis/search-integrator/overview), [Asset Catalog OMVS](/services/omvs/asset-catalog/overview) | -| [Asset Lineage](/services/omas/asset-lineage/overview) | The Asset Lineage OMAS listens to relevant lineage related events on the enterprise topic level and publishes these on the Asset Lineage OutTopic, combined with relevant context information on the described entities. These events are listened to by the open lineage services governance server. | [Lineage Warehouse Services](/services/lineage-warehouse-services) | -| [Asset Manager](/services/omas/asset-manager/overview) | The Asset Manager OMAS manages the exchange of metadata with third party metadata catalogs and asset managers. It is typically called by the [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview) to send and receive asset information, including schemas, profiles, policies and lineage information with a third party asset manager. Typical examples of asset managers include data catalogs that are managing metadata for a collection of data assets for a data-serving solution. | [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview), [Lineage Integrator OMIS](/services/omis/lineage-integrator/overview), [Glossary Browser OMVS](/services/omvs/glossary-browser/overview), [Glossary Workflow OMVS](/services/omvs/glossary-workflow/overview), [Feedback Manager OMVS](/services/omvs/feedback-manager/overview) | -| [Asset Owner](/services/omas/asset-owner/overview) | The Asset Owner OMAS provides services for an asset owner to curate metadata about their asset(s) and understand how these assets are being used and governed. | [Survey Action OMES](/services/omes/survey-action/overview), [Automated Curation OMVS](/services/omvs/automated-curation/overview) | -| [Community Profile](/services/omas/community-profile/overview) | The Community Profile OMAS supports the administration for a community and related user profiles. These communities are involved in reviewing and crowd-sourcing knowledge about the data assets and their use. | [Organization Integrator OMIS](/services/omis/organization-integrator/overview), [My Profile OMVS](/services/omvs/my-profile/overview) | -| [Data Engine](/services/omas/data-engine/overview) | The Data Engine OMAS provides APIs and events for a data movement/processing engine to record the changes it is making the the data landscape. This information forms a key part of asset lineage. | [Data Engine Proxy Services](/services/data-engine-proxy-services) | -| [Data Manager](/services/omas/data-manager/overview) | The Data Manager OMAS provides an integration point to enable technologies that manage collections of data such as database servers, file systems, file managers and content managers to publish metadata to the metadata repositories about the changing structures and content stored in the data platform. It is typically called from the [Database Integrator OMIS](/services/omis/database-integrator/overview) and [Files Integrator OMIS](/services/omis/files-integrator/overview) integration services. | [API Integrator OMIS](/services/omis/api-integrator/overview), [Database Integrator OMIS](/services/omis/database-integrator/overview), [Display Integrator OMIS](/services/omis/display-integrator/overview), [Files Integrator OMIS](/services/omis/files-integrator/overview), [Topic Integrator OMIS](/services/omis/topic-integrator/overview) | -| [Data Privacy](/services/omas/data-privacy/overview) | The Data Privacy OMAS supports a privacy officer as they manage data privacy in their organization. This includes managing privacy impact assessments and reviews of software services that use personal data as they move through their development, deployment and use. | | -| [Data Science](/services/omas/data-science/overview) | The Data Science OMAS provides access to metadata for data assets, connections and projects, plus the ability to maintain metadata about data science notebooks and models and log activity during the analytics development process. It is designed for data science and analytics management tools. | [Analytics Integrator OMIS](/services/omis/analytics-integrator/overview) | -| [Design Model](/services/omas/design-model/overview) | The Design Model OMAS provides the ability to manage information from all types of design models. These models may come from tools or be part of a packaged standard. This content is useful for governance, system integration and software development. | | -| [DevOps](/services/omas/dev-ops/overview) | The DevOps OMAS provides services for a DevOps pipeline to query and maintain metadata about systems, processes and software components that are being deployed into the information landscape. | | -| [Digital Architecture](/services/omas/digital-architecture/overview) | The Digital Architecture OMAS provides the ability to define information standards, definitions, solution blueprints and models for an organization. It is designed for architecture tools. It is able to support the definition and management of a digital service through concept to deployment. | | -| [Digital Service](/services/omas/digital-service/overview) | The Digital Service OMAS provides services for a managing the lifecycle of an Egeria Digital Service. | [Collection Manager OMVS](/services/omvs/collection-manager/overview) | -| [Governance Engine](/services/omas/governance-engine/overview) | The Governance Engine OMAS provides APIs and events that retrieve and manage metadata for [governance action services](/concepts/governance-action-service). | [Governance Action OMES](/services/omes/governance-action/overview), [Context Event OMES](/services/omes/context-event/overview) | -| [Governance Program](/services/omas/governance-program/overview) | The Governance Program OMAS provides the ability to maintain a governance program in the open metadata repositories. It is designed for governance and CDO tools. | [Governance Author OMVS](/services/omvs/governance-author/overview) | -| [Governance Server](/services/omas/governance-server/overview) | The Governance Server OMAS supplies the [governance engine definitions](/concepts/governance-engine-definition) to the [engine hosts](/concepts/engine-host) and the and [integration group definitions](/concepts/integration-group) to the [integration daemons](/concepts/integration-daemon). | [Integration Daemon Services](/services/integration-daemon-services), [Engine Host Services](/services/engine-host-services) | -| [IT Infrastructure](/services/omas/it-infrastructure/overview) | The IT Infrastructure OMAS provides support for the design and planning of the information infrastructure that supports the data assets. This includes the development of system blueprints that link down to the metadata about real infrastructure components. This metadata helps in the linkage between information governance metadata and IT infrastructure management (ITIL) metadata typically stored in a Configuration Management Database (CMDB). | [Infrastructure Integrator OMIS](/services/omis/infrastructure-integrator/overview) | -| [Project Management](/services/omas/project-management/overview) | The Project Management OMAS supports the metadata associated with projects and campaigns. These projects and campaigns may be for governance projects, or generic data use projects. | [Project Manager OMVS](/services/omvs/project-manager/overview) | -| [Security Manager](/services/omas/security-manager/overview) | The Security Manager OMAS provides the services to exchange security tags with access control and data protection technology services. It is called by the [Security Integrator OMIS](/services/omis/security-integrator/overview). | [Security Integrator OMIS](/services/omis/security-integrator/overview) | -| [Security Officer](/services/omas/security-officer/overview) | The Security Officer OMAS provides the services to support the definition of roles and rules for managing the protection of metadata and assets, plus work with the audit logs captured by the open metadata and governance tools. It is typically used by the security, compliance and auditing teams. | | -| [Software Developer](/services/omas/software-developer/overview) | The Software Development OMAS provides access to metadata needed to build compliant APIs, data stores and related software components. | | -| [Stewardship Action](/services/omas/stewardship-action/overview) | The Stewardship Action OMAS provides services for managing exceptions discovered in the information landscape that need correcting. These exceptions may be quality errors, missing or outdated information, invalid licensing, job failures, and many more. The Stewardship Action OMAS also enables the review and triage of the exceptions, simple remediation and status reporting. | [Stewardship Integrator OMIS](/services/omis/stewardship-integrator/overview), [Notification Manager OMVS](/services/omvs/notification-manager/overview) | -| [Subject Area](/services/omas/subject-area/overview) | The Subject Area OMAS is for tools that support subject matter experts who are defining glossaries, reference data and rules around data for a specific subject area, such as "customer data". It supports the development of a comprehensive definition of the subject area and the standards that support it. These definitions can then be folded into the Governance Program, and used by Asset Owner's to improve the findability and understandability of their assets by linking their asset's structure to relevant parts of the subject area definition. | [Glossary Author OMVS](/services/omvs/glossary-author/overview) | +| OMAS | Description | Supplies APIs and events to | +|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [Asset Consumer](/services/omas/asset-consumer/overview) | The Asset Consumer OMAS is designed for applications that are using [OCF](/frameworks/ocf/overview) connectors to access data stores, APIs and functions such as analytics. The Asset Consumer OMAS provides a factory function for the connectors, the ability to retrieve all of the metadata about the asset and the ability to add feedback on the asset. | [Search Integrator OMIS](/services/omis/search-integrator/overview), [Asset Catalog OMVS](/services/omvs/asset-catalog/overview) | +| [Asset Lineage](/services/omas/asset-lineage/overview) | The Asset Lineage OMAS listens to relevant lineage related events on the enterprise topic level and publishes these on the Asset Lineage OutTopic, combined with relevant context information on the described entities. These events are listened to by the open lineage services governance server. | [Lineage Warehouse Services](/services/lineage-warehouse-services) | +| [Asset Manager](/services/omas/asset-manager/overview) | The Asset Manager OMAS manages the exchange of metadata with third party metadata catalogs and asset managers. It is typically called by the [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview) to send and receive asset information, including schemas, profiles, policies and lineage information with a third party asset manager. Typical examples of asset managers include data catalogs that are managing metadata for a collection of data assets for a data-serving solution. | [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview), [Lineage Integrator OMIS](/services/omis/lineage-integrator/overview), [Glossary Browser OMVS](/services/omvs/glossary-browser/overview), [Glossary Manager OMVS](/services/omvs/glossary-manager/overview), [Feedback Manager OMVS](/services/omvs/feedback-manager/overview) | +| [Asset Owner](/services/omas/asset-owner/overview) | The Asset Owner OMAS provides services for an asset owner to curate metadata about their asset(s) and understand how these assets are being used and governed. | [Survey Action OMES](/services/omes/survey-action/overview), [Automated Curation OMVS](/services/omvs/automated-curation/overview) | +| [Community Profile](/services/omas/community-profile/overview) | The Community Profile OMAS supports the administration for a community and related user profiles. These communities are involved in reviewing and crowd-sourcing knowledge about the data assets and their use. | [Organization Integrator OMIS](/services/omis/organization-integrator/overview), [My Profile OMVS](/services/omvs/my-profile/overview) | +| [Data Engine](/services/omas/data-engine/overview) | The Data Engine OMAS provides APIs and events for a data movement/processing engine to record the changes it is making the the data landscape. This information forms a key part of asset lineage. | [Data Engine Proxy Services](/services/data-engine-proxy-services) | +| [Data Manager](/services/omas/data-manager/overview) | The Data Manager OMAS provides an integration point to enable technologies that manage collections of data such as database servers, file systems, file managers and content managers to publish metadata to the metadata repositories about the changing structures and content stored in the data platform. It is typically called from the [Database Integrator OMIS](/services/omis/database-integrator/overview) and [Files Integrator OMIS](/services/omis/files-integrator/overview) integration services. | [API Integrator OMIS](/services/omis/api-integrator/overview), [Database Integrator OMIS](/services/omis/database-integrator/overview), [Display Integrator OMIS](/services/omis/display-integrator/overview), [Files Integrator OMIS](/services/omis/files-integrator/overview), [Topic Integrator OMIS](/services/omis/topic-integrator/overview) | +| [Data Privacy](/services/omas/data-privacy/overview) | The Data Privacy OMAS supports a privacy officer as they manage data privacy in their organization. This includes managing privacy impact assessments and reviews of software services that use personal data as they move through their development, deployment and use. | | +| [Data Science](/services/omas/data-science/overview) | The Data Science OMAS provides access to metadata for data assets, connections and projects, plus the ability to maintain metadata about data science notebooks and models and log activity during the analytics development process. It is designed for data science and analytics management tools. | [Analytics Integrator OMIS](/services/omis/analytics-integrator/overview) | +| [Design Model](/services/omas/design-model/overview) | The Design Model OMAS provides the ability to manage information from all types of design models. These models may come from tools or be part of a packaged standard. This content is useful for governance, system integration and software development. | | +| [DevOps](/services/omas/dev-ops/overview) | The DevOps OMAS provides services for a DevOps pipeline to query and maintain metadata about systems, processes and software components that are being deployed into the information landscape. | | +| [Digital Architecture](/services/omas/digital-architecture/overview) | The Digital Architecture OMAS provides the ability to define information standards, definitions, solution blueprints and models for an organization. It is designed for architecture tools. It is able to support the definition and management of a digital service through concept to deployment. | | +| [Digital Service](/services/omas/digital-service/overview) | The Digital Service OMAS provides services for a managing the lifecycle of an Egeria Digital Service. | [Collection Manager OMVS](/services/omvs/collection-manager/overview) | +| [Governance Engine](/services/omas/governance-engine/overview) | The Governance Engine OMAS provides APIs and events that retrieve and manage metadata for [governance action services](/concepts/governance-action-service). | [Governance Action OMES](/services/omes/governance-action/overview), [Context Event OMES](/services/omes/context-event/overview) | +| [Governance Program](/services/omas/governance-program/overview) | The Governance Program OMAS provides the ability to maintain a governance program in the open metadata repositories. It is designed for governance and CDO tools. | [Action Author OMVS](/services/omvs/action-author/overview) | +| [Governance Server](/services/omas/governance-server/overview) | The Governance Server OMAS supplies the [governance engine definitions](/concepts/governance-engine-definition) to the [engine hosts](/concepts/engine-host) and the and [integration group definitions](/concepts/integration-group) to the [integration daemons](/concepts/integration-daemon). | [Integration Daemon Services](/services/integration-daemon-services), [Engine Host Services](/services/engine-host-services) | +| [IT Infrastructure](/services/omas/it-infrastructure/overview) | The IT Infrastructure OMAS provides support for the design and planning of the information infrastructure that supports the data assets. This includes the development of system blueprints that link down to the metadata about real infrastructure components. This metadata helps in the linkage between information governance metadata and IT infrastructure management (ITIL) metadata typically stored in a Configuration Management Database (CMDB). | [Infrastructure Integrator OMIS](/services/omis/infrastructure-integrator/overview) | +| [Project Management](/services/omas/project-management/overview) | The Project Management OMAS supports the metadata associated with projects and campaigns. These projects and campaigns may be for governance projects, or generic data use projects. | [Project Manager OMVS](/services/omvs/project-manager/overview) | +| [Security Manager](/services/omas/security-manager/overview) | The Security Manager OMAS provides the services to exchange security tags with access control and data protection technology services. It is called by the [Security Integrator OMIS](/services/omis/security-integrator/overview). | [Security Integrator OMIS](/services/omis/security-integrator/overview) | +| [Security Officer](/services/omas/security-officer/overview) | The Security Officer OMAS provides the services to support the definition of roles and rules for managing the protection of metadata and assets, plus work with the audit logs captured by the open metadata and governance tools. It is typically used by the security, compliance and auditing teams. | | +| [Software Developer](/services/omas/software-developer/overview) | The Software Development OMAS provides access to metadata needed to build compliant APIs, data stores and related software components. | | +| [Stewardship Action](/services/omas/stewardship-action/overview) | The Stewardship Action OMAS provides services for managing exceptions discovered in the information landscape that need correcting. These exceptions may be quality errors, missing or outdated information, invalid licensing, job failures, and many more. The Stewardship Action OMAS also enables the review and triage of the exceptions, simple remediation and status reporting. | [Stewardship Integrator OMIS](/services/omis/stewardship-integrator/overview), [Notification Manager OMVS](/services/omvs/notification-manager/overview) | +| [Subject Area](/services/omas/subject-area/overview) | The Subject Area OMAS is for tools that support subject matter experts who are defining glossaries, reference data and rules around data for a specific subject area, such as "customer data". It supports the development of a comprehensive definition of the subject area and the standards that support it. These definitions can then be folded into the Governance Program, and used by Asset Owner's to improve the findability and understandability of their assets by linking their asset's structure to relevant parts of the subject area definition. | [Glossary Author OMVS](/services/omvs/glossary-author/overview) | ## Using the OMAS's diff --git a/site/docs/services/omvs/governance-author/overview.md b/site/docs/services/omvs/action-author/overview.md similarity index 77% rename from site/docs/services/omvs/governance-author/overview.md rename to site/docs/services/omvs/action-author/overview.md index 1a48420ae6..f2e2f35c6d 100644 --- a/site/docs/services/omvs/governance-author/overview.md +++ b/site/docs/services/omvs/action-author/overview.md @@ -8,9 +8,9 @@ hide: --8<-- "snippets/content-status/tech-preview.md" -# Governance Author Open Metadata View Service (OMVS) +# Action Author Open Metadata View Service (OMVS) -The Governance Author OMVS provides services to create an maintain governance actions: +The Action Author OMVS provides services to create an maintain governance actions: * Setting up [governance action type](/concepts/governance-action-type) definitions. * Setting up [governance action process](/concepts/governance-action-process) definitions. diff --git a/site/docs/services/omvs/asset-catalog/asset-catalog.drawio b/site/docs/services/omvs/asset-catalog/asset-catalog.drawio new file mode 100644 index 0000000000..24056eae88 --- /dev/null +++ b/site/docs/services/omvs/asset-catalog/asset-catalog.drawio @@ -0,0 +1,376 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/site/docs/services/omvs/glossary-workflow/external-workflow-engine-2.svg b/site/docs/services/omvs/glossary-manager/external-workflow-engine-2.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/external-workflow-engine-2.svg rename to site/docs/services/omvs/glossary-manager/external-workflow-engine-2.svg diff --git a/site/docs/services/omvs/glossary-workflow/external-workflow-engine.svg b/site/docs/services/omvs/glossary-manager/external-workflow-engine.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/external-workflow-engine.svg rename to site/docs/services/omvs/glossary-manager/external-workflow-engine.svg diff --git a/site/docs/services/omvs/glossary-workflow/glossary-workflow.drawio b/site/docs/services/omvs/glossary-manager/glossary-workflow.drawio similarity index 100% rename from site/docs/services/omvs/glossary-workflow/glossary-workflow.drawio rename to site/docs/services/omvs/glossary-manager/glossary-workflow.drawio diff --git a/site/docs/services/omvs/glossary-workflow/harvested-glossary.md b/site/docs/services/omvs/glossary-manager/harvested-glossary.md similarity index 100% rename from site/docs/services/omvs/glossary-workflow/harvested-glossary.md rename to site/docs/services/omvs/glossary-manager/harvested-glossary.md diff --git a/site/docs/services/omvs/glossary-workflow/harvested-glossary.svg b/site/docs/services/omvs/glossary-manager/harvested-glossary.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/harvested-glossary.svg rename to site/docs/services/omvs/glossary-manager/harvested-glossary.svg diff --git a/site/docs/services/omvs/glossary-workflow/multi-level-glossaries.md b/site/docs/services/omvs/glossary-manager/multi-level-glossaries.md similarity index 100% rename from site/docs/services/omvs/glossary-workflow/multi-level-glossaries.md rename to site/docs/services/omvs/glossary-manager/multi-level-glossaries.md diff --git a/site/docs/services/omvs/glossary-workflow/multi-level-glossaries.svg b/site/docs/services/omvs/glossary-manager/multi-level-glossaries.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/multi-level-glossaries.svg rename to site/docs/services/omvs/glossary-manager/multi-level-glossaries.svg diff --git a/site/docs/services/omvs/glossary-workflow/open-contribution-glossary.md b/site/docs/services/omvs/glossary-manager/open-contribution-glossary.md similarity index 100% rename from site/docs/services/omvs/glossary-workflow/open-contribution-glossary.md rename to site/docs/services/omvs/glossary-manager/open-contribution-glossary.md diff --git a/site/docs/services/omvs/glossary-workflow/open-contribution-glossary.svg b/site/docs/services/omvs/glossary-manager/open-contribution-glossary.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/open-contribution-glossary.svg rename to site/docs/services/omvs/glossary-manager/open-contribution-glossary.svg diff --git a/site/docs/services/omvs/glossary-workflow/overview.md b/site/docs/services/omvs/glossary-manager/overview.md similarity index 96% rename from site/docs/services/omvs/glossary-workflow/overview.md rename to site/docs/services/omvs/glossary-manager/overview.md index a04afe43aa..d6145ab42e 100644 --- a/site/docs/services/omvs/glossary-workflow/overview.md +++ b/site/docs/services/omvs/glossary-manager/overview.md @@ -3,9 +3,9 @@ --8<-- "snippets/content-status/tech-preview.md" -# Glossary Workflow OMVS +# Glossary Manager OMVS -The Glossary Workflow Open Metadata View Service (OMVS) is a REST API designed to support UIs that enable the maintenance of [glossary content](/practices/common-data-definitions/anatomy-of-a-glossary) using a controlled workflow process. It runs in a [View Server](/concepts/view-server) and calls the [Asset Manager OMAS](/services/omas/asset-manager/overview) to retrieve and make changes to the glossary. +The Glossary Manager Open Metadata View Service (OMVS) is a REST API designed to support UIs that enable the maintenance of [glossary content](/practices/common-data-definitions/anatomy-of-a-glossary) using a controlled workflow process. It runs in a [View Server](/concepts/view-server) and calls the [Asset Manager OMAS](/services/omas/asset-manager/overview) to retrieve and make changes to the glossary. ## Why use a controlled glossary workflow @@ -40,16 +40,16 @@ Where multiple glossaries are in play, each can operate a different style. The | Release-controlled glossary | Glossary authoring team. | Coordination of all changes to the glossary, which terms are included, their exact content and when updates are to be included. | Changes are delayed waiting for the next release. | For glossaries that must present a coherent scope. | === "Harvested Glossary" - ---8<-- "docs/services/omvs/glossary-workflow/harvested-glossary.md" + ---8<-- "docs/services/omvs/glossary-manager/harvested-glossary.md" === "Multi-level Glossaries" - ---8<-- "docs/services/omvs/glossary-workflow/multi-level-glossaries.md" + ---8<-- "docs/services/omvs/glossary-manager/multi-level-glossaries.md" === "Open Contribution Glossary" - ---8<-- "docs/services/omvs/glossary-workflow/open-contribution-glossary.md" + ---8<-- "docs/services/omvs/glossary-manager/open-contribution-glossary.md" === "Release Controlled Glossary" - ---8<-- "docs/services/omvs/glossary-workflow/release-controlled-glossary.md" + ---8<-- "docs/services/omvs/glossary-manager/release-controlled-glossary.md" ---- @@ -168,7 +168,7 @@ This approach provides a simple integration path that acts when the external pro ![Handing over responsibility](external-workflow-engine-2.svg) -The Asset Manager OMAS is the same service called by the Glossary Workflow OMAS. +The Asset Manager OMAS is the same service called by the Glossary Manager OMAS. ---8<-- "snippets/abbr.md" diff --git a/site/docs/services/omvs/glossary-workflow/release-controlled-glossary.md b/site/docs/services/omvs/glossary-manager/release-controlled-glossary.md similarity index 100% rename from site/docs/services/omvs/glossary-workflow/release-controlled-glossary.md rename to site/docs/services/omvs/glossary-manager/release-controlled-glossary.md diff --git a/site/docs/services/omvs/glossary-workflow/release-controlled-glossary.svg b/site/docs/services/omvs/glossary-manager/release-controlled-glossary.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/release-controlled-glossary.svg rename to site/docs/services/omvs/glossary-manager/release-controlled-glossary.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-1.svg b/site/docs/services/omvs/glossary-manager/rolling-editing-glossary-1.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-1.svg rename to site/docs/services/omvs/glossary-manager/rolling-editing-glossary-1.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-2.svg b/site/docs/services/omvs/glossary-manager/rolling-editing-glossary-2.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-2.svg rename to site/docs/services/omvs/glossary-manager/rolling-editing-glossary-2.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-3.svg b/site/docs/services/omvs/glossary-manager/rolling-editing-glossary-3.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-3.svg rename to site/docs/services/omvs/glossary-manager/rolling-editing-glossary-3.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-4.svg b/site/docs/services/omvs/glossary-manager/rolling-editing-glossary-4.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-4.svg rename to site/docs/services/omvs/glossary-manager/rolling-editing-glossary-4.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-5.svg b/site/docs/services/omvs/glossary-manager/rolling-editing-glossary-5.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-editing-glossary-5.svg rename to site/docs/services/omvs/glossary-manager/rolling-editing-glossary-5.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-1.svg b/site/docs/services/omvs/glossary-manager/rolling-staging-glossary-1.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-1.svg rename to site/docs/services/omvs/glossary-manager/rolling-staging-glossary-1.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-2.svg b/site/docs/services/omvs/glossary-manager/rolling-staging-glossary-2.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-2.svg rename to site/docs/services/omvs/glossary-manager/rolling-staging-glossary-2.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-3.svg b/site/docs/services/omvs/glossary-manager/rolling-staging-glossary-3.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-3.svg rename to site/docs/services/omvs/glossary-manager/rolling-staging-glossary-3.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-4.svg b/site/docs/services/omvs/glossary-manager/rolling-staging-glossary-4.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-4.svg rename to site/docs/services/omvs/glossary-manager/rolling-staging-glossary-4.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-5.svg b/site/docs/services/omvs/glossary-manager/rolling-staging-glossary-5.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-5.svg rename to site/docs/services/omvs/glossary-manager/rolling-staging-glossary-5.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-6.svg b/site/docs/services/omvs/glossary-manager/rolling-staging-glossary-6.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-6.svg rename to site/docs/services/omvs/glossary-manager/rolling-staging-glossary-6.svg diff --git a/site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-7.svg b/site/docs/services/omvs/glossary-manager/rolling-staging-glossary-7.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/rolling-staging-glossary-7.svg rename to site/docs/services/omvs/glossary-manager/rolling-staging-glossary-7.svg diff --git a/site/docs/services/omvs/glossary-workflow/sourced-from-template.svg b/site/docs/services/omvs/glossary-manager/sourced-from-template.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/sourced-from-template.svg rename to site/docs/services/omvs/glossary-manager/sourced-from-template.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-1.svg b/site/docs/services/omvs/glossary-manager/temporary-editing-glossary-1.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-1.svg rename to site/docs/services/omvs/glossary-manager/temporary-editing-glossary-1.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-2.svg b/site/docs/services/omvs/glossary-manager/temporary-editing-glossary-2.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-2.svg rename to site/docs/services/omvs/glossary-manager/temporary-editing-glossary-2.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-3.svg b/site/docs/services/omvs/glossary-manager/temporary-editing-glossary-3.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-3.svg rename to site/docs/services/omvs/glossary-manager/temporary-editing-glossary-3.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-4.svg b/site/docs/services/omvs/glossary-manager/temporary-editing-glossary-4.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-editing-glossary-4.svg rename to site/docs/services/omvs/glossary-manager/temporary-editing-glossary-4.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-1.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-1.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-1.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-1.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-2.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-2.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-2.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-2.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-3.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-3.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-3.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-3.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-4.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-4.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-4.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-4.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-5.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-5.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-5.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-5.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-6.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-6.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-6.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-6.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-7.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-7.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-7.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-7.svg diff --git a/site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-8.svg b/site/docs/services/omvs/glossary-manager/temporary-staging-glossary-8.svg similarity index 100% rename from site/docs/services/omvs/glossary-workflow/temporary-staging-glossary-8.svg rename to site/docs/services/omvs/glossary-manager/temporary-staging-glossary-8.svg diff --git a/site/docs/services/omvs/index.md b/site/docs/services/omvs/index.md index 18c1315c37..29f65dac35 100644 --- a/site/docs/services/omvs/index.md +++ b/site/docs/services/omvs/index.md @@ -15,14 +15,14 @@ The view services are as follows: | [Collection Manager](/services/omvs/collection-manager/overview) | **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. | | [Automated Curation](/services/omvs/automated-curation/overview) | **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. | | [Data Discovery](/services/omvs/data-discovery/overview) | **Documenting specifications that describe the data needed for a project.** | The Data Discovery Open Metadata View Services (OMVS) is a REST API designed to support user interfaces (UIs) for documenting specifications that describe the data needed for a project. These are known as DataSpecs and they can be used to specify schemas for data pipelines as well as saved searches. | -| [Governance Author](/services/omvs/governance-author/overview) | **Create and maintain governance actions.** | The Governance Author OMVS is for user interfaces supporting the governance team to set up governance definitions and actions. | +| [Action Author](/services/omvs/action-author/overview) | **Create and maintain governance actions.** | The Action Author OMVS is for user interfaces supporting the governance team to set up governance definitions and actions. | | [Notification Manager](/services/omvs/notification-manager/overview) | **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. | | [Project Manager](/services/omvs/project-manager/overview) | **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. | | [Reference Data](/services/omvs/reference-data/overview) | **Create and maintain reference data values and their mappings.** | The Reference Data Open Metadata View Services (OMVS) is a REST API designed to support user interfaces (UIs) that maintain reference data values and their mappings. | | | [Valid Metadata](/services/omvs/valid-metadata/overview) | **Create and maintain metadata valid values.** | The Valid Metadata Open Metadata View Services (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. | | | [Template Manager](/services/omvs/template-manager/overview) | **Create and maintain templates used to create new metadata elements.** | The Template Manager Open Metadata View Services (OMVS) is a REST API designed to support user interfaces (UIs) that support the management of templates that are used when creating new metadata. | | [Glossary Browser](/services/omvs/glossary-browser/overview) | **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](/services/omvs/glossary-workflow/overview) | **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. | +| [Glossary Manager](/services/omvs/glossary-manager/overview) | **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. | | [Glossary Author](/services/omvs/glossary-author/overview) | **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. | | [Repository Explorer](/services/omvs/rex/overview) | **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](/services/omvs/tex/overview) | **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. | diff --git a/site/docs/types/0/0010-Base-Model.md b/site/docs/types/0/0010-Base-Model.md index 1139aa870c..1fc4e7ee63 100644 --- a/site/docs/types/0/0010-Base-Model.md +++ b/site/docs/types/0/0010-Base-Model.md @@ -82,7 +82,11 @@ The *SampleData* relationship links an *Asset* entity describing a collection of ## Anchors classification -The *Anchors* classification is used internally by the open metadata ecosystem to optimize the lookup of the entity at the root of a cluster of elements that represents a larger object. Currently, there is support for objects uniquely "owned" by an entity to store the GUID of that entity along with its type. +The *Anchors* classification is used internally by the open metadata ecosystem to optimize the lookup of the entity at the root of a cluster of elements that represents a larger object. Currently, there is support for objects uniquely "owned" by an entity to store the GUID of that entity along with its type and domain. + +* *anchorGUID* - unique identifier of the anchor. +* *anchorTypeName* - type name of the anchor. +* *anchorDomainName* - type name of the anchor's domain. This is the super type of the anchor that is one level below *Referenceable*. For example, if the anchor is of type *DataSet*, then the domain is *Asset*. If the anchor does not inherit from Referenceable, then the type of the anchor is used. !!! info "Further information on the use of Anchors" * [Anchor Management](/concepts/anchor). diff --git a/site/docs/types/0/0010-Base-Model.svg b/site/docs/types/0/0010-Base-Model.svg index 0d10931337..67f9d712c3 100644 --- a/site/docs/types/0/0010-Base-Model.svg +++ b/site/docs/types/0/0010-Base-Model.svg @@ -1,4 +1,4 @@ -
0010 - Base Model
0010 - Base Model
«entity»
Referenceable
«entity»...
«entity»
Infrastructure
«entity»...
deployedImplementationType : string
deployedImplementationType : string
qualifiedName : string
additionalProperties : map<string, string>
qualifiedName : string...
«entity»
Asset
«entity»...
name : string
versionIdentifier : string
description : string
name : string...
«entity»
Process
«entity»...
formula : string
formulaType : string
formula : string...
«entity»
DataSet
«entity»...
formula : string
formulaType : string
deployedImplementationType : string
formula : string...
«entity»
OpenMetadataRoot
«entity»...
«classification»
Anchors
«classification»...
anchorGUID : string
anchorTypeName : string
anchorGUID : string...
«classification»
Memento
«classification»...
archiveDate : Date
archiveUser : string
archiveProcess : string
archiveService : string
archiveMethod : string
archiveProperties : map<string, string>
archiveDate : Date...
«relationship»
SampleData
«relationship»...
samplingMethod : string
samplingMethod : string
*
*
*
*
sampleData
sampleData
sourceOfSample
sourceOfSampleText is not SVG - cannot display \ No newline at end of file +
0010 - Base Model
«entity»
Referenceable
«entity»
Infrastructure
deployedImplementationType : string
qualifiedName : string
additionalProperties : map<string, string>
«entity»
Asset
name : string
versionIdentifier : string
description : string
«entity»
Process
formula : string
formulaType : string
«entity»
DataSet
formula : string
formulaType : string
deployedImplementationType : string
«entity»
OpenMetadataRoot

«classification»
Anchors
anchorGUID : string
anchorTypeName : string
anchorDomainName : string
«classification»
Memento
archiveDate : Date
archiveUser : string
archiveProcess : string
archiveService : string
archiveMethod : string
archiveProperties : map<string, string>
«relationship»
SampleData
samplingMethod : string
*
*
sampleData
sourceOfSample
 \ No newline at end of file diff --git a/site/docs/types/0/area-0-basic-types-and-infrastructure.drawio b/site/docs/types/0/area-0-basic-types-and-infrastructure.drawio index 074251ff5a..fc093fec11 100644 --- a/site/docs/types/0/area-0-basic-types-and-infrastructure.drawio +++ b/site/docs/types/0/area-0-basic-types-and-infrastructure.drawio @@ -1,4 +1,4 @@ - + @@ -320,7 +320,7 @@ - + @@ -385,28 +385,28 @@ - + - + - - + + - + - + - + diff --git a/site/docs/types/3/0385-Controlled-Glossary-Development.md b/site/docs/types/3/0385-Controlled-Glossary-Development.md index 5e81050db6..390667ec3a 100644 --- a/site/docs/types/3/0385-Controlled-Glossary-Development.md +++ b/site/docs/types/3/0385-Controlled-Glossary-Development.md @@ -19,7 +19,7 @@ In addition, the following associations are made: Once the updates are complete, they go through a review and approval process. -Once approved, the changes identified in the editing glossary are made to the terms in the live glossary. The [Glossary Workflow OMVS](/services/omvs/glossary-workflow/overview) supports a simple model that updates a glossary term based on the values from another glossary term and this can be used to perform a simple *merging* process. Alternatively, a [Governance Action Process](/concepts/governance-action-process) can perform the merging process. This would run asynchronously to the end user request, which is useful if the editing glossary is large, and it can manage conflicts and organize the subsequent correction and resubmission of the changes through its stewardship support. +Once approved, the changes identified in the editing glossary are made to the terms in the live glossary. The [Glossary Manager OMVS](/services/omvs/glossary-manager/overview) supports a simple model that updates a glossary term based on the values from another glossary term and this can be used to perform a simple *merging* process. Alternatively, a [Governance Action Process](/concepts/governance-action-process) can perform the merging process. This would run asynchronously to the end user request, which is useful if the editing glossary is large, and it can manage conflicts and organize the subsequent correction and resubmission of the changes through its stewardship support. ![UML](0385-Controlled-Glossary-Development.svg) diff --git a/site/docs/user-interfaces/ui-migration-api-styles.svg b/site/docs/user-interfaces/ui-migration-api-styles.svg index 5d83ad554b..53906beaba 100644 --- a/site/docs/user-interfaces/ui-migration-api-styles.svg +++ b/site/docs/user-interfaces/ui-migration-api-styles.svg @@ -1,4 +1,4 @@ -
<uiURLRoot>/api/glossaries/...
<uiURLRoot>/api/glossaries/...
<uiURLRoot>/api/assets/...
<uiURLRoot>/api/assets/...
<uiURLRoot>/api/lineage/...
<uiURLRoot>/api/lineage/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/glossary-author/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/glossary-author/users/{{u...
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-browser/glossaries/....
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-browser/glossaries/....
{{baseURL}}/servers/{{server}}/api/open-metadata/asset-catalog/lineage/....
{{baseURL}}/servers/{{server}}/api/open-metadata/asset-catalog/lineage/....
{{baseURL}}/servers/{{server}}/open-metadata/view-services/dino/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/dino/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/rex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/rex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-workflow/...
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-workflow/...
{{baseURL}}/servers/{{server}}/api/open-metadata/my-profile/...
{{baseURL}}/servers/{{server}}/api/open-metadata/my-profile/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/tex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/tex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/server-author/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/server-author/users/{{use...
The following view services will
follow the URL segments used
by other registered services
in order to retain compatibility
with React UI
The following view services wil...
The following view services
(and all future view services)
will follow this style of URL.
There is no userId passed
and the URL includes the
'/api/' segment which is an industry
standard for public APIs.  
The following view services...
{{baseURL}}/servers/{{server}}/api/open-metadata/project-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/project-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/collection-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/collection-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-inbox/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-inbox/...
URLs currently supported by
the Egeria UI Application
URLs currently supported by...
<uiURLRoot>/api/about
<uiURLRoot>/api/about
<uiURLRoot>/api/public/app/info
<uiURLRoot>/api/public/app/info
<uiURLRoot>/api/token
<uiURLRoot>/api/token
<uiURLRoot>/api/logout
<uiURLRoot>/api/logout
Move support to a new common module called user-security.
Also include the different user directory support (demo/ldap/redis).
Move support to a new common module called user-security....
This new module will be included into into all 3 runtimes:
  • Egeria UI Application
  • OMAG Server
  • OMAG Server Platform
This new module will be included into into all 3 runt...
Egeria UI Application APIs
Egeria UI Application APIsText is not SVG - cannot display \ No newline at end of file +
<uiURLRoot>/api/glossaries/...
<uiURLRoot>/api/glossaries/...
<uiURLRoot>/api/assets/...
<uiURLRoot>/api/assets/...
<uiURLRoot>/api/lineage/...
<uiURLRoot>/api/lineage/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/glossary-author/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/glossary-author/users/{{u...
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-browser/glossaries/....
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-browser/glossaries/....
{{baseURL}}/servers/{{server}}/api/open-metadata/asset-catalog/lineage/....
{{baseURL}}/servers/{{server}}/api/open-metadata/asset-catalog/lineage/....
{{baseURL}}/servers/{{server}}/open-metadata/view-services/dino/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/dino/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/rex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/rex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/glossary-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/my-profile/...
{{baseURL}}/servers/{{server}}/api/open-metadata/my-profile/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/tex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/tex/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/server-author/users/{{user}}/...
{{baseURL}}/servers/{{server}}/open-metadata/view-services/server-author/users/{{use...
The following view services will
follow the URL segments used
by other registered services
in order to retain compatibility
with React UI
The following view services wil...
The following view services
(and all future view services)
will follow this style of URL.
There is no userId passed
and the URL includes the
'/api/' segment which is an industry
standard for public APIs.  
The following view services...
{{baseURL}}/servers/{{server}}/api/open-metadata/project-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/project-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/collection-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/collection-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-manager/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-inbox/...
{{baseURL}}/servers/{{server}}/api/open-metadata/notification-inbox/...
URLs currently supported by
the Egeria UI Application
URLs currently supported by...
<uiURLRoot>/api/about
<uiURLRoot>/api/about
<uiURLRoot>/api/public/app/info
<uiURLRoot>/api/public/app/info
<uiURLRoot>/api/token
<uiURLRoot>/api/token
<uiURLRoot>/api/logout
<uiURLRoot>/api/logout
Move support to a new common module called user-security.
Also include the different user directory support (demo/ldap/redis).
Move support to a new common module called user-security....
This new module will be included into into all 3 runtimes:
  • Egeria UI Application
  • OMAG Server
  • OMAG Server Platform
This new module will be included into into all 3 runt...
Egeria UI Application APIs
Egeria UI Application APIsText is not SVG - cannot display \ No newline at end of file diff --git a/site/mkdocs.yml b/site/mkdocs.yml index 986494d05d..92ba3d3729 100644 --- a/site/mkdocs.yml +++ b/site/mkdocs.yml @@ -555,14 +555,14 @@ nav: - Topic Integrator: services/omis/topic-integrator/overview.md - View Services (OMVS): - Open Metadata View Services: services/omvs/index.md + - Action Author: services/omvs/action-author/overview.md - Asset Catalog: services/omvs/asset-catalog/overview.md - Automated Curation: services/omvs/automated-curation/overview.md - Collection Manager: services/omvs/collection-manager/overview.md - Data Discovery: services/omvs/data-discovery/overview.md - Feedback Manager: services/omvs/feedback-manager/overview.md - Glossary Browser: services/omvs/glossary-browser/overview.md - - Glossary Workflow: services/omvs/glossary-workflow/overview.md - - Governance Author: services/omvs/governance-author/overview.md + - Glossary Manager: services/omvs/glossary-manager/overview.md - My Profile: services/omvs/my-profile/overview.md - Notification Manager: services/omvs/notification-manager/overview.md - Project Manager: services/omvs/project-manager/overview.md @@ -650,6 +650,7 @@ nav: - Audit Log: concepts/audit-log.md - Audit Log Destination Connector: concepts/audit-log-destination-connector.md - Catalog Target: concepts/catalog-target.md + - Catalog Template: concepts/catalog-template.md - Cohort Events: concepts/cohort-events.md - Cohort Member: concepts/cohort-member.md - Cohort Registry: concepts/cohort-registry.md @@ -779,12 +780,14 @@ nav: - Server Name: concepts/server-name.md - Software Capability: concepts/software-capability.md - Software Server Capability: concepts/software-server-capability.md + - Specification: concepts/specification.md - Star Rating: concepts/review.md - Subject Area: concepts/subject-area.md - Survey Report: concepts/survey-report.md - Survey Action Engine: concepts/survey-action-engine.md - Survey Action Service: concepts/survey-action-service.md - Tag: concepts/informal-tag.md + - Template: concepts/template.md - To Do: concepts/to-do.md - Uni-link Relationships: concepts/uni-multi-link.md - Useful Resource: concepts/useful-resource.md diff --git a/site/snippets/admin/configuring-the-view-services.md b/site/snippets/admin/configuring-the-view-services.md index daaa1a44da..c1f6ab2ece 100644 --- a/site/snippets/admin/configuring-the-view-services.md +++ b/site/snippets/admin/configuring-the-view-services.md @@ -47,11 +47,11 @@ To get a description of each of the view services that are supported by an [OMAG }, { "serviceId": 806, - "serviceName": "Glossary Workflow OMVS", + "serviceName": "Glossary Manager OMVS", "serviceDevelopmentStatus": "IN_DEVELOPMENT", - "serviceURLMarker": "glossary-workflow", + "serviceURLMarker": "glossary-manager", "serviceDescription": "Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states.", - "serviceWiki": "https://egeria-project.org/services/omvs/glossary-workflow/overview/" + "serviceWiki": "https://egeria-project.org/services/omvs/glossary-manager/overview/" }, { "serviceId": 807, @@ -260,11 +260,11 @@ It is possible to list the configured view services for a view Server using the }, { "serviceId": 806, - "serviceName": "Glossary Workflow OMVS", + "serviceName": "Glossary Manager OMVS", "serviceDevelopmentStatus": "IN_DEVELOPMENT", - "serviceURLMarker": "glossary-workflow", + "serviceURLMarker": "glossary-manager", "serviceDescription": "Create glossary terms and organize them into categories as part of a controlled workflow process. It supports the editing glossary and multiple states.", - "serviceWiki": "https://egeria-project.org/services/omvs/glossary-workflow/overview/" + "serviceWiki": "https://egeria-project.org/services/omvs/glossary-manager/overview/" }, { "serviceId": 807,