Kumu
  • Getting started
    • Welcome
    • Kumu 101
    • First steps
    • Quick tips
    • Webinars
  • Overview
    • Kumu's architecture
    • Accounts and workspaces
    • Kumu.io and Kumu Enterprise
    • Billing
    • User interfaces
      • Dashboard
      • Settings
      • Map editor
      • View editors
      • Quick Actions
    • Collaborating and sharing
    • Actions and permissions
    • Security
    • Advanced Editor hub
      • @settings reference
      • @controls reference
      • Color reference
      • Property reference
      • Selector reference
  • DISCIPLINES
    • SNA / Network Mapping
    • Systems mapping
    • Systems Practice workbook
  • Guides
    • Activity feed
    • Add-ons
      • Disqus
    • Bridge
    • Cluster
    • Controls
      • Cluster control
      • Color-legend control
      • Filter control
      • Focus control
      • Image control
      • Label control
      • Showcase control
      • SNA-dashboard control
      • Tagged-timeline control
      • Text Control
      • Title Control
      • View toggle control
    • Decorations
      • Direct decorations
      • Data-driven decorations
      • Flags
      • Icons
      • Images
      • Label templates
      • Popovers
    • Default view settings
    • Export
    • Fields
      • Computed fields
    • Filter
    • Focus
    • Forking
    • Grids & Guides
    • Import
      • Structure your data for Kumu
      • Excel / CSV
      • Google Sheets
      • JSON / Blueprints
    • Imported views
    • Layouts
      • Fixed
      • Force-directed
      • Remove overlap
      • Scatter
      • Snap-to
    • Legends
    • Licensing
    • Lightbox
    • Loops
    • Metrics
    • Two-factor authentication
    • Pro workspaces
      • Archiving projects
      • Discussions
    • Partial views
    • Presentations
    • Profiles
      • Markdown
    • Project admin
    • Selectors
    • Shapes
    • Share and embed maps
    • Shortcuts
    • Showcase
    • Slugs
    • Table
    • Templates
      • Geo template
    • URLs
    • Views
    • Widgets
  • About Kumu
    • What is Kumu?
    • How does it work?
    • Where can I get help?
  • Enterprise
    • About enterprise
    • Getting started with VMWare
    • Upgrading
    • Configuration
    • Creating user accounts
    • SSH Access
    • Single sign-on
    • Backing up enterprise data
    • Restoring enterprise data
    • Command line utilities
    • Changelog
  • Frequently Asked Questions
    • Does Kumu have a public API?
    • Does Kumu make use of AI?
    • How do I add annotations?
    • How do I add anchors to my map description?
    • How do I add arrows to my connections?
    • How do I add documents to profiles?
    • How do I add more than one element with the same label?
    • How do I add text dropdowns to my map overview?
    • How do I adjust arrow size?
    • How do I avoid duplicating data?
    • How do I change connection curvature?
    • How do I change font color?
    • How do I change font size?
    • How do I change the default for currency fields?
    • How do I change the length or strength of connections?
    • How do I change the order of control options?
    • How do I change the position of my element labels?
    • How do I cite Kumu?
    • How do I collapse duplicate connections?
    • How do I copy a map to another project?
    • How do I control label size while scaling element size?
    • How do I control text wrapping?
    • How do I convert a project from private to public?
    • How do I convert a project from public to private?
    • How do I create dynamic on/off toggles for my map?
    • How do I customize link text in popovers?
    • How do I customize the order of my legend?
    • How do I delete a project, map, or view?
    • How do I delete data from my project?
    • How do I downgrade my subscription?
    • How do I edit virtual elements?
    • How do I get rid of duplicates?
    • How do I hide elements without connections?
    • How do I hide images from the map but keep them in the profile?
    • How do I hide labels on my map?
    • How do I hide the settings button?
    • How do I keep elements from moving?
    • How do I list an element's connections in its profile?
    • How do I make elements transparent?
    • How do I make sense of my receipt?
    • How do I open a sub-system when clicking on an element?
    • How do I remove the Opposite entry from my legend?
    • How do I remove unneeded controls?
    • How do I remove unwanted legend entries?
    • How do I rename my map/view?
    • How do I restructure my adjacency matrix?
    • How do I save my changes in Kumu?
    • How do I select options by default in my control?
    • How do I set a minimum or maximum zoom level for my map?
    • How do I show the Settings button?
    • How do I size elements based on number of connections?
    • How do I transfer a project?
    • How do I update my credit card information?
    • How much data can my Kumu project handle?
    • How do my readers switch between maps and views?
    • My data won't import. What can I do?
    • My Kumu embed is not working. What can I do?
    • My map disappeared. How do I bring it back?
    • My PDF won't export. What can I do?
    • What pricing plans does Kumu have?
    • Where can I find my invoices?
    • Where can I find example Kumu projects?
Powered by GitBook
On this page
  • Why is clustering valuable?
  • Cluster in the Basic Editor
  • Cluster in the Advanced Editor
  • Fine-tune cluster settings
  • Fine-tune in the Basic Editor
  • Fine-tune in the Advanced Editor
  • When is it useful to fine-tune element type?
  • Limiting which fields can be clustered

Was this helpful?

Edit on GitHub
  1. Guides

Cluster

PreviousBridgeNextControls

Last updated 1 month ago

Was this helpful?

Clustering is a powerful tool that allows you to connect elements based on the data in their , and it's particularly useful on stakeholder and network maps.

