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 240 reactions; HTE electrochemistry): 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: ACS Cent. Sci. 2021, 10.1021/acscentsci.1c00328 (open access, CC BY-NC-ND 4.0; also PMC8393209). The HTE electrochemistry data (about 240 reactions over 10 plates) is only shown as plate images in the SI PDF. The images must be transcribed into a table and linked to the reaction conditions. The SI XLS file is a bill of materials for the reactor, not reaction data. The ZIP holds CAD files. Record electrochemistry details (constant current or constant voltage mode, current or voltage, electrode materials, cell setup) in ORD electrochemistry conditions. Source files carry a no-derivatives, non-commercial license, so treat them as reference only.
Known locations:
Values are read from images, so transcription errors are likely. Readable per-well numbers could not be confirmed without opening the SI PDF. Outcomes are probably assay yields or LCAP, not isolated yields. Electrochemical parameters must be encoded properly. The 10 plates may span several reaction classes and need consistent reactant/product SMILES per plate.
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.