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 100 reactions; parallel): 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 is a parallel screen of an organocatalytic asymmetric Michael addition of an isatin-derived Schiff base, where isatin acts as amine protecting group, umpolung reagent and chiroptical reporter. It covers 10 chiral organocatalysts (Cat 1-10, including cinchona alkaloid-derived squaramides) x 5 solvents (e.g. toluene, 1,2-difluorobenzene, 1,2-dichloroethane, THF, acetonitrile) x 2 temperatures (10 and 25 C), 100 reactions in total. Outcomes are UV absorbance increase and CD/UV induction ratios measured directly on the crude mixtures. These serve as proxies for yield and ee. Confirmatory scale-up runs with Cat 4 and Cat 9 give isolated yield and chiral-HPLC ee. The data are in the SI PDF as about 10 small tables. The article is open access (CC BY-NC 4.0) and on PMC (PMC12188155). Catalyst structures are drawn, not named with identifiers. Cite DOI 10.1002/chem.202500881.
Known locations:
The primary outcomes are spectroscopic proxies (UV at ~423 nm, CD 425 nm/UV 423 nm ratio), not yields or ee. They should be recorded as custom analyses or measurements, with the calibration/correlation noted. Only the scale-up runs have isolated yield and HPLC ee. Catalyst SMILES must be built from drawings, including stereochemistry.
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.