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
I was wondering why the cheatsheet for FAIRcode specifies specifically to use Zenodo instead of just any repository that allows file upload. The Zenodo integration might be nice for Zenodo to 'automatically' pickup any release made on Git and publish it, but it basically just made a download of the master branch released and uploaded it to Zenodo. Such actions can simply be done manually (download zip of master branch and upload zip wherever is possible). In that way it might be much simpler for those that want to upload their Git main with associated data (if code was relatively small and associated with data to analyse and process) in 1 repository (Yoda, 4TU, DANS, depending on file sizes DatVerse, etc) and results in less doi cluttering. But if the automatic integration is a key aspect, I believe 4TU.ResearchData also have their own integration with GitHub. And what about people not using GitHub but another Git instance (GitLab, BitBucket, etc), or are just not using Git at all but still have code or scripts they want to publish? What if someone made a release but wasn't meant as a release or sensitive information was accidentally present that should be removed, the automatic integration published it with a DOI and Zenodo can be a bit picky in retracting which may be an issue with accidental sensitive information:
This can be avoided by keeping manual control of the process.
The text was updated successfully, but these errors were encountered:
I was wondering why the cheatsheet for FAIRcode specifies specifically to use Zenodo instead of just any repository that allows file upload. The Zenodo integration might be nice for Zenodo to 'automatically' pickup any release made on Git and publish it, but it basically just made a download of the master branch released and uploaded it to Zenodo. Such actions can simply be done manually (download zip of master branch and upload zip wherever is possible). In that way it might be much simpler for those that want to upload their Git main with associated data (if code was relatively small and associated with data to analyse and process) in 1 repository (Yoda, 4TU, DANS, depending on file sizes DatVerse, etc) and results in less doi cluttering. But if the automatic integration is a key aspect, I believe 4TU.ResearchData also have their own integration with GitHub. And what about people not using GitHub but another Git instance (GitLab, BitBucket, etc), or are just not using Git at all but still have code or scripts they want to publish? What if someone made a release but wasn't meant as a release or sensitive information was accidentally present that should be removed, the automatic integration published it with a DOI and Zenodo can be a bit picky in retracting which may be an issue with accidental sensitive information:
![image](https://private-user-images.githubusercontent.com/45395070/323116782-db733b12-c74f-4752-abdf-4344e4ea29df.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3Mzk1NTM4MTIsIm5iZiI6MTczOTU1MzUxMiwicGF0aCI6Ii80NTM5NTA3MC8zMjMxMTY3ODItZGI3MzNiMTItYzc0Zi00NzUyLWFiZGYtNDM0NGU0ZWEyOWRmLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAyMTQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMjE0VDE3MTgzMlomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTc2YmNlOWRhYjY0MzI1NjU1NDM0Y2UzMzExNmUxMWI5MzE1YzRhOTA5MTEwNTgyYTlhZmM4ZjA0NTEyYzJmMzAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.DVgARdeaObAvPRJotBLprP84lFIvZD4sXMrY2abmNZ8)
This can be avoided by keeping manual control of the process.
The text was updated successfully, but these errors were encountered: