Major UX improvements to Dataset creation and file uploading
6 months ago we announced the release of the Storage extension to CKAN which provided integrated upload and storage support for data in CKAN.
The basic architecture of the Storage system has proved very robust. However we know that the integration with the front end, and the general user experience, has been far from perfect. We’ve therefore worked heavily over the last few months to greatly improve this, and today we can announce that the changes are done in CKAN and live on the DataHub.
The main changes are (see the ticket for more):
- Completely rework layout of Dataset creation and editing, with both simplified and improved
- Separate, dedicated form for creating Dataset Resources (the data associated to Datasets, in the form of data files and APIs)
- In-place previewing for text fields that use http://daringfireball.net/projects/markdown/ (e.g. description / notes)
- Upload is now an integrated part of this process (if Storage is enabled) — it was previously separate (and rather clunky!)
Uploading in particular has seen a lot of work:
- You can choose between linking to a file, linking to an API, and uploading each time you create a Dataset Resource
Here’s a walkthrough of the process of uploading a file which also illustrates the new form layout:
‘Example Dataset’ has no data resources. We’re about to add one by choosing ‘Upload a file’.
A file chooser button appears, and when we click on it …
… a file browser lets us choose the data file we want.
Ok, we’ve got the right file. Let’s click ‘Add’.
The file is being uploaded over the network from our local disk into CKAN.
Hurrah! The Dataset has been edited. All that remains is to save the result, by hitting ‘Save Changes’ …
… and the Dataset view now shows the new resource.