Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EMODnet data product author checklist #20

Open
20 tasks
maelle opened this issue Feb 28, 2022 · 0 comments
Open
20 tasks

EMODnet data product author checklist #20

maelle opened this issue Feb 28, 2022 · 0 comments

Comments

@maelle
Copy link
Collaborator

maelle commented Feb 28, 2022

General

  • I have used EMODnet data product template.
  • I have put together a clear README including (potentially via rendering dataspice JSON)
    • a title;
    • a description of about 300 words (including context, story);
    • keywords;
    • temporal coverage;
    • geographic coverage (MRGIDs from MarineRegions);
    • if applicable: Taxonomic coverage (AphiaIDs from WoRMS)
    • what datasets does this product uses? List the IMIS dasids, and/or DOIs from datasets not listed in IMIS.
    • Is this product a continuation of an older product? Does it uses another product? If yes, please provide its IMIS dasid.
  • I have run a spell check on text parts.

Authorship and citation

  • I have listed all authors.
  • I have listed contact information.
  • I have added citation information in the README as: Last name, First name. Year. Title. Funding e.g.
Beauchard, Olivier, Herman, Peter M.J., Fernández-Bejarano, Salvador.  2021. Data product numerical abundance of benthic macroinvertebrates in  North Sea and Baltic Sea. Integrated data products created under the  European Marine Observation Data Network (EMODnet) Biology project  (EASME/EMFF/2017/1.3.1.2/02/SI2.789013), funded by the by the European  Union under Regulation (EU) No 508/2014 of the European Parliament and  of the Council of 15 May 2014 on the European Maritime and Fisheries  Fund.

(I might have added a citation.cff file)

Code

  • I have listed dependencies (e.g. with the renv R package).
  • I have written how to re-run the code, e.g. in a main script that has commands.

Data

  • I have documented datasets e.g. with dataspice.

Upkeep

  • I have added a lifecycle badge to the README or some sentences about the project status.
  • I have created a changelog (NEWS.md) for keeping tracks of changes.
  • I have recruited a reviewer for the data product.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant