Closed p-a-s-c-a-l closed 5 years ago
Is this metadata format extracted from the netcdf files or has it been developed ad-hoc? If it is latter, I would strongly suggest to use our data package specification metadata structure, otherwise it is going to be a nightmare with several ways of "metadating" the same resources.
In fact, IMHO CLARITY Data Package should be the way to harmonize all different metadata formats (and data structures) we have in the project.
Btw, I will be taking some attributes ideas from this example to improve our Data Package specification.
I asked this question about the origin of the JSON meta-data, but didn't get and answer (yet). I invited Astrid and Robert to the join Science Support Team to discuss this issue about Meta-Data Harmonisation.
Maybe it is time to stop answering tech-related emails and force them to use github if they want to continue the discussion.
According to https://github.com/clarity-h2020/ckan/issues/9#issuecomment-441967233, the datasets are published on data.ccca.ac.at. So this Example is no longer needed.
done
Deposit Tx75p_consecutive_max_EUR-11_ICHEC-EC-EARTH_rcp85_r12i1p1_SMHI-RCA4_v1_day_20110101-20401231_netcdf3.nc in Zenodo andcreate a respective resource entry in ckan which represent CLARITY's "living" Data Management Plan.Meta-Data describing the .netcdf file can be found in Hazard_definitions.docx
This task depends on