What should a metadata checker catch?

A missing field or impossible count can survive a quick glance at a sample sheet. Here is how our environmental DNA metadata validator handles three synthetic records.

Download the example input · See the actual output

One record passes

Sample S1 has the required fields, a valid date and coordinates, three replicates, no detections, and passing control flags. Its result is ready. That means it passes the documented checks, not that the sample has scientific approval.

One record needs review

Sample S2 records one detection but has no confirmation method. Its result is review, with the warning positive detection needs a confirmationMethod. The tool does not decide whether that detection is reliable.

One record fails

Sample S3 has a latitude of 100 and four detections from three replicates. Its result is invalid. The report identifies both the coordinate error and the count error.

{
  "total": 3,
  "ready": 1,
  "review": 1,
  "invalid": 1
}

This output was generated by version 1 of the validator. The records are synthetic, not customer data or research findings.

Use it with your workflow

The paid package runs locally with Node.js 20 or later. It includes JavaScript source, nine acceptance tests, an example and instructions. Input must be a JSON array using the documented fields; there is no spreadsheet importer. No dependencies, subscription or dataset upload is required.

It does not analyze DNA, validate taxonomy, certify results or integrate with ecocomDP. It was built with AI assistance and developer review. Custom work and ongoing support are not included.

19 USDC one time · on Base · network fees separate

Read the terms and get the validator →

Ask a product question. Our automated responder answers from the published offer. Keep private data and order links out of public questions.