FAIRness of WDCC - technical details

The self-evaluation of the FAIRness of WDCC as described here is based on the point-by-point evaluation of WDCC characteristics regarding the FAIR data guiding principles as detailed and published by the GOFAIR Initiative. Here, we show the results of this detailed evaluation in tabular form (see below).
FAIR PrinciplesWDCC SpecificationFAIRness of WDCC specifications?
F1: (meta) data are assigned globally unique and persistent identifiers
Data is included into the OAIS AIP Content Data Objects (Fig. 1 on the summary page)
Metadata is included into the OAIS AIP
The AIPs are identified by DataCite DOIs
OAIS binds are dataset URLs which include the WDCC entry_acronym, e.g.

https://www.wdc-climate.de/ui/entry?acronym=CEOP2_NCEP_GRID_B
DataCite DOI assignment on OAIS AIP (WDCC Experiment/Dataset group)
F2: data are described with rich metadata If WDCC metadata have reached the ‘completely archived’ state then they are described with rich metadata (OAIS AIPs are complete)
WDCC (Experiment/Dataset_group and Datasets) are 'completely archived'.
During the DOI publication process, the metadata are extended with additional metadata, e.g. accuracy and statistical reports, which increases re-usability. (see Fig. 3 on the summary page)
F3: metadata clearly and explicitly include the identifier of the data they describe If WDCC metadata have reached the ‘completely archived’ state then they are described with AIP 'PDI-Reference' (Fig. 2 on the summary page) and 'Package Info - identifier' (OAIS AIPs are complete)
WDCC (Experiment/Dataset_group and Datasets) are 'completely archived'.
With a DataCite DOI assignment the identifier becomes persistent.
F4: (meta)data are registered or indexed in a searchable resource
Metadata records are available for external harvesters through an OAI PMH interface and a mapping to the Dublin Core, ISO 19135 and DataCite XML metadata sets.
Important harvesters currently active are DWD-Gisc, WDS and Google dataset search. Moreover, WDCC data with DOIs are visible in EUDAT B2FIND. Finally, the local WDCC GUI offers to search and browse.
WDCC (Experiment/Dataset_group and Datasets) are 'completely archived'.
With a DataCite DOI assignment the (meta)data obtain increased visibility.
A1: (meta)data are retrievable by their identifier using a standardised communication protocol
Data and metadata are accessible via HTTP.
Metadata harvesting via OAI PMH
For data access, a login is required (WDCC account)
metadata: FAIR
data: WDCC (Experiment/Dataset_group and Datasets) are 'completely archived'.
A1.1: the protocol is open, free and universally implementable HTTP and OAI-PMH are open, free and universally implementable. FAIR
A1.2: the protocol allows for an authentication and authorisation when required
Metadata is openly accessible.
For data access, authentication is required with user account (HTTP). The WDCC has published its terms of use </a>
metadata: FAIR
data: WDCC (Experiment/Dataset_group and Datasets) are 'completely archived'.
A2: metadata should be accessible even when the data is no longer available If data are lost or removed for any reason, remaining metadata remain available but can be changed. In particular, metadata may be modified to indicate the cause of data removal or loss. FAIR
I1: (meta)data use a formal, accessible, shared, and broadly applicable language for knowledge representation
Dublin Core, ISO 19135 and DataCite XML schema mappings are openly accessible for all metadata.
Data are stored in domain specific open file formats. Data content relies on commonly used controlled vocabularies, particularly the CF conventions.
metadata: FAIR
data: FAIR
If other data formats are used, these need to be assessed according to FAIR specifications.
I2: (meta)data use vocabularies that follow the FAIR principles
CF–netcdf is publicly documented and openly accessible. Making these conventions citable via DOIs is an ongoing discussion within the CF committee.
metadata: FAIR, e.g. DataCite vocabularies
data: FAIR (CF-netcdf)
Citable conventions via DOIs would increase FAIRness
If other data formats are used, these need to be assessed according to FAIR specifications.
I3: (meta)data include qualified references to other (meta)data The relations possible to specify via the DataCite ‘relationType’ attribute are implemented in WDCC and are accessible from the WDCC web user interface and the harvesting interfaces.
Every OAIS AIP needs specification:
references exist in WDCC table y/n
R1: (meta)data are richly described with a plurality of accurate and relevant attributes In general, WDCC metadata contain rich information about the context in which data was generated, ensured by the metadata requirements for data submission (see also F2).
data: FAIR
Specifically, items covered by WDCC metadata are relevant timestamps (creation and collection date), conditions under which data were created, actors involved in preparing the data, and model-related technical attributes such as model parameters and model descriptions.
During the DOI publication process, the metadata are extended with additional metadata e.g. accuracy and statistical reports (see F2).
Observational data also include error estimates for accuracy and usability assessment.
R1.1: (meta)data are released with a clear and accessible data usage license Metadata is released under CC0 universal license terms. The data licenses are dependent on the user. However, WDCC recommends using CC-by 4.0. FAIR
R1.2: (meta)data are associated with detailed provenance WDCC metadata includes basic provenance information such as:
  • Citation information: WDCC references DOI authors.
  • The workflow that led to the data: WDCC project and experiment summary
  • Who generated or collected it: DOI authors and contributors
metadata provenance: contact type 'metadata' in block contact is required.
data: DataCite DOI assignment on OAIS AIP (WDCC Experiment/Dataset_group)
R1.3 (meta)data meet domain-relevant community standards Most metadata meet relevant community standards, in particular, CF-netcdf and the DataCite metadata kernel (cf. I1, I3).
Projects meet domain-relevant community standards: y/n
data: FAIR data format CF-netcdf.
Other formats need FAIR specification