Writing Repository Connectors¶
The repository connector's API is provided by the Open Metadata Repository Services (OMRS). It defines a call interface to create, search, query, update and delete metadata stored in the metadata repository.
You may want to see the OMRS metamodel for more details on the granularity of metadata exchange.
A common tripping point for conformance
The routing behavior described for homed metadata instances can only be enforced when the requests go through OMRS itself. For third party tools that provide their own services / user interface through which updates can be made, a common tripping point becomes the fact that these services / user interfaces need to adhere to the same protocol principles outlined above -- specifically, ensuring reference copies are also immutable through these product-native interfaces -- in order to conform to the Egeria protocol.
For cases where the tool is unable to do so, we are actively investigating other mitigation measures like providing a Smart Repository Proxy to ensure that any changes to metadata that violate the protocol remain isolated in that third party technology and are not inadvertently propagated elsewhere in the cohort.
Consider integrating Catalogs with Asset Manager OMAS
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.
If your catalog is not able to support reference copies, you may want to consider this option