IRUS-UK is a national aggregation service which contains details of all content downloaded from participating UK institutional repositories (IRs). It follows on from the successful PIRUS2 project ( http://www.cranfieldlibrary.cranfield.ac.uk/pirus2/tiki-index.php ), which demonstrated how COUNTER-compliant article-level usage statistics could be collected and consolidated from Publishers and Institutional Repositories, IRUS-UK is a Jisc-funded repository and infrastructure service.
IRUS-UK enables UK IRs to access and share comprehensive and comparable usage statistics using the COUNTER standard. The service collects usage data from participating repositories, processes the data into COUNTER-compliant statistics and then presents statistics back to originating repositories to be used in a variety of ways.
The service aims to provide a nation-wide view of UK institutional repository use to help demonstrate the importance and value of IRs. The service will also provide opportunities for benchmarking and act as an intermediary between UK repositories and other agencies, e.g. global central clearinghouse, national shared services, Research Councils, SCONUL, OpenAIRE.
IRUS-UK provides COUNTER-compliant usage statistics on items downloaded from participating repositories. It covers all item types within repositories.
PIRUS2 worked with a limited number of item types (article, book chapter, book section, conference or workshop item, dataset, manual, other, presentation, report, technical report, thesis or dissertation, working paper) to which all other item types were mapped. IRUS-UK continued to use these item types but, following research into guidelines on and actual usage of item types ( http://www.irus.mimas.ac.uk/help/toolbox/IRUS_item_type_report_v3.3.pdf ), we are now using the following set of item types:
Art/Design Item; Article; Audio; Book; Book Section; Conference or Workshop Item - Other; Conference Papers /Posters; Conference Proceedings; Dataset; Exam Paper; Image; Learning Object; Moving Image; Music/Musical Composition; Other; Patent; Performance; Preprint, Report; Show/Exhibition; Text; Thesis or Dissertation; Unknown; Website; Working Paper.
In each case, the original item type is stored so that this list can be expanded or modified over time.
IRUS-UK is being developed by a consortium involving Jisc Mimas, Cranfield University and Evidence Base at Birmingham City University.
All UK institutional repositories are welcome to participate in IRUS-UK.
A pilot group of repositories was involved in the initial stage of the project. Participation is now open to all interested UK repositories. Participating repositories are listed at http://www.irus.mimas.ac.uk/participants/. We are successfully receiving download activity data from these repositories and currently hold data from July 2012 or from an institution's participation date if later.
IRUS-UK has been designated as one of Jisc's 'core services' for 2014/15 and 2015/16. So funding has been assigned to cover ongoing support and development of IRUS-UK in the current year and next, though obviously the 2015/16 Jisc budget is to be confirmed.
Our website has an overview of the project and contact information if you want to get in touch. We speak about IRUS-UK at conferences, events and webinars. A list of events that the IRUS-UK team has attended is featured at http://www.irus.mimas.ac.uk/news/. The page also contains links to papers, presentations and webinar recordings. You can follow us on Twitter @irusnews.
Participation is open to all interested UK HE and Research Council institutional repositories.
We are currently working with EPrints, DSpace and Fedora repositories, which account for about two thirds of all UK repositories, and will be working with others in the future. Please feel free to contact us if you are interested in working with us and you use or supply other repository software.
Contact us at firstname.lastname@example.org if you are interested in joining IRUS-UK. Let us have details of the repository software that you use, the version and whether or not you have a hosted repository. We will then be able to either supply the appropriate plug-in or patch, advise you where to obtain it or advise you who you need to contact.
We gather data using tracker code plugins and patches and have initially focussed on developing tracker functionality for DSpace and EPrints repositories. We have patches available for DSpace (1.8.x, 3.x, 4.1 and 4.2) and plug-ins available for EPrints (works with 3.2 or greater).
We use a "push" mechanism whereby a notification is sent to the IRUS-UK server as an OpenURL key-value pair string every time a file is downloaded from a repository.
Data is stored in daily log files which are usually processed the following day. The data for each item are consolidated into daily statistics and are filtered to remove robots and double clicks. These daily statistics are then consolidated into monthly statistics, the traditional COUNTER granularity.
Access to the portal is available via a Shibboleth login.
The portal provides a number of different reports and data views together with an author/title search.
Reports can be generated in HTML, CSV or TSV formats.
Further information about each of these reports can be found here ( http://www.irus.mimas.ac.uk/help/available/ ).
We welcome your feedback on further developing these outputs.
This is something a number of IRUS-UK users have asked about, so we have been investigating it further. The only practical way for IRUS-UK to obtain school/department metadata related to individual items for each repository is to use the ‘ListSets’ mechanism which is included in the OAI-PMH. Having looked at this for our current IRUS-UK repositories, some repositories do map their schools and departments to OAI Sets but many do not. In fact there are over 28,000 different ‘sets’ in use, and many of those define the status/subject/type of items rather than their affiliation, so it’s not a simple process!
We will however be looking into this in more detail to see if there’s a way we can share downloads by set. In the meantime, if you would like to use this functionality in future we would recommend you check your repository configuration to ensure that you map your schools and departments into corresponding OAI Sets.
We remove entries from known robots appearing on the COUNTER robots list (found in Appendices I and J of the COUNTER Code of Practice ( http://www.projectcounter.org/code_practice.html )).
As repositories have joined IRUS-UK, we have identified other robots not on the COUNTER list and have started to compile an additional IRUS-UK list of robots. In order for this to be sustainable in the long term, we commissioned a piece of work to develop an adaptive filtering system ( http://www.irus.mimas.ac.uk/news/IRUS_download_data_Final_report.pdf ).
For further information see our position statement on the treatment of robots and unusual usage ( http://www.irus.mimas.ac.uk/news/IRUS-UK_position_statement_robots_and_unusual_usage_v1_0_Nov_2013.pdf ).
Work on filtering robots is ongoing.
Different repository usage statistics packages produce data for different purposes. For example, IRStats provides information on what is downloaded from a repository and who is doing the downloads whereas Google Analytics aims to present a picture of visitor traffic. Each package will have a different set of criteria as to how they treat accesses by robots and “double clicks” and hence are likely to give different figures for total downloads.
IRUS-UK provides usage statistics on items downloaded from participating repositories in accordance with COUNTER guidelines ( http://www.projectcounter.org/ ). The data provided by IRUS-UK are, therefore, comparable across all participating repositories.
We have an initial API available. Please contact our helpdesk email@example.com if you wish to explore its use.
We are a community resource and welcome your comments and suggestions at any time. Please get in touch with our helpdesk at firstname.lastname@example.org. A few weeks after you join we'll send you a survey asking for your views, and any ideas you have for how we can develop the service. We also have an email list for participants (email@example.com).