3. •Support the proposal that all researchers at the
University of Stirling register for an ORCID ID and
that they record this ID within RMS.
•Recommend a senior colleague to champion
the take-up of ORCID by emailing all staff
Invited them to
4. • Recommend that Directors of
Research encourage their
researchers to register for an ORCID
ID, and to record this within RMS
Invited them to (contd.)
5. • Deputy Principal emailed all researchers via
a generic email 11 August 2016 – 111
ORCID
• Update at Sept RC 2016 meeting – 162
ORCID
• Personalised email from me in September
2016 to those without ORCIDs – 225 ORCID
Actions
6. • Deputy Principal emailed
all researchers via a
generic email August
2016 – 111 ORCID
• Update at Sept RC 2016
meeting – 162 ORCID
• Personalised email from
me in September 2016 to
those without ORCIDs –
225 ORCID
7. Challenges
• Non-current staff in RMS
• Lack of developer time, e.g. API 2.0
• Disparity between ORCID report and
RMS numbers
• May 2018 694 vs 402 on RMS
8. Current situation
• Moved from Converis to Worktribe
• Worktribe and ORCID working together
(from Crossref)
• Papers in CrossRef with ORCIDs matching
Worktribe ORCIDs are automatically
imported
Also started doing Faculty reports giving them a breakdown – but change in Assoctie Deans and busy doing other stuff meant didn’t do regularly!
This relies on the ORCIDs being included in the data sent to Crossref (from the publisher normally). The next step is to have a direct link between Worktribe and ORCID.