eox-cs1
commented
1 year ago - After the latest design decision to harmonize the metadata ingestion process, and therefore skipping the sidepath from EDC ( also using the yaml files from EDC, to immediately have access to the "simple statis catalog") no yaml files are created in FiC anymore. see also: https://github.com/FAIRiCUBE/FAIRiCUBE-Hub-issue-tracker/issues/9#issuecomment-1584156217
- The import from the EDC catalog data will now be based directly on STAC-JSON files. see also: https://github.com/FAIRiCUBE/FAIRiCUBE-Hub-issue-tracker/issues/6#issuecomment-1580839593
- If there will be a requirement in the future, that metadata from FiC shall be imported/provided to EDC, a transformation process from the STAC-JSON to STAC-YAML can easily be established
- a lossless transformation should, to the best of our knowledge, be possible
- [ ] needs to be tested and demonstrated (https://github.com/FAIRiCUBE/FAIRiCUBE-Hub-issue-tracker/issues/8#issue-1745710947)
KathiSchleidt
jetschny
pebau
Do we foresee interaction of FiC data with EDC catalogue?
Making FiC data products available to EDC?
Keeping all FiC data products "in house"?
The decision has implications for the provision of yaml files -> EDC hosts data meta data as yaml files
FiC catalogue will in any case need to convert EDC yaml files to make it visible under FiC catalgoue Currently, EDC yaml files are by default converted to STAC json, can therefor be harvested and used in a [future] FiC catalogue easily.