Create Asset Manager OMAS and Catalog Integrator OMIS

odpi / egeria

Egeria core

https://egeria-project.org

Apache License 2.0

808 stars 261 forks source link

Create Asset Manager OMAS and Catalog Integrator OMIS #3562

Closed mandy-chessell closed 2 months ago

mandy-chessell commented 4 years ago

This issue covers the creation of a new integration path for metadata catalogs the goes via an integration service hosted in an integration daemon.

Catalogs will be able to have a two-way integration through this path without needing to conform to the repository service rules for managing home and reference copies. This is possible for two reasons:

Since the metadata from the catalog passes through an OMAS, Egeria will be able to have a better control of the metadata from the catalog.
Since the catalog is not part of a federated query, any inconsistent updates to metadata that occurs in its repository, only impacts the users of that catalog and not the whole cohort.

mandy-chessell commented 4 years ago

There are a number of teams waiting for this feature and so it will be delivered in increments:

[x] Glossaries
[x] Assets
[x] Schemas
[x] Connections (including endpoints and connector types)
[x] Infrastructure (applications, platforms etc)
[x] Governance Definitions (policy, rules etc)
[x] Valid values and reference data
[x] Collaboration (comments and other feedback, informal tagging)
[x] Stewardship (todos, tasks, incidents etc)

mandy-chessell commented 4 years ago

The Asset Manager OMAS and Catalog Integrator OMIS need to support identifiers from external asset manager (eg metadata catalog). These external identifiers are present in the APIs of both modules and they are stored in the ExternalId entity - see https://egeria.odpi.org/open-metadata-publication/website/open-metadata-types/0017-External-Identifiers.html

I have extended this entity type with 2 additional attributes:

mappingProperties - to allow the external asset manager's integration connector to add additional values to help it correlate the open metadata versions of its metadata with the contents of its store.
lastVerified - to allow the external asset manager's integration connector to record when it last verified that the open metadata versions are in synch with the external asset manager's store. This helps to verify that the values have not changed since the last synch when updating elements that are not locked read-only using external provenance.

This is the new model: 0017-External-Identifiers

mandy-chessell commented 4 years ago

This picture shows the use of the ExternalId.

external-identifier-mapping

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

mandy-chessell commented 3 years ago

This issue is still in progress since there are sections of the API still to be built

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.