| | 165 | * According to the Zenodo helpdesk, two options exist to connect the GRASS codebase to the Zenodo archive: |
| | 166 | 1. REST-API (of Zenodo) or manual upload into Zenodo |
| | 167 | 2. !GitHub Integration |
| | 168 | * It is possible to start the process with !GitHub Integration and then (for whatever reason) fall back to the REST-API/manual upload. |
| | 169 | * It is NOT possible to start with the REST-API/manual upload and to switch to !GitHub Integration later. |
| | 170 | * Zenodo helpdesk on !GitHub Integration: ''If you want to use our !GitHub integration, then you must move the source code to !GitHub and activate the repository in Zenodo (see the !GitHub guide). Afterwards, you make a new release in GitHub for each of your releases (see also the !GitHub guide). You have to make the releases in the order you want them to appear in Zenodo. If you have tags push to !GitHub, then you can upgrade a tag to a release in the !GitHub interface.'' |
| | 171 | * Zenodo helpdesk on DOI versioning scheme: ''Zenodo keeps the version number and date in a metadata field that you can change as you see fit even after publishing. By default Zenodo orders the releases in the order we receive them (i.e. by date). This is however only for display purposes, and it is essentially the same way !GitHub orders their releases page. In the metadata however, we do not care about ordering (because it's very hard to model the ordering correctly). We simply have a concept DOI that links to all the the specific version DOIs via !HasVersion/IsVersionOf relationship.'' |
| | 172 | * Zenodo helpdesk on mishaps: ''...in case you make a mistake, we do have the possibility to reorder the releases manually. Naturally we would like to avoid this, however just rest assured that we can fix it if you make a mistake.'' |
| | 173 | |
| | 174 | |
| | 175 | |
