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

DOIs no longer created automatically by zenodo? #7

Open
gaelforget opened this issue Feb 11, 2020 · 7 comments
Open

DOIs no longer created automatically by zenodo? #7

gaelforget opened this issue Feb 11, 2020 · 7 comments

Comments

@gaelforget
Copy link
Member

gaelforget commented Feb 11, 2020

The latest releases for both MeshArrays (now 0.2.6) and IndividualDisplacements (now 0.1.6) do not seem to have gotten DOI'ed the way I would have expected. I noticed this because DOI and DOI kept pointing to earlier release archives

edit: the fix for this is explained in the first few posts below

I am rather confused by the fact that v0.2.5 of MeshArrays (NO DOI) and v0.1.5 of IndividualDisplacements (with DOI) were both released after transfer to the org & before the tagbot action PRs. Most recently, neither MeshArrays 0.2.6 nor IndividualDisplacements 0.1.6 seem to have gotten a DOI (or I just don't know where to find them).

In addition when I look under the GitHub list in zenodo under my account, I cannot find either of these packages. This made me wonder if somehow we have another account for the org at zenodo that I do not know how to access. Where is the list that allow me to switch zenodo on / off for MeshArrays & IndividualDisplacements?

In contrast, I noted that ClimateTools has been getting DOI'ed as I would expect for the other packages. @Balinus do you have an idea of what I might be missing or overlooked?

Maybe I need to do something else at the org, team, or repo level?

edit: the first few posts below provide explanations & links related to this. Thanks @Balinus

@Balinus
Copy link
Member

Balinus commented Feb 11, 2020

I must say that I have not modified anything related to ClimateTools and Zenodo since the migration. So, I'm rather confused as to why it worked in the 1st place.

@Balinus
Copy link
Member

Balinus commented Feb 11, 2020

Important! If you want to archive a repository that belongs to an organization on GitHub, you will need to make sure that the organization administrator has enabled third-party access to the Zenodo application

https://guides.github.com/activities/citable-code/

While browsing though, I can't see how I can authorize Zenodo at the org level. https://github.com/organizations/JuliaClimate/settings/oauth_application_policy

Zenodo is not listed and I can't find how to let Zenoda "ask" the permission.

@Balinus
Copy link
Member

Balinus commented Feb 11, 2020

Just found it, buried under my personal settings. I just granted the access to the JuliaClimate org.

In your zenodo settings, you should be able to see the repos: https://zenodo.org/account/settings/github/

@gaelforget
Copy link
Member Author

gaelforget commented Feb 11, 2020

Just found it, buried under my personal settings. I just granted the access to the JuliaClimate org.

Great! I think you were referring "personal settings" and "GitHub OAuth settings" on GitHub (not zenodo) based on https://help.zenodo.org (see next post)

@gaelforget
Copy link
Member Author

gaelforget commented Feb 11, 2020

The answer under My organizational repository does not show up on the GitHub list @ https://help.zenodo.org does help and is consistent

In your zenodo settings, you should be able to see the repos:

The juliaclimate repos now appear in list. I might just have overlooked to do the correctsync.

Trying another release now as a test...

@Balinus
Copy link
Member

Balinus commented Feb 11, 2020

Well, what I meant is that I found the Zenodo app in my personal setting, which then allowed me to configure the app for JuliaClimate 😄

edit- Before that, the repos were not showing in the Zenodo web setting page.

@gaelforget
Copy link
Member Author

Trying another release now as a test...

Everything seems to be back in order now as illustrated in https://github.com/JuliaClimate/IndividualDisplacements.jl/releases/tag/v0.1.8

Ps. For now I keep this issue open since the thread & links might help the next person to do this. Happy to close if that's the consensus though.

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

2 participants