A subsystem that is in development means that the Egeria community is still building the function. The code is added continuously in small pieces to help the review and socialization process. It may not run, or do something useful - it only promises not to break other function. There will be git issues describing the end state.
Community Profile Open Metadata Access Service (OMAS)¶
The Community Profile OMAS provides APIs and events for tools and applications that are managing information about people and the way they work together.
With this information, open metadata reduces the friction between people from different silos of an organization that can prevent the effective use of data. For example, an Asset Owner can monitor who is using their asset and for what purposes. At the same time, consumers or assets, such as a data scientist or business analyst, can find out which assets their colleagues are using, and any feedback that they gave, which helps to guide them to the most appropriate assets for their work.
Is this metadata ?¶
Data about people and organizations is not strictly metadata. It is master data. This means it is a type of data that is widely duplicated across an organization's systems but mercifully slowly changing. Open metadata is therefore only one of many systems making use of this data.
Many organizations use a centralized user directory, such as LDAP, for their employees. In addition large organizations with thousands of systems may also have a master data management (MDM) program to keep their data about people and organization's synchronized amongst their systems.
With or without MDM, it is important that the Community Profile OMAS can operate as a downstream consumer of this data, rather than operating as an independent island. This way it adds value to the organization by enabling the recording of asset ownership, use and feedback, without an excessive amount of additional administration.
Using the Community Profile OMAS¶
The Community Profile OMAS running in the metadata access server is also monitoring changes to open metadata. It will emit an event whenever profile, organizational or community related metadata is created or changed in some way. The java client provides a mechanism for third party technology to register a listener to receive these events.
The Community Profile OMAS is responsible for maintaining the count of the karma points for an individual based on their contributions to open metadata. It does this by listening to the metadata changes occurring in the metadata repositories and updates the personal profile of each user making a contribution.
The Community Profile OMAS java client provides a method to retrieve the current karma point total for an individual.
The access service option property KarmaPointPlateau indicates the multiple of karma points for an individual that results in an external event being published - the default is 500. This means that when an individual gets to 500 karma points, an event is sent on the Community Profile OMAS Out Topic, and other event is sent when they get to 1000 karma points and so on. These events can be used to trigger additional recognition activities for the individuals concerned.