Metadatapp logoMetadatapp

FAIR-by-Design approach

Maximize scientific insight while minimizing animal use by making every asset findable, accessible, interoperable, and reusable.

FAIR as workflow

  • Capture metadata at the point of experiment
  • Validate with schemas and controlled vocabularies
  • Reuse-ready assets for analytics and AI
Learn More

Standards alignment

  • SEND, IND, and IMPD-aligned structures
  • Audit trails and traceability across studies
  • Evidence packages aligned with expectations
Learn More

FAIR pillars in practice

Findable

F1. Globally unique, persistent identifiers

  • HTTP URI per entity (e.g., https://api.metadatapp.net/v2/Experiment/{id}) with content negotiation.
  • Relay-style id: ID! as persistent key; DOIs/ARKs for published datasets.
    F2. Rich metadata descriptions
  • Keywords, abstract, methods + JSON-LD contexts for harvesting.
    F3. Metadata includes data identifiers
  • Embed @id in JSON-LD and return id prominently in GraphQL payloads.
    F4. Indexed, searchable resources
  • Elastic/Solr index, faceted search, /search REST alongside GraphQL.

Accessible

A1. Retrievability via standard protocol

  • HTTPS REST + GraphQL; JSON and JSON-LD via Accept negotiation.
    A1.1. Open, free protocols
  • HTTP(S)/GraphQL, documented via OpenAPI/introspection.
    A1.2. Auth where necessary
  • OAuth2/JWT scopes (Keycloak/Auth0), Symfony security; public metadata when possible.
    A2. Metadata persistence
  • Retain metadata even if raw data is archived; expose status/provenance.

Interoperable

I1. Formal, shared language

  • JSON-LD context/RDF schema mapping GraphQL types to Schema.org/OBO; SPARQL for federation.
    I2. Community vocabularies
  • NCBI Taxonomy, EDAM, OBO terms; validate on ingestion.
    I3. Qualified references
  • Resolvable URIs with relation metadata; GraphQL edges with cursor + node.id; relation types in JSON-LD.

Reusable

R1. Rich description

  • Provenance (createdBy/At, modifiedBy/At), license, usage notes; domain fields (dose, protocol, environment).
    R1.1. License
  • Top-level license (CC0/CC-BY) exposed machine-readably; UI license picker.
    R1.2. Detailed provenance
  • Auto-track “who did what when” via triggers/events; expose provenance subtype in GraphQL.
    R1.3. Community standards
  • Validate against ARRIVE/MIAME/other schemas at ingestion; UI templates enforce required fields.

Need a FAIR plan?

See how Metadatapp implements FAIR in practice and how it supports the 3Rs.

Talk to us