Help shape a "BIOFAIR-ready" preflight check

Who this is for

• Sequencing cores / wet-lab researchers submitting to GEO/ENA/etc.
• Environmental monitoring / ecology / biodiversity data teams
• Collections managers / data stewards who get stuck cleaning other people’s spreadsheets
• Anyone who has to convince collaborators “no, we actually need ISO dates and site IDs, I’m not being difficult”

What FAIRy does today

• Runs locally / offline before you submit data anywhere
• Checks basic metadata and structure
• Gives you PASS / WARN / FAIL with “why it matters” and “how to fix”
• Generates a shareable, data-free readiness sheet you can send to PIs, curators, or collaborators

What I’m looking for now

I’m lining up 1–2 pilot partners in different domains to co-develop tiny “readiness rulepacks.”

Here’s what that means:

• We write down the 5–7 “don’t publish without this” metadata fields you absolutely need in your world (e.g. stable sample/site ID, ISO date, location/site, method/instrument, contact).
• FAIRy enforces that locally and generates a data-free PASS / WARN / FAIL sheet plus fix hints.
• You can attach that sheet to submissions, internal handoffs, data management plans, etc.
• I’ll summarize the most common blockers (e.g. missing site coordinates, non-ISO dates, unclear method) and share those patterns — without your raw data — back to the BIOFAIR community as gap analysis.

What you get

• A data-free readiness sheet (PASS / WARN / FAIL + how to fix) you can show to a PI, collaborator, repository, program officer, etc.
• A short internal summary of the top recurring issues FAIRy found, which you can reuse when you argue for better upstream metadata practices.
• Acknowledgment as an early contributor when I circulate the first “BIOFAIR-ready preflight” pattern back to this community.

How much time is this?

• Express (≈ 90 min, 1 week): tiny sample → one pass with FAIRy → readiness sheet.
• Standard (≈ 3–5 hrs, 2 weeks): one iterate-and-re-run loop + short “top blockers” summary.
• Deep-dive (≈ 6–8 hrs, 4 weeks): a couple of loops + a v0 rulepack draft and teaching note.

No raw data needed. We can do this mostly async; calls optional.