Output / Outcome Type Phase Brief Description and URLs (where applicable)
Report 1 Project plan
Report 1 Feasibility study report, describing the requirements for harmonisation of reporting and the recommendations for further development
Journal paper 1 Feasibility Study Into the Reporting of Research Information at a National Level Within the UK Higher Education Sector. New Review of Information Networking Volume 18, Issue 2, 2013, pp.74-105. DOI:10.1080/13614576.2013.841446
Report 2 Phase 2 project plan
Software 2 UKRISS model validation tool
Software 2 UKRISS CERIF schema visualisation tool
Software 2 UKRISS Aggregation tools
Software 2 Crosswalk Connector


Code and source files:

Java source, documentation source and build scripts

Kettle plugins, README for installation instructions:

Documentation build:


Report 2 Final report
Model 2 Core Information Reporting Profile in CERIF

Final report – Appendix 4 (CERIF XML examples).

Website 1 & 2 UKRISS blog

Project Management

Proposal and Plan

The original proposal to the JISC for the UKRISS project can be found here: JISC RIM proposal Final_PUBLIC (omitting the budget information). We were funded on the condition that a number of issues be addressed, so we produced a project plan which more clearly laid out our plans, which can be found here: 2012-02-20 UKRISS Project plan_final_nofinancials.

In outline, the structure of the project is as in this diagram, which shows the dependencies of each part of the work. The deliverables and outputs presented on this page will tie directly to the activities here.

Project Board and Steering Board

The Project Board consists of those project members who are listed on the contacts page.

Throughout the project we are publishing summaries of minutes from Project Board and Steering Board meetings on the blog, under the category “Project Management”. A list of all such posts is available here:

Communication & Dissemination

Over the course of the project we will be attending a number of events to present the findings of our work. The events attended so far are:

6th – 9th June 2012. Proposal, Poster

ARMA conference
12th – 13th June 2012. Proposal, Poster

A full list of Communication & Dissemination blog posts can be found here:


A key to the project was to identify the stakeholders in the sector (of which there are many), and to categorise them into broad groups for interview during the Requirements Gathering part of the project. The categories are:

  • Research Funders (e.g. Research Councils and Charities)
  • Umbrella bodies (e.g. ARMA, UCISA, RCUK, HEFCE-led consortia)
  • Higher Education Institutions and Research Organisations of different sizes and research focus (covering role types: PVC Research, ICT support, Research Administrators, Researchers)
  • Data providers  (e.g. HESA, Thompson Reuters)
  • Data standards community (e.g. euroCRIS community)
  • CRIS systems (e.g. National systems and commercial vendors)

A more detailed coverage of the methodology can be found here.

A full list of stakeholder related blog posts can be found at

Background Research

In the early stages of the project we conducted a range of background research tasks to inform our position for the requirements gathering and ultimately the second phase.

The initial research was in the form of a landscape study, which covers all projects, organisations, software, etc, in the research information space. You can read the latest version of the study here:

A full list of background research related blog posts can be found at:

International Perspective

There are a number of efforts in other countries to provide research information services at a national level, and as part of the background research for this project, we have examined some of them:

A full list of blog posts about the international perspective on this project can be found at:

Requirements Gathering

The early portion of the project focuses on gathering requirements from the project stakeholders. The process of requirements gathering is covered by research ethics guidelines, and each stakeholder is presented with our participant consent form.

The requirements are being categorised into some high-level Functional and Non-Functional requirements

Functional Non-Functional
  • functionality
  • performance
  • interoperability
  • hardware
  • software
  • standards
  • scalability
  • flexibility
  • usability
  • ease of adoption
  • strategic
  • ethical
  • legal
  • business flexibility
  • resourcing
  • governance
  • transition management
  • business sustainability
  • business scalability

You can read a more detailed treatment of the requirements categorisation here.

A full list of the blog posts associated with requirements capture can be found at: