This toolbox is primarily intended for institutional repository managers and technical developers who wish to participate in IRUS-UK.
The toolbox offers a number of resources which should help you to:
COUNTER provides a set of international, extendible Codes of Practice that allow the usage of online information products and services to be measured in a credible, consistent and compatible way using vendor generated data.
The current Codes of Practice are:
For further information see the COUNTER web site.
The IRUS-UK Code of Practice for recording and reporting Institutional Repository usage at the individual item level has been established as an outcome of the Jisc-funded IRUS-UK (Institutional Repository Usage Statistics - United Kingdom) service. It defines the technical, organisational and economic models for the recording, reporting and consolidation of usage of all item types hosted by participating UK Institutional Repositories.
It is consistent with and supplements Release 4 of the COUNTER Code of Practice for e-Resources and Release 1 of the COUNTER Code of Practice for Articles and has been developed in consultation with COUNTER. IRUS-UK is responsible for its ongoing management and implementation.
The IRUS-UK CoP provides the specifications and tools that will allow UK Institutional Repositories (IRs) to participate in IRUS-UK and thus record and report usage statistics at the individual item level that are credible, compatible and consistent. It also provides guidelines for data processing by IRUS-UK and auditing protocols. Institutional repositories participating in IRUS-UK will be considered to be COUNTER/IRUS-UK compliant.
Download the IRUS-UK CoP: PDF
The IRUS-UK service provides a single gateway for institutions to access statistics relating to usage events recorded within their institutional repositories (IRs). In particular, it contains COUNTER-compliant usage statistics for each participating UK higher education institution's IR.
The SLA includes the specification of the service, including its features and reports; agreed service level details and performance indicators; and reporting methods.
Download the IRUS-UK SLA: PDF
The IRUS-UK Takedown Policy applies to the rare occasions when an item in a participating institutional repository has been uploaded in error or has been deemed to be commercially or otherwise sensitive and the repository itself has received a takedown request for that item.
Takedown requests to IRUS-UK must be made by a designated repository manager/administrator.
Download the IRUS-UK Takedown Policy: PDF
If you wish us to implement this process for an item in your repository, please complete our Takedown Request Form.
The 'Notice and Takedown' procedure is then invoked as follows:
Item identifiers play an important role in allowing IRUS-UK to produce accurate statistics and to interoperate with other services. We have produced a brief document outlining our recommended methods of cataloguing several key identifiers and how they should be exposed in repository OAI interfaces.
Download the IRUS-UK Best Practices document: PDF
We have DSpace Tracker patches, developed by @mire, for versions 1.8.1, 1.8.2, 1.8.3, 3.1, 3.2 and 4.x, which are are available on request. Please contact email@example.com for more information.
There is an Eprints Tracker plug-in, developed by Eprints Services, for Eprints 3.2.x and 3.3.x. It is available from the Eprints Bazaar: PIRUS/IRUS-UK PUSH Implementation
IRUS-UK excludes robots and rogue usage from usage statistics, by using:
See our position statement on the treatment of robots and unusual usage.
As part of the IRUS-UK project, we have examined a number of standards that have been proposed for the use of item types in institutional repositories, together with the item types that are actually being used. We have identified a number of issues affecting any attempts to standardise item types across UK repositories and have proposed an initial listing of item types for use in IRUS-UK. This is a pragmatic solution for the immediate future and can be extended as the project progresses as the original item types for each download are being stored and can be remapped at any stage.
Download the report: PDF
The IRUS-UK SUSHI-Lite (Beta) API is now available for trial use. To see how it works, have a look at:
If you want to harvest reports from IRUS-UK using the SUSHI Protocol you will need a suitable SUSHI client. Freely available and easy to use clients are limited, so we offer a sample Perl script to help get you started:
Project Honey Pot is a free, distributed, web-based, open source system for identifying the IP addresses of spammers and spambots. IRUS-UK is participating in Project Honey Pot and has contributed to the project by identifying a previously unknown email harvester. We recommend that our users also participate. Further information can be found on the Project website (http://www.projecthoneypot.org/index.php).
If you are a UK repository wishing to participate in IRUS-UK, please contact firstname.lastname@example.org.