odpi · mandy-chessell · Jun 6, 2024 · Jun 6, 2024 · Jun 6, 2024
diff --git a/saved/README.md b/saved/README.md
@@ -0,0 +1,7 @@
+<!-- SPDX-License-Identifier: CC-BY-4.0 -->
+<!-- Copyright Contributors to the Egeria project. -->
+
+# Saved files
+
+In V5.0 the code when through a simplification and a number of features were removed.  
+This directory contains the documentation from these capabilities in case we need to reinstate any of the modules in the future.
diff --git a/...mas/asset-catalog/egeria-asset-search.png → ...ces/asset-catalog/egeria-asset-search.png b/...mas/asset-catalog/egeria-asset-search.png → ...ces/asset-catalog/egeria-asset-search.png
diff --git a/...mas/asset-catalog/egeria-asset-search.xml → ...ces/asset-catalog/egeria-asset-search.xml b/...mas/asset-catalog/egeria-asset-search.xml → ...ces/asset-catalog/egeria-asset-search.xml
diff --git a/...sset-catalog/get-asset-classifications.md → ...sset-catalog/get-asset-classifications.md b/...sset-catalog/get-asset-classifications.md → ...sset-catalog/get-asset-classifications.md
diff --git a/...s/omas/asset-catalog/get-asset-context.md → ...rvices/asset-catalog/get-asset-context.md b/...s/omas/asset-catalog/get-asset-context.md → ...rvices/asset-catalog/get-asset-context.md
diff --git a/...s/omas/asset-catalog/get-asset-details.md → ...rvices/asset-catalog/get-asset-details.md b/...s/omas/asset-catalog/get-asset-details.md → ...rvices/asset-catalog/get-asset-details.md
diff --git a/.../asset-catalog/get-asset-relationships.md → .../asset-catalog/get-asset-relationships.md b/.../asset-catalog/get-asset-relationships.md → .../asset-catalog/get-asset-relationships.md
diff --git a/.../omas/asset-catalog/get-asset-universe.md → ...vices/asset-catalog/get-asset-universe.md b/.../omas/asset-catalog/get-asset-universe.md → ...vices/asset-catalog/get-asset-universe.md
diff --git a/...omas/asset-catalog/get-supported-types.md → ...ices/asset-catalog/get-supported-types.md b/...omas/asset-catalog/get-supported-types.md → ...ices/asset-catalog/get-supported-types.md
diff --git a/...s/services/omas/asset-catalog/overview.md → ...access-services/asset-catalog/overview.md b/...s/services/omas/asset-catalog/overview.md → ...access-services/asset-catalog/overview.md
@@ -36,7 +36,7 @@ The module structure for the Asset Catalog OMAS is as follows:
 * [asset-catalog-api](asset-catalog-api) supports the common Java classes that are used both by the client and the server.
 * [asset-catalog-server](asset-catalog-server) supports the server side implementation of the access service.
   This includes the
