FOR HBCD: publish on Zenodo to obtain DOI specifically linked to the current version of software #882
Comments
|
We can add it, but version-specific DOIs aren't really useful. There's no good workflow (AFAIK) to generate a version-specific DOI and then put that DOI in the boilerplate (where most people get their reference list) or even the project documentation for that version. |
|
It's up now! https://zenodo.org/records/14187328 |
|
@mattcieslak and @tsalo thank you both. Do you mind adding the Zenodo badge to your readthedocs page as well? Then you'll be ready for the NMIND team to perform the final review The same will need to be done for QSIRecon, I'll open a separate issue on the GitHub |
@tsalo Zenodo has a top-level DOI and per-version DOI (see Nibabies Zenodo for example). I believe it automatically generates per-version DOIs when there's a new release on GitHub |
@mattcieslak -
The MIDB team has submitted an initial NMIND checklist review for QSIPrep as part of efforts to standardize pipelines used for HBCD data processing (detailed here)
QSIPrep hits all major requirements for HBCD and was very highly rated otherwise! The only item remaining is to provide a DOI that specifically links to the current version of the software. Please self-publish on Zenodo and add the DOI to your webpage (it should be quick and easy)
Though not required, if you would like to view additional checklist items that QSIPrep did not meet in order to address them, you can make a copy of the json from this issue and import it to https://www.nmind.org/standards-checklist/
The text was updated successfully, but these errors were encountered: