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

add chapter on deprecating a data package? #74

Open
cgries opened this issue Sep 14, 2021 · 1 comment
Open

add chapter on deprecating a data package? #74

cgries opened this issue Sep 14, 2021 · 1 comment
Labels
BP committee task things the BP committee will need to do

Comments

@cgries
Copy link
Contributor

cgries commented Sep 14, 2021

use case: long-term observation dataset was archived as two packages, in the latest update the author wants most tables in one package and get rid of others. And updated tables have slightly different structures.

@rfbrown
Copy link
Collaborator

rfbrown commented Sep 14, 2021

Good idea. Another use case I've been thinking about at MCM: we currently archive monthly and/or daily summaries of our met and hydro data as separate packages from the high-frequency data. So this means for each met station or stream gage, we have 2-3 packages per station. It's a ton of extra work on my part, and creates confusion to our researchers (they often download the wrong package). I would like to consider consolidating into a single package per station, but I also wonder how others are tackling? If we consolidate, then we'll have to depreciate some packages...

@rfbrown rfbrown added the BP committee task things the BP committee will need to do label Feb 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BP committee task things the BP committee will need to do
Projects
None yet
Development

No branches or pull requests

2 participants