Merge pull request #8218 from mandy-chessell/oak2024

Add new methods for Feedback Manager OMVS

CODEOWNERS

@@ -25,9 +25,7 @@ open-metadata-implementation/access-services/asset-owner/ @mandy-chessell
 open-metadata-implementation/access-services/community-profile/ @mandy-chessell
 open-metadata-implementation/access-services/data-manager/ @mandy-chessell
 open-metadata-implementation/access-services/data-engine/ @popa-raluca @lcpopa
-open-metadata-implementation/access-services/data-privacy/ @mandy-chessell
 open-metadata-implementation/access-services/design-model/ @mandy-chessell
-open-metadata-implementation/access-services/dev-ops/ @mandy-chessell
 open-metadata-implementation/access-services/digital-architecture/ @mandy-chessell
 open-metadata-implementation/access-services/digital-service/ @mandy-chessell
 open-metadata-implementation/access-services/discovery-engine/ @mandy-chessell

Content-Organization.md

@@ -26,10 +26,8 @@ The Egeria core repository contains the core Egeria functionality, and is organi
     * **[community-profile](open-metadata-implementation/access-services/community-profile)** - manage personal profiles and communities.
     * **[data-engine](open-metadata-implementation/access-services/data-engine)** - exchange metadata with a data processing engine.
     * **[data-manager](open-metadata-implementation/access-services/data-manager)** - exchange metadata with a technology that manages collections of data.
-    * **[data-privacy](open-metadata-implementation/access-services/data-privacy)** - support a data privacy officer.
     * **[data-science](open-metadata-implementation/access-services/data-science)** - manage metadata for analytics.
     * **[design-model](open-metadata-implementation/access-services/design-model)** - manage content from design models.
-    * **[dev-ops](open-metadata-implementation/access-services/dev-ops)** - manage metadata for a devOps pipeline.
     * **[digital-architecture](open-metadata-implementation/access-services/digital-architecture)** - support the definition of data standards and models.
     * **[digital-service](open-metadata-implementation/access-services/digital-service)** - manage metadata for a Digital Service.
     * **[discovery-engine](open-metadata-implementation/access-services/discovery-engine)** - manage metadata for metadata discovery services.

open-metadata-distribution/omag-server-platform/build.gradle

@@ -63,8 +63,6 @@ dependencies {
 //    implementation project(':open-metadata-implementation:access-services:data-engine:data-engine-client')
     implementation project(':open-metadata-implementation:access-services:it-infrastructure:it-infrastructure-client')
     implementation project(':open-metadata-implementation:access-services:data-manager:data-manager-client')
-    implementation project(':open-metadata-implementation:access-services:data-privacy:data-privacy-client')
-    implementation project(':open-metadata-implementation:access-services:dev-ops:dev-ops-client')
     implementation project(':open-metadata-implementation:access-services:digital-architecture:digital-architecture-client')
     implementation project(':open-metadata-implementation:access-services:digital-service:digital-service-client')
     implementation project(':open-metadata-implementation:access-services:governance-engine:governance-engine-client')

open-metadata-distribution/open-metadata-assemblies/build.gradle

@@ -71,8 +71,6 @@ dependencies {
     implementation project(':open-metadata-implementation:access-services:data-engine:data-engine-client')
     implementation project(':open-metadata-implementation:access-services:it-infrastructure:it-infrastructure-client')
     implementation project(':open-metadata-implementation:access-services:data-manager:data-manager-client')
-    implementation project(':open-metadata-implementation:access-services:data-privacy:data-privacy-client')
-    implementation project(':open-metadata-implementation:access-services:dev-ops:dev-ops-client')
     implementation project(':open-metadata-implementation:access-services:digital-architecture:digital-architecture-client')
     implementation project(':open-metadata-implementation:access-services:digital-service:digital-service-client')
     implementation project(':open-metadata-implementation:access-services:governance-engine:governance-engine-client')

open-metadata-implementation/access-services/README.md

@@ -63,13 +63,6 @@ It is called from the
 [Topic Integrator OMIS](../integration-services/topic-integrator).
 
 
-* **[data-privacy](data-privacy)** - support a data privacy officer.
-
-  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](data-science)** - manage metadata for analytics.
 
   The Data Science OMAS provides access to metadata for data assets,
@@ -83,11 +76,6 @@ It is designed for data science and analytics management tools.
 These models may come from tools or be part of a packaged standard.
 This content is useful for governance, system integration and software development.
 
-* **[dev-ops](dev-ops)** - manage metadata for a DevOps pipeline.
-
-  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](digital-architecture)** - support the design and architecture of the digital services
 that support the business.