Egeria provides the Apache 2.0 licensed open metadata and governance type system, frameworks, APIs, event payloads and interchange protocols to enable tools, engines and platforms to exchange metadata in order to get the best value from data whilst ensuring it is properly governed.

• What is Egeria and what does it do?
• Why is this open metadata and governance capability supported by Egeria important?
• Where is the design documentation?
• Where are the open metadata specifications?
• How do I run Egeria?
• How do I contribute to Egeria?
• How do I raise a bug or feature request?
• How do I enhance my product to support open metadata?
• How do I test that a product is compliant with the open metadata standards?

The Egeria content is organized into the following modules:

• developer-resources - contains useful files and documentation for an Egeria developer.
• open-metadata-implementation - implementation of standards, frameworks and connectors.
  • access-services - domain specific APIs known as the Open Metadata Access Services (OMAS).
    • asset-catalog - search for assets.
    • asset-consumer - create connectors to access assets.
    • asset-owner - manage metadata and feedback for owned assets.
    • community-profile - manage personal profiles and communities.
    • connected-asset - provide metadata about assets for the connectors.
    • data-infrastructure - manage metadata about deployed infrastructure.
    • data-platform - exchange metadata with a data platform.
    • data-privacy - support a data privacy officer.
    • data-process - exchange metadata with a data processing engine.
    • data-protection - set up rules to protect data.
    • data-science - manage metadata for analytics.
    • dev-ops - manage metadata for a devOps pipeline.
    • digital-architecture - support the definition of data standards and models.
    • discovery-engine - manage metadata for metadata discovery services.
    • governance-engine - manage metadata for an operational governance engine.
    • governance-program - set up and manage a governance program.
    • information-view - configure and manage metadata for data tools that create virtual views over data - such as business intelligence tools and data virtualization platforms.
    • project-management - manage definitions of projects for metadata management and governance.
    • software-developer - deliver useful metadata to software developers.
    • stewardship-action - manage metadata as part of a data steward's work to improve the data landscape.
    • subject-area - develop a definition of a subject area including glossary terms, reference data and rules.
  • adapters - pluggable component implementations.
    • open-connectors are connectors that support the Open Connector Framework (OCF).
      • connector-configuration-factory creates Connection objects to configure the open connectors.
      • access-services-connectors contains the topic connector implementations for each of the access services that support inbound events through an InTopic.
      • repository-services-connectors contains connector implementations for each type of connector supported by the Open Metadata Repository Services (OMRS).
        • audit-log-connectors supports different destinations for audit log messages.
        • cohort-registry-store-connectors contains connectors that store the cohort membership details used and maintained by the cohort registry.
        • open-metadata-archive-connectors contains connectors that can read and write open metadata archives.
        • open-metadata-collection-store-connectors contains connectors that support mappings to different vendors' metadata repositories.
          • graph-repository-connector - provides a local repository that uses a graph store as its persistence store.
          • inmemory-repository-connector - provides a local repository that is entirely in memory. It is useful for testing/developing OMASs and demos.
          • omrs-rest-repository-connector - uses the OMRS REST API to call an open metadata compliant repository.
      • configuration-store-connectors contains the connectors that manage the open metadata configuration.
      • event-bus-connectors supports different event/messaging infrastructures. They can be plugged into the topic connectors from the access-service-connectors and repository-service-connectors.
      • governance-daemon-connectors contains connectors for the governance daemon servers that monitor activity or synchronize metadata and configuration asynchronously between different tools.
      • data-store-connectors contain OCF connectors to data stores on different data platforms.
    • authentication-plugins support extensions to technology such as LDAP that are used to verify the identity of an individual or service requesting access to data/metadata.
    • governance-engines-plugins support plugins to governance engines to enable them to use open metadata settings in their validation and enforcement decisions, and the resulting actions they take.
  • frameworks - frameworks that support pluggable components.
    • open-connector-framework provides the interfaces and base implementations for components (called connectors) that access data-related assets. OCF connectors also provide detailed metadata about the assets they access.
    • open-discovery-framework provides the interfaces and base implementations for components (called discovery services) that access data-related assets and extract characteristics about the data that can be stored in an open metadata repository.
    • governance-action-framework provides the interfaces and base implementations for components (called governance actions) that take action to correct a situation that is harmful the data, or the organization in some way.
  • governance-servers - servers and daemons to run open metadata and governance function.
    • server-chassis - the server chassis provides an "empty" server to host the open metadata services.
    • admin-services - the admin services support the configuration of the open metadata server chassis. This configuration determines which of the open metadata services are active.
  • repository-services - metadata exchange and federation - aka the Open Metadata Repository Services (OMRS).
  • user-interfaces - browser based user interfaces.
    • access-services-user-interface - provides a user interface that supports the user-facing Open Metadata Access Services (OMASs).
    • server-configuration-user-interface - provides the administration user interface for an open metadata server.
• open-metadata-compliance-suite - implementation of the tests that determine if a vendor or open source technology is compliant with the open metadata and governance standards.
• open-metadata-distribution - contains scripts to extract the completed artifacts from the other modules and stores them together to make it easy to find them.
• open-metadata-publication - contains scripts that send artifacts collected together by the open-metadata-distribution module to external parties.
• open-metadata-resources - contains the open metadata demos and samples.

This content is maintained by the Egeria community. To understand how to join and contribute see the Community Guide.

This project aims to operate in a transparent, accessible way for the benefit of the Egeria community. All participation in this project is open and not bound to any corporate affiliation. Participants are bound the ODPi's Code of Conduct. The governance of the project is described in more detail in the Egeria Operations.