MIMAS Workshop5th April, 2012

Andrew Dorward, Leah Halliday (RepNet), Balviar Notay (JISC), Keith Cole, Ross Macintyre (MIMAS)

2

Agenda1. Introductions, aims of meeting (BN)

2. Project Summary to Date (AD)– RepNet components– Wave 1 functionality

– Wave 2 functionality

– RepNet Website– Innovation Zone– Project Governance– Helpdesk and Support

3. Updates on MIMAS components outside RepNet (BN/KC)

– IRS Search– NAMES 2

4. System demonstration of IRUS (RM)– IRUS and JUSP (KC/RM)

– IRUS Current Functionality (RM)

– IRUS Future functionality and Roadmap (RM)

5. IRUS – future development – Funding (BN)– API Development for harvesting

and processing at local level (all)– Review international scope and

engagement (all)

– Development Required (RM)– Possible new business models

(RM)– Developing SLAs for RepNet

Service (all)

6. Any other business

3

RepositoryNet Production Environment

hosted

…

…

curationmicro-services

InnovationZone

Rapid Innov.

/

…

hacks

…

Service components

Service DeskService Support Service Directory

remote

Funders’Repositories

SubjectRepositories

InstitutionalRepositories

consumers

Sketch of RepositoryNet Infrastructure & Components

4

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

Summary of Components by Functional Area

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

5

RJBroker Wave 1

Components for Wave 1

RoMEO

Juliet

Wave 1

Wave 1

ORI Wave 1

IRUS-UK Wave 1

OpenDepot

UI for OARJ

NAMES2 Align with ORCID

ROAR

Open DOAR

ITT - OARR

ITT - 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

6

Web Site

www.repositorynet.org

Nb: to migrate to repositorynet.ac.uk following JANET registration

7

Roadmap with functional areas

8

Interactions with Innovation Zone

9

Interactions with Innovation Zone

Development & Production Environment Containers

11

Governance of component projects

Proposal ? A project board per owner consisting of

Project Executive – JISC Senior User – RepNet Senior Supplier – Component Owner

Why?JISC provide/decide on fundingRepNet uses the component

Components Owners – SIPG

12

1st line helpdesk and support will come from RepNet, 2nd line from MIMAS.

What will we need from MIMAS to facilitate this? •Full documentation for IRUS•Link from RepNet to IRS•Contact details for 2nd line support person at MIMAS

Helpdesk and support

13

Other MIMAs components and IRUS demo

1.Updates on MIMAS components outside RepNet (BN/KC)– IRS Search– NAMES 2

2.System demonstration of IRUS (RM)– IRUS and JUSP (KC/RM)– IRUS Current Functionality (RM)

– IRUS Future functionality and Roadmap (RM)

Benchmarking and Statistics - IRUS

IRUS – future development – Funding (BN)– API Development for harvesting and processing

at local level (all)

– Review international scope and engagement (all)

– Development Required (RM)– Possible new business models (RM)– Developing SLAs for RepNet Service (all)

•Any other business

– Ideas for Innovation Zone