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 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
  • When does Kumu create, and when does it update?
  • Connections
  • Alternatively...delete all data to avoid duplicates

Was this helpful?

Edit on GitHub
  1. Frequently Asked Questions

How do I avoid duplicating data?

PreviousHow do I adjust arrow size?NextHow do I change connection curvature?

Last updated 21 days ago

Was this helpful?

If you're , you'll most likely want to add new data, edit existing data, or maybe just fix a typo at some point. When that happens, you will want to make sure that Kumu isn't duplicating data when you re-import your up-to-date dataset.

To avoid duplicating data, you first need to understand how Kumu decides whether to create new elements & connections or update existing elements & connections.

When does Kumu create, and when does it update?

The rules are a bit different for elements and connections, so we'll tackle them one at a time below.

Elements

For the simplest possible element spreadsheet, which only contains a Label column, Kumu will create a new element for each unique label. Kumu would create three elements for this example (a list of famous surfing waves in Hawaii):

Label

Waimea Bay

Pipeline

Sunset Beach

For this next example, Kumu will also create only three elements, since one of the Labels is repeated in the data:

Label

Waimea Bay

Pipeline

Pipeline

Sunset Beach

You can use this behavior to your advantage when you want to update an existing element's data. Let's say you have already imported the first dataset, which created three elements in Kumu, and now you want to add a new field to those existing elements, using this data:

Label
Live Surf Report

Waimea Bay

http://www.surfline.com/surf-report/waimea-bay-oahu_4755/

Pipeline

http://www.surfline.com/surf-report/pipeline-oahu_4750/

Sunset Beach

http://www.surfline.com/surf-report/sunset-beach-oahu_4746/

Pua'ena Point

http://www.surfline.com/surf-report/puaena-point-oahu_49940/

When you import this spreadsheet, Kumu will search through all existing elements to find any Labels that match the Labels in your import file. Then, Kumu will update the matched elements with your new field.If you had any existing data in an element's field, it would be replaced by the data in the new import.

If Kumu can't find a match, it will add a new element to the map. In the example above, Kumu would update the existing Waimea Bay, Pipeline, and Sunset Beach elements, and it would create a new element for Pua'ena Point, which wasn't included in the original dataset.

Now, if you also include a Type column on your spreadsheet, Kumu will create a new element for each unique Label-Type combination. For example, this dataset will create five elements, even though one Label is repeated:

Label
Type

Waimea Bay

Double overhead

Pipeline

Head high

Pipeline

Double overhead

Sunset Beach

Head high

Pua'ena Point

Head high

The same rules apply here when updating data on existing elements: if Kumu can find a Label-Type match for the elements you uploaded, it will update that element's data, otherwise, it will create a new element.

Use IDs to separate identical labels

Finally, you can use an ID column to tell Kumu to ignore both Label and Type, and only match existing elements based on their unique ID. This can be really useful when you want to change the Label and/or Type of elements without creating duplicates:

ID
Label
Type

Wave-1

Waimea Bay

Double overhead

Wave-2

Pipeline

Head high

Wave-2

Pipeline

Double overhead

Wave-3

Sunset Beach

Head high

Wave-4

Pua'ena Point

Head high

In the earlier example, before we added ID, Kumu was creating two elements with the label Pipeline. One of those elements had the type Head high, and the other had the type Double overhead. But now that we're using ID, Kumu understands that those are the same element with the ID Wave-2.

With the help of this new ID column, Kumu will only create one Wave-2 element, and it will import the data from the Wave-2 that is furthest down on the list (i.e. the type will be Double overhead, not Head high).

If you're using IDs on your elements sheet, you need to use those IDs in the From and To columns on your connections spreadsheet, instead of using Labels.

Connections

If you want to create multiple connections between the same elements, or want to update existing connections with future imports, make sure to add IDs for each connection:

ID
From
To

Connection-1

Oahu

Waimea Bay

Connection-2

Oahu

Waimea Bay

In a future import for this example, we could use the ID Connection-2 to update the existing connection with any new data, including a new From or To value:

ID
From
To
Type

Connection-2

Oahu

Sunset Bay

Location

This import would update the map without merging your connections, or creating a new, duplicate connection.

If you're using an ID column on your connections sheet, you don't necessarily have to add IDs to your elements sheet. However, if you are using IDs on your elements sheet, you need to use those IDs in the From and To columns on your connections spreadsheet, instead of using Labels.

Good to know:

  • You can't update map data when clustering is turned on. Make sure to turn off all clustering options before importing any data into Kumu.

  • If you use underscores _ or periods . in your IDs, you won't be able to select elements from the search results in your map

  • To send somebody a link directly to an element, connection, or loop, you can follow this pattern: https://kumu.io/YourUsername/ProjectName#MapName/ViewName/ID

Alternatively...delete all data to avoid duplicates

Happy importing!

All of the same import rules apply when you are importing a

To remove duplicates,

Before you start:

We get it—sometimes, you just don't want to think through the complexity of Kumu's import rules; all you want is a nice, clean map with no duplicates. In that case, your best option might be to and start over with a fresh import.

importing spreadsheet data into Kumu
JSON blueprint
check out these steps
delete all the data from your project
Learn how to create a full project backup