-
Notifications
You must be signed in to change notification settings - Fork 0
Updating the ESS-DIVE submission #270
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
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,38 @@ | ||
|
||
# Steps to update ESS-DIVE submissions | ||
|
||
0. Run processing pipeline to produce L1 data for synoptic and TEMPEST sites | ||
|
||
1. Move L1 data to folders labeled `vX-X` \> `vX-X_SYN` and `vX-X` \> `vX-X_TMP` . Each folder gets a copy of the `READMD.txt` and `README_vX-X.txt` files. | ||
|
||
2. Prep package metadata files | ||
|
||
- Produce flmd using `flmd-generator.R` | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Is it obvious how to do this? Do you need to point the script to where the L1 data are? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good question, I think currently flmd-generator requires the files to be in the L1 folder (at least i havent tried otherwise) which would impact the steps here |
||
- Copy over `dd.csv` from previous version (this file does not change unless we change or add a new L1 column) | ||
- Run `availability_graph.R` to produce availability graphs. | ||
- Add saved graphs to quick start documents located in the FME Data Management folder | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Do you create a new copy of the documents for each release? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes |
||
- Export Google document as a PDF and move to submission folders | ||
|
||
3. Prep data | ||
|
||
- Compress all folders into \_.zip\_ format | ||
|
||
4. ESS-DIVE submission | ||
|
||
- If a minor version change: | ||
|
||
- Remove all data files | ||
|
||
- Add new files | ||
|
||
- Update data date range in submission metadata | ||
|
||
- Change version name in title and abstract | ||
|
||
- Finally, email ESS-DIVE support to start the re-review | ||
|
||
- If a major version change: | ||
|
||
- Create new submission | ||
|
||
- *More steps to come*... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
README.md
?