GEN2PHEN GAM8 meeting Leiden - Update on ORCID and other ID developments

G. A. Thorisson, ULEIC

Update on ORCID and
other ID developments
Gudmundur A. Thorisson <gt50@leicester.ac.uk> ULEIC

-- Overview --
✴ ORCID status update and outlook for 2012
✴ Report from IRISC identity workshop in Helsinki
✴ ID-related projects
✴ Contribution tracking tools for Drupal-based websites
✴ Some notes on identifying vs. locating digital resources

This work is published under the Creative Commons Attribution license
(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.

GEN2PHEN 8th General Assembly Meeting, Leiden, Jan 24-25 2012 1
Friday, 27 January 12


ORCID - unique identifers for
scholarly authors
?

ORCID ID: 935-352-535-11 ORCID
G. Thorisson, Univ. Leicester
G. A. Thorisson, Univ. Leicester
G. A. Thorisson, Cold Spring Harbor Lab. F67572010
ORCID ID: 935-352-987-11
J. Smith, Univ. North Pole
ORCID ID: 883-352-334-01
J. Smith, Luthor Corporation

Centrally-managed, sustainable informatics infrastructure:
i) for researchers to manage & use profile
ii) for tracking author-to-publication attribution links
iii) interaction with other systems (e.g. publishers, digital libraries, univ.)
GEN2PHEN 8th General Assembly Meeting, Leiden, Jan 24-25 2012
Friday, 27 January 12 2


The organization
ORCID transcends discipline, geographic, national and
institutional boundaries

Taken from http://www.orcid.org/participants


tio ns
a ni sa
Org
>1 50



tio ns
a ni sa
Org
10
>3 50
150
>



Update on ORCID Phase 1 development
• Beta development well underway
• API speciﬁcation documents:
http://orcid.org/twg
• Mock API Code for download:
https://github.com/orcid
• Early adopters now have
something hands-on to work
with
• Key API features
– Retrieve proﬁle data in multiple formats
– OAuth authenticated read/write access



Outlook for ORCID in 2012
• Enough $$$ to start operations now secured, so organization is
hiring Executive Director, Technical Director & other staff
• Complete Phase 1 development and launch public beta service
– Focus on active researchers: register to populate own profile, select institutions
depositing profiles for their staff, API for interacting with external profile systems

• Flesh out Phase 2 development roadmap
– More extensive functionality: disambiguation, deposit profiles by non-institutional
3rd parties, record contributor roles, users to claim non-article published works

• Key challenges
– Phase 2 discussions in TWG at near-standstill recently - NEED full-time staff!
– ORCID Board politics
– Community outreach, to users and especially developers
– Support in journal MS tracking systems <-- main point of contact for academics



The 1st IRISC workshop @CSC, Helsinki
• Workshop themes
– unambiguously identifying authors/creators & attributing their scholarly works
– individual identiﬁcation and access management in the context of identity
federations

• Workshop aims
– Raising overall awareness of key technical and non-technical challenges,
opportunities and developments.
– Facilitating a dialogue, cross-pollination of ideas, collaboration and coordination
between diverse – and largely unconnected – communities.
– Identifying & discussing existing/emerging technologies, best practices and
requirements for researcher identiﬁcation.

• >60 participants, 2/3 from IDF community
• Mixture of plenary sessions & facilitated, interactive discussions
in 2x parallel breakout sessions



IRISC workshop summary, key points
• End user adoption of the ORCID identifier service and its future
expanded role
– Encourage developers to use ORCID API sandbox to build proof-of-concept apps
– Promoting benefits of scholary IDs and identifier infrastructure in the scientific
community

• Identity federations and interfederation services and their role
in research e-infrastructure
– Many issues relating to usability, outreach, privacy risks with releasing user data,
attribute harmonization, etc

• Opportunities for collaboration and interoperability
– ORCID-to-IDF connectivity - solution for ‘homeless’ & ‘nomadic’ researchers?
– Interest piloting IDF-based access management for biomedical data
– Best way to express a user’s ORCID author identifier as an IDF attribute



IRISC dissemination
• Report published online on website & deposited in Nat Precedings:
http://dx.doi.org/10.1038/npre.2011.6609.1

• Summary document circulated
via E-mail
• Extended abstracted submitted to
TNC2012 networking conference
• Planning to submit short
correspondence to a journal



Other identity-related developments
• Piloting GWAS ‘nanopublications’ (joint with OpenPHACTS)
– GWAS Central as ‘nanopublisher’
– Core variant<->disease assertions from GWAS papers published as Linked Data
– Provenance section of nanopub RDF to include attribution via ORCID URIs

• Publication credit for Cafe Variome deposits
– O. Lancaster (orcid:934-342-433-91). 4x variants in BRCA2 gene. Published online
via Cafe Variome. 21 January (2011) doi:10.1255/caferouge.BRCA2-2352354
=> http://api.caferouge.org/atomserver/v1/caferouge/mutations/2352354
– Assertion in ORCID: orcid:934-342-433-91 <created> doi:10.1255/caferouge.BRCA2-2352354

