UK RepositoryNet+: Jisc Oversight Group, 2012-11-29

1RCSI Oversight Group 29th Nov’12

RCSI Oversight Group29th November, 2012

Peter Burnhill, Andrew Doward, Terry Sloan for RepNet Project Team

roles & introductions

2

• Part 1: UKRepNet as Project– What we said we would do

• Our proposal• The landscape & required infrastructure• Engagement

– Project Plan & Timeline• Summary of progress• Stakeholder Engagement• Changes along the way

– What is planned over next 8 months• Moving to a Service-Orientation

• Part 2 (after lunch): making UKRepNet a Service

Overview

3

• … firm focus on Open Access research literature … :

a) Set up a production environment [for repositories] which works closely with the innovation [zone]

b) Scope/deliver (.. partnership with others) repository & curation services via a production environment that offer economies of scale & scope

c) Provide market research/ intelligence, quality assurance, business case and sustainability planning to support the project.

• In meeting this Call … we will:

(1) provide socio-technical infrastructure that supports the deposit, curation & maximal exposure of Open Access research literature

(2) ensure the delivery of services that assist sustainability & embedding within institutional processes to demonstrate value for institutions, their researchers & their funders, and

(3) assist JISC achieve overall aims for JISC Digital Infrastructure.

Proposal in response to the JISC Call

4

Understanding the Repository Landscape

Eval

Academic

reader

researcher

ResearchOutcomes

UKPMC

HEI Institution

[OA mandate]

Library

CRIS

InstitutionalRepository

Publisher

author(s)

editorreferee

teacherstudent

P.I.

journal

monographLicensed/tollgate

access toPublisher’s Final Copy

(PFC)

ARMA

ResearchAward reporting

Deposit of metadata/text of

Authors’ Final Copy(AFC)

DigitalLibrary

curation micro - services

Research Excellence Framework

metrics

SubjectRepository

stewardship budgets

NORA

UK Research Funder

[OA mandate]

HEFCE, SFC …

EU RCUK WellcomeTrust

SWORD

CERIF

UKCoRR

EU

5

Institutions Have Mixed Purposes for Repositories

PublishersAcademics

Institutions

Funders

Reader

Author

P.I.

Teacher

Faculty

ResearchAwards

Institutional Repository

Subject Repository

Funders Repository

Monograph

JournalArticle

CRISLibrary

Open Open AccessAccess

Research Research Information Information

ManagementManagement

Research Grant Office

6

Sketch of RepositoryNet Infrastructure & Components

RepositoryNet Production Environment

hosted

…

…

curationmicro-services

InnovationZone

Rapid Innov.

/

…

hacks

…

Service components

Service DeskService Support Service Directory

remote

Funders’Repositories

SubjectRepositories

InstitutionalRepositories

consumers

7

• Advisory Board• William Nixon (University of Glasgow)

• Chair (& Senior User on Project Board)

• Chris Awre (University of Hull)• Les Carr (University of Southampton)• Simon Kerridge (University of Kent)• Stuart Lewis (University of Edinburgh)• Kevin Ashley (DCC)• Paul Walk (UKOLN)

• UKCORR• Workshops at OR12 conference• RCUK• OpenAIRE

Engagement

8






Overview

9

UK RepositoryNet Plan/Timeline as at last OSG

10

NAMES2Naming Authority for the UK assigning identifiers to organisations and individuals engaged in research

Components considered by OSG for Wave 1 funding

ROAR

Open DOAR

ORI

Authoritative, manually curated registry of OA repositories, combined with harvested metadata

Registry of OA repositories compiled with statistics in mind

Organisation based with information on repositories

Research funders’ policies on OA

RJBroker

RoMEO

Juliet

OpenDepot

Publisher policies on OA deposit

Redirect facility to OA IRs, and default OA repository

M2M direct for multi-authored works to OA repository(ies)IRUS-UK Centralised service for collection of OA

usage statistics

IRS

REPUK

CORE

Aggregated set of metadata for development

Search, aggregation, full-text mining for OA repositoriesSearch, aggregation, data-mining for all IRs

A: Aggregation, Text mining & Search

B: Benchmarking, Statistics and Report

C: Creating Relevant Registries

D: Deposit Tools

E: Enhancing Metadata Quality

11

RJBroker Wave 1

Wave 1 Decisions by JISC/OSG

RoMEO

Juliet

Wave 1

Wave 1

ORI Wave 1

IRUS-UK Wave 1

NAMES2 Align with ORCID

