You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To keep a consistent record of the development progress and get a DOI, station catalog the content of the repository will be added to Zenodo.
This will occur every time a new release is made on GitHub, which will depend on the development progress. The releases will be named based on the date, e.g., 2024-03-05.
After some thought, I've decided that it's overkill adding the entire repository to Zenodo and undesireable as this gets uploaded as a zip file and thus it's not possible for parse the station catalog csv file directly from Zenodo.
Instead, I suggest writing a custom GitHub action / function that uploads a new version of the station catalog upon a new GH release. The releases will be named based on data and be used to set the Zenodo version.
Should consider adding a header with the DOI number?
It is not possible to pre-reserve DOIs before using GitHub integration with Zenodo. You can however manually upload your release to Zenodo, in which case it is possible to pre-reserve a DOI. See https://help.zenodo.org/docs/deposit/describe-records/reserve-doi/ for further details.
To keep a consistent record of the development progress and get a DOI, station catalog
the content of the repositorywill be added to Zenodo.This will occur every time a new release is made on GitHub, which will depend on the development progress. The releases will be named based on the date, e.g.,
2024-03-05
.This action is enabled through Zenodo: https://zenodo.org/account/settings/github/The text was updated successfully, but these errors were encountered: