Member enrichment

Member enrichment allows you to automatically populate community member profiles with additional data points. When a member is enriched, you can gain deep insights into a member's skills, open-source contributions, education, work experience, and more.

The enrichment is based on publicly available information spread across various social platforms.

Which members can be enriched?

For a member to be successfully enriched, they must have either a GitHub identity or an email address. Without both of these pieces of information, the enrichment will fail. When this happens, don't worry, we will not deduct any enrichment credits.

How do you enrich a community member?

There are two ways you can enrich a community member:

1. Single or bulk add from the Members page

On the Members page, you can either select all members at the top of the directory list or select several by checking the boxes on the left of each member you would like to enrich. Then from the dropdown menu "actions," select "Enrich members."

If you are enriching a single member, you can click the three dots on the right of a member and, from the dropdown, select "Enrich member."

2. Directly from a Member profile page

On a Member Profile page, you will see a purple colored box on the top right corner, just click "Enrich member."

📘

What happens if enrichment fails?

If the enrichment fails, it could be for one of two reasons. Either the member you are attempting to enrich does not have an email or a GitHub identity associated with them, or despite the member having an email or a GitHub identity, we do not have it in our enrichment database.

It is important to note that in the event of an enrichment failure, no enrichment credits will be deducted. We understand that sometimes, the enrichment process may not be successful due to reasons beyond your control, and we do not want to penalize you for this.

What information do you get about members?

We add many attributes (listed below) to the members and enrich them with their open-source contributions. We can also populate their GitHub, LinkedIn, and Twitter identities, as well as their email field.

Attributes

• Location (string): The member's location.
• Job Title (string): The member's job title.
• GitHub URL (string): The profile URL of the member on GitHub.
• LinkedIn URL (string): The profile URL of the member on LinkedIn.
• Twitter URL (string): The profile URL of the member on Twitter.
• Bio (string): A bio or summary of the member.
• Seniority Level (string): The seniority level of the member, e.g. Junior, Middle, Senior.
• Emails (multiple select): The email addresses associated with the member.
• Expertise (multiple select): The member's expertise clustered by topics (including non-technical skills).
• Skills (multiple select): The member's technical skills based on their OSS contributions. Skills are displayed sorted by relevance (high to low).
• Country (string): The member's country.
• Programming Languages (multiple select): The programming languages the member is proficient in.
• Languages (multiple select): The languages the member is proficient in.
• Years of Experience (number): The number of years of work experience the member has.
• Education (JSON): A JSON object containing the following keys:
  • campus (string): The members' campus name.
  • major (string): The member's major.
  • specialization (string): The member's specialization.
  • startDate (string): The members' education start date.
  • endDate (string): The members' education end date (if it has ended). If the member is still studying, it will be 'Present'.
• Awards (multiple select): The member's awards.
• Certifications (JSON): A JSON object containing the following keys:
  • title (string): The members' certification title.
  • description (string): The members' certification description.
• Work Experiences (JSON): A JSON object containing the following keys:
  • title (string): The member's job title.
  • company (string): The member's company.
  • location (string): The members' company location.
  • startDate (string): The members' job start date.
  • endDate (string): The members' job end date (if it has ended). If the member is still working, it will be 'Present'.

📘

Not all of these attributes may be found for every member.

Our dataset is based on publicly available data from various platforms. Depending on whether a member has a public profile on these platforms or, for example, always uses an anonymous handle, it may be that we cannot enrich all attributes.

Open Source Contributions

Enrichment provides insights into a member's open-source contributions and uses this information to create a network graph.

Visualizing a member's open-source contributions is a powerful way to understand their skills, expertise, and interests in a way that is easy to understand and interact with.

The graph is made up of two main elements:

• Nodes: represent the repositories the member has contributed to. The size of a node is proportional to the number of contributions the member has made to that repository.
• Edges: connect the nodes and represent the relationships between different repositories. Nodes are joined together if they have any repository topics in common, and the thickness of an edge is proportional to the number of topics the two repositories have in common.

Clicking on a node will give you more information about the repository, including all the topics and the number of contributions. Similarly, clicking on an edge will show all the topics that connect the two repositories.

📘

Will data be overwritten?

No member data will not be overwritten from our enrichment feature. Identities and emails will only be added if they do not exist before. All attributes are added so that they will not overwrite any pre-existing attributes. If we have the same attribute coming from any integration and enrichment, both will be stored, but the one from the integration will show up in the app.