Open agahkarakuzu opened 5 years ago
>>>> TO BE DISCUSSED START __
Good practice recommendations:
Parameters that are unchanged across the constituents of a
grouped scan collection
MAY repeat in every JSON file belonging to that group. To avoid such redundancy, all the fixed metadata fields MAY be included only in the JSON file of the first member of agrouped scan collection
, where constituent images are sorted in ascending alphabetical order. If this convention is followed, then the remaining JSON files MAY only contain parameters that are subjected to at least one change across all the member images.
TO BE DISCUSSED END <<<<
@Gilles86 and I are reviewing this PR and although we can see the benefits of not having to write out the same metadata over and over, we both agree that this proposal breaks the inheritance principle and ends up being much more complicated to implement 😭
I've deleted it for now....sorry @agahkarakuzu! I hope that's ok 😬
suffix
suffix
justification section w.r.t. thesuffix
classes.suffix
.MPM
&MTS
convention.Improved main spec
suffix
section in the specification: Created 3 classesgrouping suffix
,indexable_metadata
andacq-<label>
Added new text for elaborating on JSON files accompanying
grouping suffixes
grouping suffixes
with metadata fieldsparent
&child
TO BE CHANGED intohigh
&low
level, or some other proper pairsession-<>
into account in the explanation of the higher level JSON forgrouping suffix
B1DAM
suffix.indexable_metadata
,acq
and JSON fields.