-    * interaction with the [administration services](../../admin-services) for
+    * interaction with the [administration services](../../../site/docs/services/admin-services) for
       registration, configuration, initialization and termination of the access service.
     * interaction with the [repository services](../../repository-services) to work with open metadata from the
       [cohort](https://egeria-project.org/concepts/cohort-member).

diff --git a/...Catalog-endpoints.postman_collection.json → ...Catalog-endpoints.postman_collection.json b/...Catalog-endpoints.postman_collection.json → ...Catalog-endpoints.postman_collection.json
diff --git a/...ocs/services/omas/asset-catalog/search.md → ...d/access-services/asset-catalog/search.md b/...ocs/services/omas/asset-catalog/search.md → ...d/access-services/asset-catalog/search.md
diff --git a/...rvices/omas/data-engine/add-data-flows.md → ...ss-services/data-engine/add-data-flows.md b/...rvices/omas/data-engine/add-data-flows.md → ...ss-services/data-engine/add-data-flows.md
diff --git a/...ices/omas/data-engine/create-data-file.md → ...-services/data-engine/create-data-file.md b/...ices/omas/data-engine/create-data-file.md → ...-services/data-engine/create-data-file.md
diff --git a/...mas/data-engine/create-database-schema.md → ...ces/data-engine/create-database-schema.md b/...mas/data-engine/create-database-schema.md → ...ces/data-engine/create-database-schema.md
diff --git a/...vices/omas/data-engine/create-database.md → ...s-services/data-engine/create-database.md b/...vices/omas/data-engine/create-database.md → ...s-services/data-engine/create-database.md
diff --git a/...ces/omas/data-engine/create-event-type.md → ...services/data-engine/create-event-type.md b/...ces/omas/data-engine/create-event-type.md → ...services/data-engine/create-event-type.md
diff --git a/...data-engine/create-port-implementation.md → ...data-engine/create-port-implementation.md b/...data-engine/create-port-implementation.md → ...data-engine/create-port-implementation.md
diff --git a/...rvices/omas/data-engine/create-process.md → ...ss-services/data-engine/create-process.md b/...rvices/omas/data-engine/create-process.md → ...ss-services/data-engine/create-process.md
diff --git a/...as/data-engine/create-relational-table.md → ...es/data-engine/create-relational-table.md b/...as/data-engine/create-relational-table.md → ...es/data-engine/create-relational-table.md
diff --git a/...es/omas/data-engine/create-schema-type.md → ...ervices/data-engine/create-schema-type.md b/...es/omas/data-engine/create-schema-type.md → ...ervices/data-engine/create-schema-type.md
diff --git a/...services/omas/data-engine/create-topic.md → ...cess-services/data-engine/create-topic.md b/...services/omas/data-engine/create-topic.md → ...cess-services/data-engine/create-topic.md
diff --git a/...cs/services/omas/data-engine/de-client.md → .../access-services/data-engine/de-client.md b/...cs/services/omas/data-engine/de-client.md → .../access-services/data-engine/de-client.md
diff --git a/...ces/omas/data-engine/delete-connection.md → ...services/data-engine/delete-connection.md b/...ces/omas/data-engine/delete-connection.md → ...services/data-engine/delete-connection.md
diff --git a/...ices/omas/data-engine/delete-data-file.md → ...-services/data-engine/delete-data-file.md b/...ices/omas/data-engine/delete-data-file.md → ...-services/data-engine/delete-data-file.md
diff --git a/...mas/data-engine/delete-database-schema.md → ...ces/data-engine/delete-database-schema.md b/...mas/data-engine/delete-database-schema.md → ...ces/data-engine/delete-database-schema.md
diff --git a/...vices/omas/data-engine/delete-database.md → ...s-services/data-engine/delete-database.md b/...vices/omas/data-engine/delete-database.md → ...s-services/data-engine/delete-database.md
diff --git a/...vices/omas/data-engine/delete-endpoint.md → ...s-services/data-engine/delete-endpoint.md b/...vices/omas/data-engine/delete-endpoint.md → ...s-services/data-engine/delete-endpoint.md
diff --git a/...ces/omas/data-engine/delete-event-type.md → ...services/data-engine/delete-event-type.md b/...ces/omas/data-engine/delete-event-type.md → ...services/data-engine/delete-event-type.md
diff --git a/...data-engine/delete-port-implementation.md → ...data-engine/delete-port-implementation.md b/...data-engine/delete-port-implementation.md → ...data-engine/delete-port-implementation.md
diff --git a/...rvices/omas/data-engine/delete-process.md → ...ss-services/data-engine/delete-process.md b/...rvices/omas/data-engine/delete-process.md → ...ss-services/data-engine/delete-process.md
diff --git a/...as/data-engine/delete-relational-table.md → ...es/data-engine/delete-relational-table.md b/...as/data-engine/delete-relational-table.md → ...es/data-engine/delete-relational-table.md
diff --git a/...es/omas/data-engine/delete-schema-type.md → ...ervices/data-engine/delete-schema-type.md b/...es/omas/data-engine/delete-schema-type.md → ...ervices/data-engine/delete-schema-type.md
diff --git a/...services/omas/data-engine/delete-topic.md → ...cess-services/data-engine/delete-topic.md b/...services/omas/data-engine/delete-topic.md → ...cess-services/data-engine/delete-topic.md
diff --git a/.../services/omas/data-engine/find-entity.md → ...ccess-services/data-engine/find-entity.md b/.../services/omas/data-engine/find-entity.md → ...ccess-services/data-engine/find-entity.md
diff --git a/...ata-engine/initial-load-igc-data-stage.md → ...ata-engine/initial-load-igc-data-stage.md b/...ata-engine/initial-load-igc-data-stage.md → ...ata-engine/initial-load-igc-data-stage.md
diff --git a/...s/omas/data-engine/lookup-registration.md → ...rvices/data-engine/lookup-registration.md b/...s/omas/data-engine/lookup-registration.md → ...rvices/data-engine/lookup-registration.md
diff --git a/...ocs/services/omas/data-engine/overview.md → ...d/access-services/data-engine/overview.md b/...ocs/services/omas/data-engine/overview.md → ...d/access-services/data-engine/overview.md
diff --git a/.../data-engine/register-data-engine-tool.md → .../data-engine/register-data-engine-tool.md b/.../data-engine/register-data-engine-tool.md → .../data-engine/register-data-engine-tool.md
diff --git a/...ws_granular_level.postman_collection.json → ...ws_granular_level.postman_collection.json b/...ws_granular_level.postman_collection.json → ...ws_granular_level.postman_collection.json
diff --git a/...e-asset_endpoints.postman_collection.json → ...e-asset_endpoints.postman_collection.json b/...e-asset_endpoints.postman_collection.json → ...e-asset_endpoints.postman_collection.json
diff --git a/...process_endpoints.postman_collection.json → ...process_endpoints.postman_collection.json b/...process_endpoints.postman_collection.json → ...process_endpoints.postman_collection.json
diff --git a/...-lineage_examples.postman_collection.json → ...-lineage_examples.postman_collection.json b/...-lineage_examples.postman_collection.json → ...-lineage_examples.postman_collection.json
diff --git a/...data-engine/samples/collections/README.md → ...data-engine/samples/collections/README.md b/...data-engine/samples/collections/README.md → ...data-engine/samples/collections/README.md
diff --git a/...ntegration-tests.postman_environment.json → ...ntegration-tests.postman_environment.json b/...ntegration-tests.postman_environment.json → ...ntegration-tests.postman_environment.json
diff --git a/...mples/events/DataEngine_delete_events.txt → ...mples/events/DataEngine_delete_events.txt b/...mples/events/DataEngine_delete_events.txt → ...mples/events/DataEngine_delete_events.txt
diff --git a/...mples/events/DataEngine_upsert_events.txt → ...mples/events/DataEngine_upsert_events.txt b/...mples/events/DataEngine_upsert_events.txt → ...mples/events/DataEngine_upsert_events.txt
diff --git a/...omas/data-engine/samples/events/README.md → ...ices/data-engine/samples/events/README.md b/...omas/data-engine/samples/events/README.md → ...ices/data-engine/samples/events/README.md
diff --git a/...ngine/model/LineageObjects-Conceptual.png → ...ngine/model/LineageObjects-Conceptual.png b/...ngine/model/LineageObjects-Conceptual.png → ...ngine/model/LineageObjects-Conceptual.png
diff --git a/...-load/data-engine/model/file_to_table.png → ...-load/data-engine/model/file_to_table.png b/...-load/data-engine/model/file_to_table.png → ...-load/data-engine/model/file_to_table.png
diff --git a/...l-load/data-engine/model/initial_load.png → ...l-load/data-engine/model/initial_load.png b/...l-load/data-engine/model/initial_load.png → ...l-load/data-engine/model/initial_load.png
diff --git a/...s/initial-load/data-stage/01_sequence.png → ...s/initial-load/data-stage/01_sequence.png b/...s/initial-load/data-stage/01_sequence.png → ...s/initial-load/data-stage/01_sequence.png
diff --git a/...mples/initial-load/data-stage/02_jobA.png → ...mples/initial-load/data-stage/02_jobA.png b/...mples/initial-load/data-stage/02_jobA.png → ...mples/initial-load/data-stage/02_jobA.png
diff --git a/...mples/initial-load/data-stage/02_jobB.png → ...mples/initial-load/data-stage/02_jobB.png b/...mples/initial-load/data-stage/02_jobB.png → ...mples/initial-load/data-stage/02_jobB.png
diff --git a/...mples/initial-load/data-stage/02_jobC.png → ...mples/initial-load/data-stage/02_jobC.png b/...mples/initial-load/data-stage/02_jobC.png → ...mples/initial-load/data-stage/02_jobC.png
diff --git a/...data-stage/LineageObjects-Screenshots.png → ...data-stage/LineageObjects-Screenshots.png b/...data-stage/LineageObjects-Screenshots.png → ...data-stage/LineageObjects-Screenshots.png
diff --git a/...ata-stage/LineageObjects-eg DataStage.png → ...ata-stage/LineageObjects-eg DataStage.png b/...ata-stage/LineageObjects-eg DataStage.png → ...ata-stage/LineageObjects-eg DataStage.png
diff --git a/...s/services/omas/glossary-view/overview.md → ...access-services/glossary-view/overview.md b/...s/services/omas/glossary-view/overview.md → ...access-services/glossary-view/overview.md
diff --git a/...ervices/omas/security-officer/overview.md → ...ess-services/security-officer/overview.md b/...ervices/omas/security-officer/overview.md → ...ess-services/security-officer/overview.md
diff --git a/...esign/Subject Area OMAS API proposal.docx → ...esign/Subject Area OMAS API proposal.docx b/...esign/Subject Area OMAS API proposal.docx → ...esign/Subject Area OMAS API proposal.docx
diff --git a/...ct-area/design/Subject Area use cases.png → ...ct-area/design/Subject Area use cases.png b/...ct-area/design/Subject Area use cases.png → ...ct-area/design/Subject Area use cases.png
diff --git a/...ct-area/design/Subject Area use cases.xml → ...ct-area/design/Subject Area use cases.xml b/...ct-area/design/Subject Area use cases.xml → ...ct-area/design/Subject Area use cases.xml
diff --git a/...ject-area/design/brain storming terms.png → ...ject-area/design/brain storming terms.png b/...ject-area/design/brain storming terms.png → ...ject-area/design/brain storming terms.png
diff --git a/...ject-area/design/brain storming terms.xml → ...ject-area/design/brain storming terms.xml b/...ject-area/design/brain storming terms.xml → ...ject-area/design/brain storming terms.xml
diff --git a/...cs/services/omas/subject-area/overview.md → .../access-services/subject-area/overview.md b/...cs/services/omas/subject-area/overview.md → .../access-services/subject-area/overview.md
diff --git a/...configuring-a-data-engine-proxy-server.md → ...configuring-a-data-engine-proxy-server.md b/...configuring-a-data-engine-proxy-server.md → ...configuring-a-data-engine-proxy-server.md
diff --git a/...ocs/services/data-engine-proxy-server.svg → ...engine-proxy/data-engine-proxy-server.svg b/...ocs/services/data-engine-proxy-server.svg → ...engine-proxy/data-engine-proxy-server.svg
diff --git a/...cs/services/data-engine-proxy-services.md → ...ngine-proxy/data-engine-proxy-services.md b/...cs/services/data-engine-proxy-services.md → ...ngine-proxy/data-engine-proxy-services.md
diff --git a/site/docs/concepts/data-engine-proxy.md → saved/data-engine-proxy/data-engine-proxy.md b/site/docs/concepts/data-engine-proxy.md → saved/data-engine-proxy/data-engine-proxy.md
diff --git a/site/docs/concepts/data-engine-proxy.svg → ...d/data-engine-proxy/data-engine-proxy.svg b/site/docs/concepts/data-engine-proxy.svg → ...d/data-engine-proxy/data-engine-proxy.svg
diff --git a/...tors/discovery/discovery-service-intro.md → ...orks/discovery/discovery-service-intro.md b/...tors/discovery/discovery-service-intro.md → ...orks/discovery/discovery-service-intro.md
diff --git a/...onnectors/discovery/discovery-service.svg → ...rameworks/discovery/discovery-service.svg b/...onnectors/discovery/discovery-service.svg → ...rameworks/discovery/discovery-service.svg
diff --git a/...docs/frameworks/odf/discovery-context.svg → saved/frameworks/odf/discovery-context.svg b/...docs/frameworks/odf/discovery-context.svg → saved/frameworks/odf/discovery-context.svg
diff --git a/...docs/frameworks/odf/open-discovery.drawio → saved/frameworks/odf/open-discovery.drawio b/...docs/frameworks/odf/open-discovery.drawio → saved/frameworks/odf/open-discovery.drawio
diff --git a/site/docs/frameworks/odf/overview.md → saved/frameworks/odf/overview.md b/site/docs/frameworks/odf/overview.md → saved/frameworks/odf/overview.md
diff --git a/...rvices/omis/search-integrator/overview.md → ...on-services/search-integrator/overview.md b/...rvices/omis/search-integrator/overview.md → ...on-services/search-integrator/overview.md
diff --git a/site/docs/concepts/presentation-server.md → ...resentation-server/presentation-server.md b/site/docs/concepts/presentation-server.md → ...resentation-server/presentation-server.md
@@ -10,7 +10,7 @@ hide:
 
 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)
