This document summarizes work at Cornell University to integrate their VIVO researcher profile system with the ORCID identifier system. It describes a two-step process for users to authenticate their ORCID ID within VIVO and share their VIVO ID with ORCID. This integration will allow linking of profiles between the two systems. It is being implemented in Cornell's VIVO instance and the code will be available in the next VIVO software release, with potential reuse for graduate student profiles where VIVO is not used.

1. ORCIDVIVO 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

2. 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

3. Add iD page in VIVO explains
process and goals
User clicks “Continue Step 1”
when ready

4. 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)

5. 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

6. 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

7. 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

8. VIVO shows process complete.
Can now see ids in
• ORCID record
• VIVO profile

9. Linked VIVO id on
ORCID record

10. Linked ORCID iD in VIVO
profile
Shows “(confirmed)” because
user has gone through
authentication step

11. 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

12. • 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)

13. 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...

14. 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)

15. Thanks! Talk to me at the poster reception or via
simeon.warner@cornell.edu
http://orcid.org/0000-0002-7970-7855