Publishers in the Earth and Space Sciences Team

1. AGU FAIR Data:
Targeted Adoption
Group (TAG) B
Publishers in Earth and
Space Sciences Team
TAG Co-Chairs:
Joerg Heber jheber@plos.org
Anita de Waard/
Helena Cousijn
(now with DataCite)
a.dewaard@elsevier.com
TAG Members:
Brooks Hanson bhanson@agu.org
Michael Friedman mfriedman@ametsoc.org
Sophie Hou hou@ucar.edu
Phill Jones p.jones@digital-
science.com
Etta Kavanagh EKavanagh@nas.edu
Jens Klump Jens.Klump@csiro.au
Meredith Morovati Previously at Dryad
Kate Perry kperry@wiley.com
Jake Yeston jyeston@aaas.org
H. Jesse Smith hjsmith@aaas.org
Natasha Simons natasha.simons@ands.org.
au
Monica Bradford mbradfor@aaas.org
Hannah Smith hansmith@wiley.com
TAG Support:
Shelley Stall sstall@agu.org
Lynn Yarmey yarmel@rpi.edu

2. What we did:
• We met a lot
• We discussed a lot
• We talked about Data Availibility Statements a bit too much, but…
• We came up with a shared set of authoring guidelines (yay!) which all
publishers signed up to…

3. The Authoring Guidelines:
All publishers who are part of the Coalition on Publishing Data in the Earth and Space Sciences (COPDESS) support the efforts of trusted repositories that curate
research data, software, and physical samples for use by the scientific community. These Data Guidelines align the author instructions for the submission of data
in the Earth, space, and environmental sciences, for all affiliated publishers. Specifically, these publishers require authors to:
1. Deposit research data1 in a FAIR-aligned repository, with a preference for those that explicitly follow the FAIR Data Principles and demonstrate
compliance with international standards for data repositories, (e.g. CoreTrustSeal). Supplements to articles must not be used as an archive for data.
2. Cite and link to the data in the article, following the Joint Declaration of Data Citation Principles and ESIP Guidelines, using the unique, resolvable, and
persistent identifiers provided by the repository in which the data are archived. In particular:
• Citations should appear in the body of the article with a corresponding reference in the reference list.
• Citations should include persistent identifiers in well-formed references to data and software allowing that information to be tracked in global
information systems for impact, integrity, and innovation (see Scholix).
• Citations should include software used in the research following the FORCE11 Software Citation Principles, which recommends a similar depositing of
the software in an archival repository, and citation/references that include the persistent identifiers provided by the repository.
3. Include a Data Availability Statement describing how the data underlying the findings of their article can be accessed and reused.
• In special cases, where data access is restricted, authors are required to mention these restrictions in the Data Availability Statement provided with the
article. Such restrictions might be determined by applicable laws, university and research institution policies, funder terms, privacy, intellectual
property and licensing agreements, and the ethical context of your research.
• If the data cannot be made open, it should still be preserved in a FAIR-compliant repository with appropriate access and controls in place. Repositories
that provide appropriate access controls can be found here.
4. Provide unrestricted access to all data and materials underlying reported findings for which ethical or legal constraints do not apply.
These restrictions can include:
• Data Disclosure Risks. If there are possible data disclosure risks (the data pose privacy, confidentiality, or legal concerns, e.g., where data might reveal
the identity or location of participants), the authors must specify that data are available on request in the Data Availability Statement, and identify the
group to which requests should be submitted. The reasons for restrictions on public data deposition must also be specified. Note that it is not
acceptable for the authors to be the sole named individuals responsible for ensuring data access.
• Data made available by a third party that is not located in a FAIR-aligned repository and without a persistent identifier. We consider third-party data to
be data that can not be legally distributed by the authors. Authors should share any data specific to their analysis that they can legally distribute. If an
author does not have the rights to distribute the data, they must include all necessary contact information in the Data Availability Statement to gain

4. Still to be resolved:
• Implementation, implementation, implementation!
• All publishers are different, all journals are different, ….
• Resolution with the rest of the website/messaging not completely solved:
• Overlap/contradictions with the FAQs?
• Link to COPDESS Statement: how do we share/market this?
• Follow up?
• Who leads?
• Who checks?
• What if there need to be tweaks, new meetings, etc?