Our ORCID journey - University of Liverpool
•Download as PPTX, PDF•
1 like•421 views
A presentation by University of Liverpool from our Cultivating ORCID: growing together event.
Recommended
Recommended
More Related Content
What's hot
What's hot (17)
Similar to Our ORCID journey - University of Liverpool
Similar to Our ORCID journey - University of Liverpool (20)
More from Jisc
More from Jisc (20)
Recently uploaded
Recently uploaded (20)
Our ORCID journey - University of Liverpool
- 2. OVERVIEW • Starting Point • Plan • What Actually happened • Benefits we saw from UK Consortium Membership • Lesson Learned
- 3. INTERNAL INFRASTRUCTURE • Elements CRIS • Eprints OA Repository • Successful Project to Launch Elements completed as UK Consortium Launched
- 4. PLAN • Join Consortium • Enable Orcids on CRIS (Symplectic Elements) • Pass through to OA repository (eprints) • Reap Benefits • Cake!
- 5. ACTUAL PROCESS • Sign up to Consortium • Enable Elements Orcid feature without really understanding what it did • Find out CoreHR HESA module was storing Orcids • STOP CoreHR storing Orcids • Advocacy and launch – mixed reception • Medical & Science faculty – we all already have one • Arts & Humanities – what’s this for? • Find out how Elements worked (populating search, no direct interaction with Orcid records) • Early version of Elements didn’t pass Orcid through in person data (v4) Continued . . .
- 6. ACTUAL PROCESS (2) • Manually curate CoreHR Orcid records that had been created (not many) • Create custom UoL workflow to populate CoreHR HESA module with Orcid from Elements • Schedule Upgrade for Elements due to Orcid API 1.2 sunsetting deadline • Test Elements upgrade by enabling Orcid sandbox in DEV/ TEST • Continued advocacy & training – PGR / Outreach • Develop Eprints v5 crosswalks to move Orcid from Elements and display using Orcid level 1 plugin • Order Cake . . .
- 7. BENEFITS (UK CONSORTIUM) • Support provided best understanding of Elements behaviour before Symplectic . . . • Mailing lists /fora were great place for technical questions and advocacy awareness • Meetings provided training on API development and BoF for understanding how best to interact with systems • Access to advocacy and materials developed specifically for the UK
- 8. LESSONS • Be aware of all the places in your institution person data is stored and ensure they are aware of how / when Orcid are being registered and utilised • Investigate the capabilities of your platforms and manage expectations around that • Use the advocacy and training material templates where you can • Be sensitive to the different levels of awareness within your discipline areas
Editor's Notes
- Have 3 institutions talk about what they have done since joining the consortium. Internal infrastructure Benefits What have they learned? Tech/policy/advocacy etc Questions to give to institutions What have you done since joining the consortium? How have you used the support service? What have you found useful? What has changed in the institution? What are you planning to do next? What lessons could you pass on to others? 3 institutions: 10min each. 10min presentation.