Jisc UK ORCID Hackday April 2018: summary
This blog post is derived from notes and analysis by Owen Stephens, consultant. Thanks are due to Owen for his contributions to the hackday planning, running and reporting.
The Jisc UK ORCID hackday took place in Jisc’s London offices on 24th April 2018. It was a gathering of developers and practitioners who came together to:
- Undertake playful and experimental exploration of APIs and data sources linked to the use of ORCID IDs
- Think about how the ORCID API can be used to deliver value to institutions and researchers
- Build on the following areas and use cases that had been discussed in the run up to the event (follow the links for notes)
The day was a mix of presentations, small-group work and discussions. The themes that emerged from the different activities can be summarised as:
Need to share and use IDs (of different types, but including ORCID IDs) across different systems and services
Some of the challenges explored within this theme included how repositories and aggregators can use ORCID IDs. Some participants worked on a proposal for an oai_dc_plus schema to expose ORCID IDs in metadata for harvesting; others extracted ORCID IDs from full-text articles and RIOXX, or discussed APIs for related identifiers (not just ORCID IDs).
Desire to improve the information available to institutions about the use of ORCID by their researchers and to make better use of that information
Work undertaken within this them encompassed a visual and interactive interface built on the monthly reports provided by ORCID to membership organisations to help institutions easily see trends; going beyond member reports – asking questions like “could ORCID provide information on the number of views of ORCID profiles in a time period” – to help advocacy; and exploring the idea that data from multiple services (e.g. ORCID, Core, Sherpa, …) could be used to help nudge items through an Open Access workflow by prompting the appropriate people to do things at an appropriate time via email
Improving services and workflows through the use of data available via ORCID
Exploring the idea of event data – where an event represents the assertion of some type of link between two things – e.g. “this tweet mentioned this DOI”. Could Universities serve as a source for Event data? For example, the assertion that a researcher with a specific ORCID ID had authored a paper with a specific DOI could be treated as an Event, and might be the first link between that ORCID ID and that DOI.
The discussion on delegated permissions also continued: how can an institution manage (or help researchers to manage) permissions to access/update their ORCID profiles that have been given to third party systems as part of the researchers institutional membership?
The full report on the activities of the hackday is available to download as a pdf or read in GoogleDocs. Owen’s slides which summarise the hackday outcomes can be viewed through the resources page from the June UK ORCID members event.