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

Retaining complete date/time information and repeat measurements vs fully collating data #19

Open
natashagriffin opened this issue May 16, 2022 · 0 comments
Labels
core relating to core functionality of pkg

Comments

@natashagriffin
Copy link

Problems: It's hard to collate data when...
a. the date doesn't line up for some variables collected at the same site during the same season (could be water chem vs YSI, water vs sed chem, etc)
(bad solution? = ignore day/time and just merge by season, year, and site)
b. hard to merge data / assign a unique ID when there are repeat measurements (like two d18O values for the same site and date, for whatever reason)
(bad solutions? = average the two values (bad if the reason there are two measurements is that one was not good), or use only one (how to decide which?))

If we don't address those issues, the collated table will not retain as many measurements as possible. One option is to have multiple versions of the collated table, with different degrees of data cleaning / intervention to make things match? Or just keep intervention very minimal and leave further collation up to the user to figure out.

@atn38 atn38 added the core relating to core functionality of pkg label May 23, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core relating to core functionality of pkg
Projects
None yet
Development

No branches or pull requests

2 participants