ROAR

Open DOAR

Closed Call - OARR

Closed Call - OARR

IRS

REPUK

CORE

Innovation Zone

Innovation zone

Innovation Zone

A: Aggregation, Text mining & Search

B: Benchmarking, Statistics and Report

C: Creating Relevant Registries

D: Deposit Tools

E: Enhancing Metadata Quality

KPL Report on

Search

Awaiting notification of

outcome

12

RoMEO-Hosted JULIET-Hosted

IRUS-UK ORI

RJBroker

Retired Services

Third-party components

Continual Service

Improvement Service

Concepts

Market Research

Service Transition

Service Design

Innovation Zone

(REPUK, CORE, IRS)

Operational Services

RoMEO JULIET

ITIL Service Portfolio

13

Plan: What has happened (thus far)

as planned

as happened

14

Brief note on changing environment during project timeline

UK-Corr meeting

First briefing to users

GA Report on CRIS/IR and RIM

publishedNordBib

CopenhagenMeet with OpenAIRE

Finch Report

published

JISC RIM meet

Bristol

OR 12 RepNet workshops with

SIPG, OpenAIRE,

users

JISC announce no Wave

2

Formulate use cases for Wave 2

with IZ, SIPG, stakeholders

UK-CoRR meeting Teeside.

Validate new applications for

Wave 1

Curation/ preservation workshop at

UKOLN

2012

2013

15






Overview

16

UK RepositoryNet Revised Plan

17

• RepNet Advisory Board– 4th meeting in January’13 on sustainability– Further meetings planned for April and June’13

• RepNet SIPG ‒ 3rd meeting in February’13 on Sustainability‒ Further meetings planned for April and June’13‒ January’13 meeting with RJB with variety of repository software platforms ‒ Support for RJB roll-out expert IR advice

• UKCORR‒ November’12 meeting‒ Gathered IR requirements through survey to reinforce use cases for new applications

• ARMA (TBA)• With Repository Support Project (RSP)

‒ Jan 21st’ ’13 workshop on planned services and new applications‒ Further events in March (Complying with Funder Policies) and June’13 (Increasing

Deposit Rates) and webinars

Dissemination & Engagement Plan

18






Overview


RepNet Website - Schematic UI


Service Component update: IRUS-UK

IRUS-UK

•Pilot since June 2012, transitioning to RepNet operational service, currently undergoing service acceptance testing – testplans and matrices to be uploaded to the RepNet Git repository.

•DSpace and EPrints tracker code enabled, Fedora to follow by 31/3.

•API to be delivered 30/11/ for testing

•By 31st March 2013 IRUS will deliver: ingest scripts; a lightweight UI; authentication layer; SUSHI server; CSV export utilities.

•Targets for IRs: 50%-75% of UK IRs with Eprints; 30-50% with Dspace, 1 Fedora

•Project Status snapshot Service Status snapshot


Service Component Update: SHERPA RoMEO

SHERPA RoMEO

•Exists in RepNet Service Portfolio as a production service and service in transition – service launch scheduled on 3 rd May 2013

•Development of component into new RepNet service involves modularisation of the API and database to allow the development and management of modules as separate entities and hosting migrated to RepNet.

•Current plan to have mirrored service (2 database instances load-balanced between CRC and RepNet) available for testing 7/12/12, in production by 31/1/13

•SLD output is behind schedule, currently being drafted and reviewed.

•API output is behind schedule due to dependence on delivery of phrase admin tool. Initial deliverable 30/11/12 put back to 21/12/12

•Project status snapshot

•Service status snapshot

22

Service Component Update: SHERPA JULIET

SHERPA JULIET

•Like RoMEO, JULIET exists in RepNet Service Portfolio as a production service and service in transition – service launch scheduled on 22nd May 2013

•Development of component into new RepNet service involves an audit and enhancement of data, development of an API and search interface and improvement of internal admin of data.

•Current plan to have mirrored service (2 database instances load-balanced between CRC and RepNet) available for testing 7/12/12, in production by 31/1/13

•Search interface on schedule – delivery 30/11/12

•Audit JULIET data on schedule – complete by 21/12/13

•Page on funder’s best practise – delivery on 27/1/13

•API on schedule – delivery 22/2/13

•Internal admin tool with Google Analytics – delivery14/3/13

•Implementation of new features arising from stakeholder review – delivery 26/4/13


•Service status snapshot

23

Service Component Update – RJ Broker

RJ Broker