• Contributor tracking for Drupal sites (joint with BioSHaRE-IT)
– Extensions for tracking contributions to project outputs & ORCID integration



Contribution tracking for Drupal websites
• Currently, in a typical Drupal CMS installation
– Registered users have account on site (a local user ID)
– System tracks which users post which bits of content
– Reporting tools provided to see who posted what

• But poster is frequently NOT the person(s) who actually created
the work



Aim #1: Enhance provenance of site content
• Make it possible to
– link multiple local user IDs on Drupal site with content of certain types (nodes)
– browse, search & discover content based on “contributorship” information
– e.g. list all deliverables associated with Adam Webb
– e.g. which persons have contributed to deliverable XX
– Example of enriched attribution metadata:
– D9.3 Draft Report on Incentives [...]
A. Reiche [posted]



A. Reiche [posted]
G.A. Thorisson [authored]
A. Cambon-Thomsen [authored]
O. Lancaster [authored]
D. Atlan [authored]



A. Reiche [posted]
G.A. Thorisson [authored]
A. Cambon-Thomsen [authored]
O. Lancaster [authored]
D. Atlan [authored]
A. Devereau [reviewed]
T. Beck [reviewed]
J. Celli [reviewed]



Aim #2: enable linking to ORCID ID service
• Extend Drupal to add ORCID integration in order to:
– enable users to link their local user ID with an ORCID and
– submit author <-> publication assertions to central ORCID index

• How will this work?
– Button for signing in with ORCID (think “Sign in with Twitter”)
– User authorizes KC site to interact with ORCID on his behalf

• How will this be implemented?
– Build as a standalone Drupal module that any site can take and use
– Main targets: GEN2PHEN KC, BioSHaRE Mica platform, UoIceland inst. site



Key benefits / motivation
• General: enhanced visibility for contributors on community site
– Deliverable reports, dissemination activities, working papers, software etc.
– Who has contributed to what content

• ORCID-enablement
– NOT totally essential, BUT would support a range of important use cases, e.g.:
• Starting from ORCID site, discover a person’s GEN2PHEN/BioSHARE contributions and
learn more about the nature of those contributions
• Starting from GEN2PHEn/BioSHARE site, find the author’s primary scholarly profile on
IRCID and discover more of his/her works

• Use as a platform for experimenting with ID-based functionality
– Technical “nuts&bolts” of integration via the ORCID API
– Workflows for: authors assigning authorship via IDs, claiming authorship, etc.
– Capturing&displaying nature of contribution: author/analyst/curator/reviewer


Identifiers vs. locators
• Identification == crucial requirement for attributing credit
– Who contributed?
– What was contributed to?

• ORCID needs some sort of handle or pointer to the “stuff”
• URL location <-- workable for general content if no other option
– Internet location + some basic metadata to indicate what kind of content
• Example: http://www.le.ac.uk/~gt50/very_important_report.pdf
– Content moves => link is broken => users cannot access => BAD!

• Persistent identifier <-- vital for ‘proper’ scholarly record, long term
– DOI or other persistent identifer + copy of bibliographic info
– Identifier resolves to metadata record, link to location of content
• Example: http://dx.doi.org/10.1038/nbt1109-984b => ‘landing page’ on journal website
– Content moves => DOI metadata is updated => identifier points to new location


IDs in GEN2PHEN, 12-18 month outlook
• Continue to support (and inﬂuence) ORCID development
– TWG discussions, feedback on specs, piloting, promote at meetings etc.

• Contributor tracking and related work
– tooling potentially widely useful to many websites based on same CMS
– develop/promote, good progress achievable before end of GEN2PHEN

• WP9 - sustainability, incentivization for sharing
– Contributor IDs and resource IDs key components in BRIF

• ID-based data access management - need to continue to
investigate & liase with IDF community
• Repeat IRISC workshop
– Autumn this year, or maybe Q2 2013

• Beyond GEN2PHEN, Q3 2013 - ?


Acknowledgements
ORCID Technical Working Group
This work has received funding from the
GEN2PHEN Consortium European Community's Seventh
Framework Programme (FP7/2007-2013)
http://www.gen2phen.org/about-gen2phen/partners
under grant agreement number 200754 -
the GEN2PHEN project.
Prof Anthony J. Brookes Bioinformatics Group, Leicester

Contact me!

<gt50@le.ac.uk> |<gthorisson@gmail.com>
http://www.linkedin.com/in/mummi
http://www.twitter.com/gthorisson
Published under the CC BY license (http://
http://www.gthorisson.name creativecommons.org/licenses/by/3.0/)


GEN2PHEN GAM8 meeting Leiden - Update on ORCID and other ID developments

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (19)

Ähnlich wie GEN2PHEN GAM8 meeting Leiden - Update on ORCID and other ID developments

Ähnlich wie GEN2PHEN GAM8 meeting Leiden - Update on ORCID and other ID developments (20)

Mehr von Gudmundur Thorisson

Mehr von Gudmundur Thorisson (14)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

GEN2PHEN GAM8 meeting Leiden - Update on ORCID and other ID developments