ioos / ioos/bio_data_guide

Data management advices before scientists leave for fieldwork

Open
#268 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
55
Forks
24
PR merge metrics
No merged PRs in 30d

Description

This issue summarizes the thread from Slack about useful data management tips for scientists BEFORE they leave for field works. Thank you everyone who chimed in!

Dean Pentcheff: You are probably planning to deposit your specimens in a museum (or similar) collection. BEFORE THE TRIP, have a conversation with the collections manager at that institution to find out what their data guidelines are for event/collection/specimen metadata. If you know those guidelines before you design your data log format for the trip, it can make specimen deposition much easier, and leads to better permanent metadata,.
You don't have to limit yourself to the data fields your target organization uses, but if you collect data in a way that makes it easy to transform for deposit, everyone saves time, and less data tweaking means fewer inadvertent editing errors.

@MathewBiddle Through the Earth Science Information Partners (ESIP) and the Deep Ocean Observing Strategy (DOOS) we built an "Easy Resources for Managing your Ocean Data" infographic:
https://www.deepoceanobserving.org/pages/41e5b75c2c49442eb40b968d9ccff411

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files or tests are named. Start by reviewing the issue body and the linked ocean-data infographic, then determine where fieldwork data-management guidance belongs in the guide. Done would mean an agreed, published documentation change, but this issue does not define the target file or acceptance criteria.

Written by the indexing model from the issue text.

Assessment

Domain
content, data, documentation
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.