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.
What needs to be fixed
| Severity | Code | Where it failed | Why it matters | How to fix |
|---|---|---|---|---|
| FAIL | CORE.ID.UNMATCHED_SAMPLE | samples.tsv → sample_id (row 2 mismatch) | Every file must map to a described sample and vice versa. | Align sample_id across tables. |
| FAIL | GEO.REQUIRED.MISSING_FIELD | metadata.tsv → platform_type (missing) | The repository requires platform_type to process your submission; missing this will delay acceptance. | Add platform_type column with values like 'Illumina HiSeq 2000' or 'Affymetrix Human Genome U133 Plus 2.0 Array'. |
| WARN | CORE.DATE.INVALID_ISO8601 | row 0, column 'collection_date' | Ambiguous dates hurt reuse; a curator will probably ask you to fix this before accepting. | Use ISO8601 (YYYY-MM-DD). |
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.