+![A presentation server in the open metadata ecosystem](../../site/docs/concepts/view-server.svg)
 
 !!! education "Further information"
     [Setting up the presentation server](/guides/admin/user-interfaces/configuring-the-presentation-server)

diff --git a/.../configure-and-run-presentation-server.md → .../configure-and-run-presentation-server.md b/.../configure-and-run-presentation-server.md → .../configure-and-run-presentation-server.md
diff --git a/...rfaces/ecosystem/ecosystem-ui-planning.md → ...rfaces/ecosystem/ecosystem-ui-planning.md b/...rfaces/ecosystem/ecosystem-ui-planning.md → ...rfaces/ecosystem/ecosystem-ui-planning.md
diff --git a/site/docs/user-interfaces/ecosystem/index.md → saved/user-interfaces/ecosystem/index.md b/site/docs/user-interfaces/ecosystem/index.md → saved/user-interfaces/ecosystem/index.md
diff --git a/...interfaces/ecosystem/ui-components.drawio → ...interfaces/ecosystem/ui-components.drawio b/...interfaces/ecosystem/ui-components.drawio → ...interfaces/ecosystem/ui-components.drawio
diff --git a/...rfaces/ecosystem/ui-components.drawio.svg → ...rfaces/ecosystem/ui-components.drawio.svg b/...rfaces/ecosystem/ui-components.drawio.svg → ...rfaces/ecosystem/ui-components.drawio.svg
diff --git a/...terfaces/general/egeria-ui-about-icon.png → ...terfaces/general/egeria-ui-about-icon.png b/...terfaces/general/egeria-ui-about-icon.png → ...terfaces/general/egeria-ui-about-icon.png
diff --git a/...er-interfaces/general/egeria-ui-about.png → ...er-interfaces/general/egeria-ui-about.png b/...er-interfaces/general/egeria-ui-about.png → ...er-interfaces/general/egeria-ui-about.png
diff --git a/...faces/general/egeria-ui-asset-details.png → ...faces/general/egeria-ui-asset-details.png b/...faces/general/egeria-ui-asset-details.png → ...faces/general/egeria-ui-asset-details.png
diff --git a/...terfaces/general/egeria-ui-asset-list.png → ...terfaces/general/egeria-ui-asset-list.png b/...terfaces/general/egeria-ui-asset-list.png → ...terfaces/general/egeria-ui-asset-list.png
diff --git a/...rfaces/general/egeria-ui-asset-search.png → ...rfaces/general/egeria-ui-asset-search.png b/...rfaces/general/egeria-ui-asset-search.png → ...rfaces/general/egeria-ui-asset-search.png
diff --git a/...general/egeria-ui-glossary-categories.png → ...general/egeria-ui-glossary-categories.png b/...general/egeria-ui-glossary-categories.png → ...general/egeria-ui-glossary-categories.png
diff --git a/...faces/general/egeria-ui-glossary-icon.png → ...faces/general/egeria-ui-glossary-icon.png b/...faces/general/egeria-ui-glossary-icon.png → ...faces/general/egeria-ui-glossary-icon.png
diff --git a/...aces/general/egeria-ui-glossary-terms.png → ...aces/general/egeria-ui-glossary-terms.png b/...aces/general/egeria-ui-glossary-terms.png → ...aces/general/egeria-ui-glossary-terms.png
diff --git a/...interfaces/general/egeria-ui-glossary.png → ...interfaces/general/egeria-ui-glossary.png b/...interfaces/general/egeria-ui-glossary.png → ...interfaces/general/egeria-ui-glossary.png
diff --git a/...ces/general/egeria-ui-include-process.png → ...ces/general/egeria-ui-include-process.png b/...ces/general/egeria-ui-include-process.png → ...ces/general/egeria-ui-include-process.png
diff --git a/...faces/general/egeria-ui-lineage-graph.png → ...faces/general/egeria-ui-lineage-graph.png b/...faces/general/egeria-ui-lineage-graph.png → ...faces/general/egeria-ui-lineage-graph.png
diff --git a/...er-interfaces/general/egeria-ui-login.png → ...er-interfaces/general/egeria-ui-login.png b/...er-interfaces/general/egeria-ui-login.png → ...er-interfaces/general/egeria-ui-login.png
diff --git a/...rfaces/general/egeria-ui-profile-icon.png → ...rfaces/general/egeria-ui-profile-icon.png b/...rfaces/general/egeria-ui-profile-icon.png → ...rfaces/general/egeria-ui-profile-icon.png
diff --git a/...-interfaces/general/egeria-ui-profile.png → ...-interfaces/general/egeria-ui-profile.png b/...-interfaces/general/egeria-ui-profile.png → ...-interfaces/general/egeria-ui-profile.png
diff --git a/.../docs/user-interfaces/general/overview.md → saved/user-interfaces/general/overview.md b/.../docs/user-interfaces/general/overview.md → saved/user-interfaces/general/overview.md
diff --git a/...es/configuring-the-presentation-server.md → ...es/configuring-the-presentation-server.md b/...es/configuring-the-presentation-server.md → ...es/configuring-the-presentation-server.md
diff --git a/site/docs/services/omvs/dino/overview.md → saved/view-services/dino/overview.md b/site/docs/services/omvs/dino/overview.md → saved/view-services/dino/overview.md
diff --git a/...services/omvs/glossary-author/overview.md → ...view-services/glossary-author/overview.md b/...services/omvs/glossary-author/overview.md → ...view-services/glossary-author/overview.md
diff --git a/site/docs/services/omvs/rex/overview.md → saved/view-services/rex/overview.md b/site/docs/services/omvs/rex/overview.md → saved/view-services/rex/overview.md
diff --git a/...s/services/omvs/server-author/overview.md → ...d/view-services/server-author/overview.md b/...s/services/omvs/server-author/overview.md → ...d/view-services/server-author/overview.md
diff --git a/site/docs/services/omvs/tex/overview.md → saved/view-services/tex/overview.md b/site/docs/services/omvs/tex/overview.md → saved/view-services/tex/overview.md
@@ -52,7 +52,6 @@ Some examples:
 
 | OMAS | Description |
 |---|---|
