ess-dive-community / essdive-model-data-archiving-guidelines Goto Github PK

Submitter:

I have the following question:

For model data, what are the start / end dates for the dataset? Are dates required for model data? If yes, how to determine the dates. Some models are running for a time-period (150-day simulation) and not necessarily over a time period (e.g. 2020-2050)

Terri

Submitter: Rob C-O

I suggest the following changes: In previous brainstorming sessions we mentioned the possibility of turning the decision tree image from the manuscript into a more interactive decision tree that users can click through.

• Could use Canva website to do this.

Submitter: Rob Crystal-Ornelas

I suggest the following changes:

After reading through the associated manuscript, and adding content to the GitHub repo, there are a few other additions we should consider

• Which usage license should we select. In ESS-DIVE you’ll have the option to select CC BY 1.0 or CC BY 4.0. Then, I can create a .txt file for the license so that is clearly visible in the GitHub repo.

• Which document should we encourage users to cite on our README page? The manuscript that is soon to be submitted?

• I created a small set of GitHub issue templates that can help to organize feedback. Any other templates that I should add or are the 2 that I have OK for now?

• Documentation reference (URL): README and instructions document
• Submitter: RCO
• Justification (why is this change necessary?): We are making updates to the documentation that correspond to reviewer feedback from our manuscript

I suggest the following changes:

• Update instructions by removing image of guidelines, and replace with text-based guidelines
• Update citation
• Remove FLMD figure, and replace with figure that has the terminology used in v1.0.0 of the FLMD reporting format.
• Do final read through of repository and align with terms used throughout manuscript.