[ckan-dev] Hierarchical folder structure for a dataset
d.steer at bris.ac.uk
Fri Aug 11 09:24:30 UTC 2017
On 11/08/17 09:04, Harald von Waldow wrote:
> Hi Damian
> That looks pretty interesting. I would also not mind seeing how you
> designed the user-interface to let people upload hierarchically
> structured datasets. Is the code for that publicly available?
Ah, I was too brief originally:
> We only use CKAN as a catalogue - the data is held externally
Our data publications come from our institutional research data store: a
fancy shared drive essentially. Our publications are stored on the same
We have a publication tool that lets users enter metadata and pick the
folder they want to deposit. We then copy the data to our space, and
save the metadata with it in a hidden file. The folder is shared over
the web (example  and the corresponding ckan page ).
We have deposits up to 100GB, which would be painful to do in the
repositories we looked at. There are some custom uploaders now, and
things like rsync of course. But hacking in that simple pick-a-folder
thing was hard.
We also think we can maintain a static folder shared over apache for up
to 20 years (which is our guarantee). 
So CKAN comes in right at the end, and is an nice, searchable shop-front
for our datasets. We periodically look for new or changed datasets (via
http), grab the metadata and push it into CKAN using the web api.
Working well so far, I'm happy to say.
 Obviously we hope CKAN is around forever!
Senior Technical Researcher
+44 (0) 117 39 41724
More information about the ckan-dev