Zenodo: deposit: automatically add ORCID id of contributor if the account is linked to an ORCID

Created on 6 Jun 2016 · 6Comments · Source: zenodo/zenodo

I have just uploaded https://zenodo.org/record/55004 and I am surprised that my ORCID id does not show up in the metadata. I have not specified it in the deposit interface but my ORCID account is linked to my Zenodo account.

I understand the list of authors of an upload is distinct from its owner, but maybe there could be a workaround for that case?

Keep up the good work!

Enhancement i - Support Accepted Needs design

Source

wetneb

👍14

Most helpful comment

Any updates on this?

banesullivan on 18 May 2019

👍3

All 6 comments

Adding to this. It is not clear how to associate an ORCID with my authorship on software that I've gotten into the Zenodo ecosystem via GitHub integration. When editing an upload, I only see an affliation field, but that only shows up as a tooltip and not the special orcid icon ala https://sandbox.zenodo.org/record/18401

denis-yuen on 6 Dec 2016

👍1

Hi all. I am following this issue. In my case, my zenodo account is linked to ORCID and GitHub. I pull things into my ORCID from DataCite once they have been deposited in Zenodo - this works fine for me.

My issue is that I want to be sure I'm adding the right person when adding _co-authors_ and this is where the ORCID field would come in really handy.

Is this just not part of the metadata schema or am I missing something ? ?

brucellino on 8 May 2017

Indeed it would be handy, and would also allow me to verify, before I hit "publish", that Zenodo has the right ORCID everyone.

Really, it should be as much a part of the UI and schema as "name" and "institution"...

jmason888-berkeley on 19 Jul 2017

I just want to support this, too. I can add orcids when manually creating a new upload but it would be great to specify this also for uploads created from github releases

fredRos on 19 Mar 2018

👍3

Any updates on this?

banesullivan on 18 May 2019

👍3

I found this issue a few weeks ago and have just found a solution (or workaround?)

If you create .zenodo.json in the root of your repo, you can specify particular metadata to send through to Zenodo, and override the default values Zenodo derives from the repo.

Here's an example from a repo I've been testing Zenodo functionality with.