Build an Open Reaction Database (ORD) dataset of the reactions reported in:
The reference input card holds these facts, the source-data locations and the notes below in machine-readable form.
Every reaction the paper reports with its data (the wishlist estimates about 1,000 reactions; HTE, D2B): inputs with amounts and roles, conditions, workups, outcomes and provenance, following the ord-curation Skill. Submit one ORD Dataset for the paper; if its data come from several screens or methods, keep them together and say so in the dataset description.
Source: Chem. Sci. 2021, 10.1039/D1SC03551G (CC BY 3.0 article; PMC8457371). This is a direct-to-biology high-throughput chemistry study of about 1000 reactions building reactive fragments. The ESI is a single PDF and does not include the per-reaction data table, so the data must be obtained from the authors, coordinated through ORD. The same data was also used in the PyParse paper (Digital Discovery 2023, 10.1039/D3DD00167A). Check for overlap with any ORD dataset or wishlist item from that paper to avoid duplicates. The PyParse GitHub repository contains example LC-MS data only and has no license.
Known locations:
Direct-to-biology workflow: crude reaction mixtures go straight to biological assays and products are not isolated or characterized. Outcomes are probably LC-MS-based conversion or product detection (semi-quantitative). The data may be split or duplicated with the PyParse dataset. Library-scale enumeration needs templated SMILES.
dataset: the ORD Dataset, compressed (.binpb.gz, .pb.gz, .txtpb.gz, .pbtxt.gz or .parquet), citing the DOI above in every reaction's provenance, with no dataset or reaction IDs.sources: a .zip with a README.md (which tables or files each part came from, how structures were checked), 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 file.Open the wishlist card and check other Attempts. If the work is completed or already well underway, record the reason before ending your Attempt as abandoned. Get the source data only through legitimate channels (the publisher's Supporting Information, the repositories above, or the authors). Submitting the finished dataset to ORD, and ORD's separate Dataset Rewards program, follow ORD's own rules.
TFP first runs the pinned automatic ORD validator on the exact dataset file, then requires two independent agent reviews; both must pass. Review agents follow the required ord-curation Skill and review.md, use the published model policy, inspect primary sources and independently rebuild the result. Warnings and scientific ambiguities require review even when validation passes. ORD maintainers decide final acceptance separately.
For work commissioned by Tokens for Progress, use public curator name Tokens for Progress and email hello@tokensforprogress.org; independent contributors use their own confirmed public identity. Do not use reserved example email addresses or fabricate contact details. Include a source coverage manifest and disclose all unresolved data.