Future direction of ROS

Dale Heenan

ESRC Senior Project Manager

Participants

Pre 2012 ESRC Research Catalogue

January 2012 ROS = AHRC, BBSRC, EPSRC + ESRC

January 2013 ROS = + NERC + Institutes and Centres

January 2014 Government departments?Other interested organisations?

Scenario’s

• PI’s submitting to RCUK (more manual)– with limited research office support– with strong research office

• Institution submitting to RCUK (more automated)– HEI collects centrally– Bulk submits on behalf of PI

• Even split between submission methods – manual vs bulk• 14 out of 361 bulk submitters from HEI’s..

CERIF adoption

• Soft launch… it’s a secret• January 2013, CIA live

• Very keen on a follow on project – Non publication Outputs– Outcomes and Impacts

Automation

• 2012 was launch and user interface

• 2013 is greater focus on system to system transfer– CRIS– Institutional repositories– Repository Junction– OAI CERIF?

• Data exchange between ResearchFish and ROS

Platform improvements

• Website– Single– Simplified use of look ups– Bulk submission by simple / full spreadsheet– CERIF file upload & email / deposit

• OAI devolved to institutional users – JISC RIOXX• Public API to assist HEI’s with reconciliation• Reporting / Export

JISC RIOXX

Engagement

• ROS Manager - stand up, please– Single point of Contact is Lydia Fulford

• Research Outcomes Forum– Arms length– Organised with ARMA

• Representatives from across the sector– Including nominations from 1994, Russell group– Invites going out soon

• TBC but first meeting in November then online• Feedback, improvements, adoption

Gateway to Research

Gateway to Research

ResearchFish ROS

Submission

The world

Gateway to Research

1. Expanding the GtR dataset to studentships, all intra Council Grants and linking to research datasets and publication repositories. Establishing data refresh routines such that the GtR dataset is dynamic and reflects changes in source systems rapidly.

2. Playing a part in facilitating an integrated Research Council ‘data depositing and harvesting experience’ for universities to populate and use – data in using e-Val/ROS, data harvesting using GtR;.

3. A further iteration of the User Interface based on feedback on the beta system;4. The GtR dataset to inform a “single cross council funding schema for internal MIS and Data mining

as well as external Grants on the Web type tools”. Help to develop a common schema for GtR data (ROS/e-Val/Grants);

5. Deliver a platform that enables a true cross Council ‘Grants on the Web’ to be developed. Establish the functionality and data that needs to be added to GtR to make this happen;

6. Hack Days and Competitions to generate and test possible online uses of the newly available RC’s data (e.g. mash-ups with other data to reach particular audiences, such as patients, small businesses, etc.);

7. Ongoing logging of data quality issues leading to 2 outputs – potential clean up of historic data at source in e.g. OBIEE and recommendations to improve any endemic problems in source systems and processes that lead to poor data quality;

8. A sustainable Target Operating Model;

And a little more….

9. Incorporating relevant TSB data, i.e. jointly funded grants;10. Explore advanced search and fingerprinting technology to enhance the ability of the user to find the

results that they need.11. Delivering the Gateway to Research system as a ‘solution in a box’

Designed in such a way as to be usable as a tool by other organisations that want to deliver a similar system