-| [Asset Catalog OMAS](/services/omas/asset-catalog/overview) | provides a search service for locating assets. |
 | [Asset Consumer OMAS](/services/omas/asset-consumer/overview) | provides a service for accessing the content of an asset, extracting additional information that is known about the asset and providing feedback about the asset. It is designed for tools that consume assets to support the work of their users. These users can provide feedback on the asset description and the resource that it describes. |
 | [Asset Manager OMAS](/services/omas/asset-manager/overview) | provides a service for exchanging metadata about assets and related information with a third party [asset manager](/concepts/server-capability). This API supports the many-to-many correlation of identifiers used in the third party asset manager and the open metadata ecosystem. |
 | [Asset Owner OMAS](/services/omas/asset-owner/overview) | provides a service for the owner of an asset to classify and manage the asset, and understand how it is being used by the organization. |

@@ -20,7 +20,6 @@ The table below shows the different types of governance servers and the OMASs th
 |:----------------------------------------------------|:-------------------------------------------------------------------------|:---------------------------------------------------------------------|:-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| 
 | [Integration Daemon](/concepts/integraition-daemon) | Manages the capture of metadata through configured integration services. | [Integration Daemon Services](/services/integration-daemon-services) | [Governance Server OMAS](/services/omas/governance-server/overview) provides support for retrieving governance engine definitions.  The [integration services](../../integration-services) define the OMASs that support each type of integration connector. |
 | [Engine Host](/concepts/engine-host)                | Manages governance engines.                                              | [Engine Host Services](/services/engine-host-services)               | [Governance Server OMAS](/services/omas/governance-server/overview) provides support for retrieving governance engine definitions. The [engine services](../../engine-services) define the OMASs that support each type of governance engine.                |
