DOI/admin rights

[mjt320]

Hi there,

Before submitting the manuscript we were planning to create a release + DOI for the repository using Zenodo.
I'm happy to do this but need to be an admin. @LucyKershaw @stadmill are you able to give me that status temporarily?

Thanks,
Michael

[LucyKershaw]

I'd be delighted to do this, if only I knew how. What is zenodo?

[plaresmedima]

Hi Michael - is there an OSIPI community onZenodo? Briefly discussed this with Henk as there will be a software release for teh challenge as well and presumaably others. Would be great if these all come under the same community Prof. Steven Sourbron, PhD Chair in Medical Imaging Physics University of Sheffield, UK *https <https://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron>://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron <https://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron>* *Sheffield abdominal imaging research page* <https://www.sheffield.ac.uk/medicine/research/research-themes/medical-imaging/medical-imaging-research/abdominal-imaging> *Open source initiative in perfusion imaging* <http://www.osipi.org> *Magnetic resonance imaging biomarkers for chronic kidney disease <https://renalmri.org/>*

…

On Wed, 8 Mar 2023 at 16:04, mjt320 ***@***.***> wrote: Hi there, Before submitting the manuscript we were planning to create a release + DOI for the repository using Zenodo. I'm happy to do this but need to be an admin. @LucyKershaw <https://github.com/LucyKershaw> @stadmill <https://github.com/stadmill> are you able to give me that status temporarily? Thanks, Michael — Reply to this email directly, view it on GitHub <#128>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOFKA4FAS7WTVECQFNU2QTW3CUYXANCNFSM6AAAAAAVT6ORF4> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[petravanhoudt]

@HenkMutsaerts, do you know if we are the first that want to create something on Zenodo?

[petravanhoudt]

Hi @mjt320, I guess you need admin rights to the repository? Henk recently reorganized the rights and put everyone in teams, where members have write access. Only lead/colead + management team have admin rights at the moment. I added you as an individual member now with maintain rights. Are these sufficient or do you need a level higher to create the DOI?

Let me know when you are done, such that we can remove the rights to keep things clean according to Henk's standards :)

Petra

[mjt320]

Thanks @petravanhoudt . That should work.
@LucyKershaw It stores a frozen snapshot of the repo and makes a DOI for it
@plaresmedima I can't see an OSIPI community on zenodo.

[mjt320]

I can create a zenodo group now and transfer the ownership later, if nobody objects.
Ultimately, it might be easiest to set up an osipi github account for this purpose (if there isn't already one)

[petravanhoudt]

sounds good!

[plaresmedima]

I think that's great but please check with Henk as he was looking at this too. I have copied him in. Just so we don't end up with two ;-) Prof. Steven Sourbron, PhD Chair in Medical Imaging Physics University of Sheffield, UK *https <https://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron>://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron <https://www.sheffield.ac.uk/medicine/people/iicd/steven-sourbron>* *Sheffield abdominal imaging research page* <https://www.sheffield.ac.uk/medicine/research/research-themes/medical-imaging/medical-imaging-research/abdominal-imaging> *Open source initiative in perfusion imaging* <http://www.osipi.org> *Magnetic resonance imaging biomarkers for chronic kidney disease <https://renalmri.org/>*

…

On Thu, 9 Mar 2023 at 15:50, Petra van Houdt ***@***.***> wrote: sounds good! — Reply to this email directly, view it on GitHub <#128 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOFKAZBCOW53C6Z4KOPP3TW3H34DANCNFSM6AAAAAAVT6ORF4> . You are receiving this because you were mentioned.Message ID: <OSIPI/DCE-DSC-MRI_CodeCollection/repo-discussions/128/comments/5256124@ github.com>

[notZaki]

For zenodo, will the co/authors be a catch-all like "OSIPI Community" or will it be every code contributor?

Also, if the citability of the zenodo DOI is important, then it might be worth adding a small "How to cite" section, such as a paragraph in the readme, to help out people that may be unfamiliar with zenodo. For example, there's usually multiple zenodo DOIs: each release gets its own and then there is one which always resolves to the latest release, so we could include the always-resolves-to-latest DOI in the readme to simplify it for users.

[mjt320]

Thanks @notZaki . I'm new to Zenodo so that's helpful.
The idea is to provide a DOI referencing the data presented in the paper, i.e. the first release. Authors would be all of us, I guess.
Agree it's important to consider how users can cite code and when to make future releases - probably something for the current TF & leadership to discuss @stadmill @LucyKershaw

[plaresmedima]

You can have an osipi community but then inside of that any number of code releases or data each with their own set of authors. For this I think you should also use a versioned DOI so that the same DOI can be used to refer to any future versions as well. As an example we just set a community up for Sheffield https://zenodo.org/communities/qib-sheffield/?page=1&size=20 It contains one software release with a versioned DOI cited in the accompanying paper https://zenodo.org/record/7507642#.ZAo6caTLc0E

…

On Thu, 9 Mar 2023, 18:18 Zaki A., ***@***.***> wrote: For zenodo, will the co/authors be a catch-all like "OSIPI Community" or will it be every code contributor? Also, if the citability of the zenodo DOI is important, then it might be worth adding a small "How to cite" section, such as a paragraph in the readme, to help out people that may be unfamiliar with zenodo. — Reply to this email directly, view it on GitHub <#128 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABOFKAY7L3OZ24BVO746RDDW3INGLANCNFSM6AAAAAAVT6ORF4> . You are receiving this because you were mentioned.Message ID: <OSIPI/DCE-DSC-MRI_CodeCollection/repo-discussions/128/comments/5257753@ github.com>