At the moment it is not possible for a Webjive user to export a dashboard (represented as a json string) and import it later on on the same instance of Webjive or in other instances. Furthermore, upgrading to newer versions of Webjive should not hinder the ability to use previously defined dashboards (up to some limit - major changes in Webjive should bring some risk from this point of view). Whenever possible, Webjive should be smart enough to "understand" when an imported string can be safely transformed into a correct dashboard.
See how the Grafana editor handles dashboards in terms of import/export (each dashboard has a unique id, and probably a version number too).

Acceptance Criteria

• A user can export on local file system and import from it (file upload).
• Dashboards have a unique ID; uploading with same ID overwrites existing dashboard.
• user is given the option to "regenerate" new ID (and avoid overwriting).
• dashboards have a URL that is preserved as is their ID.
• json representation is tagged with webjive version; migration across different versions of webjive is guaranteed with no errors or malfunctions.
• import implies that json is validated, errors are shown to user, and imported dashboard works as if it were created by hand with the dashboard editor.