| Topic | Agreed consolidation |
|---|---|
Checksum management : the standard STAC checksum property is not suitable for asset downloaded as ZARR folder | To be discussed with Cloud Ferro during STAC catchup meeting. |
Test compliance suite : how to manage generic test compliance suite and mission specific test compliance suite | At least a minimum test framework should be initialized in order to ensure the qualification. At the end, two sets of test compliance are identified:
|
Definition of mission specific queryable schemas | OK, agreed to managed that in the mission specification configurations. |
Verification of the alignment of the ICD with EOPF spec (is the EOPF specification released ?) | Meeting to be scheduled with Vincent to get the current status. |
Search API to support (cross-collection and/or single collection) | Ok to support both. |
Quota management | Important to put requirement on the download of product. byte per period of time. terrabytes per month. |
Comment from Mario on section 2 Objectives and needs: The STAC concepts are already described in [STAC_EOF_ICD]. The scope of this section could be more on the PRIP and its objectives and context, as in the current OData ICD. | To reproduce the general explanation text already available in the OData based PRIP ICD. |
Comment from Mario on Product Type: The "unpublished" property would perhaps be semantically closer to the OData property EvictionDate than "expires". | Agreed to keep the "expires" field. For AIP ICD, to involve Matthias in the discussion to choose the proper fields to support LTA use cases. |
Reference to the Central Authentication Service ICD | Jolyon will ask for update on this specification. In the meanwhile, to add an entry in the list of applicable documents of the PRIP ICD to point to this upcoming document. |
Overview
Content Tools
Add Comment