FAIR R1.3 for database evaluation
This feature and the entire section is in active development.
FAIR Principle R1.3: (meta)data meet domain-relevant community standards
https://doi.org/10.25504/FAIRsharing.87d197
FAIR Principle R1.3 requires that (meta)data meet domain-relevant community standards. Within the ARK-based benchmarks, this principle focuses on the extent to which databases adopt, support, and expose community standards and practices that enable FAIR use of their content.
Community standards play a central role in FAIR implementation because they provide shared approaches for describing, exchanging, interpreting, and reusing information. Databases that adopt recognised standards, support community engagement, provide documentation and training, and expose clear information about their scope and content are better positioned to enable FAIR use of the records they contain.
Within the ARK-based benchmarks, R1.3 evaluates both the adoption of community standards and the wider ecosystem of support, documentation, training, and trust signals that help users understand and effectively use a database.
The metrics associated with R1.3 evaluate database governance characteristics relating to standards adoption, community engagement, documentation, trust, and FAIR-support capabilities.
Database FAIR-Enabling Characteristics
🧩
Database defines its community
🧩
Database documents user-facing data submission processes
Presence of documentation for data processes where access method is User Interface and process type includes Write or Read and Write.
🏛
Database adopts community-relevant terminologies or models/formats
Linked terminologies and/or models/formats where at least one subject tag is identical to or a child of at least one of the subject tags within the database record.
🏛
Database follows community-relevant best practices
Linked reporting guidelines where at least one subject tag is identical to or a child of at least one of the subject tags within the database record.
🏛
Database adopts one or more community or general standards to provide at least a minimal level of structured (meta)data
Presence of any linked terminology, model/format, or reporting guideline.
🏛
Database provides support through user-facing help documentation
Support links include at least one Help Documentation entry.
🏛
Database provides community support channels
Support links include one or more of GitHub, mailing list, forum, Facebook, blog/news, or Twitter/X.
🏛
Database supports community interaction
Support links include the presence of community discussion channels such as forum, Facebook, or Twitter/X.
🏛
Database demonstrates external trust or recognition
Presence of one or more badges or certifications.
🏛
Database provides training resources
Support links include the presence of training information or linked TeSS resources.
Future Work
Future iterations of the ARK-based benchmarks may introduce stricter interpretations of standards adoption. For example, evaluations may distinguish between databases that merely reference standards and those that explicitly accept, implement, require, or validate against those standards. Such distinctions are not currently represented consistently within FAIRsharing and are therefore not part of the current benchmark definitions.
Last updated
Was this helpful?
