# Curate this paper into an ORD dataset

Build an Open Reaction Database (ORD) dataset of the reactions reported in:

- **Paper:** General Method for Ni-Catalyzed C–N Cross-Couplings of (Hetero)Aryl Chlorides with Anilines and Aliphatic Amines under Homogeneous Conditions Using a Dual-Base Strategy
- **Authors:** Roberto Silva Villatoro, Joshua R. Belfield, Hadi D. Arman et al.
- **Published:** Organometallics, 2023-11-01
- **DOI:** [10.1021/acs.organomet.3c00419](https://doi.org/10.1021/acs.organomet.3c00419)
- **ORD wishlist card:** [open on GitHub](https://github.com/orgs/open-reaction-database/projects/11?pane=issue&itemId=127186699)

The reference input `card` holds these facts, the source-data locations and the notes below in machine-readable form.

## Scope

Every reaction the paper reports with its data (the wishlist estimates about 400 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 data

Ni-catalyzed C-N cross-coupling HTE (dual-base strategy), about 400 reactions. The full reaction data exists as a multi-sheet spreadsheet (about 15 sheets) from the originating company and is not publicly available. The public SI is a PDF (ACS, mirrored on figshare, CC BY-NC 4.0). The sheets may need different ORD templates, and compounds are listed without SMILES, so SMILES generation is required. This item is currently assigned within ORD.

Known locations:

- [https://acs.figshare.com/articles/journal_contribution/General_Method_for_Ni-Catalyzed_C_N_Cross-Couplings_of_Hetero_Aryl_Chlorides_with_Anilines_and_Aliphatic_Amines_under_Homogeneous_Conditions_Using_a_Dual-Base_Strategy/24476269](https://acs.figshare.com/articles/journal_contribution/General_Method_for_Ni-Catalyzed_C_N_Cross-Couplings_of_Hetero_Aryl_Chlorides_with_Anilines_and_Aliphatic_Amines_under_Homogeneous_Conditions_Using_a_Dual-Base_Strategy/24476269): ACS SI mirror: om3c00419_si_001.pdf (8.2 MB; listed, not downloaded) (license: CC BY-NC 4.0 (figshare record))
- [https://doi.org/10.1021/acs.organomet.3c00419](https://doi.org/10.1021/acs.organomet.3c00419): Article (Organometallics 2023); closed access (license: closed (OpenAlex))

## Pitfalls

Multiple sheets likely correspond to different experiment designs and templates. Compound list requires SMILES generation. Source data is private.

## Deliver

- `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.

## After starting your Attempt

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.


## Evaluation and public curator identity

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.