Criteria for revision r1 · fixed when you start an Attempt
Verified when a reviewer with ORD curation experience accepts the dataset as a valid, faithful and complete Open Reaction Database dataset of the paper bound in card, and the sources archive rebuilds it and records ORD's validator output.
Checks run in this order. Open a step to inspect its rules, checker or review rubric.
A reviewer with ORD curation experience compares the dataset with the paper: coverage, structures, amounts, conditions, outcomes and provenance, and checks the validator output in the sources archive.
Eligible reviewers must complete the pinned rubric. Seat availability and completion are not guaranteed.
Compare the dataset with the paper named in card (its tables and Supporting Information), using the sources archive to see how it was built. Pass only if you would accept it into ORD after at most cosmetic fixes. Check: validation.txt in the sources archive shows ORD's validator (ord-schema 0.8.3) passing this exact dataset file with no errors (re-run it if in doubt); every reaction in the stated scope is present and none is invented; every SMILES matches the compound the paper names (enumeration mix-ups, one abbreviation mapped to two structures, a similar compound substituted); amounts, reaction roles, conditions and workups (internal standards belong in the workup); outcomes (is_desired_product, yields within 0-100% with an analysis); provenance (the paper's DOI, a real curator name and email); a meaningful dataset name and description. List every defect you find, with where it is.
coverage · required "complete" / "partial" / "insufficient"defects · required arrayverdict · required "pass" / "fail" / "uncertain"{
"additionalProperties": false,
"properties": {
"coverage": {
"description": "How much of the paper's in-scope reaction data the dataset captures.",
"enum": [
"complete",
"partial",
"insufficient"
]
},
"defects": {
"items": {
"additionalProperties": false,
"properties": {
"severity": {
"enum": [
"must_fix",
"should_fix",
"note"
]
},
"what": {
"maxLength": 1000,
"type": "string"
},
"where": {
"maxLength": 300,
"type": "string"
}
},
"required": [
"severity",
"where",
"what"
],
"type": "object"
},
"maxItems": 200,
"type": "array"
},
"verdict": {
"enum": [
"pass",
"fail",
"uncertain"
]
}
},
"required": [
"verdict",
"coverage",
"defects"
],
"type": "object"
}{
"reviewers": {
"allowed": null,
"assistance": {
"allowed": [],
"required": false
},
"count": 1,
"eligibility": {
"organization_id": null,
"rule": "campaign_reviewers",
"user_ids": null
},
"independent": true,
"kind": "human"
},
"conflicts": {
"exclude_submitter": true,
"exclude_submitter_organization": false
},
"visibility": {
"hidden": [
"submitter_identity",
"submitter_organization"
],
"prior_nodes": [],
"stage_evidence": true
},
"skills": [
{
"requirement": "required",
"skill_version_id": "skv_k5sivlohu1"
}
]
}verdict equals "pass". Reject when at least 1 have verdict equals "fail". Otherwise unresolved.curator · decisionFinal outcome comes from decision. Accept passes this stage; reject refutes it; unresolved is inconclusive. All verification stages must pass.
rpt_mumofu1g8rsha256:b603bab4f3d212cc983c1ec2ba54252a4b34cf47fe3362387f1e5783b8daaa8dRead the complete pinned protocol →
{
"output": "decision",
"policy": {
"assignment_timeout_hours": 336,
"claim_hold_minutes": 1440
}
}dataset — The ORD Dataset, compressed: .binpb.gz, .pb.gz, .txtpb.gz, .pbtxt.gz or .parquet. No dataset or reaction IDs. · up to 25 MBsources — A .zip with a README, the template and spreadsheet or the script or notebook that rebuild the dataset, and validation.txt: the output of ORD's validator (ord-schema 0.8.3) on the dataset. · up to 25 MBA text-only Submission is not accepted.
card · requiredcard.json ↗application/json · 3.6 KBRevision prv_5uv21m28nv
Contract vct_4t6ri8zibj
Complete evaluation Contract →
[
{
"key": "card",
"content_hash": "sha256:8fc6caa8b686c9deac7da9e68773a2ad8cbb41eefd2500be3a52e00b9102107b",
"size_bytes": 3717,
"media_type": "application/json",
"filename": "card.json"
}
]