Support for the ORCID v3 APIs

[crawley]

From what I can see, there is nothing in the current codebase to support the ORCID v3 APIs. Is anyone working on this?

(I am kind of worried that they are going to deprecate / de-support the v2 APIs and we will be stranded.)

[astrochun]

I recently contacted the maintainer (@MSusik) about this. He mentioned that he would revisit the code some time in the near future to determine issues, etc.

[commonism]

The Swagger 2.0 REST API requires a client with oauth

https://github.com/ORCID/orcid-model/blob/master/src/main/resources/record_2.1/README.md#rest-api-reference

https://pub.orcid.org/v3.0/ https://pub.orcid.org/resources/swagger.json

https://api.orcid.org/v2.1/#/ https://api.orcid.org/resources/swagger.json

[MSusik]

@commonism : In ORCID's 2.0 one was doing the Oauth through the https://orcid.org/oauth/custom/login.json endpoint. I can't make it work anymore, probably because I'm missing the CSRF token that must have been moved somewhere else. See https://github.com/ORCID/python-orcid/issues/37

@astrochun The problem is I can't make the library work with the API version 2.0. It used to work well. I unfortunately couldn't get a response from the ORCID team if there is any way to go around the issue above. And from what I see I don't have anymore permissions to this repo, therefore I can sadly only state that this repo won't be maintained anymore: https://github.com/ORCID/python-orcid/pull/36