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 150 reactions; MTE mechanochemistry): 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.
Nickel-catalysed C-N cross-coupling aminations run as high-throughput mechanochemistry with resonant acoustic mixing (RAM), from Nanni et al., Green Chem. 2024 (doi:10.1039/D4GC01790K), about 150 reactions. The article is open access under CC BY-NC 3.0 (article-level licence; the ESI licence was not confirmed). Data is expected in the article tables and figures and the ESI PDF; no separate data repository deposit was found. Structures are drawn, not given as SMILES. Solvent-free or liquid-assisted milling conditions need careful ORD encoding: the mixing device and parameters (acceleration or intensity, time), additives or grinding auxiliaries, and the absence of bulk solvent. The ORD Dataset must cite the paper DOI.
Known locations:
Mechanochemical (RAM) conditions do not map cleanly onto standard ORD stirring and solvent fields, so reviewers must check how mixing and liquid-assisted grinding are encoded. Outcomes may mix screening (assay) yields and isolated yields. Structures must be transcribed.
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.