by Dr Adam Vials Moore

1. Community ORCID Dashboard - COrDa
Overview
Dr Adam Vials Moore

2. Overview
2
•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. Jisc Hub / DashBoard
Orcid
Registry
Jisc Common Abstraction Layer
CRIS
Repository
Repository
CRIS HR /
Inst.
Member
Reports
Open
Sources
(Crossref/
Core.ac.uk)
Persistance
hackday-admin Zzr1161

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 an access method
•a CRIS abstraction might connect to a Haplo API connector
•a repository abstraction might connect to an eprints export
method.

6. Solution (2)
6
•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