Import
Kumu's import feature makes it possible to map your existing data, without recreating every bit of it by hand.
Before you import your data, make sure to structure it for Kumu to understand.
Three options for importing data
Kumu offers three ways to import data. Read about them below!
Excel /CSV
An Excel sheet or a Comma Separated Value (CSV) file is one of the most common ways to hold and edit data.
Pros
Most platforms allow you to export data into an .xlsx or a .csv file. You'll then be able to easily structure it for Kumu and import it into your project
Great for bulk-editing data by dragging cells and using formulas in your Excel sheet
Cons
Not great for cases where data requires frequent updating: each edit to your Excel sheet requires a re-import into Kumu
Re-imports into Kumu increase the chances of duplicating data. Read how to prevent this in this guide
As soon as you make changes to your data directly in Kumu, your Excel sheet will be outdated. (Luckily, you can always export your Kumu map into an Excel sheet to get the most updated version again)
Visit our guide to import data with Excel/CSV here
Google Sheets
Google Sheets provides online spreadsheets that can be edited by multiple people at the same time.
Pros
Updates data in your Kumu map after each page refresh
Great for crowdsourcing: allow people to add/edit their data without giving direct access to the Kumu map
Allows for real-time collaboration: multiple people can work on the sheet at the same time
Allows for versioning and activity-tracking: you can always see who made changes and/or restore to an earlier version of your data
Cons
Data in Kumu is read-only. Any changes to underlying data must be made in the Google Sheet.
Some Kumu features (such as pinning elements in place, popovers, and direct decorations) don’t work for maps connected to a Google Sheet
Visit our guide to import data with Google Sheets here
JSON / Blueprints
You can create our JSON imports—we call them blueprints—in any language from any dataset. Kumu can interpret JSON files and JSON remote links. A JSON file simply holds data structures and objects, while a JSON link is commonly used for transmitting data between web applications (e.g., sending some data from an external server to Kumu, so it can be displayed on your map).
Pros
A remote JSON link is the closest thing Kumu has to a public API
JSON files are great to use as downloadable backups of your project
Cons
Not easy for bulk-editing data
Requires knowledge of JSON-structured data or a willingness to learn
Visit our guide to import data with JSON here
Want to dive right in? Find some example data sets here.
Need some inspiration? Find some Kumu Projects in the Wild here.
Want to add your Kumu project to this map? Submit it here.
Last updated