ORCID API and use-case workshop
•Als PPTX, PDF herunterladen•
0 gefällt mir•507 views
An introduction to ORCID
Empfohlen
Weitere ähnliche Inhalte
Ähnlich wie ORCID API and use-case workshop
Ähnlich wie ORCID API and use-case workshop (20)
Mehr von Jisc
Mehr von Jisc (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
ORCID API and use-case workshop
- 1. ORCID API and Use- Case workshop Introduction to ORCID
- 2. Structure of this event • Plenaries: • Introduction (now) • ORCID Eprints Implementation Survey Analysis • Two strands: • Introduction to the ORCID API • Development of user stories and use cases
- 3. What’s next? ORCID API hack day • 10:30-16:30 on 18 October 2016 in London • Developers and non-developers encouraged to attend • See https://www.jisc.ac.uk/events for more details and to sign up
- 4. What is ORCID? • A unique and persistent identifier for researchers • A service which collects information about researchers and makes it available (only with the permission of the researcher) through a website and machine-to- machine interfaces (APIs) • A not-for-profit organisation that maintains ORCID identifiers and services
- 5. How do you get an ORCID? https://orcid.org/register
- 6. How do you get an ORCID?
- 10. Record ORCIDs
- 12. Import publications from an ORCID profile
- 13. Login via ORCID
- 15. Notifications Slide taken from UKSG Webinar by Josh Brown (ORCID) http://www.uksg.org/webinars/identifiers
Hinweis der Redaktion
- The structure for today is that we’ll have two plenary sessions - this one, and then a presentation from Lizz Jennings and Helen Cooper on a recent survey that collected information from the eprints community about what they wanted to see in terms of integrating ORCID with the eprints repository software
- The use cases developed today will feed into this hack day to give the attendees some focus for what they develop. We’d like to see a mixture of developers and non-developers at the event, with the non-developers acting as the user or customer answering questions the developers might have about different use cases and how they want the software to work.
- This is how I think about it - so when we talk about ORCIDs or “integrating ORCID” we need to think about which aspects of this we are trying to work with. I think it is fair to say that the role of ORCID as a unique and persistent identifier for researchers is at the heart of ORCID, and why it was created in the first place. Putting the researcher at the centre of the process and giving them control over the information is also a key principle of ORCID. However many of the benefits to researchers and institutions is through bringing together information about the researcher, not about the identifier per se
- You can register for an ORCID on the ORCID website
- Or you can login with some existing social media or institutional account and create an ORCID account and link it to those details and institutional systems can offer the ability to register for an ORCID - for example the Pure CRIS has an option to allow researchers to create an ORCID and link it to their profile in Pure (or link an existing ORCID if they already have one)
- Example ORCID record. Point out various sections and user privacy controls that are available. Stress principal that the researcher is the owner of the record
- Doesn’t require any integration - just a place to record the ORCID in the application - as can be seen in this example in Monitor Local (an upcoming service from Jisc for tracking and managing APC payments, currently in Beta) Monitor Local eprints examples DSpace e.g. …
- However ORCID tend to encourage the use of their API to look up ORCIDs to avoid mistypes/mis-assignment of ORCIDs This example is from DSPace - lookup from ORCID is seamlessly integrated with look up from existing authors in DSpace Screenshot taken from https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration
- Requires use of the API Note how it requires quite granular permissions to do stuff - this is integral to ORCID putting control in the hands of the researcher Screenshot taken from http://program.or2015.net/grenz-24x7_orcid_integration-72.pdf
- Requires use of the public API Example here from an eprints plugin Screenshot taken from http://wiki.eprints.org/w/ImportFromORCID
- Example from a report by the THOR project http://project-thor.eu THOR is developing ways to support the inclusion of ORCID iDs in databases and services and has recently published a report summarising a number of different integrations with data services https://zenodo.org/record/58971/files/de-Mello_THOR_ORCID-Integration.pdf (screenshot is taken from this report)
- I’m using the KAUST example again here just for a screenshot, but the ability to to update an ORCID record (with permission of the owner of the profile) is something that has been done in eprints at the Open University and is available in DSpace-CRIS, and other systems Screenshot taken from http://program.or2015.net/grenz-24x7_orcid_integration-72.pdf
- The left hand side of this diagram is already live, but I’ve not identified examples of the lefthand side happening yet - so if you know of some, please let me know