Overview of content related to 'multimedia' http://www.ariadne.ac.uk/taxonomy/term/1197/all?article-type=&term=&organisation=&project=&author=paul%20meehan&issue= RSS feed with Ariadne content related to specified tag en SUSHI: Delivering Major Benefits to JUSP http://www.ariadne.ac.uk/issue70/meehan-et-al <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue70/meehan-et-al#author1">Paul Meehan</a>, <a href="/issue70/meehan-et-al#author2">Paul Needham</a> and <a href="/issue70/meehan-et-al#author3">Ross MacIntyre</a> explain the enormous time and cost benefits in using SUSHI to support rapid gathering of journal usage reports into the JUSP service.</p> </div> </div> </div> <p>A full-scale implementation of the Journal Usage Statistics Portal (JUSP) would not be possible without the automated data harvesting afforded by the Standardized Usage Statistics Harvesting Initiative (SUSHI) protocol. Estimated time savings in excess of 97% compared with manual file handling have allowed JUSP to expand its service to more than 35 publishers and 140 institutions by September 2012. An in-house SUSHI server also allows libraries to download quality-checked data from many publishers via JUSP, removing the need to visit numerous Web sites. The protocol thus affords enormous cost and time benefits for the centralised JUSP service and for all participating institutions. JUSP has also worked closely with many publishers to develop and implement SUSHI services, pioneering work to benefit both the publishers and the UK HE community.</p> <p style="text-align: center; "><img alt="Journal Usage Statistics Portal (JUSP)" src="http://ariadne-media.ukoln.info/grfx/img/issue70-meehan-et-al/jusp-logo.png" style="width: 145px; height: 133px;" title="Journal Usage Statistics Portal (JUSP)" /></p> <h2 id="JUSP:_Background_to_the_Service">JUSP: Background to the Service</h2> <p>The management of journal usage statistics can be an onerous task at the best of times. The introduction of the COUNTER [<a href="#1">1</a>] Code of Practice in 2002 was a major step forward, allowing libraries to collect consistent, audited statistics from publishers. By July 2012, 125 publishers offered the JR1 report, providing the number of successful full-text downloads. In the decade since COUNTER reports became available, analysis of the reports has become increasingly important, with library managers, staff and administrators increasingly forced to examine journal usage to inform and rationalise purchasing and renewal decisions.</p> <p>In 2004, JISC Collections commissioned a report [<a href="#2">2</a>] which concluded that there was a definite demand for a usage statistics portal for the UK HE community; with some sites subscribing to more than 100 publishers, just keeping track of access details and downloading reports was becoming a significant task in itself, much less analysing the figures therein. There followed a report into the feasibility of establishing a ‘Usage Statistics Service’ carried out by Key Perspectives Limited and in 2008 JISC issued an ITT (Invitation To Tender). By early 2009 a prototype service, known as the Journal Usage Statistics Portal (JUSP) had been developed by a consortium including Evidence Base at Birmingham City University, Cranfield University, JISC Collections and Mimas at The University of Manchester; the prototype featured a handful of publishers and three institutions. However, despite a centralised service appearing feasible [<a href="#3">3</a>], the requirement to download and process data in spreadsheet format, and the attendant time taken, still precluded a full-scale implementation across UK HE.</p> <p style="text-align: center; "><img alt="COUNTER" src="http://ariadne-media.ukoln.info/grfx/img/issue70-meehan-et-al/counter-header.png" style="width: 640px; height: 45px;" title="COUNTER" /></p> <p>Release 3 of the COUNTER Code of Practice in 2009 however mandated the use of the newly-introduced Standardized Usage Statistics Harvesting Initiative (SUSHI) protocol [<a href="#4">4</a>], a mechanism for the machine-to-machine transfer of COUNTER-compliant reports; this produced dramatic efficiencies of time and cost in the gathering of data from publishers. The JUSP team began work to implement SUSHI for a range of publishers and expanded the number of institutions. By September 2012, the service had grown significantly, whilst remaining free at point of use, and encompassed 148 participating institutions, and 35 publishers. To date more than 100 million individual points of data have been collected by JUSP, all via SUSHI, a scale that would have been impossible without such a mechanism in place or without massive additional staff costs.</p> <p>JUSP offers much more than basic access to publisher statistics, however; the JUSP Web site [<a href="#5">5</a>] details the numerous reports and analytical tools on offer, together with detailed user guides and support materials. The cornerstone of the service though is undeniably its SUSHI implementation, both in terms of gathering the COUNTER JR1 and JR1a data and - as developed more recently - its own SUSHI server, enabling institutions to re-harvest data into their own library management tools for local analysis.</p> <h2 id="JUSP_Approach_to_SUSHI_Development_and_Implementation">JUSP Approach to SUSHI Development and Implementation</h2> <p>Once the decision was made to scale JUSP into a full service, the development of SUSHI capability became of paramount importance. The team had been able to handle spreadsheets of data on a small scale, but the expected upscale to 100+ institutions and multiple publishers within a short time frame meant that this would very quickly become unmanageable and costly in staff time and effort - constraints that were proving to be a source of worry at many institutions too: while some sites could employ staff whose role revolved around usage stats gathering and analysis, this was not possible at every institution, nor especially straightforward for institutions juggling dozens, if not hundreds, of publisher agreements and deals.</p> <p>Two main issues were immediately apparent in the development of the SUSHI software. Firstly, there was a lack of any standard SUSHI client software that we could use or adapt, and, more worryingly, the lack of SUSHI support at a number of major publishers. While many publishers use an external company or platform such as Atypon, MetaPress or HighWire to collect and provide usage statistics, others had made little or no progress in implementing SUSHI support by late 2009 - where SUSHI servers were in place these were often untested or unused by consumers.</p> <p>An ultimate aim for JUSP was to develop a single piece of software that would seamlessly interact with any available SUSHI repository and download data for checking and loading into JUSP. However, the only client software available by 2009 was written and designed to work in the Windows environment, or used Java, which can be very complex to work with and of which the JUSP team had limited expertise. The challenge therefore became to develop a much simpler set of code using Perl and/or PHP, common and simple programming languages which were much more familiar to the JUSP team.</p> <p></p><p><a href="http://www.ariadne.ac.uk/issue70/meehan-et-al" target="_blank">read more</a></p> issue70 feature article paul meehan paul needham ross macintyre birmingham city university cranfield university elsevier intute jisc jisc collections mimas niso university of manchester university of oxford jusp nesli pirus2 zetoc archives authentication csv data data set database digital library dublin core html identifier interoperability java multimedia openurl passwords perl php portal raptor repositories research shibboleth software standards sushi windows xml Wed, 05 Dec 2012 17:54:19 +0000 lisrw 2396 at http://www.ariadne.ac.uk