Use ORCID data to populate academic profile page
As discussed at today's CUNY CAT meeting, it would be great if the new profile page template that is in the works could pull your publication data from ORCID.
#1 Updated by Matt Gold almost 3 years ago
Hi Stephen -- my understanding of your request was that publication info be pulled into your profile page -- e.g. https://commons.gc.cuny.edu/members/stephenfrancoeur/ -- rather than into the academic portfolio website we are talking about creating. I am not sure we can set up a website template to have that functionality unless there is an existing ORCHID WordPress plugin that does it and that could be added by default to the template.
#2 Updated by Boone Gorges almost 3 years ago
The documentation is not totally clear to me, but it looks like it should theoretically be possible to pull in a publication record, based on a user's ORCID id, and then to use that data in various places on the Commons. This could be a WordPress widget for use on a site, or it could integrate somehow with the Publications widget on user's public portfolios (or perhaps be a separate widget there).
A brief review of existing tools suggests that we'd probably basically have to start from scratch. https://members.orcid.org/resources has some third-party tools, but none do what's suggested here. https://github.com/ulsdevteam/pkp-orcidprofile/blob/master/pages/OrcidHandler.inc.php looks like it does something similar-ish, but it uses an outdated version of the API and would need heavy adaptation. https://github.com/hubzero/orcid-php looks like it probably works, but it's built around the oAuth workflow, which introduces read/write stuff that I think is only available for Premium ORCID members, which we are not.
I'd suggest that ORCID is not used widely enough to warrant the work we'd need to do for this sort of integration.
#3 Updated by Matt Gold almost 3 years ago
- Status changed from New to Assigned
- Assignee set to Boone Gorges
- Target version set to Future release
Thanks for looking into this, Boone. For now, given our funding situation and available dev time, I think we should put this in "Future Release" and come back to it if time/resources allow. I hope that's okay with you, Stephen.