Latest Release

• The Anchors classification is able to store the type of the anchor as well as its GUID.
• A new classification called RootCollection can be added to a collection entity to indicate that it is the root of collection hierarchy.
• The Collection entity has a new attribute called collectionType that can be used to identify the concept that the collection represents.
• A new supertype called Action has been added to the ToDo and EngineAction.
• The ActionSponsor relationship now links an Action to a Referenceable.
• The ToDo entity has a new attribute called lastReviewTime.
• The EngineAction entity has new attributes called requesterUserId and requestedStartDate.
• A new classification called PersonalProject can be added to a project entity to indicate that it is an informal project that have been created by an individual to help them organize their work.
• A new classification called StudyProject can be added to a project entity to indicate that it is a focused analysis of a topic, person, object or situation.
• New properties called priority, projectHealth and projectPhase has been added to the Project entity to represent the status of the project.
• A new classification called DataScope can be added to a referenceable entity (typically a DataStore or DataSet) to define the scope of the associated data resource in space and time.
• Although not yet implemented in the Engine Host, there are types for a new type of governance engine called the ContextEventEngine and its corresponding governance service called ContextEventService. This new engine is for managing context events, scheduling and associated actions.
• A new entity called a ContextEvent plus associated elements has been added to provide a means to capture significant events that impact users, data, services, etcetera, to be recorded and used to explain why blips occurred in the past, or plan and take action to mitigate against blips in the future.
• There is a new schema extraction relationship called DiscoveredLinkedDataField that can be used to describe associations between data fields. The DataField entity has new attributes to align it more closely with SchemaAttribute.
• There are new lineage relationships called UltimateSource and UltimateDestination can be used to capture the size and edges of an element's lineage graph have been added.
• The GroupedMedia relationship is deprecated in favour of DataContentForDataSet.
• The DataFile type has a attribute called fileExtension. New types that inherit from DataFile have been defined for a wide range of file types: SpreadsheetFile, XMLFile, AudioFile, VideoFile, 3DImageFile, RasterFile, VectorFile, SourceCodeFile, ExecutableFile, ScriptFile, BuildInstructionFile, YAMLFile, PropertiesFile, and ArchiveFile. There is also a new relationship called ArchiveFileContents to identify the contents of an archive file.
• There are new attributes called isCaseSensitive and category for ValidValueDefinition that provides additional information used to match valid values. In addition, there are two new types of valid value relationship: ValidValueAssociation and ConsistentValidValues.
• The ConnectorType entity has a new attribute called deployedImplementationType to allow a connector writer to record the deployed implementation type that the connector works with.
• The Template classification has a new property called versionIdentifier. This model also includes a new relationship called CatalogTemplate to identify a template for a particular type of technology.
• The CatalogTarget relationship has two new properties: configurationProperties and metadataSourceQualifiedName.
• The Topic entity how has a topicName attribute.
• ConsistentValidValue is a new relationship that links valid values that represent different properties, and are typically seen together in the same data item.
• SpecificationPropertyAssignment is a new relationship that links a valid value that represents a type of configurable property with the element that represents the associated implementation.

A new python client called pyegeria for Egeria's administrative, platform and server operational services is available on pypi. It also includes coverage of many of the view services. Future versions will add the metadata highway and governance server operational services.

Integration connectors running in an integration daemon are now each given their own thread to run in so that a busy integration connector does not prevent other integration connectors from running.

It is possible to add placeholders to properties in metadata elements that are used as templates when creating new metadata elements. The replacement values are supplied on the request to create the new element from the template.

The framework services provide common services to the Open Metadata Access Services (OMASs). The Governance Action Framework Service includes a new set of services called the Open Governance Service that provides services to define governance actions such as governance action processes and governance action types, and the initiation of engine actions either directly or via a governance action process or governance action type.

All OMASs now have clients for the Connected Asset Service, Open Metadata Store, Open Governance Service and the Open Integration Service.

The Survey Action Framework (SAF) supports a new type of connector called a survey action service that implements a survey of the contents of a particular digital resource such as a directory (folder) on the filesystem, a database or a file. The results of its analysis are stored in open metadata as a survey report linked off of the asset that describes the surveyed resource. The purpose of the survey report is to help in the initial understanding of a deployed IT landscape to help decide where to focus future effort in cataloguing and governing key resources. They can also be scheduled to run at regular intervals, creating a history of how the digital resource is changing over time.

