# Curate this paper into an ORD dataset

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

- **Paper:** Exploring the hydrogenation of furfural in the liquid phase by high-throughput screening of commercial catalysts: Effects of temperature, solvents, and promoters on the production of 2-methylfuran
- **Authors:** Gianfranco Giorgianni, Siglinda Perathoner, Gabriele Centi et al.
- **Published:** Chemical Eng. R. and Des., 2023-08-16
- **DOI:** [10.1016/j.cherd.2023.08.010](https://doi.org/10.1016/j.cherd.2023.08.010)
- **ORD wishlist card:** [open on GitHub](https://github.com/orgs/open-reaction-database/projects/11?pane=issue&itemId=126569946)

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 864 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

Source: Giorgianni et al., Chem. Eng. Res. Des. 2023, 197, doi:10.1016/j.cherd.2023.08.010 (closed access; no open-access copy found). This is high-throughput screening of about 864 liquid-phase hydrogenations of furfural toward 2-methylfuran over commercial heterogeneous catalysts, varying temperature, solvent and promoters. Curators need subscription access to the article and supplementary data, or the data from the authors. No public data deposit was found. Pitfalls: heterogeneous catalysts must be described in ORD (composition, support, metal loading, supplier and product code, pretreatment), and product mixtures are complex, with multiple quantified products per run.

Known locations:

- [https://doi.org/10.1016/j.cherd.2023.08.010](https://doi.org/10.1016/j.cherd.2023.08.010): Chem. Eng. Res. Des. article and Elsevier-hosted supplementary data (not inspected; paywalled) (license: Closed (Elsevier user/TDM license only))
- [https://resolver.tno.nl/uuid:e444e01d-19f0-49b8-a9d9-0376580b9b53](https://resolver.tno.nl/uuid:e444e01d-19f0-49b8-a9d9-0376580b9b53): TNO repository record (submitted version); files available only by email request to the repository (license: not stated)

## Pitfalls

Heterogeneous commercial catalysts (no SMILES; need catalyst descriptors). Complex multi-product outcomes (selectivities to several furanic products). Data form (tables vs figures) unknown because the source is paywalled.

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