An update on ORCID
•Download as PPTX, PDF•
0 likes•455 views
This document summarizes a presentation given by ORCID staff at a JISC Consortium Member Event. It discusses ORCID's activities over the last 12 months, including a focus on adding trusted affiliation assertions from research organizations and launching new outreach resources. It provides statistics on ORCID membership and notes upcoming developments like the launch of API version 3.0 with new affiliation types, and vendor integration updates. Challenges of integrating HR systems and collecting information in a centralized manner are also discussed. The presentation concludes by taking questions from attendees.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to An update on ORCID
Similar to An update on ORCID (20)
More from Jisc
More from Jisc (20)
Recently uploaded
Recently uploaded (20)
An update on ORCID
- 1. ORCID: JISC Consortium Member Event 2018 June 28 2018 @ORCID_Org Paula Demain Senior Community Manager EMEA p.demain@orcid.org orcid.org/0000-0001-9389-7387
- 2. ORCID EMEA team Paula Demain, Senior Community Manager Gabriela Meijas, Community Manager Nabil Ksibi, Membership Specialist (Middle East & Africa) Ivo Wijnbergen, Membership Manager (Europe)
- 3. Looking back over the last 12 months... • Focus on Research Organisations adding trusted affiliation assertions • New Outreach Resources and help pages launched • Communication toolkit • Resources toolkit • API 2.1 was launched in Oct • Moving members to 2.0 or higher • Don’t forget that 1.2 and earlier versions will be sunset on 1st August 3
- 4. Looking back over the last 12 months... • Collect & Connect program reviewed and relaunched • Member Self Service and API 3.0 development work • GDPR changes completed • Held our first Consortium workshop • Ivo Wijnbergen joined ORCID to support the region 4
- 5. THE ORCID COMMUNITY https://orcid.org/statistics • 888 members from 43 countries • 550+ system connectors: all research sectors • Over 4.96 million researchers • 121 members in the UK (91 consortium) • 486 members in EMEA (365 consortia members) • 17 consortia in: ○ Americas: Brazil, Canada & US (2) ○ EMEA: UK, Norway, Finland, Sweden, South Africa, Netherlands, Belgium, Germany, Italy, Portugal ○ APAC: Australia, New Zealand, Taiwan
- 6. What’s next? • API 3.0 is coming…. • New affiliation types • Education • Employment and qualifications • Invited Positions and Distinctions • Membership and Services • New Research Resources section • Infrastructure • Collection • Equipment • Service 6
- 7. What’s next ... • Vendor Updates • PURE - In October 2018 PURE will harvest data from ORCID records • Elements - Ability to assert affiliations being assessed • Worktribe - Launch integration to assert affiliations and harvest data from ORCID records • Converis - Ability to assert affiliations being assessed 7
- 8. What’s next… • Collect & Connect changes • working closely with the JISC support team to map and award your integration badges • User Interface updates • Make it easier for researchers to: • Update records and to control data quality • Group work items within their record • Grant permission to member organisations 8
- 9. What’s next... • ORBIT - ORCID Reducing Burden and Improving Transparency • Working with key funders to identify essential information required for funding applications and post-award reporting • Repositories Task Force • Input into recommendations for supporting ORCID in repository platforms 9
- 10. QUESTIONS 10
- 11. HR Systems: Integration Challenges June 28 2018 Paula Demain orcid.org/0000-0001- 9389-7387 Adam Vials Moore orcid.org/0000-0002-2085-1908
- 12. AGENDA • What would you like to get out of the session? • Community comments on the listserv • What are the challenges of integrating with a HR System • Collecting information in a centralised system 12
- 14. Challenges Let’s document the challenges to see if we can work through them together… 14
- 16. Researcher university Gives permission to COLLECT iD and access the record Registers & manages ORCID record Employment: XXX University Source: XXX University (ID139) ORCID record CONNECTS affiliation 16 funder CONNECTS grant Funding: YYY Foundation, Grant #123 Source: YYY Foundation (ID45) CONNECTS publication Works: Journal ZZZ, vol. 45, 2016 Source: ZZZ Publishing (ID675) publisher orcid.org/xxxx-xxxx-xxxx-xxxx ORCID ID Researcher Name Basic information • Other names • Email addresses • Biography Account settings Activities & affiliations Controls visibility
Editor's Notes
- Thank all for attending Introduce the newly formed EMEA team
- Research orgs Focus of last year Uniquely assert affiliation – Trusted assertion for the wider community. You decide how your name is displayed which is the fed into Publishers and Funding systems through their own integrations with ORCID. Updated all documentation Outreach resources Launched in October 2017 3 A’s Anticipation, Action, and awareness – Ideas for each stage of your integration Resources toolkit – Includes material that can be customised and downloaded to help with your outreach – emails, banners, fliers, bookmarks etc API 2.1 launched in October as well which included ORCIDS in the form - Not mandatory upgrade Prime focus – working with both vendors and members on the integration upgrades to 2.0 or higher.
- C&C Re-launch – reviewed the program to make it easier for members to understand the elements of each badges API Checklist Documentation throughout the website Changes in our CRM Self certify 3-0 development – will cover some of the features in the next few slides GDPR Changes – As you all did we took time to review our systems and processes to ensure they were GDPR compliant. We made a number of changes within the UI and the OAuth screens
- The ORCID community consists of 888 members from 43 countries, and over 550 connectors build in all research sectors. We’re 28,000 ID’s short of reaching 5m researchers. Given our regular growth rate of roughly 4000 iDs a day, we should reach 5m iDs on July 2nd. – an extremely impressive number when you consider that researchers register for their ORCID iDs themselves. About 2/3rds of these researchers obtain an iD in the middle of a research workflow that they care about, like submitting a manuscript for publication or applying for a grant. And note that half of the new sign-ups happen through member integration, not through the ORCID website. 2 million of the iDs have records with connected information. As more ORCID member organizations build connectors, the whole community will benefit from increasing numbers of records with connections. Finally, many of the 888 member organizations of ORCID participate in national or regional consortia such as JISC. These consortia benefit from shared approaches, synergies in messaging, and increased national or regional information sharing. Members also benefit from reduced costs for ORCID membership. __ In some locations consortia facilitate activities like national research outcomes reporting. In others, consortia are facilitating the use of ORCID iDs as national research identifiers for people.
- We need your help!
- ORBIT project - establish what information is essential for funding applications and post-award reporting, and demonstrate how funders can engage with researchers to use ORCID record information to populate funder forms ORCID Reducing Burden and Improving Transparency
- Really want the session to be more of a discussion than a structured presentation
- These are the summary points from a discussion on the list serv from Dr Alison L Weightman Head of Research & Academic Engagement Director, Specialist Unit for Review Evidence (SURE) Cardiff
- good example of an institutional integration by Czech Technical University where ORCID iDs are used downstream across systems. Prompt questions: Possible at your organisation?
- This diagram illustrates how it works. And, please bear with me as I tell you a small story. As you can see, we have put the researcher at the center of this circle. This is because the researcher controls when and if information is connected to or shared from his or her ORCID record. Let’s suppose that a new faculty member has been hired by your research institution. Like many other organizations, you ask to COLLECT her ORCID iD by having her sign into the ORCID site for ORCID to reliably provide her identifier to you. In addition to providing an error-free iD, this process also provides permission to your institution to read and write to her ORCID record. With the permission to write to her ORCID record, your institution can CONNECT affiliation information to her ORCID record. This means the addition of authoritative metadata describing the faculty member’s association to your institution is provided **by your institution**, complete with a unique identifier for your institution, the ability to precisely control how your institution’s name is expressed, and a clear articulation when faculty member’s connection to your institution began. Note that this permission to write to the record extends to the ability to update or correct the data that you have added when needed. Once this authoritative affiliation assertion is CONNECTED to the ORCID record by you, the faculty member may grant permission to others to read it. For example, let’s imagine that she is now at the start of a research project. She has decided to apply for funding, and starts the application process on the funders website or system. During this process the funder asks to COLLECT her ORCID iD so that it can be included in the application. As part of this exchange, the funder ALSO receives permissions to read and write to her ORCID record. In reading her ORCID record, information stored in her is used to facilitate or even automate the population of the grant application. Included in this information is the affiliation that your institution had CONNECTED previously. This delights the funder because of the additional confidence that they get from this authoritative piece of data – an affiliation related to the iD, provided by the institution themselves! In this story, our researcher is successful in her proposal. The grant is awarded, and metadata about the grant is CONNECTED to her ORCID record by the funder, complete with the funder’s unique identifier, a universal grant ID and high-level information about the grant. AND... Since your institution has already COLLECTED permissions to read her record, your systems are automatically notified about this great news in near real time. Your systems can be updated to record this successful award! Now, research has been going on, and it is time for her to publish some results. She signs into the publisher’s manuscript submission system where the publisher asks to COLLECT her ORCID iD, again by signing into the ORCID site, and for ORCID to provide the information. Along with the iD, the publisher also COLLECTS permissions to read and write to her ORCID record. In reading the record, the publisher is also delighted to find your authoritative affiliation assertion, and offers to use it for the affiliation on this publication. In addition, the grant ID included in the award assertion CONNECTED by the funder is also available. If applicable, the publisher uses this information to include it in the metadata for the manuscript, should it be accepted. Again successful, our researcher’s paper is accepted for publication. The ORCID iD and grant ID are included in the paper’s metadata, and the publisher CONNECTS metadata about this publication to her ORCID record. AGAIN- since your institution has already COLLECTED permissions to read her record, your systems are automatically notified about this publication, and the information can be stored in your systems. In addition, since the funder also has already COLLECTED permission to read her record, their systems are also notified about the publication. By including the publication in their records the our researcher no longer has to type in this output from the grant reducing her burden. The institution, funder and publisher have all received accurate and up-to-date information, and the researcher only needed to sign into the ORCID site as part of existing workflows to provide permission for this exchange to happen. As publishers are collecting affiliation data, data included in WOS, Scopus etc, which feed into the University ranking data.