Lessons in Open Access Compliance for Higher Education (LOCH)
Upcoming SlideShare
Loading in...5

Lessons in Open Access Compliance for Higher Education (LOCH)



Presentation by Dominic Tate, University of Edinburgh, at Repository Fringe 2014

Presentation by Dominic Tate, University of Edinburgh, at Repository Fringe 2014



Total Views
Views on SlideShare
Embed Views



1 Embed 4

https://twitter.com 4



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment
  • The LOCH Project will provide a series of re-useable, Open Access resources which will be of use to practitioners working with Open Access in Higher Education Institutions across the UK over the next few years. These resources will outline the rich experiences of the three project partners of implementing systems to enable, verify and report on Open Access at each institution. The resources (case studies, workshops, webinars, workflows etc.) support Jisc’s commitment to making compliance with Open Access requirements as easy as possible for researchers and as efficient as possible for HEIs. <br />
  • Heriot-Watt University and St Andrews University were joint submission partners with the University of Edinburgh in the 2014 REF. All three universities are members of the Scottish Digital Library Consortium (SDLC) and Heriot-Watt and St Andrews use DSpace Repositories hosted by the SDLC at the University of Edinburgh. All three partner universities use Elsevier’s PURE current research information system and the proposed project officers are all active members of the PURE UK User Group on behalf of their institution. All three partners have significant research collaborations with one another, with implications for shared responsibilities for Open Access to research publications and research data. <br />
  • We will write and publish case studies based on work already undertaken and, working with other pathfinder projects, we will report on the landscape as things stand during the summer of 2014. <br />   <br /> Using this work as a basis, we will seek to improve institutional workflows and pilot new services over the course of the following 12 months which will inform a second round of case studies, workshops and webinars. <br /> Project partners will further improve workflows with the aim of having systems and practices ready to enable researchers to comply with requirements for Open Access in the post-2014 REF ahead of those requirements going live in April 2016. We have already kick-started this process by comparing the REF requirements with current Pure functionality, and drafting development proposals for discussion by UK User Group. Project partners were also heavily involved in developing specifications for the Pure REF module. A final round of case studies and webinars and a related event will be made available early in 2016. <br />   <br /> The project will be run by existing staff in all institutions. Some partners intend to redirect salary savings offered by project income into a small number of part-time temporary staff to look at different models of uploading content to repositories (e.g. staff based in Schools), or part-time compliance checking in the library. Progress with these new approaches will be reported on in the project. <br />
  • There will be six case studies overall – two delivered in each calendar year the project operates in (2014, 2015 and 2016). This offers good value for money as there will be three years’ worth of case studies from a two-year project. A minimum of two partners (but in most cases all three) will contribute to each case study. <br /> The case studies will focus on one particular aspect of the project, such as managing Open Access funds, technical developments needed to introduce new functionality to PURE to cope with the requirements for the next REF, or the approach taken to reporting compliance to RCUK. <br /> Case studies will be authored collaboratively and peer-reviewed by members of UKCoRR and/or ARMA prior to publication. The intention is that they will be light-touch yet informative, relevant and current. <br /> <br /> There will be three webinars, one in each year of the project, presenting the case studies and associated materials. These will allow participants the opportunity to ask the project team questions about their experiences and will contribute to sharing good practice. <br /> <br /> There will be three workshops over the course of the project. Two of the workshops will take place at the annual Repository Fringe event which will take place in Edinburgh in July 2014 and July 2015. These workshops will be primarily aimed at Repository Managers and Open Access practitioners, who would be attending these events anyway. It is also anticipated that these workshops could also be promoted to members of the Research Manager community via ARMA. <br /> The third event would be a final workshop in early 2016, primarily aimed at Research Managers and Administrators. This would be organised and promoted via ARMA and might take place in Manchester, Birmingham or London. This would present the project’s final experiences ahead of the Open Access requirements for the next REF going live in April 2016. <br /> <br /> There would be a minimum of one blog post per month for the duration of the project (24 months) via the Project Blog, which would also feed the OA Good Practice Blog at http://openaccess.jiscinvolve.org/wp/. <br /> Furthermore, the project officers would undertake to write guest blog posts and news items for other relevant organisations such as UKCoRR, CILIP, CILIPS, SCURL, SCONUL, RLUK, ARMA, RCUK (and member funding councils), Wellcome Trust and Jisc. Partners undertake to use Twitter to provide frequent updates on project progress, developments and new outputs. <br /> <br /> Each partner will pilot new services and/or workflows within its institution and will report on these pilots in short reports (one per year). These pilots may also inform blog pots and case studies. <br /> <br /> Each partner institution will undertake to present at one external conference or meeting during the course of the project. Examples of such meetings could be: UKCoRR meeting, ARMA annual conference, PURE UK User Group meeting, Open Repositories etc. <br />
  • Each partner will undertake to write one article for a professional publication during the course of the project (Ariadne, CILIP News etc). <br /> <br /> Via the PURE UK User Group, the partners will lead on the development of a specification for PURE to “enable, verify and report on” compliance with Wellcome Trust, RCUK and post-2014 REF requirements for Open Access. <br /> <br /> There will be two formal reports to Jisc during the project, at the end of year one, and at the end of the project. These will be made Open Access and will be reusable, licenced using CC-BY. <br /> <br /> The project will prepare a series of template texts which could be used by other universities with agreed wording on research funder policies, REF requirements, processes and associated topics. <br /> <br /> The project will contribute to programme meetings and work closely and collaboratively with other projects in the programme. <br />

Lessons in Open Access Compliance for Higher Education (LOCH) Lessons in Open Access Compliance for Higher Education (LOCH) Presentation Transcript

  • Lessons in Open Access Compliance for Higher Education (LOCH) Dominic Tate Scholarly Communications Manager University of Edinburgh
  • Who We Are… • University of Edinburgh – Large, research-intensive Russell Group University with 30,000 students and 12,000 staff • Heriot-Watt University – One of the top UK universities for business and industry with 11,800 students in 150 countries • St Andrews University – Scotland’s oldest university founded in 1413. Research-intensive with over 25% of turnover from research grants and contracts.
  • Approach • Managing Open Access payments, (including a review of current reporting methods and creation of shareable spreadsheet templates for reporting to funders), • Using PURE as a tool to manage Open Access compliance, verification and reporting, • Adapting institutional workflows to pre-empt Open Access requirements and make compliance as seamless as possible for academics.
  • What we are working on… • A functional specification for PURE, to ensure compliance with the OA requirements for the next REF, • Baseline case studies to review the OA landscape at each partner institution, • First look at revising workflows and communications in light of REF requirements.
  • Planned Outputs (1) • Six Case Studies • Three Webinars • Three Workshop Events • 24 Blog Posts • Pilot Services/New Workflows • Three Conference Presentations
  • Planned Outputs (2) • Three Journal Articles • Specification for PURE • Two Formal Reports • Web Template Texts
  • Questions? dominic.tate@ed.ac.uk