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 96 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.
Aminoglutarimide C-N cross-coupling (BMS), a 96-reaction HTE screen. Source data is in the ChemRxiv preprint SI (CC-BY-NC 4.0; the JOC version of record is ACS, closed). Outcomes are given as an image of a table of LC area percentages. A bubble plot in the SI appears to show the same data, so use it to cross-check the transcription. Ligands appear as named structure images, so their SMILES must be drawn or looked up and verified. Record LC area % as an area-percent measurement, not a yield. Cite the JOC DOI (10.1021/acs.joc.4c02536) and note the preprint DOI (10.26434/chemrxiv-2024-1skr0). The source files cannot be rehosted under CC-BY-NC, so the Problem should reference them by link only.
Known locations:
Values are transcribed from an image, so transcription errors are likely without double-entry or a cross-check against the bubble plot. Outcomes are LC area %, not isolated or assay yields. Ligand identities are resolved from images and names. The pages were bot-blocked, so the SI layout was not confirmed.
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.