Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create a DOI for this repository #273

Open
dawehner opened this issue Jun 3, 2014 · 6 comments
Open

Create a DOI for this repository #273

dawehner opened this issue Jun 3, 2014 · 6 comments

Comments

@dawehner
Copy link

dawehner commented Jun 3, 2014

Since https://guides.github.com/activities/citable-code/ you can create a DOI for your git repositories which could be a better alternative than just linking to repo URL or the arXiv paper.

What do you think about this?

@hannorein
Copy link
Member

I looked into this while ago, but their system does currently not support organization based repositories (such as this one). I was told this feature will be added some time soon. If so (did they already?), then I see no reason why we shouldn't do that.

@ryanvarley
Copy link
Contributor

My organisation repos show up on Zenodo so i assume you can

@hannorein
Copy link
Member

They've just added it. Nice.

@hannorein
Copy link
Member

So this works on a release basis. How shall we do that given that the catalogue is constantly updated.

@ryanvarley
Copy link
Contributor

Thats a good point, you can edit the DOI so perhaps they will let you move it with releases.

Given that I am not sure a DOI will be useful for this project. Surely a reference to the paper, the date of the commit and the SHA-1 is much more meaningful and useful.

@dawehner
Copy link
Author

In theory zenodo has an API https://zenodo.org/dev so you could use the hooks built into github to create releases on every commit OR run some cron every N days ...
On the other hand it is a good point that the repo is always updated, so a commit hash as well as the ArXiV paper would be fine as well.

Feel free to mark this issue as closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants