From 3b9cabdb06336a5f4e46189a050a5ce01950007c Mon Sep 17 00:00:00 2001 From: Mandy Chessell Date: Wed, 12 Jun 2024 12:12:39 +0100 Subject: [PATCH] June newsletter Signed-off-by: Mandy Chessell --- .../access-services}/data-privacy/overview.md | 0 .../dev-ops/dev-ops-omas.drawio | 0 .../access-services}/dev-ops/overview.md | 0 saved/getting-started-text.md | 16 ++++ site/docs/concepts/index.md | 3 - site/docs/frameworks/saf/annotation-intro.md | 2 +- .../saf/survey-action-pipeline-intro.md | 10 +-- site/docs/guides/community.md | 2 +- .../release-process/egeria-core-release.md | 4 +- .../guides/developer/pyegeria/overview.md | 7 ++ site/docs/patterns/.DS_Store | Bin 6148 -> 0 bytes site/docs/release-notes/5-0.md | 52 +++--------- site/docs/release-notes/egeria-status.drawio | 2 +- site/docs/release-notes/june-2024.md | 77 ++++++++++++++++++ site/docs/services/omas/index.md | 4 +- site/mkdocs.yml | 1 + 16 files changed, 124 insertions(+), 56 deletions(-) rename {site/docs/services/omas => saved/access-services}/data-privacy/overview.md (100%) rename {site/docs/services/omas => saved/access-services}/dev-ops/dev-ops-omas.drawio (100%) rename {site/docs/services/omas => saved/access-services}/dev-ops/overview.md (100%) create mode 100644 saved/getting-started-text.md create mode 100644 site/docs/guides/developer/pyegeria/overview.md delete mode 100644 site/docs/patterns/.DS_Store create mode 100644 site/docs/release-notes/june-2024.md diff --git a/site/docs/services/omas/data-privacy/overview.md b/saved/access-services/data-privacy/overview.md similarity index 100% rename from site/docs/services/omas/data-privacy/overview.md rename to saved/access-services/data-privacy/overview.md diff --git a/site/docs/services/omas/dev-ops/dev-ops-omas.drawio b/saved/access-services/dev-ops/dev-ops-omas.drawio similarity index 100% rename from site/docs/services/omas/dev-ops/dev-ops-omas.drawio rename to saved/access-services/dev-ops/dev-ops-omas.drawio diff --git a/site/docs/services/omas/dev-ops/overview.md b/saved/access-services/dev-ops/overview.md similarity index 100% rename from site/docs/services/omas/dev-ops/overview.md rename to saved/access-services/dev-ops/overview.md diff --git a/saved/getting-started-text.md b/saved/getting-started-text.md new file mode 100644 index 0000000000..1bc127a2b2 --- /dev/null +++ b/saved/getting-started-text.md @@ -0,0 +1,16 @@ + + + + +There are a couple of options available to you: + +**Running Egeria** + +The [Getting Started with Egeria](https://getting-started-with-egeria.pdr-associates.com/introduction.html) blog provides a step-by-step guide to building, installing, configuring and running Egeria on your machine, or in a docker container. + +**Developing with Egeria in IntelliJ** + +See [Setting up IntelliJ to develop components for Egeria](https://egeria-project.org/education/tutorials/developer-intellij-tutorial/overview/). + + + diff --git a/site/docs/concepts/index.md b/site/docs/concepts/index.md index 3ea22de07d..5d4bda1062 100644 --- a/site/docs/concepts/index.md +++ b/site/docs/concepts/index.md @@ -79,14 +79,12 @@ - [Data Domain](/concepts/subject-area) - [Data Manager](/services/omas/data-manager/overview) - [Data Manager OMAS](/services/omas/data-manager/overview) -- [Data Privacy OMAS](/services/omas/data-privacy/overview) - [Data Science OMAS](/services/omas/data-science/overview) - [Database Integrator OMIS](/services/omis/database-integrator/overview) - [Default Zones](/concepts/governance-zone) - [Deployed Implementation Type](/concepts/deployed-implementation-type) - [Design Lineage](/features/lineage-management/overview) - [Design Model OMAS](/services/omas/design-model/overview) -- [DevOps OMAS](/services/omas/dev-ops/overview) - [Digital Architecture OMAS](/services/omas/digital-architecture/overview) - [Digital Product](/concepts/digital-product) - [Digital Resource](/concepts/digital-resource) @@ -351,7 +349,6 @@ - [Security Connector for OMAG Server Platform](/concepts/platform-metadata-security-connector) - [Security Integrator OMIS](/services/omis/security-integrator/overview) - [Security Manager OMAS](/services/omas/security-manager/overview) -- [Security Officer OMAS](/services/omas/security-officer/overview) - [Security Tags](/concepts/security-tags) - [Server Capabilities](/concepts/software-capability) - [Server Chassis](/services/platform-chassis) diff --git a/site/docs/frameworks/saf/annotation-intro.md b/site/docs/frameworks/saf/annotation-intro.md index 6e877942e0..b41946e5f2 100644 --- a/site/docs/frameworks/saf/annotation-intro.md +++ b/site/docs/frameworks/saf/annotation-intro.md @@ -3,7 +3,7 @@ An *annotation* describes one or more related properties about a [digital resource](/concepts/digital-resource). Some annotations refer to the entire digital resource and others refer to a data field within the digital resource. The annotations that describe a single data field are called *data field annotations*. -![Structure of survey reports](/guides/developer/open-discovery-services/survey-report-structure.svg) +![Structure of survey reports](/frameworks/saf/survey-report-structure.svg) The annotation types defined in the [Survey Action Framework (SAF)](/frameworks/saf/overview) are as follows: diff --git a/site/docs/frameworks/saf/survey-action-pipeline-intro.md b/site/docs/frameworks/saf/survey-action-pipeline-intro.md index e3fda51fcc..fc78b8f3bc 100644 --- a/site/docs/frameworks/saf/survey-action-pipeline-intro.md +++ b/site/docs/frameworks/saf/survey-action-pipeline-intro.md @@ -1,13 +1,13 @@ -There is a lot of common functions that are used repeatedly during the discovery process. +There is a lot of common functions that are used repeatedly during the surveying process. -An *open discovery pipeline* is a specialized implementation of an [open discovery service](/concepts/open-discovery-service) that runs a set of open discovery services against a single [digital resource](/concepts/digital-resource). The implementation of the open discovery pipeline determines the order that these open discovery services are run. +A *survey action pipeline* is a specialized implementation of a [survey action service](/concepts/survey-action-service) that runs a set of survey action services against a single [digital resource](/concepts/digital-resource). The implementation of the pipeline determines the order that these services are run. -![Open discovery pipeline example](/guides/developer/open-discovery-services/open-discovery-pipeline-example.svg) +![Survey action pipeline example](/frameworks/saf/survey-action-pipeline-example.svg) -Each open discovery service in the pipeline is able to access the results of the open discovery services that have run before it through the [discovery context](/guides/developer/open-discovery-services/overview/#discovery-context). The combined results of the open discovery pipeline are grouped into a single [discovery analysis report](/concepts/discovery-analysis-report) linked off of the asset. +Each service in the pipeline is able to access the results of the services that have run before it through the [survey context](/frameworks/saf/overview/#survey-context). The combined results of the pipeline are grouped into a single [survey report](/concepts/survey-report) linked off of the asset. -The aim of the open discovery pipeline is to enable reusable open discovery service implementations to be choreographed together for different types of digital resource. +The aim of the survey action pipeline is to enable reusable survey action service implementations to be choreographed together for different types of digital resource. diff --git a/site/docs/guides/community.md b/site/docs/guides/community.md index 4f9acecfc9..2e529fa227 100644 --- a/site/docs/guides/community.md +++ b/site/docs/guides/community.md @@ -9,7 +9,7 @@ This project welcomes contributors from any organization or background, provided ### Live discussions -We have weekly community meeting to which all are welcome. We cover demos, releases, meetups and other activities going on in the community ([agenda and minutes :material-dock-window:](https://wiki.lfaidata.foundation/display/EG/Community+Meetings){ target=wiki }). These calls run January to June, September to November. July, August and December are popular vacation times, and so we stop the calls while the attendance is low. +We have weekly community meeting to which all are welcome. We cover demos, releases, meetups and other activities going on in the community. These calls run January to June, September to November. July, August and December are popular vacation times, and so we stop the calls while the attendance is low. diff --git a/site/docs/guides/contributor/release-process/egeria-core-release.md b/site/docs/guides/contributor/release-process/egeria-core-release.md index 45bd7a9f65..b0518872e1 100644 --- a/site/docs/guides/contributor/release-process/egeria-core-release.md +++ b/site/docs/guides/contributor/release-process/egeria-core-release.md @@ -39,7 +39,7 @@ If an urgent release is required with, for example, a critical security fix, the ??? success "4. Update main from `x.y-SNAPSHOT` to `x.z-SNAPSHOT`" - `git checkout main` - `git pull upstream main` - - Edit all files (command line or IDE) to replace `x.y-SNAPSHOT` with the next version, e.g. change `1.3-SNAPSHOT` to `1.4-SNAPSHOT`. Most of the changes are in `pom.xml` or gradle files, however some code and documentation also has references to our versions and all need modifying. + - Edit all files (command line or IDE) to replace `x.y-SNAPSHOT` with the next version, e.g. change `1.3-SNAPSHOT` to `1.4-SNAPSHOT`. Most of the changes are in gradle files, however some code and documentation also has references to our versions and all need modifying. - If using an IDE like IntelliJ, make sure you have all hits by searching again as [by default only a limited number of hits are shown :material-dock-window:](https://youtrack.jetbrains.com/issue/IDEA-157855){ target=intellij }. - Commit - Create a PR, have reviewed / approved and merged as usual - aim to do this as quickly as reasonable so that there is no potential for version clash @@ -64,7 +64,7 @@ If an urgent release is required with, for example, a critical security fix, the ??? success "7. Create a release in GitHub" - [Create the GitHub release :material-github:](https://github.com/odpi/egeria/releases){ target=gh }. Use `Vx.y` as the tag, and ensure the correct branch is set for the target, i.e. `egeria-release-x.y` - Fill in the release notes using a title of `Release x.y`. Select the option to include automated release notes. The content will need to be trimmed by deleting from the top to the point where the release being worked on appears ie for release 3.8, look for the update to 3.8-SNAPSHOT and cut up until that point. - - Contact the release lead (Nigel Jones) to release the updated maven artifacts (this copies them from the staging repository on oss.sonatype.org to the release repository, which is what is picked up via maven central search) + - Contact the release lead (Mandy Chessell) to release the updated maven artifacts (this copies them from the staging repository on oss.sonatype.org to the release repository, which is what is picked up via maven central search) - Artifacts will be available on Maven Central within minutes, but may take a few hours to appear in searches. - Source archives will be added to the release on GitHub. - this step will also create and publish container images to quay.io and docker.io . diff --git a/site/docs/guides/developer/pyegeria/overview.md b/site/docs/guides/developer/pyegeria/overview.md new file mode 100644 index 0000000000..e619176c0a --- /dev/null +++ b/site/docs/guides/developer/pyegeria/overview.md @@ -0,0 +1,7 @@ + + + +# Python for Egeria (pyegeria) + + +--8<-- "snippets/abbr.md" diff --git a/site/docs/patterns/.DS_Store b/site/docs/patterns/.DS_Store deleted file mode 100644 index 7b29a3009909d36c8c9f09578650ebb017c958c2..0000000000000000000000000000000000000000 GIT binary patch literal 0 HcmV?d00001 literal 6148 zcmeH~KTE?v7{=ezDxn>0b#am)t|A@W)7pYKiTwioYdbWi)IT_85_E8J7ZjWXL03n= zg5Scyui*2(ceV+sG%liYFWf!pn|pG}FS)xO5vlTVyGWELA_s*vlSMTl_&k?H%$Upq zRLM2k)Sx4jb?PKq+k_=x3H&w!Ja!A@W4!XXjgH?_YEcil1L{&|zkS$h20@>1KSlF? zw^(Zh{y?5KyK)N@<<#k#q0yd2uVXbI^<4soe0=1RPxo z=me04z`;mbVc-ZqEM_uMf=vQnT*elfm) zY4F!V!_V)9;Y@8D!!mbylg1MTlB>V3dHRh{?JJ7n;kA0baV{XI`eG2~dAa=i!7m5l z5qP|s+n6&ZxmR;acrv&B%_ zj=XEyc}7F6+D=M(#&t~3%Ir{-nVOX=%}IG$ZEXoy0&xPf`e&Zk|LWKK|G3HivIH!F ze?>rLDz!=(k7U-?#KZAg>!Q?AIJjM?RV=8?ax4eD6fdJl;GD|`P|s+n6&Zy6BOn-T JWeNN!fe#VdyXgP` diff --git a/site/docs/release-notes/5-0.md b/site/docs/release-notes/5-0.md index 10fd3f7ea1..bf8f115109 100644 --- a/site/docs/release-notes/5-0.md +++ b/site/docs/release-notes/5-0.md @@ -10,7 +10,6 @@ Release 5.0 is a major functional release focused on usability, both from the po * *Simplified up and running* - improvements to the OMAG Server Platform and administration services to make it easier to set up and run, plus new sample server configurations that mean you can get Egeria up and running without needing to understand the administration services. * *A python client* - pyegeria provides a python API covering Egeria's administration and operational services plus many of the Open Metadata View Services (OMVSs) provides access to Egeria through this popular programming language for administrators and data professionals. * *Content pack of connector metadata* - metadata to pre-configure the connectors supplied with Egeria, and provide valid value sets describing technology types and file types. -* *UI back-end consolidation* - updates to the view server to allow both Egeria UIs to connect to it whether it is running in the OMAG Server Platform or OMAG Server Runtime. This eliminates the need to run the Egeria UI application. * *Digital Product Support* - new APIs for creating a [digital product catalog](/concepts/digital-product). * *Survey Support* - new framework, services and report utility to support the surveying of digital resources to understand its contents before embarking on wholesale cataloguing and governance. * *Reduction of technical debt* - there has been internal code changes to remove deprecated code, remove the duplication of type information, and many bug fixes :). @@ -139,49 +138,19 @@ Release 5.0 is a major functional release focused on usability, both from the po [Valid Metadata OMVS](/services/omvs/valid-metadata/overview) supports the retrieval and maintenance of valid values for open metadata. ??? functional "Improved anchor support" - Anchor classifications now include the type name 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. + 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. -??? functional "Consolidation of UI Backend Services" - Today there are two approaches to providing the backend services for a UI: - - * The OMAG Server Platform provides a set of view services. These are used by the React UI. - * There is also a set of services in the Egeria UI Application. These are used by the General User UI. - - The issue with this approach is when the same service is needed for both UIs, it has to be implemented twice, one in each runtime. - - There is now a common approach for backend services, centered around the [view server](/concepts/view-server). This can run in the OMAG Server Platform, or the new single server OMAG Server runtime. The Open Metadata View Services (OMVSs) running in the view server will provide all the services for the UIs. To make this possible, new services for token management have been added to the OMAG Server Platform and OMAG Server runtimes. There are also updates to the view services. The change is summarized in the diagram below: - - ![UI API migration](/user-interfaces/ui-migration-api-styles.svg) - - More details of the changes are described below: - - ??? functional "New View Service: Asset Catalog OMVS" - [Asset Catalog OMVS](/services/omvs/asset-catalog/overview) is a new view service that supports the `/assets` and `/lineage` services from Egeria UI Application. There are two versions of each call, one of which is deprecated. The deprecated version exactly matches the API supported by the Egeria UI application, however, it does not manage exceptions in the way expected by an Egeria API. It will remain in place until the existing UI components are updated to support Egeria's standard exception handling. - - ??? functional "Updates to Glossary Browser OMVS" - [Glossary Browser OMVS](/services/omvs/glossary-browser/overview) has been extended to support the `/glossary` services from the Egeria UI application. They are deprecated because they do not support the standard exception handling, but are in place to support existing UI components. Once the UI components have been updated to support the main API then these new services will be removed. - - ??? danger "Changes to view service REST API URLs" - The following Open Metadata View Services (OMVSs) (and all future OMVSs) support the new URL pattern of `{{baseURL}}/servers/{{server}}/api/open-metadata/{{serviceURLRoot}}/...` - - * [Asset Catalog OMVS](/services/omvs/asset-catalog/overview) - * [Automated Curation OMVS](/services/omvs/automated-curation/overview) - * [Collection Manager OMVS](/services/omvs/automated-curation/overview) - * [Glossary Browser OMVS](/services/omvs/glossary-browser/overview) - * [Glossary Manager OMVS](/services/omvs/glossary-manager/overview) - * [My Profile OMVS](/services/omvs/my-profile/overview) - * [Notification Manager OMVS](/services/omvs/notification-manager/overview) - - The following OMVSs will continue to support the original URL pattern of `{{baseURL}}/servers/{{server}}/open-metadata/view-services/{{serviceURLRoot}}/...` until the React UI components are updated to support the new style of URL. - - * [Dynamic Infrastructure and Operations OMVS](/services/omvs/dino/overview) - * [Glossary Author OMVS](/services/omvs/glossary-author/overview) +??? functional "Removal of JavaScript User Interfaces" + 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. ??? deprecated "Deprecation of Egeria UI Application" - Due to the addition of the new View Services and support for tokens in the OMAG Server Platform and OMAG Server runtimes, the Egeria UI Application is now deprecated. New UI components should use the [Open Metadata View Services (OMVS)](/services/omvs). + Due to the addition of the new View Services and support for tokens in the OMAG Server Platform and OMAG Server runtimes, the Egeria UI Application is now deprecated. New UI components should use the [Open Metadata View Services (OMVS)](/services/omvs). The Egeria UI Application assembly, and the open metadata assembly have also been deprecated. + + ??? deprecated "Asset Catalog, OMAS Subject Area OMAS and Glossary View OMAS" + The function of these services has now moved to Glossary Manager OMAS, Glossary Browser OMVS and Asset Catalog OMVS. - ??? deprecated "Asset Catalog OMAS and Glossary View OMAS" - The Glossary View OMAS and Asset Catalog OMAS function has now moved to Glossary Browser OMVS and Asset Catalog OMVS respectively and so Glossary View OMAS and Asset Catalog OMAS are no longer needed. They will remain in the codebase to support the Egeria UI Application and will be removed at the same time as this runtime. + ??? deprecated "Repository Explorer OMVS, Type Explorer OMVS, Dynamic Infrastructure Explorer OMVS, Server Author OMVS, Glossary Author OMVS are now deprecated" + These services have been removed from Egeria's build, but their code is temporariliy still in the Egeria.git repository. ??? functional "New file extensions to Egeria' standard files" 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`. @@ -220,6 +189,9 @@ Release 5.0 is a major functional release focused on usability, both from the po ??? info "Management of open metadata type definitions" As the Egeria code base evolved, sets of definitions for the unique identifiers and type names of the open metadata types appeared in multiple modules. There was a set in the open metadata archive helper, the generic handlers, multiple OMASs and the Governance Action Framework. This was in addition to the original definitions in the open metadata type archive itself. In release 5.0, these copies of the open metadata type identifiers have been consolidated into one set found in the Governance Action Framework. There is still work to change the type definitions in the open metadata type archive to use the definitions from the GAF. This change removes the inconsistencies and gaps in the definitions. It also makes it easier to discover where a particular open metadata type is used. +??? deprecated "Deprecation of Data Engine Proxy and Data Engine OMAS" + These services have been deprecated since they are specialized for IBM's Information Server product. IF support for this product is required in the future then it will be reimplemented in the Integration Daemon. + ??? danger "Removal of the Anonymous Repository Services" The anonymous versions to the OMRS Metadata Collection REST APIs have been removed from Egeria's runtimes since they do not include caller information, and therefore provide opportunities for a denial of service attack. These services were deprecated in version 2 of Egeria. diff --git a/site/docs/release-notes/egeria-status.drawio b/site/docs/release-notes/egeria-status.drawio index 3a6733fc9f..3df43e986d 100644 --- a/site/docs/release-notes/egeria-status.drawio +++ b/site/docs/release-notes/egeria-status.drawio @@ -1,4 +1,4 @@ - + diff --git a/site/docs/release-notes/june-2024.md b/site/docs/release-notes/june-2024.md new file mode 100644 index 0000000000..0852fbabe3 --- /dev/null +++ b/site/docs/release-notes/june-2024.md @@ -0,0 +1,77 @@ + + + +# June 2024 + +Welcome to the Egeria community's June 2024 newsletter. This is our first newsletter this year. Since our [last newsletter](/release-notes/august-2023), the community has been heads down on version 5.0. + +Version 5.0 reflects a shift in Egeria's strategy. Egeria is still essentially an [open metadata exchange and governance](/introduction/overview) capability. However, its initial remit was to supply libraries to vendors to include in their tools products so that these products could exchange metadata with one another. + +The take-up of Egeria by vendors has been slow, but the [challenge of linking the myriad of technologies deployed in many organizations](https://egeria-project.org/introduction/challenge/) is still all to prevalent in organizations, particularly as the use of data and AI grows, along with new regulations, hybrid-cloud deployments and staff turn-over. Therefore, we have shifted our focus to developing and packaging our technology for people that want to use Egeria. Version 5.0 is the first step on that path, with its focus on simplification, and supporting users with the technologies they are most comfortable working with. Most notable for V5.0 is the introduction of `pyegeria` - a comprehensive python package for open metadata and governance. + +The community has also continued to innovate. Whilst it does not aim to replace traditional data catalogs - it is still challenging the traditional approaches to metadata management through its focus on open formats for metadata, metadata distribution, linking metadata with master data and reference data, and using metadata in decision-making. To this end we have introduced a survey framework to help organizations decide which data and systems are valuable enough to add to their metadata catalogs. This aims to speed up the cataloguing process, and avoid having useless content clogging up their metadata catalogs. + +Finally, there is the standard code clean up and enhancements to existing features that is typically for any software release. + +Enjoy ... + +## Survey before catalog + +For organizations starting a data or system cataloguing initiative, the temptation is to "catalog everything" and shift through the results afterwards, using the UI of the metadata catalog. However, metadata ingestion into a catalog can take a lot of time, and results in a bloated catalog where the valuable [assets](/concepts/asset) are lost in a sea of irrelevant content. + +Instead, imaging having a [survey report](/concepts/survey-report) of one of your file systems that gives you an overview of its content, classified by type and use. You then run more detailed survey reports on specific directories, or types of files, helping you to pinpoint where the interesting data is located. The automated cataloguing is directed to this area, rapidly ingesting metadata about the most valuable [digital resources](/concepts/resource) into your catalog. + +Automated cataloguing is ongoing, constantly picking up new resources, as they are created and changed. Surveys are similar. They can be configured to run on a regular schedule, so that they capture a picture of how the resources are changing over time. This is useful for the catalog users and may identify new areas of value in your IT landscape. + +Egeria's new [survey action framework](/frameworks/saf/overview) provides the mechanisms to support pluggable [survey action services](/concepts/survey-action-service) that connect to a specific technology and produces a survey report. In version 5.0 we have developed a variety of survey action services for file systems and PostgreSQL databases as a way to validate the framework. No doubt in future release will include additional survey action services for other types of technology. There is also a SDK for [developing your own survey action services](/guides/developer/survey-action-services/overview/) to plug into Egeria. + +## First-class support for python programmers + +Python is growing in popularity, particularly amongst data professionals. Egeria's runtime is written in Java and provides REST APIs and Java clients that are used for calling Egeria. In release 5.0 we have introduced a set of python libraries for interacting with Egeria called [`pyegeria`](/guides/developer/pyegeria/overview). This is a python library that calls selective Egeria REST APIs. In particular, it supports: + +* The operational services for configuring, starting and stopping servers - and querying their status. +* The [view services](/services/omvs) to work with open metadata and governance services. These services allow you to query and maintain open metadata, and configure and run open governance services such as surveys and automated cataloguing. + +Pyegeria also provides [monitoring widgets](/user-interfaces/python-widgets/overview). + +Pyegeria can be downloaded and installed from [PyPi](https://pypi.org/project/pyegeria/) + + +## Ready to go + +Version 5.0 comes with pre-built configuration for its servers and connectors so you can simply download, build and run Egeria in three easy steps. The pre-built configuration is sufficient to run most of Egeria's features, either as part of an evaluation, or providing your first deployment. This is backed up by a new blog series called [Getting Started with Egeria](https://getting-started-with-egeria.pdr-associates.com/introduction.html). + +There is also a script for building a customized Docker image to make it easy to customize Egeria for your own container-base deployment. + +## Data (Digital) Products + +Egeria has a new REST API called [Collection Manager OMVS](/services/omvs/collection-manager/overview) that supports building a digital product catalog that is organized into a hierarchy of folders. Egeria uses the term [*digital product*](/concepts/digital-product) rather than *data product* because such products can include APIs as well as data collections. + +## Cataloguing earth observation data + +The Earth Observation professional have traditionally organized satellite data as collections of related data sets - just like a digital product. In fact the approach used by earth observation catalogs such as [USGS](https://www.usgs.gov/) and the [Spatio-Temporal Asset Catalog (STAC)](https://stacspec.org/en/) standard was used as input into the design of Egeria's digital product support. + +As a result of working with this type of data, we have extended the [Open Metadata Types](/types) to allow geo-spacial information, such as elevation and a bounded box (bbox), to be attach to a data set description. This is implemented in the [DataScope](/types/2/0210-Data-Stores) classification. + +## Egeria Explorers + +Egeria has a new graphical website for exploring [the open metadata types](https://app.thebrain.com/brain/fd306922-159f-4986-a6bc-111402be51f3/84fc92f5-0aa5-46f4-bb4d-0072f6b2634d). + +This website is built form [the brain](https://www.thebrain.com/) technology. Thank you to [Pragmatic Data Research Ltd](https://pdr-associates.com/) for hosting the website. + +## Full release notes for V5.0 + +The full release notes vor version 5.0 can be found on [Egeria's website](https://egeria-project.org/release-notes/5-0/). + +## Future plans + +Release 5.1 Will continue to build out new [view services](/services/omvs) supported by `pyegeria`, and connectors, such as survey action services, to increase its out-of-the-box connectivity. + +There is also work on a new text-based UI for supporting data professionals in their work. + +## Connecting with the project + +!!! info "Connecting with the project" + Go to our [community guide](/guides/community){target=blank} to find out how to find out more about the activities of the Egeria project. + +--8<-- "snippets/abbr.md" \ No newline at end of file diff --git a/site/docs/services/omas/index.md b/site/docs/services/omas/index.md index 73b7c92ed9..980034fccd 100644 --- a/site/docs/services/omas/index.md +++ b/site/docs/services/omas/index.md @@ -14,16 +14,14 @@ The access services are as follows: | OMAS | Description | Supplies APIs and events to | |----------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------| -| [Asset Consumer](/services/omas/asset-consumer/overview) | The Asset Consumer OMAS is designed for applications that are using [OCF](/frameworks/ocf/overview) connectors to access data stores, APIs and functions such as analytics. The Asset Consumer OMAS provides a factory function for the connectors, the ability to retrieve all of the metadata about the asset and the ability to add feedback on the asset. | [Asset Catalog OMVS](/services/omvs/asset-catalog/overview) | +| [Asset Consumer](/services/omas/asset-consumer/overview) | The Asset Consumer OMAS is designed for applications that are using [OCF](/frameworks/ocf/overview) connectors to access data stores, APIs and functions such as analytics. The Asset Consumer OMAS provides a factory function for the connectors, the ability to retrieve all of the metadata about the asset and the ability to add feedback on the asset. | [Asset Catalog OMVS](/services/omvs/asset-catalog/overview) | | [Asset Lineage](/services/omas/asset-lineage/overview) | The Asset Lineage OMAS listens to relevant lineage related events on the enterprise topic level and publishes these on the Asset Lineage OutTopic, combined with relevant context information on the described entities. These events are listened to by the open lineage services governance server. | [Lineage Warehouse Services](/services/lineage-warehouse-services) | | [Asset Manager](/services/omas/asset-manager/overview) | The Asset Manager OMAS manages the exchange of metadata with third party metadata catalogs and asset managers. It is typically called by the [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview) to send and receive asset information, including schemas, profiles, policies and lineage information with a third party asset manager. Typical examples of asset managers include data catalogs that are managing metadata for a collection of data assets for a data-serving solution. | [Catalog Integrator OMIS](/services/omis/catalog-integrator/overview), [Lineage Integrator OMIS](/services/omis/lineage-integrator/overview), [Glossary Browser OMVS](/services/omvs/glossary-browser/overview), [Glossary Manager OMVS](/services/omvs/glossary-manager/overview), [Feedback Manager OMVS](/services/omvs/feedback-manager/overview) | | [Asset Owner](/services/omas/asset-owner/overview) | The Asset Owner OMAS provides services for an asset owner to curate metadata about their asset(s) and understand how these assets are being used and governed. | [Survey Action OMES](/services/omes/survey-action/overview), [Automated Curation OMVS](/services/omvs/automated-curation/overview) | | [Community Profile](/services/omas/community-profile/overview) | The Community Profile OMAS supports the administration for a community and related user profiles. These communities are involved in reviewing and crowd-sourcing knowledge about the data assets and their use. | [Organization Integrator OMIS](/services/omis/organization-integrator/overview), [My Profile OMVS](/services/omvs/my-profile/overview) | | [Data Manager](/services/omas/data-manager/overview) | The Data Manager OMAS provides an integration point to enable technologies that manage collections of data such as database servers, file systems, file managers and content managers to publish metadata to the metadata repositories about the changing structures and content stored in the data platform. It is typically called from the [Database Integrator OMIS](/services/omis/database-integrator/overview) and [Files Integrator OMIS](/services/omis/files-integrator/overview) integration services. | [API Integrator OMIS](/services/omis/api-integrator/overview), [Database Integrator OMIS](/services/omis/database-integrator/overview), [Display Integrator OMIS](/services/omis/display-integrator/overview), [Files Integrator OMIS](/services/omis/files-integrator/overview), [Topic Integrator OMIS](/services/omis/topic-integrator/overview) | -| [Data Privacy](/services/omas/data-privacy/overview) | The Data Privacy OMAS supports a privacy officer as they manage data privacy in their organization. This includes managing privacy impact assessments and reviews of software services that use personal data as they move through their development, deployment and use. | | | [Data Science](/services/omas/data-science/overview) | The Data Science OMAS provides access to metadata for data assets, connections and projects, plus the ability to maintain metadata about data science notebooks and models and log activity during the analytics development process. It is designed for data science and analytics management tools. | [Analytics Integrator OMIS](/services/omis/analytics-integrator/overview) | | [Design Model](/services/omas/design-model/overview) | The Design Model OMAS provides the ability to manage information from all types of design models. These models may come from tools or be part of a packaged standard. This content is useful for governance, system integration and software development. | | -| [DevOps](/services/omas/dev-ops/overview) | The DevOps OMAS provides services for a DevOps pipeline to query and maintain metadata about systems, processes and software components that are being deployed into the information landscape. | | | [Digital Architecture](/services/omas/digital-architecture/overview) | The Digital Architecture OMAS provides the ability to define information standards, definitions, solution blueprints and models for an organization. It is designed for architecture tools. It is able to support the definition and management of a digital service through concept to deployment. | | | [Digital Service](/services/omas/digital-service/overview) | The Digital Service OMAS provides services for a managing the lifecycle of an Egeria Digital Service. | [Collection Manager OMVS](/services/omvs/collection-manager/overview) | | [Governance Engine](/services/omas/governance-engine/overview) | The Governance Engine OMAS provides APIs and events that retrieve and manage metadata for [governance action services](/concepts/governance-action-service). | [Governance Action OMES](/services/omes/governance-action/overview), [Context Event OMES](/services/omes/context-event/overview) | diff --git a/site/mkdocs.yml b/site/mkdocs.yml index 32a6aafef6..751689dfac 100644 --- a/site/mkdocs.yml +++ b/site/mkdocs.yml @@ -290,6 +290,7 @@ nav: - Releases: - Overview: release-notes/overview.md - Newsletters: + - June 2024: release-notes/june-2024.md - August 2023: release-notes/august-2023.md - April 2023: release-notes/april-2023.md - February 2023: release-notes/february-2023.md