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

Introduction could benefit from examples #42

Open
kesondrakey opened this issue Jan 21, 2025 · 2 comments
Open

Introduction could benefit from examples #42

kesondrakey opened this issue Jan 21, 2025 · 2 comments

Comments

@kesondrakey
Copy link

Adding examples and a bit more to the introduction page on what biological data is would be helpful for clarity for non-biologists. Or it could be generalized for data quality and best practices. Or you could just use an umbrella term like Environmental Science to cover a wider range of disciplines.

NEON data comes to mind - they are creating high standards for eddy covariance data with their flux towers, but they also have large biological data repositories including species distributions and whatnot that might have similar standards, but I'm not directly familiar with using these (https://www.neonscience.org/data)

For eddy covariance data, Fluxnet is usually considered the high standard for non-NEON towers that anyone with a tower can submit to. Fluxnet takes data in in a certain format with data requirements (.csv) and metadata in order to be able to be published, so their website will have some guidelines for these too if you were interested (https://fluxnet.org/data/).

That said, I really love what you are doing. Clear data standards are so important to increase data quality across disciplines.

@laurabrenskelle
Copy link
Contributor

@sunray1 would know more about NEON standards and how they come into play.

@sunray1
Copy link

sunray1 commented Jan 23, 2025

👍 Happy to answer any questions if needed. FWIW our bio data is stored in internalized formats that aren't technically any one global standard (though it was built from various ones). Doing it this way lets us a) keep data associated with our (relatively complicated) protocols and sampling/data storage structures intact and b) makes mapping to whatever standard needed for publication relatively easy

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

3 participants