FAIR F3 for database evaluation
This feature and the entire section is in active development.
FAIR Principle F3: Metadata clearly and explicitly include the identifier of the data they describe
https://doi.org/10.25504/FAIRsharing.820324
FAIR Principle F3 requires that metadata clearly and explicitly include the identifier of the data they describe. Within the ARK-based benchmarks, this principle focuses on whether database metadata explicitly identifies both itself and the database it describes.
This principle supports unambiguous relationships between metadata and the resources they represent. Clear identifier relationships help users, machines, and assessment services reliably determine which database is being described and which metadata record is being evaluated.
Within the ARK-based benchmarks, F3 is interpreted through two complementary requirements:
the machine-actionable metadata describing the database should contain the identifier of that metadata record itself;
the metadata should also contain the identifier of the database being described.
The metrics associated with F3 evaluate whether these identifier relationships are explicitly represented within FAIRsharing database metadata.
Database FAIR-Enabling Characteristics
🏛
Database metadata explicitly identifies itself and the database it describes
Presence of both a FAIRsharing record identifier (DOI and/or FAIRsharing URL) and a database homepage URL within the FAIRsharing metadata representation.
Future Work
The current ARK-based benchmarks evaluate the presence of identifiers describing both the FAIRsharing record and the database it represents. Future versions may introduce stricter evaluations of these identifiers, including assessment of their persistence, global uniqueness, and resolvability characteristics. Note, however, that such evaluations would likely be addressed separately through the F1 metrics.
Last updated
Was this helpful?