This is the first monthly report from the Egeria community. It is an idea that came out of the recent quarterly face-to-face meeting. Up to this point, we published release notes for each release of the core egeria repository - which occurred about once a month. If you have been watching the project, however, you will have noticed that we have been splitting our work across multiple git repositories that each have their own release schedule. With so much interesting work going on in these new repositories, it seemed appropriate that our monthly report should evolve to cover the activity of these repositories too.
Quarterly face-to-face meeting¶
This month we held a face-to-face meeting at IBM's Hursley Park. The discussions lead to this monthly newsletter and included exciting news about the new combined UI platform for Egeria.
The Linux Foundation (LF) has been encouraging its projects to focus on the terminology to ensure it is inclusive. Part of this initiative is to rename the default branch from master to main. October 2022 was the month that we completed our rename. If you have forks of our repositories, you may see messages on GitHub informing you of the change. Follow the suggested instructions and your forks/clones will be updated to work with the new default branch.
The demo users for the Egeria UI have been updated. The admin user account is now for "Generic Admin" rather than "James Bond". Also, Erin Overview and Peter Profile now have admin access which means they have access to all features of the UI including the Repository Explorer and the Type Explorer.
The Open Metadata and Governance APIs for core Egeria now support API Tokens. They are added to thread local storage when a REST API request is received by the OMAG Server Platform and can be inspected by the Server Metadata Security Connector. When Egeria makes an outbound REST call, and APITokens are propagated with the request.
Egeria's data product support is progressing well. New types based around Digital Services and Solution Components have been added to the Open Metadata Types. These types represent the business aspects of data products and link to the Assets that implement them.
Congratulations to Dan Wolfson who becomes our latest contributor.
The Core Egeria technology is located in the egeria.git repository. It provides the OMAG Server Platform, java clients for the OMAG Servers that run on the OMAG Server Platform along with the Conformance Test Suite (CTS).
Core Egeria Releases
The database support for the Data Manager OMAS REST API has had a major refactor to improve its consistency with other parts of the REST API and to allow databases to be catalogued in the Local Cohort metadata collections.
The next run of an Egeria Dojo will be the new Metadata Governance Dojo on Monday 21st November 2022.
Over the last few community meetings we have reviewed the Egeria education curriculum from Pragmatic Data Research, and a new Open Metadata Lab that demonstrates the workings of an Open Metadata Repository Cohort.
Last month, the Egeria community gave two presentations at the European Open Source Summit in Dublin.
- Building an Open Metadata and Governance Ecosystem - An overview and demo of Egeria
- Truly Open Lineage - covering the integration of the Egeria, Marquez and OpenLineage projects.
New documentation pages¶
Each month we will select a some new pages that where added/updated in the last month to https://egeria-project.org so you can keep up-to-date with how it is evolving.
Also notice the new buttons on the homepage https://egeria-project.org/.
There is new postman collect for the Asset Consumer OMAS REST API.
The postman collection for Data Manager OMAS needs updating since the updates to its REST API.
Annual Project Review¶
The Egeria project annual review by the Technical Advisory Board (TAC) of the LF AI and Data foundation is scheduled for 15th December 2022. Please encourage people who work with Egeria to Star each of our repositories on GitHub as we are trying to get our total count to 1000.
Moving to Gradle¶
Our build technology for the Java based projects has used both Maven and Gradle. We plan to move entirely to gradle in the next few months, so you will see:
- Repositories such as egeria-dev-projects.git and egeria-samples.git move from maven to gradle.
- The Egeria Development Dojo will use gradle in the exercises.
The Core Egeria repository has offered both a maven and a gradle option. The maven option will be removed once we are sure the gradle build is able to support the release process.
Connecting with the project¶
Connecting with the project
Go to our community guide to find out how to find out more about the activities of the Egeria project.
Raise an issue or comment below