Open Metadata Archives

The open metadata archives provide pre-canned content (open metadata types and instances) to load into an open metadata repository. There are two main types of open metadata archive:

A metadata server’s configuration document can list the archives to load each time the server is started. This is useful if the server does not retain metadata through a server restart (like the in memory metadata repository). Open metadata archives may also be loaded while the server is running using a REST API call.

POST {server-url-root}/open-metadata/admin-services/users/{userId}/servers/{serverName}/instance/open-metadata-archives/file

With the file name in the request body.

The archive is loaded once and its content is immediately available. If the repository persists metadata over a server restart then this archive content continues to be available after the server restarts.

It does not matter how many times an archive is loaded, only one copy of the content is added to the repository.

Inside an Open Metadata Archive

The open metadata archive has three parts to it. This is shown in Figure 1. The header defines the type of archive and its properties. Then there is the type store. This contains new types and updates to types (patches). Finally there is the instance store. This contains new instances (entities, relationships and classifications).

Figure 1

Figure 1: Inside an Open Metadata Archive

The archive loads in the following order:

Supported utilities for open metadata archives

ODPi Egeria supports the following open metadata archives. Associated with each archive are utilities that help you build additional archives of your own content.


License: CC BY 4.0, Copyright Contributors to the ODPi Egeria project.