Analytics

Every community has an analytics view that summarizes its members' expertise and activity. Every member of the community can read it — as the Signals tab of the community's People page, or at /community/<id>/analytics — so it's a shared picture, not an admin-only report.

Two modes

The dashboard auto-detects the mode that fits the community and lets you switch between research and professional for the current session (the switch isn't saved).

Research mode

For research-oriented communities:

• Overview — publications, total citations, research areas, and authors; publications by year; recent highlights; most cited publications. Group research areas by fields, subfields, topics, or MeSH terms.
• Expertise Map — drill down from topics and domains to the authors behind them.
• Trends — publication output over time, rising and declining topics.

A time-range selector (all time, last 3 years, last 2 years, this year, a specific year, or a custom range) applies across the tabs.

Professional mode

For professional and industry communities:

• Snapshot — members, organizations, skills, and cities; member roles; geographic distribution; and a member map.
• Skills & Expertise — top skills (raw or clustered), seniority distribution, Hidden Gems (niche expertise shared by two or three members), skills and education by role, career backgrounds, and career flow.
• Network — education network, shared organizations (current or all-time), and geographic clusters sized for events (15+ members), dinners (5–14), or seeds.

Member map

Two surfaces plot members geographically, and they are not the same map:

• The Map tab of the People page groups the community's geocoded members into city buckets and plots up to 3,000 of them. The cap counts buckets, not members: it was sized against one community of 15,130 members whose 15,071 geocoded members fell into 2,342 city buckets, well inside the cap for that community. A community whose members are spread across more cities reaches the limit sooner, whatever its member count.
• The standalone /community/<id>/map route reads the cached analytics locations instead and plots up to 200.