Table 1 Overview of FAIR recommendations and their implementation for marine images.
Recommendation | Description | Implementation |
---|---|---|
RDA-F1-01M* | Metadata is identified by a persistent identifier | URL:handle@ifdo |
RDA-F1-01D* | Data is identified by a persistent identifier | URL:handle@data |
RDA-F1-02M* | Metadata is identified by a globally unique identifier | image-set-uuid |
RDA-F1-02D* | Data is identified by a globally unique identifier | image-set-uuid |
RDA-F2-01M* | Rich metadata is provided to allow discovery | iFDO format |
RDA-F3-01M* | Metadata includes the identifier for the data | URL:handle |
RDA-F4-01M* | Metadata is offered in a way to be harvested and indexed | iFDO by https |
RDA-A1-01M+ | Metadata contains info to enable accessing the data | URL:handle@data |
RDA-A1-02M* | Metadata can be accessed manually | URL:handle |
RDA-A1-02D* | Data can be accessed manually | URL:MAMS |
RDA-A1-03M* | Metadata identifier resolves to a metadata record | URL:handle@ifdo |
RDA-A1-03D* | Data identifier resolves to a digital object | URL:handle@data |
RDA-A1-04M* | Metadata is accessed through standardized protocol | https |
RDA-A1-04D* | Data is accessible through standardized protocol | https, nfs, … |
RDA-A1-05D+ | Data can be accessed automatically | MAMS-API |
RDA-A1.1-01 M* | Metadata is accessible through a free protocol | https |
RDA-A1.1-01D+ | Data is accessible through a free access protocol | https |
RDA-A1.2-01D | Data is accessible with authentication and authorization | https |
RDA-A2-01M* | Metadata is guaranteed to remain available after data loss | handle system |
RDA-I1-01M+ | Metadata uses knowledge representation in standard format | iFDO format |
RDA-I1-01D+ | Data uses knowledge representation in standard format | e.g. jpg, png, mov |
RDA-I1-02M+ | Metadata uses machine-understandable knowledge representation | yaml |
RDA-I1-02D+ | Data uses machine-understandable knowledge representation | e.g. jpg, png, mov |
RDA-I2-01M+ | Metadata uses FAIR-compliant vocabularies | in preparation |
RDA-I2-01D | Data uses FAIR-compliant vocabularies | in preparation |
RDA-I3-01M+ | Metadata includes references to other metadata | ORCID etc. |
RDA-I3-01D | Data includes references to other data | image-uuid |
RDA-I3-02M | Metadata includes references to other data | image-set-uuid |
RDA-I3-02D | Data includes qualified references to other data | N/A for images |
RDA-I3-04M | Metadata includes qualified references to other data | N/A for images |
RDA-I3-03M+ | Metadata includes qualified references to other metadata | iFDO v2.0.0 |
RDA-R1-01M* | Plurality of accurate and relevant attributes are provided for reuse | iFDO capture & content fields |
RDA-R1.1-01 M* | Metadata includes information about the reuse license | iFDO core fields |
RDA-R1.1-02 M+ | Metadata refers to a standard reuse license | iFDO core fields |
RDA-R1.1-03 M+ | Metadata refers to a machine-understandable reuse license | iFDO v2.0.0 |
RDA-R1.2-02 M | Metadata includes cross-community provenance info | iFDO v2.0.0 |
RDA-R1.2-01 M+ | Metadata includes community-specific provenance info | iFDO capture & content fields |
RDA-R1.3-01 M* | Metadata complies with a community standard | iFDO file format |
RDA-R1.3-01D* | Data complies with a community standard | e.g. jpg, png, mov |
RDA-R1.3-03 M* | Metadata uses a machine-understandable standard | yaml |
RDA-R1.3-02D | Data uses a machine-understandable standard | e.g. jpg, png, mov |