We have a script, co-developed with the WOD team, that harvests metadata out of the NetCDF files hosted by WOD and renders JSON-LD/schema.org for ODIS. We also generate the sitemap which lists the JSON-LD.
This is a system-system interoperability model that simulates a "typical" node's behaviour. Ideally, WOD will take over the generation of JSON-LD/schema.org (so its under their control), but this is a reasonable short-term measure.
Tasks
Document the WOD link as a system-system interoperability model, different from but in the same category of interfaces as WIS2
Move scripts used to handle WOD (meta)data to the archinterfaces directory
... anything else?
Also relevant to #404, although Argo volumes will need different considerations and checks for redundancy with WOD products.
We have a script, co-developed with the WOD team, that harvests metadata out of the NetCDF files hosted by WOD and renders JSON-LD/schema.org for ODIS. We also generate the sitemap which lists the JSON-LD.
This is a system-system interoperability model that simulates a "typical" node's behaviour. Ideally, WOD will take over the generation of JSON-LD/schema.org (so its under their control), but this is a reasonable short-term measure.
Tasks
archinterfacesdirectoryAlso relevant to #404, although Argo volumes will need different considerations and checks for redundancy with WOD products.