Transcript Document

Repository and
Curation Shared
Infrastructure
(RCSI)
Balviar Notay,
Programme Manager
Digital Infrastructure
slide 1
Background
 Since 2002 – have grown Repository Infrastructure (200 repositories
approx)
 Programmes of activity:
– Exploratory
– Building Capacity
– Enhancement
– Rapid innovation
– Deposit
– Take-up and embedding
 Out of this activity emerged:
– Shared Infrastructure Projects “above campus” – Sherpa Romeo,
JULIET, Pirus2. OARJ, PRONOM, DROID etc
18/07/2015
slide 2
RCSI
 Aims and Objectives
– to consolidate and rationalise the services required - providing
economies of scale, economies scope, and coherence.
– to provide efficiencies and effectiveness by providing infrastructure
services at national level – enabling institutions to run their systems and
processes better
– to enable ease of use of these services.
– to offer sustainable and accountable services.
 Scope
– Underpin an infrastructure for open access research papers but where
feasible also scalable for services to support research information
management (RIM) and research data management (RDM)
infrastructure.
18/07/2015
slide 3
How
 To set up a production environment (UK RepositoryNet+) (works closely
with the Innovation Zone)
– To scope and deliver repository and curation services via the production
environment (working in partnership with others) – ensure robustness for
service delivery.
– Develop new functions/applications on top of the coherent services
– To provide market research/ intelligence, quality assurance, business
case and sustainability planning.
 Set up of an Innovation Zone (UKOLN)
– Support the development of new functionality/applications on top of the
components.
– Involve the developer community to engage with validation, testing
development and foster innovation and experimentation.
 Metadata repository interoperability – RIOXX, V4OA
 Set up strand oversight group to advise JISC on the programme
18/07/2015
slide 4
Functional Specification
– Providing awareness of what is available – Registries (to what end?/who
for)
– Depositing content in an appropriate location – Deposit tools, protocols
– Enhancing the quality of what is held – IPR/copyright information
resources, metadata generation, identifier services, authority files
– Making use of what is held – Content aggregation and discovery
services, authentication and authorisation
– Analysing what is held and how it is used – Citation analysis, statistics
aggregation, activity data
– Protecting what is held over time – Preservation and curation services
18/07/2015
slide 5
RepNet Components
 Service Components

SHERPA RoMEO – look up service for publisher deposit licences

JULIET - look up service for funder policies

Institutional Repository Usage Statistics (IRUS)

Repository Junction Broker (RJB) – facilitates deposit from one to many locations (between
scholarly systems) – first installations at Europe PMC and NPG

Organisational and Repository Identification (ORI) – a piece of middleware that drives (RJB) an aggregation of authority files to support the identification for person and location

Open Access Repository Registry – building on OpenDOAR and ROAR – information about
repositories – e,g. documenting growth, support deposit location information.

Metadata Aggregation – being scoped.
18/07/2015
slide 6
Building of Applications
 Building of Applications on top of service components
– Human interfaces, dashboards, tools for particular stakeholders etc
– Data Driven Infrastructure:
How can the services be run more efficiently and effectively through use
of common authority files, consistency of metadata, exposing of
metadata for other services.
– A possible application might be a “reporting and benchmarking
dashboard”. Statistical data could be provided by IRUS, OARR,
Metadata aggregation.
18/07/2015
slide 7
Repository Interoperability

RIOXX Project – Metadata Guidance for Repositories – Application Profile and Guidance
for aligning metadata fields with Research Councils (RCs), OpenAIRE, DRIVER and CERIF.
– Developing DC Application Profile - fields for project identifier, funder identifier, DOI,
identifier for related dataset, embargo type, embargo end date, access level semantics.
– This supports the tracking of research outputs across scholarly systems.

Vocabularies for Open Access Project (V4OA) – Developing common vocabularies
(Requirements) for rights information and also recording payment of publication fees (Gold
OA).

SWORD (is a lightweight protocol for depositing content from one location to another) –
Scoping OAI-PMH 3 integration and sustainability options.
24/09/2012
slide 8
Functionality?
18/07/2015
slide 9