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 700 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.
Source: Nature Communications 10.1038/s41467-024-47939-5 (Universities of York and Leeds; CC BY 4.0), about 700 HTE Pd-catalysed cross-coupling reactions with complex side-product and by-product distributions. The HTE data are in Research Data York (DOI 10.15124/37869e97-c94a-41a7-9f69-fe3ed1c10984, CC BY). It contains an experimental-information CSV, processed LC-MS extract CSVs (EXTRAC_1/2) and PCA input tables (2-hour and 110 °C sets), plus about 10 GB of raw LC-MS zips, which are not needed for curation. The article's Source Data CSV holds IR reaction-monitoring time courses, not the screening outcomes. Data are spread over several spreadsheets whose structure is not fully documented, so work out the mapping between conditions and outcomes first and flag any ambiguity. Author clarification may be needed. Crystal structures are in the CCDC (numbers listed in the article).
Known locations:
Outcomes are product distributions, with many products and side products per reaction, quantified as LC-MS peak areas or normalised responses rather than yields. Each reaction needs multiple product entries with a clear analysis type. The PCA tables may be processed or normalised values. SMILES must be built from the SI. Raw LC-MS archives are too large to use as review evidence. The IR Source Data is kinetic monitoring (time-course), which is different from the endpoint HTE data.
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.