Open yarikoptic opened 5 months ago
Attention: 1 lines
in your changes are missing coverage. Please review.
Comparison is base (
4423b41
) 97.66% compared to head (ddd77da
) 97.61%.
Files | Patch % | Lines |
---|---|---|
dandischema/metadata.py | 75.00% | 1 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
i'm fine with something like this being in the database, but not sure about changing the metadata model. perhaps we can brainstorm when we meet.
This is just an initial attempt open for discussion. @satra please chime in
I ran into "blobDateModified" in a zarr metadata and it raised my eyebrow since that is not really appropriate and confusing. Hence I decided to look into generalization. I also thought that it would be valuable to make "type" of the content Asset points to explicit, although that could lead to inconsistencies since information is somewhat redundant with encodingFormat and potentially could also be deduced from contenUrl since we have different end points on S3, etc.
Nevertheless I think it might be better to make it explicit. Or at least we have to rename blobDateModified.
ContenType name is quite suboptimal since there is a standard HTTP header https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Type and thus we could potential confusion.
But we should keep it a "Type" (not e.g. a Class) to be consistent with other type definitions among models.
So the other part we could try to vary is "Content". Possible alternatives are "Object", "Data", "Resource"
ATM we call all Zarrs just Zarr but it is a "ZarrFolder" really. I wonder if it would be time to start to introduce differentiation here by making it "ZarrFolder", as later we might get "ZarrHDF5" or alike