230 likes | 343 Vues
The ODIN Project, supported by the British Library, aims to simplify author disambiguation by integrating various identifiers like ORCiD, ISNI, and institutional profiles. This talk highlights the challenges faced with identifying authors in academia, exemplified by the case of a random chemistry professor. It discusses the need for a unified approach to manage identifiers and profiles, explores contrasting use cases between institutions and users, and showcases live demos that illustrate practical implementations of these solutions. We need one identifier for many profiles to effectively navigate the complexities of research outputs.
E N D
Integrating ORCiDA two way conversation Tom Demeranville ODIN Project, British Library
What is ODIN? ODIN-PROJECT.EU
In the wild Random chemistry professor example Look at that pile of identifiers and profiles Note it doesn’t include his ORCiD (he’s got one!) And an ISNI, a ScopusID & an institutional profile Not picking on him, just a regular example
Automated vs Manual Profiles Nobody wants to type the same thing in twice
Institutions vs Users Different use cases & Conflicting notions of control
We all want author disambiguation‽ There’s already 5 John Browns in ORCiD Not to mention citation practice confusion J Brown Brown, J John Brown Jonathon Brown Brown, J N JN Brown Etc. Plus name changes, colour confusion in search & more!
Obligatory XKCD “standards” refsource: http://xkcd.com/927/
What we need… One identifier Many profiles that solve different use cases
EThOS ethos.ac.uk
DANGER – LIVE DEMO AHEAD Claiming an E-Thesis The http://ethos-orcid.appspot.com tool Also… Claiming direct from eprints http://discovery.ucl.ac.uk/1431513/
MORE LIVE DEMO ANGST Who’s claiming what? The datacentre reporting tool. Reverse lookup by DOI prefix. http://ethos-orcid.appspot.com/search
Implementing it yourself. http://github.com/TomDemeranville
UNDER THE HOOD The real easy way… Implement a class, configure & deploy! The more complex, more flexible way… Utilize the library or roll your own.
Working with your repository It can be really simple You don’t always need an APIor RDF It will probably embed something in the webpage <meta content=”Bloggs, J" name="DC.creator" /> <meta content="report" name="eprints.type" /> etc.
Thanks. @tomdemeranville http://odin-project.eu tom.demeranville@bl.uk
Bonus slide if we have time(With a quick aside about trust and a bit about ISNI)