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 500 reactions; HTE): 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.
HTE and machine learning for enantio- and regioselective mono-reduction of 1,2-dicarbonyls, about 500 reactions. The ORD card cites the ChemRxiv preprint (10.26434/chemrxiv-2025-n3gff, CC BY-NC-ND 4.0), where the data is in SI Tables S2-S4 as plate images. Values would need image extraction, and compound SMILES must be generated from structures. A peer-reviewed version has been published in Angew. Chem. Int. Ed. (10.1002/anie.202519425); check whether its SI provides the data in a more usable form. The dataset should cite the published DOI (and the preprint). Obtaining numeric data (e.g. ee/regioselectivity/conversion tables) from the authors would substantially reduce extraction error.
Known locations:
Outcomes include enantioselectivity (ee) and regioselectivity, which need stereo-aware product SMILES. Values read from plate images carry transcription uncertainty. Preprint and published SI may disagree.
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.