ORCID cross-sector application and use case: Employer workflows, Stellenbosch University (M. Roux)
1. Stellenbosch University’s ORCID
integration: an overview
ORCID SOUTH AFRICA WORKSHOP
JULY 2016
Marié Roux
Manager: Research Impact and Research Commons,
Stellenbosch University Library and Information Service
4. Why ORCID
q Some support for ResearcherID, Scopus Author ID, Google Scholar
Citations Profile, and other researcher profile services such as
ResearchGate, Academia.edu existed as part of our Research Support
services
q A sense of responsibility to guide researchers in adopting a specific
standard which is interoperable with other systems and identifiers
q Started a conversation with ORCID mid 2014.
q Signed-up with ORCID (Basic Membership) late 2014 (budget: 2015)
q Some researchers already had an ORCID ID (approximately 300
researchers had an ID even before we started to promote the use of
ORCID on campus)
q Did some initial advocacy in this regard (Library Research Week, May
2015)
4
7. Technical implementation
q A cooperative project between the SU Library and Information Service and the
SU IT Division (IT)
q Use Case for ORCID articulated by the Library
q Supported by the SU Division for Research Support (DRD) from the perspective
of researcher profiling, responding to possible funder requirements, and the
optimisation of future researcher workflows
q Sanctioned by the Vice-Rector: Research, Innovation and Postgraduate Studies
q Workflow and technical implementation mediated by the IT Division
q Ownership rests with the Library, under the Manager: Research Impact
q Timeline: May 2015 – February 2016 (actual development work done in a much
shorter time…)
7
8. Method, Process and Workflow
q The implementation process consisted mostly about figuring out the process
and workflow – the rest was technical coding
q The technical development requirements are well documented by ORCID, but
the process flow and workflow can initially seem a bit confusing
q Workflow is based on entrusting your ORCID profile to a Trusted Organisation
(i.e. university)
q Workflow is initiated by an invitation to “create and/or connect” your ORCID ID
q Access Tokens are retained locally for future authorisation to manipulate ORCID
records on clients’ behalf by the Trusted Organisation
8
16. The APIs – ORCiD
q ORCID is a new and modern application, so it relies heavily on APIs.
You need to interact with ORCID using APIs for all (CRUD) transactions:
q Create an ORCID ID (create-on-demand, or batch load)
q Update ORCID records (if you have been mandated)
q Retrieve ORCID data for reporting purposes
q Delete ORCID records/data
q ORCID: we provide the platform, you provide the API expertise:
q Public API – for everybody and everything that is capable of interfacing with it
q Creator API – for those who subscribe to ORCID (Basic or Premium membership)
16
19. 19
Workshops or short sessions at
faculties and departments
q Engineering Faculty, most Departmental meetings
q Education Faculty, most Departmental meetings
q Arts and Social Sciences Faculty meeting
q Workshop at Medicine and Health Sciences Faculty
q Lunch hour session at SU Business School
q Faculty and branch librarians role:
- actively involved with promotion on an on-going basis
- organising information sessions at faculties or departments
- following up with researchers when they have not created and/or connected their
iDs yet
- assisting researchers to populate their profiles or reminding them to do so
25. Percentage iDs connected
(3 March – 1 June 2016)
25
Percentage ORCID iDs connected to SU
Total number of postgraduate students
registered (Masters, MPhil, PhD, Postdoc,
excluding Honours students)
6596 Total number of academic staff
members (researchers included)
1265
Number of ORCID iDs connected to SU 463 Number of ORCID iDs connected to SU 307
Percentage of total 7% Percentage of total 24%
26. Uptake according to position and faculty
(3 March – 1 June 2016)
26
Academic
staff, 307
Postdocs,
31
Staff, 40
PhD, 151
Masters,
281
Honours, 1 Undergrad,
1
AgriScience,
87
Arts and Soc
Sc, 110
Econ and Man
Sc, 138
Engineering,
111
EducaIon, 31
Medicine and
Health , 149
Science, 114
Theology, 26
Law, 12
Library staff,
20 Other staff, 14
Graph 1: Uptake according to position of client Graph 2: Uptake according to faculty of client
27. Connected iDs per day + cumulative
27
0
100
200
300
400
500
600
700
800
Number of connected id's per
day
CumulaIve number of id's
connected
Graph 3: Uptake according to connected id’s per day and cumulative over
the period of 3 March until 1 June 2016.
29. 29
Integration Points for Universities
q Create/Connect ORCID records – roll-out done, but ongoing
q This is only the first step in the process (to store access tokens for
future integrations)
Link ORCID IDs / Exchange data with:
q Repositories (2017: Full ORCID integration with SU repository
planned)
q Research Information Systems
q Directory / Profile Systems
q But first more adoption needed…