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.
ChemBeads-enabled HTE of Ni-catalyzed cross-electrophile coupling: aryl bromides with alkyl halides, Zn or Mn reductant coated on glass beads, several ligands including BpyCam. The paper reports an array of 3 x 222 micromolar reactions. The main-text outcomes are a color-coded grid: product ion observed at 10 umol scale, observed but not isolated in >95% purity at 100 umol, or no ion observed. Isolated yields by mass-directed HPLC are given for selected products, with ligand noted only where it mattered. A separate panel compares Zn powder with Zn@ChemBeads using GC yields against a 1,3,5-trimethoxybenzene internal standard. No machine-readable data file is known. The SI (PDF) has not been checked for a per-well table. Without one, outcomes can only be transcribed from figures as qualitative detection results, and substrate structures must be drawn.
Known locations:
Outcomes are mostly qualitative (MS ion detected / not detected), with isolated yields only for a subset. Heterogeneous reductant on glass beads, with amounts given as bead mass and loading. Three ligand/condition sets across 222 substrate pairs. Transcription from a color grid is error-prone.
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.