Apresentação ORCiD USP 2017
2 likes•1,140 views
The document outlines the purpose and benefits of ORCID, a system designed to uniquely identify researchers and connect them with their contributions and affiliations to improve accuracy and recognition in research. It emphasizes the need for such a system due to the complexity of connecting information by names, particularly with many authors sharing similar names. The document also details the integration of ORCID with various systems, offering solutions for organizations to manage researcher information and streamline reporting processes.
Apresentação ORCiD USP 2017
- 1. ORCID UNIVERSIDADE DE SÃO PAULO - USP 23 DE MARÇO DE 2017 ANA VERA WYNNE Community Support Specialist – North America 0000-0002-9810-2894
- 2. AGENDA • ORCID e os problemas que ela soluciona • A estrutura do registro ORCID • Integrando diferentes systemas • Campanha de comunicação vs tecnologia da integração • Idp e documentação • Perguntas e Respostas
- 3. ORCID Open Researcher and Contributor ID • 3,180,000 + ORCID iDs in existence • 645 members worldwide • Research institutions • Government agencies • Research funders • Publishers • Vendors • 340 integrations with ORCID API
- 5. WHY ORCID?
- 6. CONNECTING INFO BY NAMES IS COMPLICATED Of the more than 6 million authors in a major journal citations and abstracts database,+2/3 share last name and single initial with another author. An ambiguous name in the same database refers on average to 8 people. http://ands.org.au/newsletters/share_issue18.pdf
- 7. ORGANIZATION/MEMBER BENEFITS 1. Reduce/eliminate need for researcher disambiguation within and between systems 2. Enable automatic system-to-system updates for researcher reporting 3. Validate your researchers’ affiliation, awards, or works – building trust in the overall research infrastructure 4. Improve speed and accuracy of research reporting 5. Maintain connections with researchers despite name/affiliation changes 6. Ensures your researchers comply with funders and publishers requiring ORCID 7. Learn from other organizations’ experiences and share your own 8. Be eligible for public recognition of good ORCID integrations 9. Get involved and help shape ORCID’s future priorities and goals 10. Play your part in making the Internet work better for researchers Community survey (2015): orcid.org/blog/2015/11/23/survey-says-community-perceptions-orcid-part-1
- 8. RESEARCHER BENEFITS 1. Reliably and easily connects you with your contributions and affiliations 2. Alleviates mistaken identity 3. Saves you time – “enter once, re-use often” 4. Improves recognition and discoverability for you and your research outputs 5. Your lifelong digital name 6. You own and control your record, managing what information is connected and how it is shared 7. Enables you to comply with organizations that require ORCID iDs 8. Many systems you already use are connected with ORCID 9. Free to register and use 10. Enables you to play your part in making the Internet better! Community survey (2015): orcid.org/blog/2015/11/23/survey-says-community-perceptions-orcid-part-1
- 9. ORCID’S VISION IS A WORLD WHERE ALL WHO PARTICIPATE IN RESEARCH, SCHOLARSHIP, AND INNOVATION ARE UNIQUELY IDENTIFIED AND CONNECTED TO THEIR CONTRIBUTIONS AND AFFILIATIONS ACROSS TIME, DISCIPLINES, AND BORDERS.
- 10. ORCID PROVIDES Persistent digital identifiers to distinguish researchers from each other Member-built integrations that connect researchers and their activities/affiliations A hub for synchronizing machine-readable connections between identifiers for people, organizations, and research activities ✔ Plumbing for research information ✔ Tools to build trust in digital information
- 11. ORCID AS PART OF PLUMBING
- 14. Email check Name check Email displayed if public on record REGISTRATION IS SIMPLE 1. Registering for an iD Self-registration only 1. orcid.org/register 2. Less than 30 seconds Duplicate filters
- 15. THE ORCID RECORD Biographical data è ç Education data ç Employment data ç Works data ç Funding data
- 17. THE ORCID RECORD Education & employment data Organization list from è Ringgold (an ISNI Registrar)
- 18. THE ORCID RECORD Funding data Funding agency ç list consistent with FundRef Search & link wizard ê
- 19. THE ORCID RECORD Works data Structured citations in BibTeX Classifications & metadata fields consistent w/CASRAI Translated titles & language support Search & link wizards: • Crossref Metadata Search • Scopus • Europe PubMed Central • ResearcherID • Modern Language Association • DataCite Metadata Store • Redalyc • Ariti • ANDS Registry BibTeX import
- 21. THE ORCID RECORD Peer review data Only posted via API by clients approved for peer review Live: F1000,AGU/eJournalpress, Publons In progress:Aries Systems, Hindawi, Politics & Religion Journal, Peerage of Science Coming soon: Search & Link wizard!
- 22. USER PRIVACY Information in an ORCID Record has a privacy setting, which only the account owner can set – API cannot override. Account information (settings, permissions) accessible by the account owner. Public view Account ownerAccount owner, Trusted orgs & individuals Accessible by :
- 23. THE ORCID API API Features Member API ORCID member organizations • Read (Limited): Search/retrieve limited-access data • Add: Post new items to a record • Update: Edit or delete items you previously added Premium Member API Premium ORCID member organizations • Webhooks: Receive notifications of updates • Customised monthly reports (including email stats) • Access to monthly public data file
- 24. ORCID REGISTRY CONNECTIONS Two models: 1. Connect via a vendor system • Manuscript submission/publication • Document/data repositories • Profile systems • CRIS systems 2. Develop a custom connection
- 25. VENDOR CONNECTIONS Document / data repositories • DSpace • ePrints • Hydra/Fedora CRIS Systems • Converis • Elements • IRMA • Pivot (ProQuest) • PlumX • Pure • Vivo Find more: https://members.orcid.org/orcid-enabled-systems
- 26. CUSTOM INTEGRATIONS Via the ORCID API • Fine-tuned control and permissions • Customized buttons, user flows, & user feedback Current integration list: http://members.orcid.org/current-integrations
- 27. THE ORCID API IN A NUTSHELL • Permissions / scopes: your contract with the user • The ORCID messages: format of the data exchanged • OAuth calls (the permission protocol): how you execute the contract • ORCID-specific calls: to provide & receive information with the registry
- 29. COLLECT & CONNECT GOALS • Clarify goals and expectations across sectors • Standardize and improve the user experience • Improve understanding and trust in connections made between ORCID and other identifiers • Increase efficiency and quality of integrations • Help achieve the ORCID vision through a community approach NOTE: this image is much larger, so used crop tool to move it around and position in the frame here. May need to do some adjusting to this high res image in terms of contrast etc. if it looks too ”dark”
- 32. 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 institution Many vendor systems use the OAuth validation process
- 33. GET & USE PERMISSIONS ORCID Record Yes! Do you have permission to do what you want to do? Get the permission; store iD and “token” Read the record or update the record No OAuth
- 34. GET PERMISSION ORCID registry depends on user-based permissions: Can I... • have your iD (/authenticate) • read limited-access data on your record (/read-limited) • interact with the activities on your record (/activities/update) • interact with your biographical information (/person/update)
- 35. INVOLVING THE USER Key benefits: • You know the user controls the iD • User knows what’s going on/ user choice • Privacy/ data control trends • Position/ strengthen your system as a service How? • Just a “fancy” URL • Prior iD not needed • Hard things: promotion, finding touch points
- 36. GET PERMISSION: TOUCHPOINTS Look for natural fits: • Your sign in – why not link your iD? • Your account settings/user profile • Submission (of any type) • Form fills: pre-fill from your record! • Registration: for conference or meeting • Reporting: Link your iD to get started link to “fancy” URL
- 37. STEP 1: FANCY URL https://sandbox.orcid.org/oauth/authorize? client_id=APP-E422WM33OPZWKKMQ& response_type=code& scope=/read-limited%20/activities/update& redirect_uri=https://my.URL.org& family_names=Researcher&given_names=Bob&[email protected] &orcid=0000-0002-0491-7882& state=UNI-ID Base URL, displays ORCID sign in screen Who’s asking? What permissions? Where the user goes next Personalize the experience The OAuth call: part I Extra info to identify user to your system
- 38. WHAT THE USER SEES Already signed in Sign in form (already registered) Registration form
- 39. STEP 2: AUTH CODE & USER FEEDBACK ORCID sends the user to your redirect, with a code (and any state parameter) appended to end https://my.URL.org?htA3yE&state=UNI-ID • Save the code – you need it for the next step • Display something useful to the user auth code deny message authorize message
- 40. STEP 3A: TRANSFORM THE CODE INTO A TOKEN Use the code to gain access using the ORCID API https://sandbox.api.orcid.org/oauth/token HEADER: accept:application/json DATA: client_id=APP-XT8FBKJRO3MR8WDR client_secret=e285575c-4794-464b-a807-6f1c06b63 grant_type=authorization_code code=htA3yE redirect_uri=https%3A%2F%2Fblue-sea-697d.quartiers047.workers.dev%3A443%2Fhttps%2Fmy.URL.org our API calls always look like URLs (RESTful) what format? the auth code confirming that you are the right one to get this information
- 41. STEP 3B: STORE THE RESULT The result of the call "access_token":"6710dfee-6aab-445b-a266-205dd9085273", "token_type" : "bearer", "expires_in" : 631138518, "scope" : "/read-limited /activities/update", "orcid" : "0000-0002-0491-7882", "name" : "Bob Researcher" store the access token and iD when permission expires (in seconds) your permission (executed contract) iD & name for the person who gave permission what you can do ✔ iD Collected!
- 42. DISPLAY DISPLAY iDs on your website, platform, systems • iDs shown as a link • iDs in metadata • Use the ORCID Member logo • Explain why iDs are collected Signal to your researchers and the wider community that your systems are plumbed to support ORCID iDs https://orcid.org/trademark-and-id-display-guidelines
- 43. DISPLAY: IDS IN ARTICLES iDs in print (pdf) Royal Society, Biology Letters iDs in html Nature, Genetics
- 44. DISPLAY: IDS IN PROFILES ResearcherID HKUST
- 45. DISPLAY: IDS IN METADATA ORCID iD in DOI metadata: <person_name> <given_name>Karl</given_name> <surname>Ward</surname> <ORCID authenticated=“true”> http://orcid.org/0000-0002-4121-9960 </ORCID> </person_name> • iD available in search
- 46. CONNECT CONNECT your data to ORCID records • Request permission to write to records • Store long-lived tokens • Add data that you uniquely can assert • Explain the connection Enable researchers to provide validated data to other systems they use https://orcid.org/blog/2015/10/26/auto-update-has-arrived-orcid-records-move-next-level
- 47. CONNECT VIAAPI TO SEND DATA Verb: POST BASE URL: https://sandbox.api.orcid.org/v2.0_rc3/0000-0002-0491-7882/affiliations HEADERS: Content-type:application/json Authorization: Bearer 6710dfee-6aab-445b-a266-205dd9085273 DATA (if adding or updating): the file [email protected] relevant area: /orcid-bio /funding /orcid-works /peer-review data format access token from before type of action (also: GET; PUT; DELETE) 1. Your client sends data 2. Researcher’s record updated researcher’s iD your client’s name
- 48. Saved time, better reporting, improved information flow https://members.orcid.org/api/tutorial-webhooks https://orcid.org/blog/2015/10/26/auto-update-has-arrived-orcid-records-move-next-level SYNCHRONIZE with your systems • Update information when it changes • Auto-add new information • Search & link wizards • Sync data from others SYNCHRONIZE
- 49. ENABLING SYNCHRONIZATION ORCID API features & tips: • Update notifications (webhooks) • Your system registers iDs you’re watching • ORCID notifies when changes happen • Internal triggers • Employment status change • Publication acceptance • Publication correction • Funding award
- 51. API DEMO: CREATE ON DEMAND http://orcid-createondemand.herokuapp.com
- 52. SPREADING THE ORCID WORD members.orcid.org
- 54. IDEAS FOR SPREADING THE WORD • Identify/work with champions • Pilot with small groups first • Top down AND bottom up approach • Regular updates and reminders • Keep messaging relevant • Use straightforward language • Create collateral (or use ours) Ask ORCID / consortia for help! NOTE: this image is much larger, so used crop tool to move it around and position in the frame here. May need to do some adjusting to this high res image in terms of contrast etc. if it looks too ”dark”
- 57. RESOURCE: LOGOS, GRAPHICS, DISPLAY GUIDELINES
- 59. COMMS EXAMPLE – KAUST
- 60. COMMS EXAMPLE – FLINDERS
- 61. COMMS EXAMPLE – UON
- 63. RESOURCES Bootcamp: ORCID API (Searches, OAuth, Create on Demand) http://is.gd/VALA2016ORCID Collect & connect @ Member Support Centre https://members.orcid.org Workflows & integration points https://members.orcid.org/create-records ORCID-enabled systems https://members.orcid.org/orcid-enabled-systems API technical documentation https://members.orcid.org/api ORCID API users listserv https://groups.google.com/group/orcid-api-users ORCID API source (github) https://github.com/ORCID/ORCID-Source Questions? [email protected] http://support.orcid.org