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.

Sign up for GitHub

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

Jump to bottom

Define strategy for versioning in the product filenames #21

Open

5 tasks

gilbertozp opened this issue Mar 2, 2022 · 0 comments

Open

5 tasks

Define strategy for versioning in the product filenames #21

gilbertozp opened this issue Mar 2, 2022 · 0 comments

Labels

Contributor

gilbertozp commented Mar 2, 2022

Define how the filename version information will be used:

Default values
Document meaning of data version
Document meaning of processing version
Define if processing version is fixed in the code (hard-coded with the code version) or can be parameterized
Networks always in sync vs individuals running the code

Filename template:
FLX_CC-SSS_DATAPRODNAME_[SUBSET/FULLSET]_FYYY-LYYY_DATAV-PROCV.zip

Filename examples:
FLX_US-ARc_FLUXNET2015_FULLSET_2005-2006_2-3.zip
FLX_US-ARc_FLUXNET2015_FULLSET_2005-2006_2-3.zip

gilbertozp mentioned this issue

Create strategy to integrate metadata (BIF-style) into the data product #22

Open

4 tasks

gilbertozp added this to ONEFlux-Priorities

gilbertozp added the Priority:Low label

gilbertozp moved this to Priority:Low in ONEFlux-Priorities

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