To remove this from the table headers, so table files can be used across projects, this will need to be registered in the Project_CVs, with a look-up validation entry CV is required in this repo to catch invalid use cases.
As a quick pass and to account for all existing examples, we'd need something like:
{
"product": {
"model-output", # CMIP6, CORDEX-CMIP6; we also have output, output, output1 and output2 in CMIP5
"observations", # input4MIPs, obs4MIPs
"reanalysis", # input4MIPs, obs4MIPs
"forcing", # input4MIPs
"derived", # input4MIPs, obs4MIPs
...
As has now been discussed in a couple of threads across repos, the
productattribute has been used to delineate between model output in CMIPxmodel-output(e.g. `CMIP6_Amon.json), and various flavours of observational, derived and other data across input4MIPs and obs4MIPs (see discussion in https://github.com/PCMDI/cmor/issues/723#issuecomment-1912797439 and https://github.com/WCRP-CMIP/CMIP6Plus_CVs/issues/45.To remove this from the table headers, so table files can be used across projects, this will need to be registered in the Project_CVs, with a look-up validation entry CV is required in this repo to catch invalid use cases.
As a quick pass and to account for all existing examples, we'd need something like:
@taylor13 @mauzey1 @matthew-mizielinski @wolfiex ping