•RJ Broker exists as a service in transition in RepNet Service Portfolio, with the middleware tool to go into service with RepNet on 31st March 2013.

•Development includes configuring RJ Broker as stand-alone middleware, development of a GUI, supporting use cases and a template legal agreement with IRs and publishers that can be developed into a template by RepNet.

•Prototype of RJ Broker GUI on schedule for testing end December 2012, available as service end January 2013.

•Delay to planned standards review incorporating RIOXX in December. RJ Broker output is not dependent on RIOXX delivery.

•Data feeds from NPG delayed by Hurricane Sandy – resume early December

•Data feeds from EuropMC now included in EuropMC workpackage implemented by MIMAS from January 2013 – daily updates are planned.

•RepNet will take over responsibility for rollout to IRs, including legal agreements and configuration of SWORD end-points from 31/3/13 in conjunction with RSP and the RepNet Partner Repository Expert Group (PReG)

•Project status snapshot Service status snapshot

24

• OA Repository Registry (OARR)• Engage with successful bidder (in SIPG)

• ORI (Organisation & Repository Identification)• Use cases

• Aggregation• New Applications build on Wave 1 components• Preservation/Business Continuity

• Sustainability

Service-related Developments

25

OARR

26

ORI: Use Cases

Organisation and Repositories Identification (ORI)

•The ORI component project is complete. ORI was originally developed as part of the RJ Broker but has been reconfigured as a standalone middleware tool for identifying academic organisations and institutional repositories.

•ORI will be made available as a middleware resource to the successful bidders for OARR.

•Full documentation of ORI has been completed, together with a set of use cases to illustrate how the component can be employed by different users.

•Use cases for ORI have been developed for the following users:• Providers of applications making use of authentication (e.g. ORCID,

Mendeley, Symplectic, Funder reporting systems, Arkyves, publisher submission systems.

• UK Access Management Federation Service Provider• EDINA Service Authentication• EDINA Support Desk Staff• Open Access Repository Registry (OARR)• Innovation and Application Developers

•Use cases include:• Identifying a target repository for deposit• Searching for repository information


27

Aggregation

28

1. Planning for future RepNet services

2. Based on Wave 1 services & Scoping activity for Wave 2

3. List of potential services derived from Use Case approach

4. Need now to determine priority & technical challenge:

i.validate user requirements (+ feedback from survey)

ii.assess technical approach

New Applications: Use Cases

29

RepNet Use Cases: view from IZ

30

RepNet Use Cases 1-3: view from IZ

31

RepNet Use Cases 4-5: view from IZ

32

Preservation / Continuity of Access

33

Preservation: No mention, per se, in Proposal

“... interaction with the University of California Curation Center (UC3) has prompted a marker for curation micro-services …

• “The purpose of [WP3: Scope Curation Components: Tools & Services] is to appraise & propose/confirm curation components that will add value to repositories of research literature This is scoping to identify components, not to devise a curation services framework.

• “… placing emphasis on continuing access”

34

• Insert/switch to LOCKSS slides

35

Understanding Sustainability

• Value proposition – meeting a purpose that will endure

• Variety of cost models

• Variety of business/revenue models

• Choice of Technology

• Organisational Form

36

Sustainability: of what, for whom?

... for Policy (JISC & BIS / RCUK)

• Open Scholarship

Green OA (self-deposit)

Gold OA

• Research Reporting & Compliance

• Data through the lens of literature

... for Component Providers (SIPG)

• from Project funding to Service mode: Service Level Definition & Service Budget

• Medium-term planning for continual service improvement

... for UKRepNet as infrastructure• status as JISC Core Service within EDINA as JISC digital infrastructure

• Managed hosting environment for services with revenues to support this.

• ITIL-based processes for service development, transition and operation.

... for Inst. Repositories• support for Open Access

• broader institutional objectives

IR-as-CRIS; CRIS-as-IR

• Research Reporting (REF) & Compliance (RCUK)

37

Projected timelines for sustainability planning (tba with JISC)November

2012December

2012January

2013February

2013March 2013

April 2013

May 2013

June 2013

July 2013

Possible ongoing activities subject to funding

Define framework

Validate framework with focus groups

Devise cost models

Define service levels against business models

Select/appraise business models;

create business plan Prepare business model options for agreement

by JISC

Agree Sustainability Timelines with JISC (re JISC Business Review)

Write and publish RepNet Sustainability Plan for Growth with input from

JISC

38

The End – Further Questions?

Education

UK RepositoryNet+: Jisc Oversight Group, 2012-11-29