1. orcid.orgIntegration demoODIN: Linking ORCID and DataCiteGudmundur A.Thorisson, PhDORCID EU / ODIN Projectand University of Iceland Computing Servicesg.firstname.lastname@example.org http://gthorisson.name | http://orcid.org/0000-0001-5635-1860This work is published under the Creative Commons Attributionlicense (CC BY: http://creativecommons.org/licenses/by/3.0/)which means that it can be freely copied, redistributed and adapted,as long as proper attribution is given.
2. ODIN and ORCID EU• ORCID and DataCite InteroperabilityNetwork• Aim: connect researchers and datasets viapersistent identifiers• 2 year EC-funded project• 7 partners (5 EU + 2 international)• ORCID EU incorporated in Belgiumhttp://odin-project.euOdinn the WandererCredit: Wikipedia Commons
3. Technical development in ODIN• ODIN ≠ infrastructure creation project! Outputis roadmaps, technical reports, prototypes etc.• Proof-of-principle implementations• British Library: use and citation of social sciencesdata, long-running British Birth Cohort Studies• CERN: attribution in high-energy physics - dealingwith large no. of authors on HEP papers & datasets• ORCID EU “Labs” mini-projects• Work Package 4 - Interoperability
4. .. three main threats or “items of unfinished business” emanatingfrom lack of recognition of the need for robust ways ofidentifying contributors and their data in e-Science• Inability to follow interconnections between datasets andcontributors as a method of data discovery.• Inability to share and connect identifiers of contributors andauthors between different user communities.• Inability to uniquely identify datasets attributed to aparticular contributor and contributors to a particular dataset.Linking contributors and datasets
5. Linking contributors and datasetsEmbedding ORCiDs indata centre workflowsProspective - longterm aim
6. Linking contributors and datasetsEmbedding ORCiDs indata centre workflowsProspective - longterm aimAd hoc claiming of alreadypublished datasetsRetrospective - necessarynow and for quite some time
7. Terminology• “claiming” = asserting that one has authored orotherwise contributed to a published work• “I authored this paper or book”• “I created this dataset”• “I had role X in the generation of this dataset andcontributedY and Z”• Focus here on self-claims - claims bycontributors themselves about their works
8. Doing it• Existing resources available to build on• CrossRef Metadata Search tool http://search.crossref.org• DataCite search API• ORCID Member API• Technical approach• Create simple standalone, loosely coupled tool• Connect CrossRef MDS to DataCite search API• Add several functionality and UI tweaks• Aim: to get work metadata into user’s ORCIDprofile
9. The tool-- LIVE DEMO --http://datacite.labs.orcid-eu.org
10. Challenges / obstacles• Metadata quality and consistency• DataCite vs. CrossRef vs. ORCID• Basic things like date and author is handled in subtlydifferent ways in DOI metadata• Work types in ORCID hardcoded to BibTeX - w00t!• ORCID Works Metadata Working Groupdiscussing these and related issues• how can ORCID best align with and reuse/adaptexisting standards & community ontologies/vocabularies?
11. Not yet another standard please!Credit: http://xkcd.com/927/
12. The open source advantage• Key building blocks• Generic - Sinatra webapp framework, OmniAuthauthentication framework [~dozen more]• Domain-specific - CrossRef Metadata Search,omniauth-orcid Ruby gem• Reuse/Remix/Extend to build new things• ORCID to take advantage of open source• https://github.com/ORCID/ORCID-Source• http://orcid.org/about/community/orcid-technical-community
13. Acknowledgements• Martin (the other half of ORCIDEU Labs, did majority of work!)• Karl & Geoff @CrossRef for open-sourcing• ODIN partners for testing&feedback• Numerous other testers in the community
14. Published under the CC BY license (http://creativecommons.org/licenses/by/3.0/)