But following complications I see immediately which would need to be considered/addressed to make it feasible to validate using current datalad-fuse based solution:
currently we do not have zarr subdatasets installed within dandisets/* dandisets (like 000108). They all just live in their original ../dandizarrs location. So we cannot just easily use dandisets-fuse/ location we have since those subdatasets/locations would be empty
That dandizarrs itself is not even a datalad dataset, so we cannot even use datalad-fuse on that location (https://github.com/datalad/datalad-fuse/issues/35) . After that issue addressed I guess we could have implemented some adhoc jumping to another fused location upon getting into not installed submodule but it is "suboptimal" since assumes the correspondence of the git commit for submodule and repo under dandizars/ which most likely would be ok but not necessarily.
ATM we have /mnt/backup/dandi/dandizarrs/tools/jsonschema-check-zattrs which produced http://www.oneukrainian.com/tmp/dandizarrs-jsonschema-checks.out . That script avoids using fuse since just needs to access a single file. But in the long run I hope that more thorough validation of zarrs would come about (ref: https://github.com/ome/ome-zarr-py/pull/142#issuecomment-1517024760 and there on).
But following complications I see immediately which would need to be considered/addressed to make it feasible to validate using current datalad-fuse based solution:
dandisets/*dandisets (like 000108). They all just live in their original../dandizarrslocation. So we cannot just easily usedandisets-fuse/location we have since those subdatasets/locations would be emptydandizarrsitself is not even a datalad dataset, so we cannot even use datalad-fuse on that location (https://github.com/datalad/datalad-fuse/issues/35) . After that issue addressed I guess we could have implemented some adhoc jumping to another fused location upon getting into not installed submodule but it is "suboptimal" since assumes the correspondence of the git commit for submodule and repo underdandizars/which most likely would be ok but not necessarily.