CHEMeDATA Initiative

Main website of the CHEMeDATA umbrella organization

Making chemistry data more FAIR.

h3 style=”background-color:DodgerBlue;”>This page is under construction</h3> —>

Recommendations for publishers of chemistry journals

Encourage (or require) the submission of all electronic data supporting the claims of the articles. This includes spectroscopic information, spreadsheets of data, etc.

Help the author to distinguish the supplementary information which should be submitted as text (.pdf or .doc) files from the data which should be submitted in their native electronic forms.

Propose third party archiving solution (such as Zenodo, FigShare, etc.) if the publisher’s server cannot accommodate the files submitted by the authors. These repositories offer solutions based on private links to restrict access to the data to reviewers only until the publications of manuscripts. With Zenodo, a REST-API allows to fully automatize this process from the publisher’s website so that the authors do not have to re-enter information such as author names, affiliation, reference to the manuscript, etc.

Submitting supplementary data after publication

An alternative is the submission of supplementary data at the submission of a manuscript is to create a chemistry data archive after publication. A workflow taking the metadata of a manuscript (DOI, authors, ORCID, affiliations, funding, etc.) from a Journal page (or other sources of publication data such as Researchgate.org, Institutional list of publication, etc.) would be particularly practical for the author to avoid entering any information. An electronic invitation to submit associated data files could be sent to the corresponding author or the principal investigator of a research group when a new publication record is identified. A pre-filled data submission page would only require the author to drop a .zip file to satisfy the requirement to share data requested by public institutions and funding agencies.

Tentative instructions for the Authors (to be improved…)

Images of NMR spectra, chemical structures, etc. can be included as pictures in a .pdf or .doc files to constitute supplementary material complementing the main article. But in general, these data are not computer readable and only for use by humans. It is essential to understand that image inserted in .doc or .pdf files do not constitute reusable data in the FAIR sense. It is important to distinguish supplementary material (or supplementary information) from supplementary data discussed in the following paragraph.

Spectra, chemical structures, should be submitted in their native electronic format:

These individual files should be ordered in a file tree to make their relations implicit. For example, the chemical structure file and the spectroscopic data of the compound numbered 1 in the article can be saved in a folder named compound1.

Helping chemist submit well organized and complete

Instead of having the chemist prepare a .zip file on his own, a simple webpage could help him, making sure that structure files are submitted and the spectroscopic data are sorted by compounds.

Structure Spectroscopic data Other files
[drop .cdx or .mol file of compound 1 here] [drop files or folders here] [drop files or folders here]
[drop .cdx or .mol file of compound 2 here] [drop files or folders here] [drop files or folders here]
   
Other files [drop files or folder here] Generate .zip file

NMReDATA

Since 2019, all major NMR software producers introduced the NMReDATA format in their software. Exporting NMR data in this format facilitates reviewing because data in this format include the spectra, but also the assignment data and the result of the automatic evaluation of the consistency and quality of these data. Besides the commercial solutions, free web-based tools are also available for use and integration in new tools to be developed.

More information

ACS support of FAIR data

Henry Rzepa’s take on ACS’s announcement

Reach us…

If you have comments, suggestions, contributions, etc. please raise an Issue on GitHub