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

Recommendations about what to put in sampling_location_ancillary, what to put in event #10

Open
mobb opened this issue Aug 1, 2017 · 3 comments
Assignees

Comments

@mobb
Copy link
Contributor

mobb commented Aug 1, 2017

The next decision I am struggling with is, how much to put into the sampling_location_ancillary. There is a pretty wide table with lake conditions (~25 of them) should I turn them all into the long format or just leave the table as is and attach? It’ll be needed by pretty much all datasets from that survey, which includes water quality that would not go into the ecocom_dp.

@mobb
Copy link
Contributor Author

mobb commented Aug 1, 2017

I thought the idea of a long table for these was that they could all be put in (eg, 25 key-value pairs), and the wide format recreated as necessary.

@mobb mobb changed the title Recommendations about how much to put in sampling_location_ancillary Recommendations about what to put in sampling_location_ancillary, what to put in event Aug 1, 2017
@mobb
Copy link
Contributor Author

mobb commented Aug 1, 2017

info goes into samp_ancillary if info does not change from sampling event to sampling (or "infrequently"). if it does change, then its an event.
for community data, both are 'metadata'

to consider: if you drop datetime from the samp_loc_ancillary, then it is limited to things that do not change.
we added this because we suspected that people would want to describe things like the date some experimental treatment was applied, eg that fertilization occurred on date A.

@clnsmth
Copy link
Contributor

clnsmth commented Aug 3, 2021

These recommendations will be covered in the shared practice docs (soon to be released).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants