ISTP compliance check with SKTEditor library fails
Two errors are reported by the ISTP compliance check with the SKTEditor library, for instance:
Errors:
Logical_file_id should be 'co_rpws_hfr_qtn_200502160509_v03'. It is 'co_rpws_hfr_qtn_200502160509_200502171439_v10'.
spase_DatasetResourceID is missing.
The first error is based on an ISTP convention assuming the file name should contain a single date or datetime
(which would be the start datetime in our case). Our convention (<<start-datetime>>_<<end-datetime>>
) is used
by other projects like Solar-Orbiter (see section 2.1.3.1, item 5).
The second error is triggered although the spase_DatasetResourceID
is mentionned as "recommended" in the ISTP CDF web
pages. This attribute is required if the data product is planned to be listed in the SPASE registry
(under development for this dataset).
Edited by Cecconi Baptiste