When clustering is activated, Kumu will create new elements to represent each possible value for a field of your choice, and it will draw a connection between your elements and the value(s) in their field.

Here's a visual example—musical artists clustered by their genre:

This guide will make you an expert on clustering, one of Kumu's most unique and powerful tools!

Why is clustering valuable?

There are hidden relationships in much of the data you have stored in spreadsheets; they're just not stored explicitly as connections. For example, you probably have a spreadsheet full of contacts, with one column storing the person's name and another column storing the organization she works for. If you imported this directly into Kumu, you'd end up with a map like this:

Not that eye opening, right? You could click on each element to open its profile, allowing you to see each person's organization, but it would take you a long time to gain any insight into your data.

If you cluster these people by their organizations, you can start to get a better understanding of your network:

Voila! We used clustering to transform a rigid spreadsheet into a relationship map of all the people and organizations they work for.

Cluster in the Basic Editor

If your elements are people, cluster by...

  • Tags

  • Skills

  • Teams

  • Interests

  • Projects

  • Organization

  • City

If your elements are organizations, cluster by...

  • Tags

  • Initiatives

  • Populations served

  • Funding sources

  • Board members

  • Region

  • Sector

Cluster in the Advanced Editor

If you prefer working in the Advanced Editor, you can use the cluster property in the @settings block to activate clustering. Here's the simplest version of the cluster syntax:

@settings {
    cluster: "Field";
}

Just replace Field with the name of any field in your project, and any element with data in that field with be clustered!

Fine-tune cluster settings

When you're using the Basic Editor's Connect by tool or the simplest version of the Advanced Editor's cluster syntax, cluster settings follow three default rules:

  1. All elements on the map will be clustered by the field you chose.

  2. You can only cluster by one field.

  3. The new elements that get created by clustering will use the name of the cluster field as their element type (for example, if you cluster by "Organization", the created elements will have the element type "Organization").

These default rules often won't cause any problems for your map, but there are some cases where you will want to override them. To do that, you can use either the Basic Editor or Advanced Editor to fine-tune your cluster settings.

Fine-tune in the Basic Editor

If you want to cluster by more than one field, just click the Add rule button and repeat the process!

Fine-tune in the Advanced Editor

In the Advanced Editor, here's the syntax for fine-tuned clustering:

@settings {
 cluster: selector by "Field" as "Type";
}

Here's an example that clusters all elements with the element type "Person" by their organization. The organizations that are added to the map will have the type "Organization".

@settings {
 cluster: person by "Organization" as "Organization";
}

Multiple cluster rules can be added by separating them with a comma:

@settings {
 cluster: person by "Organization" as "Organization", organization by "Sector" as "Sector";
}

When is it useful to fine-tune element type?

Fine-tuning the element type is useful when you want to make sure that Kumu re-uses existing elements instead of creating new elements through clustering.

When Kumu is about to create a new clustering element, it first searches the entire project for an element with a matching Label and Type. If it finds a match (on any map), it will re-use that element (complete with any Description, Tags, and custom field data as well).

One use case for this feature is cross-matching multiple fields, such as "Skills needed" and "Skills offered". In that case, you're probably looking to see the overlap between who's looking to learn a skill and who might be able to teach it. To start, you would cluster all elements by "Skills offered", then add a second rule to cluster all elements by "Skills needed".

If you don't customize the type of the elements created by this cluster setting, the types will default to "Skills offered" and "Skills needed", and you'll get two separate elements for each skill: one with the type "Skills offered" and the other with the type "Skills needed".

But, if you set the element types to "Skill" for both clustering rules, Kumu will create only one element for each skill value—even though the values originated in different fields.

Limiting which fields can be clustered

If you'd like to hide certain fields from your Cluster Settings dropdown menus, you can click on an element, click on the downward arrow next to the field name, and use the field settings to disable clustering:

Before you start: to add additional information to your elements, connections, and loops.

To set up your first cluster, click the settings icon on the right side of the map to open the Basic Editor, and use the dropdown next to Connect by to select a field. Every dataset is unique, but here are some ideas to get you started:

If you need to restrict clustering to certain elements, cluster by more than one field, or customize the element type of the elements created by clustering, .

If you need to restrict clustering to certain elements, cluster by more than one field, or customize the element type of the elements created by clustering, .

To fine-tune your cluster settings in the Basic Editor, click the settings icon to the right of the Connect by tool, and your Basic Editor will show you the Cluster Settings menu:

Click the Add rule button to create a new cluster rule. Then, click next to "Connect" to bring up the Selector Builder, which allows you to narrow the of elements that will be clustered.

Click next to "by" to choose which field those elements will be clustered by, and click next to "as" to change the element type that will be assigned to the elements created by clustering. (Wondering when it's useful to fine-tune the element type? .)

Replace selector with any valid . Replace Field with the name of the field you want to cluster by, and replace Type with the value that Kumu should set as the element type for each element created by clustering (make sure your Field and Type are wrapped in double quotes).

(Wondering when it's useful to fine-tune the element type? .)

If you want to disable clustering on any of the core fields (label, description, tags, or type), you can click the menu icon , click FIELDS, select the field you want to disable, and un-check the clustering box in the Advanced Settings:

use fields
selection
selector
learn how to fine-tune your cluster settings
learn how to fine-tune your cluster settings
Jump to the explanation
Jump to the explanation
fields
cluster by element type
Cluster basic editor
cluster default types
cluster customized types
clustering menu
advanced settings clustering menu
Elements with no relationships
Elements with relationships