Use Case: Export as RO-Crate

[eocarragain]

As a repository manager/user, I want to be able to losslessly export a given object in RO-Crate format so that I can work with it in a different environment (local PC/offline) or migrate/replicate it to another platform.

See the final recommendations of the Research Data Alliance Repository Interoperability Working Group. Having surveyed a variety of options (e.g. OAI-PMH, ResourceSync, etc.), this RDA group came to the conclusion that a simple but extensible, BagIt-based packaging format was the best candidate to provide interoperability across diverse repositories. This particularities of the RDA spec should be considered when addressing #13

[ptsefton]

We should possibly remove mentions of "bagged crates" from the DataCrate spec and add some implementation advice about how to use it with various packaging formats - the advice for BagIt is simple - put the manifest and HTML files in the bag root and the data in data but we can make RO-Crate package agnostic.

For example, at UTS we're working on using in with OCFL and similar advice will apply. Put the data in a payload dir called /data and skip the bag it stuff as it is redundant with OCFL's inventory. BagIt would be something you do on export from the repository.