Output – IRep for NTU – Final Report: Interoperabilty

Title: IRep for NTU – Final Report

Number of pages or page numbers: 15-17, 21

Section: Interoperability and integration with other institutional systems and external systems; Implications and Recommendations

Date Released: 18/07/2008

URI for Output: http://www.ntu.ac.uk/irep/63815.doc

Summary of contents:

Discussion of how the repository integrates with particular existing systems and functions.
‘Integration with eSearch (Metalib): eSearch is the [established NTU] library federated search system
… users [can] perform ‘All Fields’ and ‘Title’ searches directly from the eSearch interface and also allowed thumbnails to be returned for display within this interface where available. … one minor drawback with returning IRep records through eSearch such as if multiple object manifestations are attached to a single record, only a link to the primary object is returned.’

‘Integration with SFX: Our approach with the “Research and Scholarly” collection was to ingest into the repository the totality of the 9000 over records from the Research Publications Database regardless whether or not we had the full text items (or equivalent) to ingest as well.’ Decision based on lack of access to local full text in short term and probable publishers’ restrictions on some pre-prints in longer term. Implemented using ‘using the SFX OpenURL link server from Ex Libris already available at NTU to allow us providing context-sensitive linking to full-text article’ to present ‘ “the most appropriate” location of an object’. This is however DOI dependent and as a result its use is currently limited. [Note full text statistics https://rrtsynthesis.wordpress.com/2008/09/30/output-ntu-irep-for-ntu-final-report-technical-implementation/ ]

‘Integration with NTU Researcher web profiles via X-Server: … IRep [may] completely replace the [Research Publications Database]. One major feature of the RPD is to publish a publications list for each researcher on their NTU profile web pages. This is supporting the RAE requirements.’ This functionality has been demonstrated and tested but is not being implemented before the current RAE review period ends.’

The learning materials system was being replaced during the project so interoperabilty testing was not possible.

Interoperability with OAI-PMH

  • Google and sitemaps

‘However by the time we went live with the repository in early May 2008, Google had released a statement saying that they were retiring support for OAI-PMH in Sitemaps [13]. This was quite a drawback for the project as one of the main pieces of feedback we received from the academics when presenting them about IRep was the clear benefit offered by the repository of having their publications found by search engines.’
Ex Libris are developing a work around (database cloned as static web pages [ functional but !!]).

  • Registry services

Registered with OpenDOAR.

‘We found it was a great advantage to have librarian cataloguers ensuring compliance and monitoring the metadata quality as they were already familiar manipulating such data within other systems. However the cataloguers felt it was a step backward to use Dublin Core as the metadata schema due to its lack of richness in comparison to other schemas they were used to manipulate. However the project team purposely selected the Dublin Core schema in part due to its simplicity for the ease of manipulation by people having no expertise in this kind of data. … Yet the use of the Dublin Core schema brought another issue in terms of interoperability with SFX due to the lack of qualification and the ambiguity in the fields.’ (p21)


No specific details about theses, data, or funding councils mentioned  though they are within scope – so general findings are of some relevance).

There is no mention of any other specific external OAI-PMH based services – harvesters??

Selection of metadata schema based on interoperability/ common ground rather than required (local) functionality?

Output – NTU: IRep for NTU – Final Report: Copyright and Intellectual Property management

Title: IRep for NTU – Final Report

Pages: 12-13

Section: Copyright and Intellectual Property management

Date Released: 18/07/2008

URI for Output: http://www.ntu.ac.uk/irep/63815.doc

Summary of contents:

NTU produced an evaluation of current IPR practice in the university and reviewed the possible use of Creative Commons licensing. It notes differences in practice between research and teaching materials within the institution. [The evaluation of the CC licenses is interesting (and has been done extensively in other projects (rightscom’s project for Jisc legal)) but the implications for the university may be of wider use:]
‘Creative Commons licences – Consequences for the University if proposal adopted
• All University materials containing third party content that are selected for deposit in the IRep would need to be checked carefully to ensure that is permissible to licence that content using Creative Commons.
• University created materials that contain third party content licensed under the Creative Commons attribution, non-commercial, share alike (by-nc-sa) licence would also need to be licensed under the same licence.
• The two University copyright policies, the Copyright in Learning and Teaching Materials and the Intellectual Property policy, would both need amending to reflect this change in policy.
• As the licences are non-exclusive the University would be able to licence commercial use of the materials if desired if either of the two most restrictive licences were used.’

