FAIRy

Example FAIRy Submission Readiness Report

Don't wait for the repository to reject your submission. Run FAIRy before you upload, and you'll see exactly what needs to be fixed — missing fields, formatting issues, inconsistent IDs — all with clear instructions on how to resolve them.

The report below shows what FAIRy generates. Fix the issues it flags, and you can submit with confidence — once, not four times.

Submission Readiness Summary
Rulepack: geo_bulk_seq@0.2.0
FAIRy version: 0.2.2
Generated locally:
1 FAIL / 1 WARN
Issues found that need attention before submission

Provenance: FAIRy preflight (local run)

Command used:
fairy preflight --rulepack rulepacks/geo_bulk_seq/v0_2_0.json --samples rulepacks/geo_bulk_seq/fixtures/samples_bad.tsv --files rulepacks/geo_bulk_seq/fixtures/files.tsv --out .tmp/geo_bulk_seq_report.json

File hash digest (so you can prove which exact files were checked):

SHA256 manifest:
samples.tsv: 96ae14a766369c0ab581bf7dc16af186fc732139adc23eb438d8de47ad49e798
files.tsv: 3305edf715ad6f1bf9ade6ee48cfc84e6599d25e42cf2a32d8741a32185ed348

What needs to be fixed

SeverityCodeWhere it failedWhy it mattersHow to fix
FAILGEO.BIO.CONTEXT_MISSINGrow 1Sample does not provide tissue/cell_line/cell_type.Fill at least one of: tissue, cell_line, or cell_type fields in your sample metadata.
WARNCORE.DATE.INVALID_ISO8601row 1, column 'collection_date'Value is not ISO8601 (YYYY-MM-DD).Use ISO8601 date format (YYYY-MM-DD), e.g., 2025-10-02.
FAIRy runs locally. You can forward this report as-is to a collaborator, student, or PI and say, "Please fix these before I can accept this dataset." No raw data is included — just the problems and how to resolve them.

See how FAIRy's rulepacks map to real repository requirements in our documentation.

Related

Try FAIRy → Run the demo to generate reports like this (2 minutes)Request a pilot → Get custom rulepacks for your institutionFor institutions → Learn about pilot programs and offerings