Presentation at ORCID Vancouver Workshop (7 October 2016)

1. ORCID: COLLECT AND CONNECT
ORCID WORKSHOP, VANCOUVER| OCTOBER 7, 2016
MATTHEW BUYS
orcid.org/0000-0001-7234-3684
REGIONAL DIRECTOR

2. OUR VISION
ORCID’s vision is a world where
all who par5cipate in research, scholarship, and
innova5on are uniquely iden5fied
and connected to their contribu5ons and
affilia5ons across 5me, disciplines, and
borders.

3. Persistent digital identifiers to distinguish researchers
from each other
Member-built integrations for automated links between
researchers and their activities/affiliations
A hub for machine-readable connections between
identifiers for organizations, funding, outputs, and people
ORCID provides
✔ Plumbing for research information
✔ Tools to build trust in digital information

4. INTEGRATIONS BY
REGION
15%
52% 1%
2%
30%
Asia Pacific
Europe
Latin America
Mid East & Africa
US/Canada

5. INTEGRATIONS BY
SECTOR
7%
5%
16%
10% 62%
Associa5ons
Funders
Publishers
Repositories/Profile organiza5ons
Research ins5tu5ons

7. COLLECT & CONNECT
GOALS
• Clarify how plumbing works
• Standardize experience
• Standard connection installation guidelines
• Increase predictability and trust in the “utility”
• Community approach to reliable connections

8. COLLECT & CONNECT
Collect
Display Connect
Synch
Authen5cate!

9. COLLECT
COLLECT validated ORCID iDs for
individuals
• Explain what ORCID is
• Explain why you’re collecting iDs
• Consistent user experience
• Authenticated connections
Ensure individuals are correctly connected with your ins5tu5on
Converis, Pure, Symplec5c Elements, VIVO use the OAuth process

10. DISPLAY
DISPLAY iDs on your website, plaUorm, systems
• iDs shown as a link
• iDs in metadata
• Use the ORCID Member logo
• Explain why iDs are collected
Signal that your systems are plumbed to support ORCID iDs
hVp://orcid.org/trademark-and-id-display-guidelines

11. CONNECT
CONNECT your data to ORCID Records
• Request permission to write to Records
• Store long-lived tokens
• Add data that you uniquely can (authoritative)
• Explain the connection
Enable researchers to provide validated data to others
hVps://orcid.org/blog/2015/10/26/auto-update-has-arrived-orcid-records-move-next-level

12. SYNCHRONIZE
SYNCHRONIZE with your systems
• Update information when it changes
• Auto-add new information
• Search & link wizards
• Sync data from others
Saved 5me, beVer repor5ng, improved informa5on flow
hVps://members.orcid.org/api/tutorial-webhooks
hVps://orcid.org/blog/2015/10/26/auto-update-has-arrived-orcid-records-move-next-level

13. DISPLAY
• In metadata
• On sites
• In publications
CONNECT
• Affiliations (employers)
• Works (publishers)
• Awards (funders)

14. PEOPLE, PLACES, AND
THINGS

15. INTEGRATION PROCESS
Technically, integra5ng ORCID involves
adding <person ID> and <source> fields to data
models, mapping to ORCID API, and
implemen5ng OAuth and RESTful calls.
Socially, it is cri5cal that researchers are
engaged in the process.

16. COMMUNITY RESOURCES
• Best practices and use cases
• Updated info on members.orcid.org
• Resources and collateral for researchers
• ORCID engagement & awareness campaign

17. BEST PRACTICES AND USE
CASES
• Sample text for describing ORCID and your
engagement
• Graphics, videos, use cases
• Collect & Connect program badges
• Code samples, workflows, and API tutorials

18. UPDATES TO
MEMBERS.ORCID.ORG

19. RESEARCHER RESOURCES
• Researcher workflow infographics
• Sofia Maria video
• Relevant blog posts
• Researcher use cases, testimonials
• Membership and integration lists
• Mini-videos of how ORCID works

20. ENGAGEMENT CAMPAIGN
• Series of blog posts
• Social media campaign
• Speaking engagements
• Ambassador outreach

22. • Find out more at http://orcid.org
• Register at http://orcid.org/register
• Twitter @ORCID_Org / @mjbuys
Thank you!
Matthew Buys
Regional Director, ORCID
m.buys@orcid.org
hVp://orcid.org/0000-0001-7234-3684