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
The DataCite Metadata Schema documentation recommends that a new DOI should be assigned when there is a new major version of the resource you are sharing
Zenodo comes to mind as a research product repository that supports versioning like this, and this has been used for some other research-focused software projects. For example:
Zenodo even offers a github integration, where a new DOI is minted and the source code archived on each github release. While this may be fine for most releases, there's a bit of a chicken-and-egg problem because it'd be great to have the DOI be available as a part of the research artifacts and not just tacked on after the fact. I believe a DOI can be reserved in advance through zenodo, but this would need to be confirmed and then integrated into the release automation if so. Otherwise, we'll just have to be OK with noting the DOI after the fact.
The text was updated successfully, but these errors were encountered:
Per the DataCite Best Practices documentation:
Zenodo comes to mind as a research product repository that supports versioning like this, and this has been used for some other research-focused software projects. For example:
Zenodo even offers a github integration, where a new DOI is minted and the source code archived on each github release. While this may be fine for most releases, there's a bit of a chicken-and-egg problem because it'd be great to have the DOI be available as a part of the research artifacts and not just tacked on after the fact. I believe a DOI can be reserved in advance through zenodo, but this would need to be confirmed and then integrated into the release automation if so. Otherwise, we'll just have to be OK with noting the DOI after the fact.
The text was updated successfully, but these errors were encountered: