3.24.15 Slides, “New Possibilities: Developments with DSpace and ORCID”

March 24, 2015 Hot Topics: DuraSpace Community Webinar Series
Hot Topics: The DuraSpace
Community Webinar Series
Series Eleven:
“Integrating ORCID
Persistent Identifiers with
DSpace, Fedora and VIVO”
Curated by Josh Brown,
Regional Director Europe, ORCID

Webinar 1:
New Possibilities:
Developments with DSpace & ORCID
Presented by:
João Moreira, Head of Scientific Information, FCT-FCCN
Paulo Graça, RCAAP Team Member
Bram Luyten, Co-Founder, @mire
Andrea Bollini, CRIS Solution Product Manager, CINECA
Michele Mennielli, International Relations Manager,
CINECA

Research Information Management:
DSpace-ORCID requirements
João Mendes Moreira (FCT)
Paulo Graça (FCT)

Agenda
• Context
– PTCRIS (integrated research management
ecosystem)
– RCAAP (national open access initiative)
– PTCRIS & RCAAP & ORCID & DSpace synergies
• DSpace-ORCID
– Requirements
– Compative analysis
• XMLUI
• JSPUI
• DSpace-CRIS
• Conclusions

Mission
Ensure the creation and sustained development of
national integrated information ecosystem (PTCRIS) to
support research management

Goals
1. Define the regulatory framework to adopt by the
various systems
2. Coordinate FCT’s systems integration in accordance
with the standards framework
3. Coordinate external systems integration with FCT
(National and International) according to the
standards framework
4. Support and promote within community the use of
the systems of the PT-CRIS.

The ecosystem
CRIS – Current Research Information Systems
Academic
expertise
Organizations
database
Scientific
equipment
Statistics
Funding
database
Grant
management
Outcomes /
outputs
Research news
Research ethics
Research portal
PTCRIS is ecosystem!

Standards
Aligned:
• H2020
• Digital ERA fórum
• RDA
PTCRIS
Data model
Dictionary / Interop.
Ontologies
Researcher Id
Org Id

Roadmap #1 Interoperability
An output should be registered only once and reused often!
Research
Institutions
Publishers
Repositori
es
Prof.
organizations
Universiti
es
Funders

Electronic Services
Portal RCAAP
Institutional
Repositories
(SARI)
Scientific
Data
(SARDC)
Scientific
Journals
(SARC)
Shared
Repository
Directory
Usage
Statistics
(SCEUR)

Metrics
● 42 Repositories (27 hosted) DSpace JSPUI
● 1 Shared Repository with 38 institutions
● 32 Scientific Journals (9 hosted)
● >200.000 Open Access Items
RCAAP - Repositório Cientifico de Acesso Aberto de Portugal

Breaking information silos
PTCRIS
Academic
expertise
Org.
database
Scientific
equipment
Statistics
Funding
database
Grant mng
Outcomes / outputs
(RCAAP)
RI
(DSpace)
Revistas
(OJS)
Dados
científicos
(CKAN)
Research
news
Research
ethics
Research
portal
Identifiers Interoperability

Breaking information silos
Outcomes / outputs
(RCAAP)
RI
(DSpace)
Journals
(OJS)
Scientific data
(CKAN)
Portal RCAAP
Identifiers Interoperability

PTCRIS Ecosystem
National CV
Open Access
Portal

Agenda
• Context
• DSpace-ORCID
– Requirements
– Comparative analysis
• XMLUI
• JSPUI
• DSpace-CRIS
• Conclusions and recommendations

Requirements sources
• COAR Roadmap Future Directions for Repository
Interoperability (Fev 2015)
• Immediate priorities:
– #3 Supporting Author Identification Systems
– #7 Supporting additional metadata formats
• XMLUI, JSPUI, DSpace-CRIS
• Needs RCAAP (national Open Access initiative)
• Needs PTCRIS (national CRIS initiative)

Requirements (our view)
Author related
R1.1 Author’s profile page
R1.2 ORCID aware every time the author is displayed
R1.3 ORCID authority control
R1.4 Search by ORCID identifier
Interoperability
R2.1 Supporting additional metadata formats
Added value DSpace‐ORCID services
R3.1 Add‐to ORCID
R3.2 Import/sync from ORCID

Supporting Author Identification Systems
• Supporting author identification systems: Author
identification systems intend to identify academic
authors in a unique way. Different systems are
available (ORCID, ResearcherID, AuthorClaim etc.)
and can be used in the repository context.
“IMHO, a very important extension of current repositories, but relying on external
authority data maintained by external systems / staff; needs a lookup service for
persons, which can be applied during indexing and searching of data”… “Clearly
supports open systems like ORCID instead of proprietary ones”

R1.2: ORCID Id aware every time the author is
displayed

R1.4: Search by ORCID identifier

R 2.1: Supporting additional metadata formats
• DC has strong limitations
• Potential formats to be considered (and depending
on the purpose) are MODS, METS, MARC, CERIF
and others.
“Adding more standards when they bring richness and detail is a key step
to move forward in the current situation. The complexity of course
depends on number and complexity of the new adoptions. DC is no
longer useful for advancing in the field.”

R 3.1: add-to ORCID (1/2)
RCAAP plug‐in available.

R 3.2: Import/Sync from ORCID (1/2)

R 3.2: Import/sync from ORCID (2/2)

Requirements analysis
Requirement DSpace flavour
Author related JSPUI XMLUI DSpace‐CRIS
R1.1 Author’s profile page N N Y
R1.2 ORCID aware every time the author is displayed N N N
R1.3 ORCID authority control N Y Y
R1.4 Search by ORCID identifier N N N
Interoperability
R2.1 Supporting additional metadata formats DC DC DC, CERIF
R3.1 Add‐to ORCID N N N
R3.2 Import/sync from ORCID N N N
Score 0/7 1/7 3/7

Two UIs: Global Adoption
891; 46%
1067; 54%
1,958 “unique”, valid DSpace sites
XMLUI
JSPUI
Source: 2015 DuraSpace Sponsor Summit, Tim Donohue

Priorities (from our perspective)
Requirement
Author related Priority
R1.1 Author’s profile page Max
R1.2 ORCID aware every time the author is displayed Min
R1.3 ORCID authority control Max
R1.4 Search by ORCID identifier Min
Interoperability
R2.1 Supporting additional metadata formats Max
R3.1 Add‐to ORCID Med
R3.2 Import/sync from ORCID Max

Agenda
• Context
• DSpace-ORCID
• Conclusions & recommendations

Conclusions
• DSpace ORCID integration level varies according with
DSpace flavor
– DSpace-CRIS appears to be the more complete
and DSpace JSPUI the less complete
– There are still some important requirements to
be fulfilled.
• R3.2 ORCID import is key for repositories and OA
• The number of DSpace flavors spreads resources
and this doesn’t seams to be beneficial (product and
community).

Recommendations
How can DuraSpace/community help us?
Decision towards a unified path for the user
interfaces (Mar 2015)
– Work with COAR on:
• #3 Supporting Author Identification Systems
• #7 Supporting additional metadata formats
– Follow VIVO Strategic Plan (2015 / 2016)
• Goal 2: Promote a more open and networked
research ecosystem (ORCID, euroCRIS, CRediT,
and CASRAI)

Recommendations
How can ORCID help us?
– think of a special membership for repositories
only purposes
How can we help?
Members of COAR, CASRAI, euroCRIS, ORCID
and DSpace (gold)
– Make add-to plug-in available
– Integrate a task force to work on DSpace-ORCID
integration

ORCID in DSpace 5
University of Missouri - @mire
Bram Luyten

OVERVIEW
Current offered feature set
Implementation use cases

IMPLEMENTED FUNCTIONALITY
ORCID and DSpace Authority Control
Integration
Author lookup for new submissions (UI)
Author lookup for edits on items (UI)
Author identiﬁers in Batch CSV editing

INTEGRATION
String representation of
the name in standard
Dublin Core metadata
enhanced with DSpace
compliant authority
control id
“authority cache”
stores extended
contributor metadata,
including ORCID ID and
alternative names

NEW SUBMISSIONS
Adding an author with an identiﬁer should
ideally be as easy as providing a simple
name.

Indicates that author is in
DSpace Authority control

Authors in red are in
DSpace Authority Control
Authors in black are NOT in
DSpace Authority Control

