This toolbox is primarily intended for institutional repository managers and technical developers who wish to participate in IRUS-ANZ.

The toolbox offers a number of resources which should help you to:

COUNTER Resources

COUNTER Codes of Practice

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.

IRUS-ANZ Resources


The IRUS widget enables IRUS-ANZ COUNTER-conformant statistics to be embedded into institutional repository pages. This user requested development offers greater flexibility to access and use IRUS-ANZ statistics.

For further information see the IRUS Widget page.

IRUS Takedown Policy

On 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, a takedown request should be made.

Takedown requests for IRUS-ANZ must be made by a designated repository manager/administrator and addressed to

Takedown Process

If you wish us to implement the takedown process for an item in your repository, please send details to Please include your contact and repository details, the item URL and the reason for the takedown request.

The 'Notice and Takedown' procedure is then invoked as follows:

IRUS Best Practices for Cataloguing Identifiers and Exposing them in OAI-PMH

Item identifiers play an important role in allowing IRUS to produce accurate statistics and to interoperate with other services. Jisc have produced a brief document outlining recommended methods of cataloguing several key identifiers and how they should be exposed in repository OAI interfaces.

Download the IRUS Best Practices document: PDF Open in new tab

The Tracker Protocol

Adding Tracker functionality to repository software enables repositories to transmit usage data to IRUS for processing into COUNTER-conformant statistics

NB. For additional guidance on implementing IRUS-ANZ tracker functionality for the platforms below please contact CAVAL: as some IRUS-ANZ specific modifications may be required.

DSpace patches

We have Tracker patches, developed by Atmire, for the three most recent versions of DSpace. To be able to install a patch, you will need the following prerequisites:

The patches are available at

Eprints plug-in

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

Haplo Repository plugin

A plugin is available for the Haplo open source repository to provide integration with IRUS-ANZ, which can be downloaded from Github. Installing this plugin will enable tracking requests for items downloaded from the public interface to the repository to be sent to IRUS-ANZ for processing into COUNTER-conformant statistics.

For more information please get in touch at

Ruby gem

There is a Ruby gem to provide integration with IRUS-ANZ, available at It can be used with Hydra/Samvera applications, but it can as easily be used with a standard rails application.

Pure Portal

Elsevier have added IRUS-ANZ Tracker functionality to their Pure Portal platform. If you have version 5.6.3 or greater you should be able to enable IRUS functionality without too much difficulty.

There are two scheduled tasks (available via the Pure admin pages) which will need to be configured to run nightly in this order:

If you run a Pure Portal and would like to participate in IRUS-ANZ please contact us at for further information.

Robots and unusual usage

IRUS excludes robots and rogue usage from usage statistics, by using:

See the IRUS position statement on the treatment of robots and unusual usage.

IRUS item type mappings

IRUS-ANZ currently uses 25 item types, to which Institutional Repository item types are mapped. The original item types for each download are stored in IRUS-ANZ and can be remapped at any stage.

The IRUS item types policy can be viewed here: DOC

Download the definitions of IRUS item types: XLSX


The IRUS-ANZ SUSHI-Lite (Beta) API is now available for trial use. To see how it works, have a look at:

Other Resources

Project Honey Pot

Project Honey Pot is a free, distributed, web-based, open source system for identifying the IP addresses of spammers and spambots. IRUS 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 (

If you are a CAUL or CONZUL repository wishing to participate in IRUS-ANZ, please contact

Jisc logo Cranfield logo CAVAL logo