I think, the findings for the university point to the following issues:

  • Significant IPR clearing workload
  • Non-trivial need to change policies
  • Concerns over potential impact on commercialization

Output – NTU: IRep for NTU – Final Report: Implementation

Title: IRep for NTU – Final Report

Number of pages or page numbers: 6-11, 14-15, 19, 27

Section: Implementation, Outputs and Results, Appendix B – Statistics

Date Released: 18/07/2008

URI for Output: http://www.ntu.ac.uk/irep/63815.doc

Summary of contents:

Report outlines a system specification identifying required standards and features for their needs (P6,7)
There is a careful delineation of technical processes of system deployment (P9-11)

NTU outline of a variety of identified types of material to be managed and creation of a functional grouping into collections (P7,8):

  • Research and Scholarly Collection
  • Learning and Teaching Collection
  • Corporate Collection

Each of these collections required different workflows, administrative processes, and had different owners (p14-15).

The Research and Scholarly Collection ‘is the most significant and contained at the launch over 9500 records ingested from the University’s Research Publications Database.’ Many not full text though. (p19)

There are less than 25 asssets in each of the other collections (p27) [!]

There are 990 full text items – however 933 of these are for ‘Web files (.html; .php, et al) [Note – current policy is to link to remote files in such cases rather than store local copies of web files)’ (p27)


NTU’s careful recording has provided a useful checklist of issues to consider when selecting a repository system and preparing to install it.

The careful policy development around the different collections highlights differing requirements of different content types.

Many problems with non research materials will not really have surfaced given numbers.

Full text non remote (i.e. ingested, not available elsewhere, stored by IR) = 57 files
It is not clear who holds these links… if many of these are to publisher sites, how the question of how the IR is better than the existing research database- may not be clear form the project as it stood at the point of reporting.

Output – NTU: IRep for NTU – Final Report: – Institutional Context

Title: IRep for NTU – Final Report

Number of pages or page numbers: 4, 5

Section: Background, Methodology

Date Released: 18/07/2008

URI for Output: http://www.ntu.ac.uk/irep/63815.doc

Summary of contents:

P4. Project arose out of identified need to have a digital asset management system.
‘We identified that digital assets such as theses, published papers, pre- and post-prints, and other e-scholarly works:

• Can be difficult to find;
• Duplicated across the University;
• Stored in an ad-hoc manner;
• Not compliant with copyright requirements;
• Deficient in appropriate metadata and open standards/access requirements;
• Under-exposed or not exposed at all;
• Cannot be searched via a single search engine;
• Cannot be ingested into a centrally management system.’

P5 NTU ‘created six workstreams (Procurement, Content, Technical, Business Processes, Communication & Training) … While the procurement process remained with the senior member of the Libraries and Learning Resources (LLR) department and was completed fairly early in the life cycle of the project, the other workstreams were a collaboration between LLR and other departments … LLR has well established close links with the University’s central Information Technology (IT) department (Information Systems) which supported with the technical and implementation process of the project. University’s Educational Development Unit and the academic schools and departments provided input and support on the content aspect. The teams of specialists within LLR would manage the workflows associated with content ingest ongoing maintenance of the repository, including the application of appropriate metadata standards.’


Project background provides example reasons why a repository can assist.

Processes developed collaboratively to account for stakeholders skills and differing internal and external needs.

Project – NTU

An institutional repository for Nottingham Trent University

Short Project Name: NTU

Programme Name: Repositories start-up and enhancement projects

Strand: SUE

JISC Project URI: http://www.jisc.ac.uk/whatwedo/programmes/programme_rep_pres/repositories_sue/ir_nott_trent.aspx

Project URI: http://www.ntu.ac.uk/irep/

Start Date: 2007-03-01

End Date: 2008-03-30


Contact Name and Role:

Sue McKnight, David Lonjon, Project Director, Project Manager

Brief project description:

“Nottingham Trent University will develop a repository for the storage of a wide variety of materials, teaching and learning, research and institutional in an eclectic variety of formats integrated into a single search mechanism which addresses all the locations we store information. Essentially we want to build a location for anything and everything which will extend the body of knowledge held by the University for the benefit and extension of our members.”

Name of Trawler: John


(only visible public output is final report…)