Staff enhances contributor
string names with ORCID
Administrator finalizes by
re-uploading edited file
Administrator exports
existing work metadata
Author identifiers in Batch CSV editing

SPREADSHEET EXAMPLE
Add ORCID identifier to spreadsheet for
batch deposit of metadata into DSpace:
“ORCID:dc.contributor.author”
Non-ORCID authors can still be imported:
“dc.contributor.author”

SPREADSHEET EXAMPLE
ORCID authors are retrieved automatically,
and the author’s name is displayed in DSpace

CAVEAT: AUTHOR ORDER
It is possible to preserve the order of the
authors IF all of them have an ORCID ID,
or NONE of them has an ORCID ID.
Addressing the mixed situation is an
important open issue.

IMPLEMENTATION USE CASES
Empty new DSpace Repository
Existing DSpace without prior usage of the
authority control functionality
Existing DSpace WITH prior usage of authority
control.

RECAP: PRE DSPACE 5 AUTHORITY CONTROL

RECAP: DSPACE 5 ORCID INTEGRATION
String representation of
the name in standard
Dublin Core metadata
enhanced with DSpace
compliant authority
control id
“authority cache”
stores extended
contributor metadata,
including ORCID ID and
alternative names

Questions?
Thank You
www.atmire.com

DSpace/DSpace-CRIS
and ORCID
1
DuraSpace Webinar:
Developments with DSpace and ORCID
March 24, 2015
Andrea Bollini
Michele Mennielli

• DSpace-CRIS/ORCID: current integrations
• DSpace (JSPUI): what’s next?
• DSpace-CRIS: what’s next?
Agenda
www.cineca.it | DSpace/DSpace-CRIS & ORCID | DuraSpace Webinar | March 24, 2015

DSpace-CRIS for euroCRIS
It is possible to (public API):
• Login through ORCID*;
• Claim profile through ORCID;
• Register/Associate an ORCID to your own DSpace-CRIS profile
First release
(part of the 4.3 version)
DSpace-CRIS 5.1.0
Release
* Authentication code is based on the work on DSpace 5 and Dryad project

DSpace-CRIS: importing BIO info

DSpace (JSPUI): what’s next?
Using API ORCID for finding authors with extreme precision during
records’ submission and editing phases (including big amounts)
– https://wiki.duraspace.org/display/DSDOC5x/ORCID+Integration
– http://www.slideshare.net/ORCIDSlides/orcid-ann-campion
Porting of the great job done by @mire for the
XMLUI into the JSPUI

DSpace 5  DSpace-CRIS 5
ResearcherPage represents the extention of the
cache authority introduced in DSpace 5
Data in ORCID are fully available in DSpace-CRIS: they
can be seen, visualised, searched and “activated”
When selecting a new record in ORCID a new Researcher Page
corresponding to this very record is automatically created

DSpace-CRIS e ORCID: next steps (1)
DSpace-CRIS 4.3.1  DSpace-CRIS 5.1.1 (June ‘15)
PUSH – services (members API)
DSpace-CRIS 5.1.2 (end ‘15)
Advanced PULL – services (members&premium API)
With the collaboration of The Hong Kong University (HKU)
and The Hong Kong Polythecnic University

DSpace-CRIS e ORCID: next steps (2)
– Research’s bibliographic data
(including the possibility to activate synchronisation for single
field)
– Publications
(with the possibility to chose the publications to sync)
– Projects
(with the possibility to chose which projects to sync)
PUSH local
information to
ORCID
PULL extended
information
from ORCID
- Propose to import records in DSpace-CRIS when
login-in looking to the Researcher’s ORCID profile
Or
- Automatically (notification and preferences
allowed) when ORCID premium membership is
available

Thanks
a.bollini@cineca.it
m.mennielli@cineca.it
March 24, 2015

QUESTIONS

3.24.15 Slides, “New Possibilities: Developments with DSpace and ORCID”

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (18)

Andere mochten auch

Andere mochten auch (7)

Ähnlich wie 3.24.15 Slides, “New Possibilities: Developments with DSpace and ORCID”

Ähnlich wie 3.24.15 Slides, “New Possibilities: Developments with DSpace and ORCID” (20)

Mehr von DuraSpace

Mehr von DuraSpace (20)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

3.24.15 Slides, “New Possibilities: Developments with DSpace and ORCID”