Incorporate ORCiDs associated with contributors into .zenodo.json files

[rebeccaringuette]

Is your feature request related to a problem? Please describe.
The link from GitHub to Zenodo is great to automate version-controlled DOI creation, but it is too time consuming to manually add every contributor to that file and especially hard to track down the ORCiD of each contributor to include in the file Zenodo uses to create those DOIs (.zenodo.json files). GitHub users now have the ability to include their ORCiD in their profile (see mine!), so the information is available in GitHub.

Describe the solution you'd like
When the allcontributors bot adds a contributor to a repository, it should add their name and the proper author or contributor role to the .zenodo.json file. If the person has an ORCiD associated with their profile, that ORCiD should be included in the .zenodo.json file.
A nice add-on here would be to scrape the contributor's affiliation and that affiliation's ROR, likely from ORCiD.

Describe alternatives you've considered
I considered asking for this for citation.cff files, but publishers regard the DataCite DOI minted through Zenodo as the "record of truth", so I am preferring the .zenodo.json file instead since that file is used in the link to Zenodo to create those DataCite DOIs. It is too much work to keep both files synchronized.

Additional context
The instructions for adding your ORCiD to your GitHub profile.
The Zenodo page about .zenodo.json files.

[Berkmann18]

I have no idea about what Zenodo/ORCiDs and it may be too specific to be something handled by AC (unless a huge amount of AC users use that).

There's some long-standing work in progress to get the CLI to auto-add contributors on a repo, I wish I was able to get it released (or at least a minimal version, as I aimed too high from the start and had to step away from OSS), so that feature should solve some of the issues you mentioned.

[lwasser]

@all-contributors please add @rebeccaringuette for ideas

[allcontributors]

@lwasser

I've put up a pull request to add @rebeccaringuette! 🎉

[lwasser]

I might be able to help a bit here @Berkmann18. Essentially, in the scientific space, there is some value to having your ORCID (which is a unique identifier) associated with your name. It's an academic identifier that facilitates the easier tracking of publications and recognition of work. Zenodo just allows us to get a DOI for any GitHub repository.

i made a video on it: https://www.youtube.com/watch?v=1pI4QU-7c98 :)

@rebeccaringuette hi 👋🏻 good to see you here!!

i think where I'm getting a bit lost in your request is the zenodo file. Are you saying that you want all contributors to update the Zenodo file for the maintainer as well (in addition to the all-contributors file created)?

I have definitely scraped user profiles on GitHub - we do it at pyOpenSci, but it takes time to run those api calls and potentially an API key (I can't remember the volume of requests that require that key, but it's good to have). So essentially, it likely would add some complexity to our workflow that would require testing and might be out of scope. But it would be a really cool plugin or add-on tool to be maintained separately.

However, I may not totally understand your goals!!

[rebeccaringuette]

I'm wondering if a simple solution is possible. The idea is to get all the contributors' ORCiDs to automatically pipe into the DOI metadata through the GitHub-Zenodo workflow. Many software packages use this link to automatically create DOIs for major releases, which depend on the .zenodo.json file description here. Additionally, GitHub now supports linking your ORCiD to your profile, but does not serve that link through their API (yet).
First, does the allcontributors bot add the person's ORCiD to a file on the repo when they are added? If not, how difficult would that be to add?
Second, can the creators/contributors list generated by the allcontributors bot be piped into a metadata file Zenodo uses to create DOIs, such as the codemeta.json file or the .zenodo.json file? This would mean the contributors are more likely to receive correct attribution when the software package is cited with its DOI.