-| [Data Engine Proxy](/concepts/data-engine-proxy)    | Manages capture of metadata from a data engine.                          | [Data Engine Proxy Services](/services/data-engine-proxy-services)   | [Data Engine OMAS](/services/omas/data-engine/overview)                                                                                                                                                                                                      | 
 | [Lineage Warehouse](/concepts/lineage-warehouse)    | Provides a historic reporting warehouse for lineage.                     | [Lineage Warehouse Services](/services/lineage-warehouse-services)   | [Asset Lineage OMAS](/services/omas/asset-lineage/overview)                                                                                                                                                                                                  | 
 
 

@@ -23,7 +23,6 @@
 
 - [Asset Catalog OMVS](/services/omvs/asset-catalog/overview)
 - [Asset Consumer OMAS](/services/omas/asset-consumer/overview)
-- [Asset Catalog OMAS](/services/omas/asset-catalog/overview)
 - [Asset log Message](/concepts/asset-log-message)
 - [Asset Manager](/concepts/software-capability/#asset-manager)
 - [Asset Manager OMAS](/services/omas/asset-manager/overview)
@@ -78,8 +77,6 @@
 - [Data Connector](/concepts/digital-resource-connector)
 - [Data Discovery OMVS](/services/omvs/data-discovery/overview)
 - [Data Domain](/concepts/subject-area)
-- [Data Engine OMAS](/services/omas/data-engine/overview)
-- [Data Engine Proxy](/concepts/data-engine-proxy)
 - [Data Manager](/services/omas/data-manager/overview)
 - [Data Manager OMAS](/services/omas/data-manager/overview)
 - [Data Privacy OMAS](/services/omas/data-privacy/overview)
@@ -303,7 +300,6 @@
 - [Platform Metadata Security Connector](/concepts/platform-metadata-security-connector)
 - [Platform Security](/features/metadata-security/overview)
 - [Platform URL Root](/concepts/platform-url-root)
-- [Presentation Server](/concepts/presentation-server)
 - [Project](/concepts/project)
 - [Project Manager OMVS](/services/omvs/project-manager/overview)
 - [Project Management OMAS](/services/omas/project-management/overview)
@@ -376,7 +372,6 @@
 - [Stewardship Server](/concepts/engine-host)
 - [Subject Area](/concepts/subject-area)
 - [Subject Area Domain](/concepts/subject-area)
-- [Subject Area OMAS](/services/omas/subject-area/overview)
 - [Subsystem](/concepts/omag-subsystem)
 - [Survey Report](/concepts/survey-report)
 - [Survey Action Engine](/concepts/survey-action-engine)

@@ -45,10 +45,9 @@ The types of OMAG Server are shown in Figure 1. The hierarchy groups similar typ
     - [Repository Proxy](/concepts/repository-proxy) - acts as an open metadata translator for a third party metadata repository. It supports open metadata API calls and translates them to the proprietary APIs of the repository. It also translates events from the proprietary repository into open metadata events that flow over the cohort.
     - [Conformance Test Server](/concepts/conformance-test-server) - validates that a member of the cohort is conforming with the open metadata protocols. This server is typically only seen in development and test cohorts rather than production.
 - [View Server](/concepts/view-server) - manages specialist services for user interfaces.
-- [Governance server](/concepts/governance-server) - supports the use of metadata in the broader IT landscape.
+- [Governance Server](/concepts/governance-server) - supports the use of metadata in the broader IT landscape.
     - [Engine Host](/concepts/engine-host) - provides a runtime for a specific type of [governance engine](/concepts/governance-engine) that runs [governance services](/concepts/governance-service) to monitor, enhance and govern the open metadata ecosystem.
     - [Integration Daemon](/concepts/integration-daemon) - manages the synchronization of metadata with third party technology that can not call the access services directly.   through the [integration services](/services/omis).
-    - [Data Engine Proxy](/concepts/data-engine-proxy) - supports the capture of metadata from a data engine. This includes details of the processing of data that it is doing which is valuable when piecing together lineage.
     - [Lineage Warehouse](/concepts/lineage-warehouse) - Manages the collation of lineage information and maintains it in a format for reporting. This includes the state of the lineage at different points in time.
 
 ## Server connectivity

@@ -35,7 +35,6 @@ The effort required to author and maintain these definitions, plus the governanc
 !!! education "Further information"
 
     - [Governance Program OMAS](/services/omas/governance-program/overview/#subject-areas) provides support for the subject area definition and the ability to retrieve details of a subject area's materials.
-    - [Subject Area OMAS](/services/omas/subject-area/overview) supports the definition of glossary terms for subject areas.
     - [Digital Architecture OMAS](/services/omas/digital-architecture/overview) supports the definition of reference data and quality rules for the subject area.
     - [Asset Manager OMAS](/services/omas/asset-manager/overview) supports the exchange of subject area information with other catalogs and quality tools.
     - [Common Data Definitions](/practices/common-data-definitions/overview) describes the management and use of subject areas.

@@ -10,7 +10,7 @@ hide:
 
 A *view server* is an [OMAG Server](/concepts/view-server) that hosts the REST API services to support a UI. These REST API services are called [Open Metadata View Services (OMVSs)](/services/omvs) and they are designed to support specific display paradigms needed by different types of UIs.
 
-The view services are typically called by the [presentation server](presentation-server.md), but may also be used by third parties. The presentation server hosts the JavaScript that controls the browser display.
+The view services are typically called by third parties.
 
 ![A view server in the open metadata ecosystem](view-server.svg)
 

@@ -6,5 +6,4 @@ The governance daemon connectors contain specialist connectors for the [governan
 * The *Integration Connector* supports the ongoing exchange of metadata between open metadata and a third party technology.  It runs in an [Integration Daemon](/concepts/integraiton-daemon).
 * The *Governance Service* is a connector that runs in a [Governance Engine](/concepts/governance-service) hosted on the [Engine Host](/concepts/engine-host).
 * The *Lineage Warehouse Connector* provides access to a specialist repository for managing lineage information extracted from the open metadata ecosystem.  It runs in a [Lineage Warehouse](/concepts/lineage-warehouse).
-* The *Data Engine Connector* extracts metadata from a data engine.  It has been designed around the needs of IBM's DataStage ETL Engine.  It runs in the [Data Engine Proxy](/concepts/data-engine-proxy).
 
@@ -86,24 +86,18 @@ In the `omag-server-platform` assembly, there is a jar file called `egeria-platf
         ```bash      
            Registered services
               Data Manager OMAS: Capture changes to the data stores and data set managed by a data manager such as a database server, content manager or file system.
-              Subject Area OMAS: Document knowledge about a subject area
-              Glossary View OMAS: Support glossary terms visualization
               Design Model OMAS: Exchange design model content with tools and standard packages
-              Security Officer OMAS: Set up rules and security tags to protect data
               Asset Manager OMAS: Manage metadata from a third party asset manager
               IT Infrastructure OMAS: Manage information about the deployed IT infrastructure
               Data Science OMAS: Create and manage data science definitions and models
               Community Profile OMAS: Define personal profile and collaborate
-              Data Engine OMAS: Exchange process models and lineage with a data engine
-              Discovery Engine OMAS: Support for automated metadata discovery engines
               Digital Architecture OMAS: Design of the digital services for an organization
               Asset Owner OMAS: Manage an asset
               Stewardship Action OMAS: Manage exceptions and actions from open governance
               Governance Program OMAS: Manage the governance program
               Digital Service OMAS: Manage a digital service through its lifecycle
               Asset Lineage OMAS: Store asset lineage
               Asset Consumer OMAS: Access assets through connectors
-              Asset Catalog OMAS: Search and understand your assets
               DevOps OMAS: Manage a DevOps pipeline
               Software Developer OMAS: Interact with software development tools
               Project Management OMAS: Manage governance related projects
@@ -112,26 +106,20 @@ In the `omag-server-platform` assembly, there is a jar file called `egeria-platf
               Security Manager OMAS: Manages exchange of metadata with a security service
               Governance Action OMES: Executes requested governance action services to monitor, assess and maintain metadata and its real-world counterparts.
               Repository Governance OMES: Dynamically governance open metadata repositories in the connected cohorts.
-              Asset Analysis OMES: Analyses the content of an asset's real world counterpart, generates annotations in an open discovery report that is attached to the asset in the open metadata repositories.
+              Survey Action OMES: Analyses the content of an asset's real world counterpart, generates annotations in an open discovery report that is attached to the asset in the open metadata repositories.
               Infrastructure Integrator OMIS: Exchange information relating to IT infrastructure such as hosts, platforms, servers, server capabilities and services.
               Files Integrator OMIS: Extract metadata about files stored in a file system or file manager.
               Topic Integrator OMIS: Exchange metadata with third party event-based brokers.
               Security Integrator OMIS: Distribute security properties to security enforcement points.
               API Integrator OMIS: Exchange metadata with third party API Gateways.
-              Search Integrator OMIS: Store metadata with a third party technology that is focused on search efficiency.
               Lineage Integrator OMIS: Manage capture of lineage from a third party tool.
               Database Integrator OMIS: Extract metadata such as schema, tables and columns from database managers.
               Catalog Integrator OMIS: Exchange metadata with third party data catalogs.
               Display Integrator OMIS: Exchange metadata with applications that display data to users.
               Analytics Integrator OMIS: Exchange metadata with third party analytics tools.
               Organization Integrator OMIS: Load information about the teams and people in an organization and return collaboration activity.
-              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 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.
+              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.
               Glossary Browser OMVS: View glossary terms and categories within a glossary.
         ```
     The registered are also retrieved through the [Platform Services](/services/platform-services/overview){ target=dojo-support } using the `getXXXServices` method as follows: