It is possible to add metadata to a metadata repository using no automation beyond the catalog management of the metadata once it is created. Individuals enter information about digital resources and associated intellectual property into Egeria through tools that call Egeria's Open Metadata Access Services (OMASs).
The Asset Owner OMAS is the principle interface for manual cataloguing of digital resources. It is possible to catalog any type of digital resource through this interface, although it is biased towards cataloging data sources such as data stores, data feeds, files, data sets, APIs and events. The digital resources are represented in the catalog as assets.
In addition, there are specific cataloguing interfaces to support particular types of subject-matter experts.
IT Infrastructure OMAS provides specialist interfaces for cataloguing infrastructure such as servers, host systems and applications.
Digital Architecture OMAS provides specialist interfaces for architects and integration engineers to manually catalog reference data sets and processes. Reference data sets are assets in their own right, and their content can be used as classifiers to augment the description of other assets. Processes are also assets that, when linked together, show the lineage of the assets they are partly responsible for maintaining.
Manual cataloguing works well for infrequent cataloguing. However, it is expensive and error-prone when aiming to systematically catalog a digital landscape if it is complex and continually changing.
How does integrated cataloguing work?¶
Integrated cataloging uses an integration daemon to monitor a specific digital technology that hosts particular types of digital resources and then automatically maintains the metadata descriptions of these digital resources in the catalog.
Figure 1: The integration daemon manages the automatic exchange of open metadata between third party technologies and Metadata Access Servers that are sharing this metadata as Open Metadata Repository Cohorts.
For example, an integration daemon may be monitoring a database server, updating the metadata catalog each time a new database is added, or a schema is changed.
Integration connectors support different integration patterns to meet the variety of capabilities of digital technologies. For example, it may poll a system or listen for events from it that indicate changes in the digital resources. They are limited to the metadata supported by the technology they are working with. Typically, the integration connectors are limited to capture
technical metadata that includes the name of the digital resource (stored in the asset) and the structure of the data fields within it (if any). This structure is described in a schema. It may be possible to also extract, or derive the connection information required to connect to the digital resource. This is stores in a connection. The technical metadata can also be augmented by using templated cataloguing.
Integration connectors can also be used to push metadata, or configuration derived from metadata, into a third party technology. For example, this is used in the maintenance of the user directory and synchronizing security tags for access control.
Finally, an integration connector can manage the two-way synchronization between an external asset manager and the open metadata ecosystem.
Other types of automation¶
Below are other types of automation to minimise the effort in managing your asset catalog.
- Templated cataloguing - copies the values from an existing catalogued asset into the catalog entry for a new asset. This can reduce the opportunities for error where similar assets are being catalogued. It can be used both in manual cataloguing and integrated cataloguing.
- Discovery and stewardship - analyses the contents of a digital resource to discover metadata and attach it as annotations to the corresponding asset in the catalog.
Raise an issue or comment below