ORCID-VIVO Integration

15
ORCIDVIVO Integration Work at Cornell University to integrate VIVO with ORCID in a way that works for Cornell and can be used in other VIVO instances Jim Blake, Kathy Chiang , Jon Corson- Rikert , Dean Krafft , Deb Schmidle , Simeon Warner , Tim Worrall (Cornell University) Work as part of the ORCID Alfred P. Sloan Foundation- funded Adoption and Integration Program Outreach Meeting, Chicago, IL, USA. 2014-05-21

description

An update on work at Cornell University to integrate VIVO with ORCID in a way that works for Cornell and can be used in other VIVO instances. Presented as part of the ORCID Outreach meeting, Chicago, 2014-05-21 (https://orcid.org/content/orcid-outreach-meeting-and-codefest-may-2014).

Transcript of ORCID-VIVO Integration

Page 1: ORCID-VIVO Integration

ORCIDVIVO IntegrationWork at Cornell University to integrate VIVO with ORCID in a way that works for Cornell and can be used in other

VIVO instances

Jim Blake, Kathy Chiang, Jon Corson-Rikert, Dean Krafft, Deb Schmidle, Simeon Warner, Tim

Worrall (Cornell University)

Work as part of the ORCID Alfred P. Sloan Foundation-funded Adoption and Integration Program

Outreach Meeting, Chicago, IL, USA. 2014-05-21

Page 2: ORCID-VIVO Integration

VIVO: an open-source linked open data researcher profile and research information system. Over 100 installations across the world(http://www.vivoweb.org)

Here I walk through the integration between VIVO and ORCID to exchange authenticated identities

Screenshots show test site and ORCID sandbox. Soon to be deployed in Cornell VIVO instance

Step 1: Add ORCID iD

Page 3: ORCID-VIVO Integration

Add iD page in VIVO explains process and goals

User clicks “Continue Step 1” when ready

Page 4: ORCID-VIVO Integration

Step 1: Add ORCID iD

ORCID shows register/login page

User logs into ORCID with existing credentials if they already have an ORCID iD. Otherwise they register and create one (very quick)

Page 5: ORCID-VIVO Integration

ORCID shows permissions page

Explains that VIVO is requesting permission to get authenticated identity

User selects either “Authorize” (hopefully) or “Deny” and is returned to VIVO

Page 6: ORCID-VIVO Integration

Having completed step 1 VIVO suggests completing a second step of adding VIVO id into ORCID record

Even if user doesn’t complete this step the ORCID iD has already been recorded in VIVO

Page 7: ORCID-VIVO Integration

ORCID shows permissions page again. No need to login again

Explains that VIVO is requesting permission push VIVO id into ORCID ids list

User selects either “Authorize” (hopefully) or “Deny” and is returned to VIVO

Page 8: ORCID-VIVO Integration

VIVO shows process complete.

Can now see ids in• ORCID record• VIVO profile

Page 9: ORCID-VIVO Integration

Linked VIVO id on ORCID record

Page 10: ORCID-VIVO Integration

Linked ORCID iD in VIVO profile

Shows “(confirmed)” because user has gone through authentication step

Page 11: ORCID-VIVO Integration

Linked ORCID iD in VIVO profile may result from another workflow (data import or manual admin entry)

Shows “(pending confirmation)” because user has not gone through authentication step

Page 12: ORCID-VIVO Integration

• Will be live at Cornell when we move to VIVO 1.6.1

• Will be in VIVO 1.7 release in July (https://wiki.duraspace.org/x/uQhVAw)

• All code available, inc. separable ORCID Java library, on github (https://github.com/vivo-project)

Page 13: ORCID-VIVO Integration

Ah! Cornell... it’s complicated

• 7 colleges, different approaches– Not all using VIVO– All benefit from ORCID iDs through improvement

of data collection via other routes (e.g. Symplectic Elements and manually)

• Graduate students don’t have VIVO profiles so exploring other integration approach...

Page 14: ORCID-VIVO Integration

Reuse of Java library created as part of VIVO integration to create stand-alone application for association of authenticated Cornell ID with ORCID iD

Possible use in graduate school (where VIVO is not used)

Page 15: ORCID-VIVO Integration

Thanks! Talk to me at the poster reception or via [email protected]://orcid.org/0000-0002-7970-7855