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
@FLomb To properly archive each new release on Zenodo, the following steps are required:
1. adding the .zenodo.json file to the repository with the following structure:
{
"creators": [
{
"affiliation": "affiliation of the first author",
"name": "name of the first author",
"orcid": "orcid id of the first author (optional)"
},
],
"keywords": [
"keyword 1",
"keyword 2",
"keyword 3"
],
"license": "software license",
"upload_type": "software"
}
2. liking the github repo to Zenodo
The text was updated successfully, but these errors were encountered:
Hi @mohammadamint, the automated archival of new releases on Zenodo is something we already have in place for other repos (e.g., RAMP-mobility: https://zenodo.org/records/4849423). So far, I have managed to make it happen by making use of an in-built functionality of Zenodo that allows you to connect to your GitHub repositories from the website interface. And I have set up the same functionality for RAMP, so it should happen when we make a new release. Is there a reason for having the zenodo.json file too?
Hi @FLomb. I believe it is not mandatory but useful for a cleaner and more customizable Zenodo citation. An alternative suggested by Zenodo is CITATION.cff.
@FLomb To properly archive each new release on Zenodo, the following steps are required:
1. adding the .zenodo.json file to the repository with the following structure:
2. liking the github repo to Zenodo
The text was updated successfully, but these errors were encountered: