CASRAI Dictionary

Tag: go fair initiative

  • FAIR Data Point: Making Data Machine-Actionable

    A FAIR data point is a lightweight metadata server that exposes structured, standardised descriptions of a dataset — its identifier, creator, licence and access route — through a REST API, so software (not just people) can discover and assess it automatically. Under the GO FAIR implementation network, FAIR Data Points are the working infrastructure that turns the FAIR principles from a policy statement into a queryable service.

    In formal terms, a FAIR Data Point (FDP) is a metadata repository that follows the DCAT2 vocabulary and organises records in a fixed hierarchy — repository, catalogue, dataset, distribution — using Linked Data Platform containers, as set out in the peer-reviewed FDP specification (da Silva Santos et al., 2023, Data Intelligence, MIT Press).

    What Is a FAIR Data Point?

    A FAIR Data Point separates metadata from data. It does not host the dataset itself; it hosts a machine-readable description of the dataset, reachable at a stable HTTP endpoint. This separation is what makes the metadata queryable independently of wherever the underlying files are actually stored.

    The reference specification defines four nested layers, each exposed as its own resource:

    • Repository — the top-level FDP instance, describing the organisation or project running it
    • Catalogue — a themed grouping of related datasets
    • Dataset — the described research object, with identifier, creator, licence and rights statement
    • Distribution — the concrete access point (a download URL, an API, a query service)

    Every layer is exposed via a REST API and encoded as RDF using the DCAT2 vocabulary, which is why an FDP can be crawled and indexed by external harvesters without bespoke integration work per institution.

    How Does the GO FAIR Initiative Use FAIR Data Points?

    GO FAIR is a grassroots, community-run implementation network for the FAIR principles, not a standards body with formal ownership of a single specification. It organises its work around three self-described pillars — GO CHANGE (policy and culture), GO TRAIN (skills) and GO BUILD (technical infrastructure) — coordinated through the GO FAIR Foundation.

    FAIR Data Points sit inside the GO BUILD pillar. GO FAIR pairs FDPs with FAIR Implementation Profiles (FIPs): a documented set of choices a specific research community makes about identifiers, vocabularies, access protocols and licensing terms. The FIP tells an FDP deployment which controlled vocabularies to use at the dataset and distribution layers, so that metadata from two unrelated institutions in the same domain remains interoperable rather than merely similar.

    The combined goal is what GO FAIR calls the “Internet of FAIR Data & Services” — a distributed network of FDPs that automated agents can traverse to locate relevant data without a central index. A working example already in production is the European Joint Programme on Rare Diseases (EJP RD) Virtual Platform, whose index runs on a federated network of FDPs contributed by member registries across Europe, funded through the EU Horizon research programme.

    FAIR Data Point vs Machine-Actionable DMP: What Is the Difference?

    The two are frequently conflated because both are described as “machine-actionable,” but they describe different objects at different points in the research lifecycle. A machine-actionable Data Management Plan (maDMP) — built on the Research Data Alliance’s DMP Common Standard and served by tools such as DMPTool or DMPonline — describes intentions: what data a project will produce, where it will deposit it and under what licence. An FDP describes an already-deployed dataset that a machine can query right now.

    Aspect FAIR Data Point Machine-Actionable DMP
    Lifecycle stage Post-deposit, dataset already exists Pre-project, data not yet produced
    Governing spec GO FAIR / FDP specification (DCAT2, LDP) RDA DMP Common Standard
    Query interface REST API over a live metadata service JSON export or plan-management tool API
    Granularity Per dataset / per distribution Per project or funding award
    Typical operator Data repository or institutional archive Institution, funder, or research office

    Confusing the two leads institutions to procure the wrong tool: an maDMP platform will not make a finished dataset crawlable, and an FDP deployment will not help a project plan its future data management obligations.

    How Is FAIRness Measured? The F-UJI Evaluator

    F-UJI is an automated FAIR assessment tool developed under the Horizon 2020 FAIRsFAIR project. It scores a dataset’s exposed metadata — including metadata served by an FDP — against a fixed set of maturity indicators grouped under the four FAIR facets, returning a numeric FAIRness score rather than a binary pass/fail.

    F-UJI can only evaluate what is machine-visible: it checks whether a licence, persistent identifier or access protocol is declared in the metadata, not whether the underlying data file is actually reusable in practice. This is precisely why the metadata layer an FDP provides matters — a well-structured FDP deployment is what allows a tool like F-UJI to detect FAIRness signals automatically, while a plain data-download page with no structured metadata will score poorly regardless of how well-organised the actual dataset is.

    Where Does DDI Fit Into the FAIR Data Point Stack?

    The Data Documentation Initiative (DDI) is an XML/RDF metadata standard maintained by the DDI Alliance for describing social, behavioural and economic science data at the variable level — survey questions, coding frames, sampling design. DCAT2, the vocabulary an FDP uses by default, describes a dataset at the catalogue-entry level; it was never designed to capture variable-level detail.

    A research community whose FAIR Implementation Profile specifies DDI alongside DCAT2 gets both: FDP-level crawlability for discovery, and DDI-level granularity for reuse. Social-science archives affiliated with the Consortium of European Social Science Data Archives (CESSDA) and the UK Data Service already publish DDI metadata; wiring that metadata into an FDP endpoint is a genuine interoperability gain rather than duplicated effort.

    Frequently Asked Questions

    What is a FAIR data point?

    A FAIR Data Point is a metadata repository that exposes a dataset’s identifier, licence, creator and access route through a REST API, structured according to the DCAT2 vocabulary. It publishes metadata about data, not the data itself, so automated tools can discover and evaluate the dataset without human involvement.

    What does FAIR data mean?

    FAIR data meets the 2016 principles of Findability, Accessibility, Interoperability and Reusability, first formally published by Wilkinson et al. in Scientific Data. The principles apply to metadata as much as to the underlying files, which is why machine-readable metadata infrastructure, such as an FDP, is required to satisfy them at scale.

    What are the four pillars of the FAIR data principles?

    The four pillars are Findable (a persistent identifier and rich metadata exist), Accessible (metadata is retrievable via an open protocol, even if the data itself is restricted), Interoperable (metadata uses a shared, formal vocabulary such as DCAT2), and Reusable (a clear licence and provenance are attached).

    What This Means for Data Stewards and Developers

    Deploying a FAIR Data Point is an infrastructure decision, not a documentation exercise. In practice it requires three steps: agreeing a FAIR Implementation Profile with the relevant research community, mapping local repository metadata onto DCAT2 at the dataset and distribution layers, and registering the resulting endpoint so external harvesters and tools such as F-UJI can find it.

    • Pair persistent dataset identifiers from DataCite with the FDP’s dataset layer so citation and discovery metadata stay consistent
    • Use ROR identifiers for the institutional agent fields rather than free-text organisation names
    • Treat the FDP as complementary to, not a replacement for, an maDMP — one documents intent, the other serves the finished product

    Funders are moving in this direction: the UNESCO Recommendation on Open Science (2021) names FAIR data as a foundational pillar, and Horizon Europe grant conditions increasingly expect data to be discoverable by machines, not just listed in a repository catalogue. For institutions building research-data infrastructure now, a standards-conformant FAIR Data Point is a defensible way to demonstrate machine-actionability rather than assert it in a data management plan.

    For related definitions and terminology, see the CASRAI dictionary and the research administration pillar.

  • F-UJI FAIR Evaluator: What It Actually Scores

    The F-UJI FAIR evaluator is an automated web service that checks whether a dataset’s metadata — not its actual data quality — satisfies a fixed set of machine-readable tests built from the FAIRsFAIR Data Object Assessment Metrics. A high F-UJI percentage means a dataset’s landing page, identifiers and schema exposed enough structured signals for a script to find and parse; it does not certify that a human researcher can actually understand, trust or reuse the data inside.

    F-UJI is one of several tools now used to operationalise the FAIR Data Principles (Findable, Accessible, Interoperable, Reusable), alongside FAIRshake, FAIR-Checker, FAIR Aware and the FAIR Data Point specification promoted by the GO FAIR Initiative. This article explains what each type of tool actually scores, where automated scoring diverges from manual FAIR maturity review, and why institutions and research data repositories should treat a high machine score as a floor, not a finish line.

    What is the F-UJI FAIR evaluator?

    F-UJI (FAIRsFAIR Research Data Object Assessment Service) is a web service and REST API that assesses a research data object against 16 core FAIR metrics. A user submits a persistent identifier — typically a DOI — and F-UJI queries external infrastructure including the DataCite API, re3data, schema.org JSON-LD embedded on the landing page, and DCAT or Dublin Core fields to determine whether each metric passes.

    The metrics were developed under the EU Horizon 2020 FAIRsFAIR project (2019–2022) and are now maintained and versioned by its successor, the FAIR-IMPACT project, with the metric set published as a citable release (DOI 10.5281/zenodo.15045911). F-UJI’s source code is maintained on GitHub by the PANGAEA data publisher, and the tool is offered as a free public assessment service and API.

    How F-UJI’s automated scoring actually works

    F-UJI does not read the dataset’s content. It inspects the metadata surrounding the dataset — the landing page markup, the identifier’s resolution behaviour, declared licences, and machine-readable provenance fields — and scores each of the 16 metrics as pass, partial or fail. The overall percentage is a weighted sum across the Findable, Accessible, Interoperable and Reusable metric groups.

    • Findable metrics check for a persistent identifier, whether the metadata is indexable by search engines, and whether the identifier resolves to rich metadata.
    • Accessible metrics check that metadata remains retrievable even if the data itself becomes unavailable, and that access protocols are standard.
    • Interoperable metrics check for structured vocabularies declared in a JSON-LD @context (schema.org, DCAT, PROV-O) and for qualified references to related resources.
    • Reusable metrics check for a machine-readable licence, provenance statements, and a community-recognised file format for the data’s actual distribution.

    A documented example from the FAIR Data Innovations Hub illustrates how mechanical this scoring is in practice: a dataset scored 67% on its first F-UJI run, with the Findable, Interoperable and Reusable metrics flagged for missing JSON-LD context, missing PROV-O provenance fields and an undeclared distribution format. After the maintainers added a single enriched schema.org/PROV-O JSON-LD block to the landing page — without changing the underlying data at all — the same dataset scored 100% on re-assessment. The data did not become more reusable in that interval; its metadata simply became more machine-legible.

    F-UJI vs FAIRshake vs manual maturity frameworks

    F-UJI is not the only FAIR assessment approach in circulation, and the three main categories differ in what they actually test and who defines “FAIR” for the purpose of the test.

    Dimension F-UJI FAIRshake Manual maturity review
    Method Fully automated, no human input Hybrid — automated tests plus human-scored rubrics Fully manual, questionnaire/checklist-based
    Basis of criteria Fixed FAIRsFAIR/FAIR-IMPACT metric set Community-defined rubrics per research domain Institution- or project-specific checklist
    Input required A persistent identifier (e.g. DOI) A URL, via web interface or browser extension The dataset, documentation and reviewer time
    Output Percentage score per metric and overall Nine-square “FAIR insignia” visualisation Narrative report with recommendations
    Scalability High — suited to bulk repository audits Moderate Low — resource-intensive
    Contextual nuance Low — rigid, rule-based Moderate — rubrics can be domain-tailored High — accounts for discipline-specific reuse

    FAIRshake was originally developed by the Ma’ayan Laboratory at the Icahn School of Medicine at Mount Sinai under the US National Institutes of Health’s Big Data to Knowledge (BD2K) programme. Rather than one fixed metric set, it lets research communities author their own rubrics and score resources — manually, automatically, or both — against them, then renders the result as a colour-coded insignia rather than a single number.

    The GO FAIR Initiative takes a different, upstream approach: instead of scoring existing datasets after the fact, it promotes the FAIR Data Point (FDP) specification — a layered REST API (FAIR Data Point → Catalog → Dataset → Distribution) that a research data repository implements so that FAIRness is built into how metadata is served, rather than retrofitted and then measured.

    What a high FAIR score does not prove

    A 100% F-UJI score is a statement about metadata exposure, not about data quality, ethical provenance, statistical validity, or whether another researcher can actually rerun the analysis. This distinction matters because automated tools are increasingly cited in funder and repository policy discussions as if they were a proxy for genuine reusability.

    • A perfectly scored dataset can still contain undocumented preprocessing steps, missing sample metadata, or errors that no metadata check can catch.
    • F-UJI cannot verify that a licence field is legally accurate — only that a machine-readable licence field exists.
    • None of F-UJI, FAIRshake or FAIR Aware assess whether the underlying research methodology or data collection itself was sound; that remains a peer-review and domain-expert function.
    • Scores are not comparable across tools: a dataset scoring 67% on F-UJI is not equivalent to 67% “FAIR” on any absolute scale, since each tool’s metric weighting differs.

    A ScienceDirect study (Devaraju et al., 2021, cited more than 90 times) frames this precisely, describing F-UJI-based measurement as “centred on core metrics” that apply until domain- or community-specific FAIR criteria are agreed — an explicit acknowledgement that the automated baseline is deliberately generic, not a final word on reusability.

    Common questions about automated FAIR scoring

    What does F-UJI actually measure?

    F-UJI measures whether a dataset’s metadata — its identifier, landing-page markup, licence declaration and provenance fields — meets 16 machine-testable criteria drawn from the FAIRsFAIR/FAIR-IMPACT metric set. It does not inspect or validate the dataset’s actual content, methodology or scientific accuracy.

    Is a high F-UJI score the same as genuinely FAIR data?

    No. A high score confirms that metadata is machine-readable and complete according to a fixed rule set. Genuine reusability additionally depends on documentation quality, data integrity and domain-specific context that automated tools are structurally unable to evaluate.

    How does FAIRshake differ from F-UJI?

    FAIRshake combines automated tests with human-scored, community-defined rubrics, whereas F-UJI applies one fixed metric set with no human input. FAIRshake reports results as a visual “FAIR insignia” rather than F-UJI’s single percentage score.

    Do funders formally require automated FAIR scores?

    No major funder currently mandates a specific F-UJI or FAIRshake score as a compliance threshold. Funder and institutional policies (for example under Horizon Europe and UKRI) reference the FAIR Data Principles as a qualitative expectation, with automated tools used voluntarily to self-check progress.

    Implications for repositories and funders

    For research data repositories, the practical use of F-UJI is diagnostic, not evaluative: it flags specific, fixable metadata gaps — a missing JSON-LD block, an undeclared licence field, an absent provenance statement — far faster than a manual audit could. Repositories improving their F-UJI scores should treat each metric failure as a discrete engineering task, not as a proxy for a broader data-quality programme.

    For institutions and funders assessing compliance, the more defensible approach combines automated metadata scoring as a first-pass filter with a manual or community-rubric review for anything reused in decision-relevant research. Relying on one automated percentage to certify “FAIR” data risks the same error as equating a spellchecker’s clean pass with a well-argued essay: necessary, not sufficient.

    As the GO FAIR Initiative’s FAIR Data Point specification gains adoption, the balance may shift from retrospective scoring toward FAIRness built into repository infrastructure from the point of deposit — making after-the-fact tools like F-UJI a verification step rather than the primary mechanism for achieving reusable research data.