diff --git a/site/docs/concepts/audit-log-destination-connector.md b/site/docs/concepts/audit-log-destination-connector.md index 998260a03d..1cf8da62a5 100644 --- a/site/docs/concepts/audit-log-destination-connector.md +++ b/site/docs/concepts/audit-log-destination-connector.md @@ -7,12 +7,13 @@ The audit log destination connector implements a common interface to an audit lo ![Audit Log Destination Connector](/connectors/runtime/audit-log-destination-connector.svg) -An [OMAG Server](/concepts/omag-server) can have [multiple audit log destinations](/guides/admin/configuring-an-integration-daemon/#configure-the-audit-log) configured. This configuration can control which severities of audit log record are sent to each destination. +An [OMAG Server](/concepts/omag-server) can have [multiple audit log destinations](/guides/admin/servers/configuring-an-integration-daemon/#configure-the-audit-log) configured. This configuration can control which severities of audit log record are sent to each destination. The implementation for the audit log destination connector can make further choices about how each log record is processed. The interface for audit log destination connectors is located in the [repository-services-apis](https://github.com/odpi/egeria/tree/main/open-metadata-implementation/repository-services/repository-services-apis/src/main/java/org/odpi/openmetadata/repositoryservices/connectors/stores/auditlogstore) module. The audit log destination connectors implemented by Egeria are described in the [connector catalog](/connectors/#audit-log-destination-connectors). +The audit log destination connectors supplied with Egeria are described in the [Connector Catalog](/connectors/#audit-log-destination-connectors) ---8<-- "snippets/abbr.md" diff --git a/site/docs/concepts/deployed-implementation-type.md b/site/docs/concepts/deployed-implementation-type.md new file mode 100644 index 0000000000..58b3651329 --- /dev/null +++ b/site/docs/concepts/deployed-implementation-type.md @@ -0,0 +1,23 @@ +--- +hide: +- toc +--- + + + + +# Deployed Implementation Type + +A *deployed implementation type* is an entity that describes a type of technology that is deployed in an organization's IT landscape. Its purpose is to describe how technology of this type should be governed and the resources available to do so. For example: + +* An instance of this technology is likely to be catalogued in the open metadata ecosystem using an [asset](/concepts/asset). The deployed implementation type can define the subtype of the asset to use. It is also possible to define a template for creating the asset and associate it with the deployed implementation type. +* The governance action processes, governance services and connectors that support this type of technology can be identified. + + +## File Type + +A *file type* is a type of *deployed implementation type* that describes a type of file. It includes the file extension for the type of file to allow matching of a file's full name to a specific file type. Again the file type links to templates and resources for processing files of this type. + + + +--8<-- "snippets/abbr.md" diff --git a/site/docs/concepts/deployed-implementation-types.drawio b/site/docs/concepts/deployed-implementation-types.drawio new file mode 100644 index 0000000000..94c254ffa4 --- /dev/null +++ b/site/docs/concepts/deployed-implementation-types.drawio @@ -0,0 +1,115 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/site/docs/concepts/integration-group.md b/site/docs/concepts/integration-group.md index 94e7a345f6..e106361ae7 100644 --- a/site/docs/concepts/integration-group.md +++ b/site/docs/concepts/integration-group.md @@ -20,7 +20,7 @@ The integration daemon is configured with a list of qualified names for various Each integration group has a unique name. An *IntegrationGroup* entity with a qualifiedName set to this unique name is created through the [Governance Engine OMAS](/services/omas/governance-engine/overview) API. This API is also used to create and link the integration connector definitions into the integration group. - The [integration group's qualifiedName is configured (/guides/admin/servers/configuring-an-integration-daemon/#configure-dynamic-integration-groups) in the [integration daemon](/concepts/integration-daemon). + The [integration group's qualifiedName is configured](/guides/admin/servers/configuring-an-integration-daemon/#configure-dynamic-integration-groups) in the [integration daemon](/concepts/integration-daemon). The open metadata types for this definition are in model [0464 - Dynamic Integration Groups](/types/4/0464-Dynamic-Integration-Groups) - specifically notice that *IntegrationGroup* and *IntegrationConnector* are linked by the *RegisteredIntegrationConnector* relationship. diff --git a/site/docs/release-notes/4-4.md b/site/docs/release-notes/4-4.md index 6b2f5448b0..41d785bf81 100644 --- a/site/docs/release-notes/4-4.md +++ b/site/docs/release-notes/4-4.md @@ -6,6 +6,7 @@ _**These are DRAFT release notes. The notes will be updated until & when 4.4 is released**_ ??? functional "Open Metadata Types" + * The [*Anchors*](/types/0/0010-Base-Model) classification is able to store the type of the anchor as well as its GUID. * A new classification called [*RootCollection*](/types/0/0021-Collections) can be added to a collection entity to indicate that it is the root of collection hierarchy. * The [*Collection*](/types/0/0021-Collections) entity has a new attribute called *collectionType* that can be used to identify the concept that the collection represents. * A new supertype called [*Action*](/types/1/0137-Actions) has been added to the [*ToDo*](/types/1/0137-Actions) and [*EngineAction*](/types/4/0463-Engine-Actions). diff --git a/site/docs/services/omas/asset-catalog/overview.md b/site/docs/services/omas/asset-catalog/overview.md index 6857e99c31..007e3b8f15 100644 --- a/site/docs/services/omas/asset-catalog/overview.md +++ b/site/docs/services/omas/asset-catalog/overview.md @@ -1,10 +1,15 @@ ---8<-- "snippets/content-status/tech-preview.md" +--8<-- "snippets/content-status/deprecated.md" # Asset Catalog Open Metadata Access Service (OMAS) +The Asset Catalog OMAS is replaced by the [Asset Catalog OMVS](/services/omvs/asset-catalog/overview). + + +## Original Description + The Asset Catalog OMAS provides services to search for data assets including: * data stores diff --git a/site/docs/services/omas/glossary-view/overview.md b/site/docs/services/omas/glossary-view/overview.md index 3d6fff0c03..fac0884101 100644 --- a/site/docs/services/omas/glossary-view/overview.md +++ b/site/docs/services/omas/glossary-view/overview.md @@ -1,10 +1,12 @@ ---8<-- "snippets/content-status/in-development.md" +--8<-- "snippets/content-status/deprecated.md" # Glossary View Open Metadata Access Service (OMAS) The Glossary View OMAS provides APIs for browsing a glossary and its contents. +It is replaced by the [Glossary Browser OMVS](/services/omvs/glossary-browser/overview). + --8<-- "snippets/abbr.md" diff --git a/site/docs/services/omas/index.md b/site/docs/services/omas/index.md index 24239bf929..0481ba1337 100644 --- a/site/docs/services/omas/index.md +++ b/site/docs/services/omas/index.md @@ -8,37 +8,35 @@ hide: # Open Metadata Access Services (OMAS) -The Open Metadata Access Services (OMAS) provide domain-specific services for data tools, engines and platforms to integrate with open metadata. +The Open Metadata Access Services (OMAS) provide domain-specific services for data tools, engines and platforms to integrate with open metadata. They run in a [Metadata Access Server](/concepts/metadata-access-server). The access services are as follows: -| OMAS | Description | -|---|---| -| [Asset Catalog](/services/omas/asset-catalog/overview) | The Asset Catalog OMAS provides search and query capabilities for tools and applications to support an asset catalog function. It supports search requests for assets with specific characteristics and returns summaries of the matching assets, plus methods to allow drill-down into the details of a specific asset to related metadata. | -| [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. | -| [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. | -| [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. | -| [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. | -| [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. | -| [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 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. | -| [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. | -| [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. | -| [Discovery Engine](/services/omas/discovery-engine/overview) | The Discovery Engine OMAS provides an API for a discovery engine to access and store metadata from an open metadata repository (or open metadata repository cohort). | -| [Glossary View](/services/omas/glossary-view/overview) | The Glossary View OMAS provides APIs to browse glossaries and their content. | -| [Governance Engine](/services/omas/governance-engine/overview) | The Governance Engine OMAS provides APIs and events that retrieve and manage metadata for governance engines. Governance engines ensure that the infrastructure supporting the data landscape is operating according to the governance program. For example, the governance engine may be ensuring that individuals and servers only have access to the data they have been authorized to see. | -| [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. | -| [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). | -| [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. | -| [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 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. | -| [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. | +| OMAS | Description | +|----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [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. | +| [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. | +| [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. | +| [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. | +| [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. | +| [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 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. | +| [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. | +| [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. | +| [Discovery Engine](/services/omas/discovery-engine/overview) | The Discovery Engine OMAS provides an API for a discovery engine to access and store metadata from an open metadata repository (or open metadata repository cohort). | +| [Governance Engine](/services/omas/governance-engine/overview) | The Governance Engine OMAS provides APIs and events that retrieve and manage metadata for governance engines. Governance engines ensure that the infrastructure supporting the data landscape is operating according to the governance program. For example, the governance engine may be ensuring that individuals and servers only have access to the data they have been authorized to see. | +| [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. | +| [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). | +| [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. | +| [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 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. | +| [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. | ## Using the OMAS's @@ -47,7 +45,7 @@ The OMAS's run in a [metadata access server](/concepts/metadata-access-server). Each OMAS typically supports a Java API, a topic where it publishes notifications of interest to its callers (called the [OutTopic](/concepts/out-topic)), and a topic where new metadata requests can be posted to the OMAS (called the [InTopic](/concepts/in-topic)). -Internally, the Java client calls the REST API of the server module to allow it to reside in remote servers. This java client is embedded in the [governance servers](/concepts/governance-server) and [view servers](/concepts/view-server). They can also be downloaded and used independently within an application. +Internally, the Java client calls the REST API of the server module to allow it to reside in remote servers. This java client is embedded in the [integration services](/services/omis), [engine services](/services/omes) and [view services](/services/omvs). ## Inside an OMAS diff --git a/site/docs/services/omvs/asset-catalog/overview.md b/site/docs/services/omvs/asset-catalog/overview.md new file mode 100644 index 0000000000..72402e22e6 --- /dev/null +++ b/site/docs/services/omvs/asset-catalog/overview.md @@ -0,0 +1,31 @@ + + + +--8<-- "snippets/content-status/in-development.md" + +# Asset Catalog Open Metadata View Service (OMVS) + +The Asset Catalog OMVS provides services to search for [data resources](/concepts/resource) including: + +* data stores +* event feeds +* APIs +* data sets + +The search locates data resources based on the content of the [asset](/concepts/asset) metadata itself and the metadata that links to it. This includes: + +* glossary terms +* schema elements +* assets +* lineage + +The Asset Catalog REST API supports: + +* the retrieval of assets based on unique identifiers +* the retrieval of asset's relationships and classifications +* the query for related assets and lineage +* the retrieval of assets based on their type +* the retrieval of glossaries and their content + + +--8<-- "snippets/abbr.md" diff --git a/site/docs/services/omvs/automated-curation/overview.md b/site/docs/services/omvs/automated-curation/overview.md new file mode 100644 index 0000000000..d069cde3f4 --- /dev/null +++ b/site/docs/services/omvs/automated-curation/overview.md @@ -0,0 +1,22 @@ +--- +hide: +- toc +--- + + + + +--8<-- "snippets/content-status/in-development.md" + +# Automated Curation Open Metadata View Service (OMVS) + +The Automated Curation OMVS provides services that can be used to set up and monitor the automation services from Egeria: + +* Retrieving information about [deployed_implementation types](/concepts/deployed-implementation-type) with their linked templates and resources. +* Setting up [integration connectors](/concepts/integration-connector) in an [Integration Daemon](/concepts/integration-daemon). +* Setting up [governance engines](/concepts/governance-engine) for an [Engine Host](/concepts/engine-host). +* Setting up [governance action process](/concepts/governance-action-process) definitions +* Initiating governance action processes and [engine actions](/concepts/engine-action). +* Monitor the outcomes of governance action processes and engine actions. + +--8<-- "snippets/abbr.md" diff --git a/site/docs/services/omvs/index.md b/site/docs/services/omvs/index.md index e1785d52ea..e01eb5c4e4 100644 --- a/site/docs/services/omvs/index.md +++ b/site/docs/services/omvs/index.md @@ -9,8 +9,10 @@ The view services are as follows: | OMVS | Summary | Description | |-----------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| +| [Asset Catalog](/services/omvs/asset-catalog/overview) | **Search for assets.** | The Asset Catalog OMVS provides search and query capabilities for tools and applications to support an asset catalog function. It supports search requests for assets with specific characteristics and returns summaries of the matching assets, plus methods to allow drill-down into the details of a specific asset to related metadata. | +| [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. | | [My Profile](/services/omvs/my-profile/overview) | **Locate, retrieve and update information relating to the calling user's profile.** | The My Profile OMVS is for user interfaces supporting a personalized experience. A registered user is able to maintain information about themselves, their roles and their network. | -| [Collection Manager](/services/omvs/collection-manager/overview) | **Locate, retrieve and update collections and their membership.** | The Collection Manager OMVS is for user interfaces supporting the ability to search for and navigate through hierarchies of collections. A registered user is able to maintain the contents of collections and attach specific collections to their profile, project or community. | +| [Automated Curation](/services/omvs/automated-curation/overview) | **Set up and monitor automated harvesting and governance services.** | 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. | | [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. | | [Notification Inbox](/services/omvs/notification-inbox/overview) | **Locate, retrieve and process the notifications for the calling user.** | The Notification Inbox OMVS is for user interfaces supporting personalized notifications to the calling user. A registered user is able to view their notifications, update their status and delete them. | | [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. | diff --git a/site/docs/types/0/0010-Base-Model.md b/site/docs/types/0/0010-Base-Model.md index 753fd9fb7d..f3b7fa0f54 100644 --- a/site/docs/types/0/0010-Base-Model.md +++ b/site/docs/types/0/0010-Base-Model.md @@ -80,7 +80,7 @@ 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. +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. !!! 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 5058398948..0d10931337 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»...
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
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
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 diff --git a/site/docs/types/0/0037-Software-Server-Platforms.svg b/site/docs/types/0/0037-Software-Server-Platforms.svg index bb96399dce..4d3d51de9d 100644 --- a/site/docs/types/0/0037-Software-Server-Platforms.svg +++ b/site/docs/types/0/0037-Software-Server-Platforms.svg @@ -1,4 +1,4 @@ - + -
0037 - Software Server Platforms
0037 - Software Server Platforms
«entity»
SoftwareServerPlatform
«entity»...
deployedImplementationType : string
platformVersion : string
source : string
userId : string
deployedImplementationType : string...
«entity»
ITInfrastructure
«entity»...Text is not SVG - cannot display \ No newline at end of file +
0037 - Software Server Platforms
0037 - Software Server Platforms
«entity»
SoftwareServerPlatform
«entity»...
platformVersion : string
source : string
userId : string
platformVersion : string...
«entity»
ITInfrastructure
«entity»...Text is not SVG - cannot display \ No newline at end of file diff --git a/site/docs/types/0/0040-Software-Servers.svg b/site/docs/types/0/0040-Software-Servers.svg index 80570444bd..31b765d7b4 100644 --- a/site/docs/types/0/0040-Software-Servers.svg +++ b/site/docs/types/0/0040-Software-Servers.svg @@ -1,4 +1,4 @@ - + -
0040 - Software Servers
0040 - Software Servers
«entity»
SoftwareServer
«entity»...
deployedImplementationType : string
serverVersion : string
source : string
userId : string
deployedImplementationType : strin...
«entity»
ITInfrastructure
«entity»...Text is not SVG - cannot display \ No newline at end of file +
0040 - Software Servers
0040 - Software Servers
«entity»
SoftwareServer
«entity»...
serverVersion : string
source : string
userId : string
serverVersion : string...
«entity»
ITInfrastructure
«entity»...Text is not SVG - cannot display \ No newline at end of file diff --git a/site/docs/types/0/0042-Software-Capabilities.svg b/site/docs/types/0/0042-Software-Capabilities.svg index 0caa029900..1dc2317471 100644 --- a/site/docs/types/0/0042-Software-Capabilities.svg +++ b/site/docs/types/0/0042-Software-Capabilities.svg @@ -1,4 +1,4 @@ - + -
0042 - Software Capabilities
0042 - Software Capabilities
«entity»
ITInfrastructure
«entity»...
«relationship»
SupportedSoftwareCapability
«relationship»...
«entity»
SoftwareCapability
«entity»...
name : string
description : string
capabilityType : string
capabilityVersion : string
patchLevel : string
source : string
name : string...
*
*
*
*
capabilities
capabilities
«entity»
Referenceable
«entity»...
deploymentTime : date
deployer : string
deployerTypeName : string
deployerPropertyName ; string
serverCapabilityStatus : OperationalStatus
deploymentTime : date...
hostedByDeployedITInfrastructure
hostedByDeployedITInfrastructure
«entity»
SoftwareServerCapability
«entity»...
«classification»
ProcessingState
«classification»...
syncDatesByKey : map <string, long>
syncDatesByKey : map <string, long>Text is not SVG - cannot display \ No newline at end of file +
0042 - Software Capabilities
0042 - Software Capabilities
«entity»
ITInfrastructure
«entity»...
«relationship»
SupportedSoftwareCapability
«relationship»...
«entity»
SoftwareCapability
«entity»...
name : string
description : string
capabilityType : string
capabilityVersion : string
patchLevel : string
source : string
name : string...
*
*
*
*
capabilities
capabilities
«entity»
Referenceable
«entity»...
deploymentTime : date
deployer : string
deployerTypeName : string
deployerPropertyName ; string
serverCapabilityStatus : OperationalStatus
deploymentTime : date...
hostedByDeployedITInfrastructure
hostedByDeployedITInfrastructure
«entity»
SoftwareServerCapability
«entity»...
deployedImplementationType : string
deployedImplementationType : stringText is not SVG - cannot display \ No newline at end of file diff --git a/site/docs/types/0/area-0-basic-types-and-infrastructure-overview.svg b/site/docs/types/0/area-0-basic-types-and-infrastructure-overview.svg index 32957d6a8b..949d7dbb44 100644 --- a/site/docs/types/0/area-0-basic-types-and-infrastructure-overview.svg +++ b/site/docs/types/0/area-0-basic-types-and-infrastructure-overview.svg @@ -1,4 +1,4 @@ - + -
Area 0 - Base Model and Infrastructure
Area 0 - Base Model and Infrastructure
0012
Search Keywords
0012...
0015
Linked Media Types
0015...
0017
External Identifiers
0017...
0020
Property Facets
0020...
0021
Collections
0021...
0030
Host and Platforms
0030...
0035
Complex Hosts
0035...
0040
Software Servers
0040...
0041
Server Classifications
0041...
0070
Networks and Gateways
0070...
0090
Cloud Platforms and Services
0090...
0050
Applications and
Processes
0050...
0052
Tools
0052...
0055
Data Processing Engines
0055...
0036
Storage
0036...
0042
Software Server Capabilities
0042...
0019
More Information
0019...
0056
Resource Managers
0056...
0010
Base Model
0010...
0011
Managing Referenceables
0011...
0057
Software Services
0057...
0025
Locations
0025...
0026
Endpoints
0026...
0037
Software Server Platforms
0037...
0045
Servers and Assets
0045...
0022
Translations
0022...Text is not SVG - cannot display \ No newline at end of file +
Area 0 - Base Model and Infrastructure
Area 0 - Base Model and Infrastructure
0012
Search Keywords
0012...
0015
Linked Media Types
0015...
0017
External Identifiers
0017...
0020
Property Facets
0020...
0021
Collections
0021...
0030
Operating Platforms
0030...
0035
Complex Hosts
0035...
0040
Software Servers
0040...
0041
Server Classifications
0041...
0070
Networks and Gateways
0070...
0090
Cloud Platforms and Services
0090...
0050
Applications and
Processes
0050...
0052
Tools
0052...
0055
Data Processing Engines
0055...
0036
Storage
0036...
0042
Software Server Capabilities
0042...
0019
More Information
0019...
0056
Resource Managers
0056...
0010
Base Model
0010...
0011
Managing Referenceables
0011...
0057
Software Services
0057...
0025
Locations
0025...
0026
Endpoints
0026...
0037
Software Server Platforms
0037...
0045
Servers and Assets
0045...
0022
Translations
0022...Text is not SVG - cannot display \ 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 167eb00cfb..ac5b015209 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,6 +1,6 @@ - + - + @@ -43,7 +43,7 @@ - + @@ -320,7 +320,7 @@ - + @@ -342,7 +342,7 @@ - + @@ -394,8 +394,8 @@ - - + + @@ -443,7 +443,7 @@ - + @@ -536,281 +536,281 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -820,7 +820,7 @@ - + @@ -913,7 +913,7 @@ - + @@ -1023,7 +1023,7 @@ - + @@ -1119,109 +1119,109 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -1262,43 +1262,43 @@ - + - + - + - + - + - + - + - + - + - + - + @@ -1353,14 +1353,14 @@ - + - + @@ -1437,23 +1437,23 @@ - + - + - + - + @@ -1510,7 +1510,7 @@ - + @@ -1533,236 +1533,236 @@ - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + - + @@ -1827,7 +1827,7 @@ - + @@ -1983,7 +1983,7 @@ - + @@ -2189,8 +2189,8 @@ - - + + @@ -2298,10 +2298,10 @@ - + - + @@ -2369,7 +2369,7 @@ - + @@ -2541,7 +2541,7 @@ - + @@ -2599,7 +2599,7 @@ - + @@ -2612,8 +2612,8 @@ - - + + @@ -2628,7 +2628,7 @@ - + @@ -2644,7 +2644,7 @@ - + @@ -2654,7 +2654,7 @@ - + @@ -2812,7 +2812,7 @@ - + @@ -2867,7 +2867,7 @@ - + @@ -2880,7 +2880,7 @@ - + @@ -2934,7 +2934,7 @@ - + @@ -3024,7 +3024,7 @@ - + @@ -3110,7 +3110,7 @@ - + @@ -3266,7 +3266,7 @@ - + @@ -3429,7 +3429,7 @@ - + @@ -3532,7 +3532,7 @@ - + diff --git a/site/docs/types/2/0207-Deployed-Implementation-Types.md b/site/docs/types/2/0207-Deployed-Implementation-Types.md new file mode 100644 index 0000000000..cf4703d888 --- /dev/null +++ b/site/docs/types/2/0207-Deployed-Implementation-Types.md @@ -0,0 +1,38 @@ + + + +# 0207 Deployed Implementation Types + +A [deployed implementation type](/concepts/deployed-implementation-type) describes a class of technology that is deployed in an organization's IT landscape. It is represented in open metadata to allow defaults for cataloguing, management and governance to be managed for this class of technology. + + +![UML](0207-Deployed-Implementation-Types.svg) + + +## DeployedImplementationType entity + +The *DeployedImplementationType* entity is a [Referenceable](/types/0/0010-Base-Model) that describes a class of technology. Its *displayName* can be used for UI dropdown menus. The *deployedImplementationType* property is the value to use in the property of the same name found in concrete *Asset* entities: + +* [Infrastructure](/types/0/0010-Base-Model) +* [DataSet](/types/0/0010-Base-Model) +* [DataStore](/types/2/0210-Data-Stores) +* [DeployedAPI](/types/2/0212-Deployed-APIs) +* [DeployedSoftwareComponent](/types/2/0215-Software-Components) +* [DataFeed](/types/2/0223-Events-and-Logs) + +In addition, *deployedImplementationType* is found in [*SoftwareServerCapability*](/types/0/0042-Software-Capabilities) entities, [*CloudPlatform*](/types/0/0090-Cloud-Platforms-and-Services) classifications and [*ServerPurpose*](/types/0/0041-Server-Purpose) classifications. + +## FileType entity + +The *FileType* entity is a specialization of *DeployedImplementationType* that captures specifics about different types of files. + +## CatalogTemplate relationship + +The *CatalogTemplate* relationship links a *DeployedImplementationType* entity with a [template](/features/templated-cataloguing/overview) for creating a catalog entry for a [digital resource](/concepts/resource) of this class. + +??? education "Further information" + + [Automated Curation OMVS](/services/omvs/automated-curation/overview) + +--8<-- "snippets/abbr.md" + \ No newline at end of file diff --git a/site/docs/types/2/0207-Deployed-Implementation-Types.svg b/site/docs/types/2/0207-Deployed-Implementation-Types.svg new file mode 100644 index 0000000000..3620bef9e4 --- /dev/null +++ b/site/docs/types/2/0207-Deployed-Implementation-Types.svg @@ -0,0 +1,4 @@ + + + +
0207 - Deployed Implementation Types
0207 - Deployed Implementation Types
«entity»
FileType
«entity»...
«entity»
DeployedImplementationType
«entity»...
«entity»
OpenMetadataRoot
«entity»...
*
*
implementationTypes
implementationTypes
templateForCataloguing
templateForCataloguing
*
*
templateName : string
templateDescription : string
replacementProperties : map<string, string>
templateName : string...
«relationship»
CatalogTemplate
«relationship»...
fileExtension : string
fileExtension : string
displayName : string
deployedImplementationType : string
assetTypeName : string
displayName : string...
«entity»
Referenceable
«entity»...Text is not SVG - cannot display \ No newline at end of file diff --git a/site/docs/types/2/area-2-assets-overview.svg b/site/docs/types/2/area-2-assets-overview.svg index 7572e53080..7a8b920d82 100644 --- a/site/docs/types/2/area-2-assets-overview.svg +++ b/site/docs/types/2/area-2-assets-overview.svg @@ -1,3 +1,4 @@ + -
Area 2 - Assets
Area 2 - Assets
0201
Connectors and Connections
0201...
0205
Connection Linkage
0205...
0215
Software Components
0215...
0217
Ports
0217...
0210
DataStores
0210...
0212
Deployed APIs
0212...
0221
Document Stores
0221...
0225
Metadata Repositories
0225...
0227
Keystores
0227...
0222
Graph Stores
0222...
0223
Events and Logs
0223...
0230
Code Tables
0230...
0235
Information Views
0235...
0224
Databases
0224...
0220
Files and Folders
0220...
0239
Reports
0239...
0265
Analytics Assets
0265...
0270
IoT Assets
0270...
0280
Software Development Assets
0280...
0260
Transformations
0260...
0281
Software Components and Modules
0281...
0282
Released Software Components
0282...
0285
Analytics Development
0285...Viewer does not support full SVG 1.1 \ No newline at end of file +
Area 2 - Assets
Area 2 - Assets
0201
Connectors and Connections
0201...
0205
Connection Linkage
0205...
0215
Software Components
0215...
0217
Ports
0217...
0210
DataStores
0210...
0212
Deployed APIs
0212...
0221
Document Stores
0221...
0225
Metadata Repositories
0225...
0227
Keystores
0227...
0222
Graph Stores
0222...
0223
Events and Logs
0223...
0230
Code Tables
0230...
0235
Information Views
0235...
0224
Databases
0224...
0220
Files and Folders
0220...
0239
Reports
0239...
0265
Analytics Assets
0265...
0270
IoT Assets
0270...
0280
Software Development Assets
0280...
0260
Transformations
0260...
0281
Software Components and Modules
0281...
0282
Released Software Components
0282...
0285
Analytics Development
0285...
0207
Deployed Implementation Types
0207...Text is not SVG - cannot display \ No newline at end of file diff --git a/site/docs/types/2/area-2-assets.drawio b/site/docs/types/2/area-2-assets.drawio index 096f16e7d3..41be2efded 100644 --- a/site/docs/types/2/area-2-assets.drawio +++ b/site/docs/types/2/area-2-assets.drawio @@ -1,6 +1,6 @@ - + - + @@ -148,11 +148,17 @@ + + + + + + - + @@ -440,7 +446,7 @@ - + @@ -537,8 +543,79 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + - + @@ -602,22 +679,22 @@ - + - + - + - + - + diff --git a/site/docs/types/2/index.md b/site/docs/types/2/index.md index 273aadf1f2..a89275891d 100644 --- a/site/docs/types/2/index.md +++ b/site/docs/types/2/index.md @@ -26,6 +26,7 @@ get access to the data assets. * **[0201 Connectors and Connections](0201-Connectors-and-Connections.md)** * **[0205 Connection Linkage](0205-Connection-Linkage.md)** +* **[0207 Deployed Implementation Types](0207-Deployed-Implementation-Types.md)** * **[0210 Data Stores](0210-Data-Stores.md)** * **[0212 Deployed APIs](0212-Deployed-APIs.md)** * **[0215 Software Components](0215-Software-Components.md)** diff --git a/site/docs/types/3/0380-Spine-Objects.md b/site/docs/types/3/0380-Spine-Objects.md index a6c2f10510..1059050d6b 100644 --- a/site/docs/types/3/0380-Spine-Objects.md +++ b/site/docs/types/3/0380-Spine-Objects.md @@ -25,10 +25,13 @@ describe spine object. Note that a term may be a spine object and/or a spine attribute and/or an object identifier at the same time. * **TermHASARelationship** - is a term relationship between a term representing a SpineObject and a term representing a SpineAttribute. -* **IsATypeOfRelationship** - is a term relationship between two SpineObjects saying that one is the subtype (specialisation) of the other. +* **TermISATYPEOFRelationship** - is a term relationship between two SpineObjects saying that one is the subtype (specialisation) of the other. * **TermTYPEDBYRelationship** - is a term relationship between a SpineAttribute and a SpineObject to say that the SpineAttribute is implemented using a type represented by the **SpineObject**. -The following relationship is deprecated, use IsATypeOfRelationship instead: -* **TermISATYPEOFRelationship** - Deprecated is a term relationship between two SpineObjects saying that one is the subtype (specialisation) of the other. +??? deprecated "Deprecated types" + The following relationships are deprecated, use TermISATYPEOFRelationship instead: + + * **TermISATYPEOfRelationship** - Deprecated to replace with relationship with the ends reversed. + * **IsATypeOfRelationship** - Deprecated to create consistent capitalization. --8<-- "snippets/abbr.md" \ No newline at end of file diff --git a/site/docs/types/3/0380-Spine-Objects.svg b/site/docs/types/3/0380-Spine-Objects.svg index bd18674ec8..332c2b5c09 100644 --- a/site/docs/types/3/0380-Spine-Objects.svg +++ b/site/docs/types/3/0380-Spine-Objects.svg @@ -1,4 +1,4 @@ - + -
0380 - Spine Objects
0380 - Spine Objects
«classification»
ObjectIdentifier
«classification»...
«entity»
GlossaryTerm
«entity»...
«classification»
SpineAttribute
«classification»...
«classification»
SpineObject
«classification»...
«entity»
GlossaryTerm
«entity»...
description : string
status : TermRelationshipStatus
steward : string
source : string
description : string...
«relationship»
TermHASARelationship
«relationship»...
«entity»
GlossaryTerm
«entity»...
objects
objects
attributes
attributes
*
*
*
*
«entity»
GlossaryTerm
«entity»...
description : string
status : TermRelationshipStatus
steward : string
source : string
description : string...
«relationship»
IsATypeOfRelationship
«relationship»...
«entity»
GlossaryTerm
«entity»...
inheritedFrom
inheritedFrom
inherited
inherited
*
*
*
*
«entity»
GlossaryTerm
«entity»...
description : string
status : TermRelationshipStatus
steward : string
source : string
description : string...
«relationship»
TermTYPEDBYRelationship
«relationship»...
«entity»
GlossaryTerm
«entity»...
attributesTypedBy
attributesTypedBy
types
types
*
*
*
*Text is not SVG - cannot display \ No newline at end of file +
0380 - Spine Objects
0380 - Spine Objects
«classification»
ObjectIdentifier
«classification»...
«entity»
GlossaryTerm
«entity»...
«classification»
SpineAttribute
«classification»...
«classification»
SpineObject
«classification»...
«entity»
GlossaryTerm
«entity»...
description : string
status : TermRelationshipStatus
steward : string
source : string
description : string...
«relationship»
TermHASARelationship
«relationship»...
«entity»
GlossaryTerm
«entity»...
objects
objects
attributes
attributes
*
*
*
*
«entity»
GlossaryTerm
«entity»...
description : string
status : TermRelationshipStatus
steward : string
source : string
description : string...
«relationship»
TermISATYPEOFRelationship
«relationship»...
«entity»
GlossaryTerm
«entity»...
inheritedFrom
inheritedFrom
inherited
inherited
*
*
*
*
«entity»
GlossaryTerm
«entity»...
description : string
status : TermRelationshipStatus
steward : string
source : string
description : string...
«relationship»
TermTYPEDBYRelationship
«relationship»...
«entity»
GlossaryTerm
«entity»...
attributesTypedBy
attributesTypedBy
types
types
*
*
*
*Text is not SVG - cannot display \ No newline at end of file diff --git a/site/docs/types/3/area-3-glossary.drawio b/site/docs/types/3/area-3-glossary.drawio index a9af95a315..e90ca16e7f 100644 --- a/site/docs/types/3/area-3-glossary.drawio +++ b/site/docs/types/3/area-3-glossary.drawio @@ -1,6 +1,6 @@ - + - + @@ -544,7 +544,7 @@ - + @@ -929,7 +929,7 @@ - + @@ -1012,7 +1012,7 @@ - + diff --git a/site/docs/types/4/0440-Organizational-Controls.svg b/site/docs/types/4/0440-Organizational-Controls.svg index 4b1e6f0993..5734bcbd3f 100644 --- a/site/docs/types/4/0440-Organizational-Controls.svg +++ b/site/docs/types/4/0440-Organizational-Controls.svg @@ -1,4 +1,4 @@ - + -
0440 - Organizational Controls
0440 - Organizational Controls
«entity»
Referenceable
«entity»...
«entity»
BusinessCapability
«entity»...
*
*
«relationship»
OrganizationalCapability
«relationship»...
scope : string
scope : string
supportedBusinessCapabilities
supportedBusinessCapa...
supportingTeams
supportingTeams
*
*
identifier : string
displayName : string
description : string
businessCapabilityType : BusinessCapabilityType
identifier : string...
«entity»
GovernanceControl
«entity»...
«entity»
GovernanceResponsibility
«entity»...
«classification»
AssetOrigin
«classification»...
«entity»
Asset
«entity»...
organization : string
organizationPropertyName
businessCapability : string
businessCapabilityPropertyName : string
otherOriginValues : map<string, string>
organization : string...
«entity»
Organization
«entity»...
«entity»
Team
«entity»...
«entity»
GovernanceProcedure
«entity»...
«enumeration»
BusinessCapabilityType
«enumeration»...
UNCLASSIFIED = 0
BUSINESS_SERVICE = 1
BUSINESS_AREA = 2
OTHER = 99
UNCLASSIFIED = 0...
«entity»
OrganizationalControl
«entity»...Text is not SVG - cannot display \ No newline at end of file +
0440 - Organizational Controls
0440 - Organizational Controls
«entity»
Referenceable
«entity»...
«entity»
BusinessCapability
«entity»...
*
*
«relationship»
OrganizationalCapability
«relationship»...
scope : string
scope : string
supportedBusinessCapabilities
supportedBusinessCapa...
supportingTeams
supportingTeams
*
*
identifier : string
displayName : string
description : string
businessCapabilityType : BusinessCapabilityType
businessImplementationType : string
identifier : string...
«entity»
GovernanceControl
«entity»...
«entity»
GovernanceResponsibility
«entity»...
«classification»
AssetOrigin
«classification»...
«entity»
Asset
«entity»...
organization : string
organizationPropertyName
businessCapability : string
businessCapabilityPropertyName : string
otherOriginValues : map<string, string>
organization : string...
«entity»
Organization
«entity»...
«entity»
Team
«entity»...
«entity»
GovernanceProcedure
«entity»...
«enumeration»
BusinessCapabilityType
«enumeration»...
UNCLASSIFIED = 0
BUSINESS_SERVICE = 1
BUSINESS_AREA = 2
OTHER = 99
UNCLASSIFIED = 0...
«entity»
OrganizationalControl
«entity»...Text is not SVG - cannot display \ No newline at end of file diff --git a/site/docs/types/4/area-4-governance.drawio b/site/docs/types/4/area-4-governance.drawio index 08d2f4527e..c7e757d671 100644 --- a/site/docs/types/4/area-4-governance.drawio +++ b/site/docs/types/4/area-4-governance.drawio @@ -1,6 +1,6 @@ - + - + @@ -1426,7 +1426,7 @@ - + @@ -1469,7 +1469,7 @@ - + diff --git a/site/mkdocs.yml b/site/mkdocs.yml index 21d568874e..2a951a71a3 100644 --- a/site/mkdocs.yml +++ b/site/mkdocs.yml @@ -379,6 +379,7 @@ nav: - Area 2 Data Assets: types/2/index.md - Connectors and Connections: types/2/0201-Connectors-and-Connections.md - Connection Linkage: types/2/0205-Connection-Linkage.md + - Deployed Implementation Types: types/2/0207-Deployed-Implementation-Types.md - Data Stores: types/2/0210-Data-Stores.md - Deployed APIs: types/2/0212-Deployed-APIs.md - Software Components: types/2/0215-Software-Components.md @@ -532,7 +533,6 @@ nav: - Registered Services: - Access Services (OMAS): - Open Metadata Access Services: services/omas/index.md - - Asset Catalog OMAS: services/omas/asset-catalog/overview.md - Asset Consumer OMAS: services/omas/asset-consumer/overview.md - Asset Lineage OMAS: services/omas/asset-lineage/overview.md - Asset Manager OMAS: services/omas/asset-manager/overview.md @@ -547,7 +547,6 @@ nav: - Digital Architecture OMAS: services/omas/digital-architecture/overview.md - Digital Service OMAS: services/omas/digital-service/overview.md - Discovery Engine OMAS: services/omas/discovery-engine/overview.md - - Glossary View OMAS: services/omas/glossary-view/overview.md - Governance Engine OMAS: services/omas/governance-engine/overview.md - Governance Program OMAS: services/omas/governance-program/overview.md - IT Infrastructure OMAS: services/omas/it-infrastructure/overview.md @@ -580,9 +579,10 @@ nav: - View Services (OMVS): - Open Metadata View Services: services/omvs/index.md - My Profile: services/omvs/my-profile/overview.md + - Asset Catalog: services/omvs/asset-catalog/overview.md - Collection Manager: services/omvs/collection-manager/overview.md + - Automated Curation: services/omvs/automated-curation/overview.md - Notification Manager: services/omvs/notification-manager/overview.md - - Notification Inbox: services/omvs/notification-inbox/overview.md - Project Manager: services/omvs/project-manager/overview.md - Glossary Author: services/omvs/glossary-author/overview.md - Glossary Browser: services/omvs/glossary-browser/overview.md