Packaging Research data with DataCrate - a cry for help!
DataCrate is specification for packaging research data with extensive human and machine readable metadata for either distribution (eg in a zip file) or hosting on the web. The specification is a final-draft form, and has been adopted at the University of Technology Sydney as a the core means of distribution for datasets in our repository, and has generated interest in Australasia and internationally. The aim is to provide "Who, what where" metadata that makes understanding and reusing data
... ical. DataCrate can express detailed information about which people, instruments and software were involved in capturing or creating data, where they did it and why, as well as how to cite a dataset. The spec is on github: https://github.com/UTS-eResearch/datacrate/blob/master/spec/1.0/data_crate_specification_v1.0.mdRelated Work: DataCrate builds on other standards, starting with BagIt for packaging files and URLs with checksums . It is similar in intent to Frictionless Data packaging , but uses JSONLD and the schema.org vocabulary rather than a simple JSON structure – this ensures that metadata will interoperate with the semantic web (eg, DataCrates are compatible with Google's Dataset search). DataCrate has a similar structure to Research Object Bundles , but a significantly simpler way of adding metadata. An innovation of DataCrate is that is has a rich HTML website that functions as a detailed README file down to the file level (and soon to the column header in tables), in an approach which has also been adopted by DataSpice . Content: This proposed session introduce the specification using extensive examples, showing how it can be used for many kinds disciplines including social history, microscopy, computational models, interview materials, environmental data about soil and atmosphere, and speleological mapping data. The session will also show how DataCrate can be used as interchange format, pulling and pushing data from multiple systems. Seeking feedback, and developers: We will [...]