add data and code availability statements

[teixeirak]

Data and code availability statements are required: https://www.nature.com/nature-portfolio/editorial-policies/reporting-standards.

We do not currently have these in the manuscript, so I have added placeholders for them.

This required form has a checkbox to indicate that these have been provided. Because they are not in the submitted manuscript, I will tell the editor that they are not yet there but that we plan to publish in GitHub/ Zenodo.

We will also need to clean up this repo for release.

[teixeirak]

Oh, hold on, the statements are to be given in the other form.

[teixeirak]

Here's a running list of what needs to be finished with these statements (for final version):

Data

• [x] verify Harvard forest dendrometer band data link
• [x] double check with Loic that his version of the dendro band data can be made public
• [ ] check if cores are in ITRDB. If not, I think we need to add them.
• [x] confirm link for leaf pheno data (@mcgregorian1 )
• [ ] add Harvard tree-ring data link

Code

• [x] check that we got all the packages (@camerondow35, maybe @rudeboybert )

[teixeirak]

Here's one from the nr-editorial-policy document:

The hyperlink for mandated accession codes is this: https://www.nature.com/nature-portfolio/editorial-policies/reporting-standards#mandates-for-specific-datasets

*From January 2019, where community repositories are available, we will require data sharing through such repositories for papers in the Earth, space and environmental sciences published in Nature, Nature Geoscience and Communications Earth & Environment. Where such repositories are not available, datasets may be hosted in general data repositories such as Figshare, Dryad or Zenodo. See our editorial for more details.

I am not certain of our answer. I'm not sure whether any of our data would be considered relevant to the available repositories. For example,

• [ ] should the SCBI weather data should be deposited in one?
• [ ] ITRDB falls under NOAA National Centers for Environmental Information (https://www.ncei.noaa.gov/products/paleoclimatology/tree-ring), so I believe we need to get the tree-ring chronologies in there.

[camerondow35]

check that we got all the packages (@camerondow35, maybe @rudeboybert )

Inserting all packages seems like overkill. I'll add rstanarm and that should cover all the "abnormal" packages we used. But let me know if we need all packages used, will be around 2 dozen or so probably.

[teixeirak]

Sounds reasonable.

[camerondow35]

should the SCBI weather data should be deposited in one?

Looking at the potential repos, I think NCEI would be the best on that list for weather data, but a NCEI weather station is what I used for filling gaps, so seems weird to upload it. I'm not sure.

[mcgregorian1]

• [x] confirm link for leaf pheno data (@mcgregorian1 )

The link in the word doc (under Data Availability Statement) is almost correct, it should be: https://developers.google.com/earth-engine/datasets/catalog/MODIS_006_MCD12Q2#description

Otherwise, the .js script that's here is correct.

[teixeirak]

Got it, thanks.

[teixeirak]

Looking at the potential repos, I think NCEI would be the best on that list for weather data, but a NCEI weather station is what I used for filling gaps, so seems weird to upload it. I'm not sure.

I mean just for our weather tower, not the one we downloaded from there. But I'd rather not deal with that unless they insist.

[teixeirak]

With the exception of putting SCBI weather tower data in the NCEI, which I only want to do if specifically requested, this is all done or covered in issue #100 , so closing this issue.