Output – IncReASe: Final Report – research management

Title: IncReASe: Final Report

Page: 14, 21-22

Date Released: 30 April 2009
URI for Output: http://eprints.whiterose.ac.uk/increase/increase_finalreportv1.pdf

Summary of contents:
All three universitiies particpating in WRRO have begun to examine Research management systems with differing results.
University of Sheffield have put their working group’s findings on hold pending more information about the REF but are investigating systems.
University of York is currently scoping a Research Information System (WRRO is likley to have a significant role)
University of Leeds has selected a system. Their RIS system “will [probably] become the primary ingest route for both metadata and full text”. As yet workflows and staffing (including any involvement of repository or library staff) for the metadata creation in this new system are unclear. As the source of metadata and primary point of contact with academic/ research staff this has the potential to greatly benefit the integration of WRRO into the publication process.

From the conlucions:
“Our discussion with researchers suggests that a comprehensive service – essentially, a publication database – is probably an easier sell than a pure “open access” repository (echoing the conclusions previously drawn by, for example, the TARIS project); its raison d’être is clearer and the possibility for providing services back to researchers in the form of full listings of research and detailed information on traffic to individual works, is increased. Currently, this is not the direction being taken by WRRO; rather, because other central services are likely to fulfil the publication database function, the emphasis remains on external dissemination of open access outputs.”
“Capturing grant and project data relevant to research outputs is likely to increase in importance; this data can help maximise the value of repository content for both research and administrative purposes.”

The RIS system at Leeds does of course also raise potential to difficulties for metadata quality.

All three institutions invovled in WRRO are actively moving towards some form of CRIS system; in all institutions this will impact significantly on the role and prominence of the repository. It is not clear how positive or negative this impact will be. What is clear is that for a institutional repositories covering the area of scholarly communicaitons CRIS systems are very likely to change what and how they operate.

Output – OARS – OARS Functional Specification Document

Output Name: Output – OARS – OARS Functional Specification

Title: OARS Functional Specificationn
Number of pages or page numbers:30 pages

Date Released: 18 January 2008

URI for Output: http://oars.forcedmigration.org/wp-content/uploads/2008/01/oars-functional-specification.pdf

Also of interest might be:


Depicting the current system in place for managing content.

Summary of contents:

Useful fucntional specification document for the OARs project.  Could be useful for instituions who need to look at exemplars of funtional specifications for their own needs, with useful fucntionality check list on page 27 (appendix 1) and for metadata requirements – appendix 2 – pages 28-30

Project – RSP

Project Name: Repositories Support Project

Short Project Name:RSP

Programme Name: Repositories and Preservation


JISC Project URIhttp://www.jisc.ac.uk/whatwedo/programmes/reppres/repsupport.aspx

Project URI: http://www.rsp.ac.uk

Start Date: October 2006

End Date: March 2009

Governance:JISC IIE

Contact Name and Role:  Bill Hubbard (Project Manager)

Brief project description:

The Repository Support Project (RSP) is a 2.5 year project to co-ordinate and deliver good practice and practical advice to English and Welsh HEIs to enable the implementation, management and development of digital institutional repositories.

Name of Trawler: Mahendra Mahey

Outputs: (just link to individual output postings) as a bulleted list

Output: VIF – VIF website: versioning issues

Title: VIF: why versioning matters

Pages: webpage
Date Released:

URI for Output: http://www.lse.ac.uk/library/vif/Problem/importance.html

Summary of contents:
The project notes the common versioning issues that repositories face.

  • ” Confusion over whether an article is the published version, a copy that is identical in content to this but unformatted, a draft version, an edited version and so on.
  • Repository searches yielding many results which ostensibly appear to refer to the same item, but actually vary in terms of content, formatting or propriety file type.
  • Research work with multiple authors being deposited in different places at different stages of development without guidance as to which is authoritative or most recent.
  • Multimedia items being handled poorly by repositories that treat them as text, and their relationship to other objects that form part of the research project being undefined by the repository.
  • Vastly inconsistent approach of different repository software packages and implementations in how versions are dealt with.”


Although this is intended to provide the context of the project, it also provides a succient introduction to the survey findings and the problem repositories face.

Output – KULTUR – Institutional Profile: University College for the Creative Arts

Title: Institutional Profile: University College for the Creative Arts
Number of pages or page numbers: pp 6-7
Section: Summation

Date Released: 27th March 2008

URI for Output: http://kultur.eprints.org/docs/Microsoft%20Word%20-%20UCCA%20profile%208%20April%20online%20version.pdf

Summary of contents:

A few observations of interest w.r.t. repositories for the arts in the ‘summation’ section of the report:

“The project will need to engage, advocate and secure ‘buy-in’ from the academic community. It will be important to establish an understanding of the culture of each college so that local differences or requirements can be taken into account. We will need to create a network of contact with key individuals and interest groups across the institution with which to communicate and gain direction on the project. Following on from this it will be imperative to be able to understand, interpret and communicate the range of differing concerns with the project team so that development is accurately representative.”

Additional information:


Output – KULTUR – Environmental Assessment of the University of the Arts, London

Title: Environmental Assessment of the University of the Arts, London
Number of pages or page numbers: pp 6-7
Section: Summary

Date Released: 8th April 2008

URI for Output: http://kultur.eprints.org/docs/UUAL%20profile%208%20april%20online%20version.pdf

Summary of contents:

The summary section has a few useful observations w.r.t. repositories in the Arts sector:

“The opportunities for a repository at UAL are great since there is a wealth of research
being produced at all levels within the University. At the same time the sheer amount of
research and research active staff can present its own problems. The targeting of key
research staff, the enlisting of research centres/units and the research offices are
essential for the success of the project. Advocacy from the top and from the bottom is
needed but this can only really be effective by establishing good relationships and links
with relevant University bodies and staff. We need to identify just what a repository can
do for each group and advocate along those lines … Populating the demonstrator with a good number of pieces of research will help the project become more attractive and viable to research staff. The interface and the software itself will also play a large part in any success.”

Additional information:


Output – NECTAR: Nectar Case History – embedding

Title: NECTAR: Northampton Electronic Collection of Theses And Research

Pages: all
Date Released: 2008

Summary of contents:
“Existing research reporting channels are being exploited to gather NECTAR content. From January 2008 the university’s Annual Research Report will be derived from NECTAR — if a research output is not in NECTAR it will not be reported.”

URI for Output: http://nectar.northampton.ac.uk/NECTAR_case_study_OR08_ver2.pdf

this case study is largely superceded by the fuller later one – but i don’t recollect this line in the later article.
This illustrates both how embedded the NECTAR repository has become within the institution and also one of the roles a repsitory can play in the institutional infrastructure.