Add ORCID iD support

pjfasano

ORCID supports Content Negotiation, and can provide a JSON-LD response with the Person type:

https://info.orcid.org/documentation/api-tutorials/api-tutorial-read-data-on-a-record/#More_information

https://github.com/ORCID/ORCID-Source/blob/development/CONTENT_NEGOTIATION.md

vladimyr

pjfasano ORCID supports Content Negotiation, and can provide a JSON-LD response with the Person type:

pjfasano https://github.com/ORCID/ORCID-Source/blob/development/CONTENT_NEGOTIATION.md

It is worth noting that ORCID's content negotiation triggers HTTP redirect to their public API endpoint:

# using official example ORCID of fictitious professor Josiah Carberry: https://orcid.org/0000-0002-1825-0097

$ curl -isH'accept:application/json' 'https://orcid.org/0000-0002-1825-0097' | grep '^location:'
#==> location: https://pub.orcid.org/0000-0002-1825-0097

$ curl -isH'accept:application/ld+json' 'https://orcid.org/0000-0002-1825-0097' | grep '^location:'
#==> location: https://pub.orcid.org/0000-0002-1825-0097

lametti

Agree - ORCiD also supports user entry of links (for example, back to a keyoxide profile) that appear in the JSON response as linked above.

lametti

Name: ORCiD
Homepage: https://orcid.org/
Short description: "ORCID provides a persistent digital identifier (an ORCID iD) that you own and control, and that distinguishes you from every other researcher. You can connect your iD with your professional information — affiliations, grants, publications, peer review, and more. You can use your iD to share your information with other systems, ensuring you get recognition for all your contributions, saving you time and hassle, and reducing the risk of errors."
Optional API documentation URL: https://info.orcid.org/documentation/features/public-api/

(used template in sticky post)

lepus2589

I opened two PRs adding this feature:

Thanks to the research provided by @pjfasano and @lametti, this was straightforward to implement.

With this change, you can place the proof in your biography, your keywords or your social links on orcid.org. Whichever place you choose must be made public, of course. This might be a privacy concern for the biography. In this case, you have to switch to keywords or social links, where you can configure visibility per keyword or link.

If you have questions or comments, please add them to the PRs.

lametti

lepus2589 Thanks! Everything looks good on the pull requests to me.

vladimyr

lepus2589 I opened two PRs adding this feature:

https://codeberg.org/keyoxide/doipjs/pulls/47
https://codeberg.org/keyoxide/keyoxide-docs/pulls/22

Both PRs have been merged and the docs are up. Great work everyone and thanks for your patience!
I'll mark this as done as soon as we cut the new doip.js release and it gets deployed on keyoxide.org!