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: 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.
This paper covers HTE plus DFT-guided development of the ring-closing metathesis step (16-membered macrocycle) in the AMG 176 synthesis (OPRD 2020, Amgen/UCLA). The SI on the ACS figshare mirror (labelled CC BY-NC 4.0) contains the HTE RCM procedure and catalyst-screening bar charts with numeric product LCAP labels. Figure SI1 covers about 10 Ru catalysts at 4 mol% with the acetate substrate, and Figure SI2 about 24 catalysts at 1 mol% with the 4-bromobenzoate substrate. The SI also has characterisation of the ester-protected substrates and macrocycles, catalyst structures (Scheme SI1), DFT data and an X-ray structure. The main-text screening and optimisation tables are in the paywalled article. Pitfalls: outcomes are LCAP (HPLC area %), not yields; the substrates are complex stereodefined macrocycle precursors that must be converted to SMILES carefully; the Ru catalysts are identified by trade codes (e.g. M71-SIPr, M73-SIMes, HG2, GreenCat) that must be mapped to structures.
Known locations:
Outcomes are LCAP (area %), not isolated yields. Values come from labelled bar charts. Ru metathesis catalysts are named by vendor codes and need SMILES for organometallic complexes, which may be imperfect. Substrates are large, stereochemically complex intermediates. Some screening conditions (loading, concentration in L/kg, temperature) are described generically and must be matched to each chart. Kinetic monitoring data, if in the main text, are figures.
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.