New data storage layout
@tischer and me have been working on updating the data storage layout, so that we can use the platy browser with data hosted via the EMBL S3 storage and our initial proto-type is working. For this to work, we need to change the data storage a bit:
- All image volumes in s3 need to be stored as n5
- The folder layout needs to change a bit, because we now have separate versions of xmls for the locally stored and remotely stored data.
This brings up a few questions:
- Should we keep the local data as h5 or can we also store it as n5? Having it as n5 as well would make synching local and remote data a lot easier and would speed up the version updates significantly, but some of the analysis workflows would need to adapt.
- Should we keep the folder layout for the old version as it is and support to schemes in the platy browser or should we change them as well?