Egeria stakeholders and Community building

Egeria stakeholders and Community building

This is a planning/discussion document as part of a follow up from the Open Source Summit in Vancouver (August 2018) where we discussed how to grow the community.

Egeria Stakeholders

Metadata repository vendors

Metadata repository vendors will integrate with Egeria through the OMRS. Typically a vendor needs to implement the OMRS Repository Connector and OMRS Event Mapper Connector to map their native repository APIs and events to open metadata formats. These connectors plug into the OMRS. The vendor then choses an integration pattern to to host OMRS and their connectors. They may need to implement some of the other OMRS connectors.

The information needed by a metadata repository vendor is as follows:

• OMRS concepts such as cohort, metadata collection id, cohort registry, connector framework (OCF)
• The open metadata types so they can build a mapping to the types in their repository.
• The way the types are represented in Entity, Relationship and Classification objects used by the connectors.
• What are the integration options/plugpoints.
• Implementation notes for each type of connector.
• Integration pattern choices and how to implement them.
• Supporting the admin interface
• Running the compliance suite.

Current engagement with metadata repository vendors:

• IBM Information Governance Catalog
• IBM Watson Knownledge Catalog
• SAS

Traditional Data Tool, Platform and Engine vendors

This integration is through the various OMASs. As we build out each OMAS ideally we need to build a community of vendors around its APIs and events. The key OMASs are:

• Asset Catalog
• Asset Consumer
• Connected Asset
• Asset Owner
• Data Platform
• Data Engine
• Data Science
• Governance Engine
• Information View

These vendors need to understand the roll and use of these OMASs.

Current engagement with data tool vendors

• Cognos
• Microsoft BI
• BigSQL

Software Development, DevOps and IT Infrastructure tools

These vendors integrate with the following OMASs - there is little to no development of these APIs at the moment.

• Software Developer OMAS
• DevOps OMAS
• Data Infrastructure OMAS

Discovery analytics vendors

Need the Open Metadata Discovery Framework (ODF), Discovery Engine OMAS and Discovery Server.

Data Governance Practitoners

Egeria offers industry unique governance capability through its Governance Program and Digital Arcitecture OMAS. In addition, the Data Security OMAS, Data Privacy OMAS, Asset Owner OMAS and Stewardship Action OMAS coupled with the Governance Action Framework (GAF) and stewardship server enables the operation of a complete governance program. There are shadow implementations of these APIs. We need to add a UI and Egeria metadata repository to the technology list and use the governance best practices to pull people into the community.

Enterprise adoptors

These are the organizations that adopt the open metadata standards as their enterprise standards and push their vendors to adopt. They need information on our vision, strategy and roadmap. The value to their operation increases and the other adoptors grow.

Random developers looking for a cool project

How do we attract these developers ?