Datasets that the CLARIAH Dataset Register harvests from the NDE Dataset Register will have to contain a FAIR assessment. Because of the differences between CLARIAH communities (CLARIN, NDE and others), it’s unlikely that we’ll end up with single FAIR Implementation Profile (FIP) for CLARIAH.
Therefore, we decided with @menzowindhouwer that each community itself will do the assessment, and make that available in an agreed-upon exchange format for CLARIAH to harvest.
For NDE, it will be hard to build an analyser, due particularly the FAIR requirements that apply to the level of the data objects, as these are very heterogeneous between heritage organisations (see the ‘NDE’ column in the FIP linked above). A possible solution is self assessment, where we ask dataset publishers to supply FAIR metrics for points we cannot validate, trusting their input. The future DANS Compliance Assessment Toolkit will also work this way.
Datasets that the CLARIAH Dataset Register harvests from the NDE Dataset Register will have to contain a FAIR assessment. Because of the differences between CLARIAH communities (CLARIN, NDE and others), it’s unlikely that we’ll end up with single FAIR Implementation Profile (FIP) for CLARIAH.
Therefore, we decided with @menzowindhouwer that each community itself will do the assessment, and make that available in an agreed-upon exchange format for CLARIAH to harvest.
For NDE, it will be hard to build an analyser, due particularly the FAIR requirements that apply to the level of the data objects, as these are very heterogeneous between heritage organisations (see the ‘NDE’ column in the FIP linked above). A possible solution is self assessment, where we ask dataset publishers to supply FAIR metrics for points we cannot validate, trusting their input. The future DANS Compliance Assessment Toolkit will also work this way.
For some context, see also the CLARIAH FAIR data requirements and #9.