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

suggestions for introduction content #10

Open
sformel-usgs opened this issue Apr 6, 2023 · 2 comments
Open

suggestions for introduction content #10

sformel-usgs opened this issue Apr 6, 2023 · 2 comments

Comments

@sformel-usgs
Copy link
Collaborator

What section of the best practices does your suggestion relate to?
Introduction

Short description of content that should be revised
This is still in a draft phase and needs a lot of work.

Suggested revision

  1. Add FAIR principles as a generally best practice
  2. Stace suggested that we overlap quite a bit with this paper: https://journals.plos.org/ploscompbiol/article?id=10.1371/journal.pcbi.1005510#sec004 and I agree, here are some follow up thoughts that might be fodder for the intro and to justify our effort:
  3. A space exists between checklists of knowledge and deep dives on data management. We want to fill that space for biologists specifically.
  4. The best practices paper is analogous to the notes you might give a naive field researcher before you send them into the field. Enough to help them avoid doing things that will cause headaches down the line.
    However, in the intro, we can emphasize that becoming a savvy data manager isn't about fulfilling a checklist, but developing a toolbox and intuition that is flexible and will ensure "good enough practices". To this end, we should include a short list of further reading in the intro, encouraging the reader to do a deep dive into this literature within x months of when they needed to lean on the best practices.
  5. Finally, one of the consistent drawbacks to other guides, like the "good enough practices" paper, is that there is no mechanism for feedback and iteration as our ideas and tools evolve. We aim to solicit and include this feedback as part of the product, in the same way the GBIF has done with their literature.
  6. Maybe we rename this from best practices to "practical practices" or something else, to make a point like the "good enough practices" folks did about the "best practices" paper that preceded theirs.
@sformel-usgs
Copy link
Collaborator Author

It was suggested that we state that this document is for English speakers until we have the bandwidth and/or community to offer translations.

@MathewBiddle
Copy link
Contributor

Once the website is published, users can get a rough translation using Google Translate. Just drop the url in this service:

https://translate.google.com/?sl=en&tl=es&op=websites

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

2 participants