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 2,000 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.
Pd-catalyzed C–N coupling HTE dataset (MIT / Merck collaboration), JACS 2025, DOI 10.1021/jacs.5c00933. The published reaction outcomes are only grid images in the SI PDF (ja5c00933_si_001.pdf on ACS figshare). There is no machine-readable SI file, and no public code or data repository was found. Many reactants and catalysts would need SMILES. The card lists about 2000 reactions, but the SI description mentions 4204 unique products, so the full dataset may be larger. Curating from the images alone is not practical, so an author-supplied tabular dataset (ideally with SMILES) is needed before this can be worked.
Known locations:
Outcomes would come from images unless tabular data appears. The size is unclear (2000 on the card vs 4204 unique products in the SI description). Pharma HTE components may use internal identifiers. Checking many generated SMILES against drawn structures needs expert review.
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.