Guide to publishing sequence-derived data opens for peer-review

Deadline for community input on latest in series of technical documentation: 22 Sept 2020

Chocolate chip lichen (Solorina crocea). Photo 2020 Ricarda Pätsch via iNaturalist Research-grade Observations, licensed under CC BY-NC-SA 4.0.

GBIF has released another technical document for peer review and welcomes community input and feedback on the guide, Publishing sequence-derived data through biodiversity data platforms, until Tuesday, 22 September 2020.

This work was made possible thanks to the active and enthusiastic involvement of co-authors from Australia, Estonia, Norway, Sweden and Denmark. We are also most grateful for their work and hope that the feedback that community members provide during this peer-review phase can further expand the list of contributors.

This release is the next in the technical documentation series described here, and another four documents are in the queue for release in the coming weeks. Feedback on the community peer review process and the digital documentation programme—including suggestions on other topics we should consider covering—are always welcomed at

How can I learn about the release of other new documents?

Whether you subscribe to other GBIF lists or not, the best way to stay informed on the upcoming releases is to add yourself to GBIF's 'digital documentation' mailing list. You can also expect to see announcements if you follow us on Twitter and LinkedIn.

How do I participate in the community peer review?

Community members interested in contributing to this peer-review process can read the overview of the digital documentation programme to place their efforts in context, then review the specific instructions and expectations on how to offer suggestions and improvements.

To lend your voice and participate as a reviewer, we ask community members to:

  1. Create a GitHub account (see video how-to).
  2. Read the document, Publishing sequence-derived data through biodiversity data platforms
  3. If you see something, say something, by creating or commenting on issues on GitHub (see video how-to)
  4. Start, follow and support discussions that arise on the GBIF Community Forum

Please remember that all interactions within this process must adhere to the GBIF Code of Conduct, which aims to encourage a "safe, hospitable, and productive environment" that is "professional, respectful and harassment-free for all participating."