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 50,000 reactions; literature review): 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: J. Org. Chem. 2025, DOI 10.1021/acs.joc.5c01641 (HeckLit, a literature-derived Heck yield dataset). The data is at github.com/AIChem-ShenWang/HeckLit-Code under data/Heck. 'Heck processed data.xlsx' has about 10,000 rows with SMILES for reactants, reagents, catalysts and solvents, plus temperature, time, yield, a Reaxys Reaction ID and the original literature or patent reference. Missing values are written as '/'. Per the repository README, the data was built from a Reaxys export, and the repository declares no licence, so redistribution rights must be confirmed before curation. Exclude the JCP files in the same folder: they come from a different publication. Each ORD reaction should cite its original source reference as well as the HeckLit paper.
Known locations:
The data is literature-derived: each row comes from a different patent or paper, so conditions are heterogeneous, yields are as reported by the original sources, and products were not characterised by the dataset authors. Multiple condition rows share an rxn_index. Metal catalysts appear as charge-separated multi-fragment SMILES. The card's size (50,000) does not match the processed sheet (about 10,000 rows). The raw sheet (10 MB) was not inspected.
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.