The infrastructure behind this is run by DKRZ and is not funded to cover projects outside CMIP6 (an possibly not for CMIP6 data added after the AR6 report), so we cannot use it in the same way here. The CMIP5 version of the tracking_id just used a unique identifier, such as 5a26143c-222d-4cea-aed2-923b45d930c9. This is not resolvable in the same way, but does provide a useful way of tracking files when publication updates lead to multiple files with the same name.
I recommend using the CMIP5 version of tracking_id here.
The
tracking_idin CMIP6 files is a resolvable handle.net identifier, e.g.hdl:21.14100/5a26143c-222d-4cea-aed2-923b45d930c9 for the file http://esgf.bsc.es/thredds/fileServer/esg_dataroot/a247-CMIP-r2/CMIP6/CMIP/EC-Earth-Consortium/EC-Earth3/historical/r2i1p1f1/Omon/tos/gr/v20201215/tos_Omon_EC-Earth3_historical_r2i1p1f1_gr_192401-192412.nc
The infrastructure behind this is run by DKRZ and is not funded to cover projects outside CMIP6 (an possibly not for CMIP6 data added after the AR6 report), so we cannot use it in the same way here. The CMIP5 version of the
tracking_idjust used a unique identifier, such as5a26143c-222d-4cea-aed2-923b45d930c9. This is not resolvable in the same way, but does provide a useful way of tracking files when publication updates lead to multiple files with the same name.I recommend using the CMIP5 version of
tracking_idhere.