Problem: we would like to forbid commits that include files bigger than XX MB.
Possible implementations:

• https://stackoverflow.com/questions/39576257/how-to-limit-file-size-on-commit/39578014#39578014
• https://gist.github.com/kiwidamien/a6a909ee196be8795b30431079074d64

Crossref: neuropoly/spinalcordtoolbox#3100 https://github.com/shimming-toolbox/shimming-tool

Use Case

Please provide a use case to help us understand your request in context

To prepare for the mass migration of TIFF -> NGFF (still looking likely Zarr) we should directly support reading Zarr files.

Solution

Please describe your ideal solution

Depends on #190

Act as a mix of #190 and the new OmeTiffWriter that accepts an OME object from ome-types.

Altern

It would be very convenient to be able to edit the currently opened dataset without going to the dashboard. One easy way to achieve this, would be an edit button in the "dataset info" tab. That edit button could open the "edit dataset" view in a modal. when that modal is saved, the entire dataset could simply reload.

If not in debug mode, intermediate files should be deleted as soon as they are not required, not all at the end, saving disk space.