This document summarizes a hackday event focused on building a system called COrDa to combine information from different institutional systems to surface which researchers have an ORCID iD and where that information can be found. The problem is that ORCID iD information is spread across privacy-restricted registry data and various institutional systems like CRIS, repositories, and HR systems. COrDa aims to develop a common abstraction layer and data model to pull this information together into a centralized dashboard. The hackday resulted in an initial technical prototype connecting to sample systems and displaying ORCID iD and repository information. Ongoing work includes further developing the data model and technical components.

1. Hackdays & Workshops - 2019
Overview
Dr Adam Vials Moore

2. Overview
2
More focused this year – defined problem “Where are my ORCID iD?”
•People want to know who does and doesn’t have an ORCID iD in their institution and where that
information resides
•This is actually a fairly complex question as the answer is spread over a number of systems and
wrapped in questions/issues such as privacy and coordination
•We aim to build a system to combine all these information sources and surface the data in a
simple and accessible way

3. Problem Space:
3
ORCID iD are becoming prevalent but it is difficult to know which of an institution’s
researchers have one
• Access to the ORCID Registry is bound in privacy/permissions and confounding information (e.g.
researchers using personal rather than institutional email addresses)
• ORCID iD are often available in other institutional systems - CRIS , repository, HR systems
• They can also be found in open sources - CrossRef / CORE

4. How have we approached the problem?
Documents, Events and people!
• Synthesized requirements and specifications from previous work
• Discussed on calls with technical developers
• Held Hackday / Code sprints to test technical platforms / develop frameworks
• Reviewed, sought wider community feedback
• Held second event – community workshop
• Ongoing work – please participate!

5. Solution:
5
COrDa aims to pull all these sources together for an institution and surface the
data of who has an ORCID iD and where it can be found
•In order that the solution works across any institutional systems a key
component is the abstraction layer, which allows the dashboard to simply
access a model component of infrastructure, which is then connected to a
specific implementation of a access method
•a CRIS abstraction might connect to a Haplo API connector
•a repository abstraction might connect to an eprints export method.

6. Jisc Hub / DashBoard
Orcid
Registry
Jisc Common Abstraction Layer
CRIS
Repository
Repository
CRIS HR /
Inst.
Member
Reports
Open
Sources
(Crossref/
Core.ac.uk)
Persistance

7. Solution (2)
7
•We have identified a need to design a data model for these shared connections that is
currently under development with input from ORCID and infrastructure systems architects.
•In the first instance the solution is a discovery solution
•In the longer term the goal would be to ensure consistency and write back discovered
information

8. Outputs and continuing work
At a high level…
• Technical prototype
• Connections to Haplo and eprints
• Shows ORCID iD with repository / registry / person lacking
• Institutional Information display
• Owen’s …
• Helper functions
• E.g Samvera Gem
• Discussions on Data Modelling
• Code available
• Github: https://github.com/adammoore/corda/wiki/Overall-Requirements
• Contribute to user stories:
• http://bit.ly/cordastory

10. Over to Owen & Karen
•Owen
•Outputs (including his own!)
•Karen
•First reports from the battlefield…