There are implementations of three survey action services: one for a directory (folder, once for a file and another, more specialised service, for CSV files. There is also a SurveyReport utility to print the resulting report.

The survey action services run in the Engine Host. There is a new Open Metadata Engine Service (OMES) to support survey action services. It is called the Survey Action OMES.

There is a new survey action service that provides a report on the content of an Apache Atlas server. It is called the Apache Atlas Survey Service. This survey action services complements the Apache Atlas Integration Connector that exchanges metadata between the open metadata ecosystem and an Apache Atlas server.

The context for all the Open Metadata Integration Services (OMIS) has been updated to support a file system listener. This means that integration connectors can easily monitor changing files and directories. This can be useful for situations where new information is being exchanged with open metadata using files such as CSV files and spreadsheets.

Action Author OMVS is a new view service for managing the definitions of governance action types and and governance action processes.

Automated Curation OMVS is a new view service that enable the user to set up integration connectors in an integration daemon, run engine actions and governance action processes.

Feedback Manager OMVS is a new view service that supports the management of feedback (comments, likes, informal tags, notelogs and reviews) from users. The feedback support in Glossary Browser OMVS has been removed.

Project Manager OMVS supports the definition and management of projects. Projects can themselves be organized hierarchically.

Collection Manager OMVS supports the organizing and browsing of metadata in collections. Collections can themselves be organized hierarchically. An example of its use is in managing the collections of assets that make up digital products.

Valid Metadata OMVS supports the retrieval and maintenance of valid values for open metadata.

Anchor classifications now include the type name and domain of the anchor entity. This allows the Anchor classification to be used to search for string values in any element that is anchored to a particular type of element.

The original intention with the UIs was to consolidate their backend services onto the OMAG Server Platform/Runtime. Unfortunately, neither UI code based is building and the security scanners are reporting serious CVEs with the JavaScript code bases. There is no-one left in the community that is able to work with the JavaScript and so, for now these UIs have been deprecated. The runtime services that support the UIs have also been deprecated and removed from the runtime build. The code is temporarily still in the repository and will be cleaned up in a future release if no progress is made on the JavaScript code.

Files produced by Egeria supplied connectors now have specific file extensions to help identify them in the file system. Previously they used the file extension for their format 9such as .json.

The developer for a connector can provide information about their connector's implementation in a connector type object that can be retrieved from its connector provider. The Open Connector Framework (OCF) has been extended to allow the connector type to include the deployed implementation type in addition to the type name of the asset subtype that this connector represents. Assets of this type are linked to connection objects via the ConnectionToAsset relationship.

The developer of an integration connector can provide information about the third party technology it exchanges metadata with through catalog target types.

An integration connector's behaviour is controlled through a map of configuration properties passed in the configurationProperties attribute of the integration connector's connection object. It is now possible to override the settings of these properties for each catalog target that the integration connector is processing. These overriding configuration properties are stored in the CatalogTarget relationship's properties. Similarly, the metadata collection that elements catalogued by an integration connector is controlled by the metadataSourceQualifiedName attribute of the RegisteredIntegrationConnector relationship. It is now possible to override the metadata source qualified name for each catalog target that the integration connector is processing. The overriding value is also stored in the CatalogTarget relationship's properties.

The developer of a governance service can provide information about the request types, request parameters and action target types it consumes and produces making it easier for consumers creating governance engine definitions, governance action types and governance action processes to incorporate the governance service into their work.

The OpenMetadataArchive.omarchive (was OpenMetadataArchive.json) now contains reference data for many file types and deployed implementation types. The deployed implementation types include details of Egeria's runtimes and services and how they link together. The deployed implementation types are also linked to details of the connectors that work with the associated technology. This is to assist someone setting up new automated curation and governance activities in the open metadata ecosystem.

The omag-server-platform assembly created during an egeria build now includes script files that exercise Egeria's REST API services using IntelliJ's HTTP Client. These mirror the Postman collections that are also found in the assembly.