CINXE.COM

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head><script type="text/javascript" src="https://web-static.archive.org/_static/js/bundle-playback.js?v=7YQSqjSh" charset="utf-8"></script> <script type="text/javascript" src="https://web-static.archive.org/_static/js/wombat.js?v=txqj7nKC" charset="utf-8"></script> <script>window.RufflePlayer=window.RufflePlayer||{};window.RufflePlayer.config={"autoplay":"on","unmuteOverlay":"hidden"};</script> <script type="text/javascript" src="https://web-static.archive.org/_static/js/ruffle/ruffle.js"></script> <script type="text/javascript"> __wm.init("https://web.archive.org/web"); __wm.wombat("http://www.eprints.org/news/features/worlds_best_practice.php","20130430191126","https://web.archive.org/","web","https://web-static.archive.org/_static/", "1367349086"); </script> <link rel="stylesheet" type="text/css" href="https://web-static.archive.org/_static/css/banner-styles.css?v=p7PEIJWi" /> <link rel="stylesheet" type="text/css" href="https://web-static.archive.org/_static/css/iconochive.css?v=3PDvdIFv" />  <title>EPrints: "World's Best Practice"</title><style type="text/css"> @import url(/web/20130430191126cs_/http://www.eprints.org/style/eprints.css); @import url(/web/20130430191126cs_/http://www.eprints.org/style/header.css); </style> </head> <body><div id="ep_org_header"> <div style="float: left">  <a id="ep_org_logo" href="https://web.archive.org/web/20130430191126/http://www.eprints.org/" title="EPrints.org Network"><span style="display: none">EPrints.org</span></a> </div> <div style="float: left; margin-left: 20px"> <ul id="ep_org_header_menu"> <li><a href="https://web.archive.org/web/20130430191126/http://www.eprints.org/software/" title="Get EPrints repository software">Software</a></li><li><a href="https://web.archive.org/web/20130430191126/http://www.eprints.org/services/" title="Get professional support from EPrints Services">Services</a></li><li><a href="https://web.archive.org/web/20130430191126/http://www.eprints.org/openaccess/" title="Open Access tools and advocacy">About Open Access</a></li> </ul> </div> <div style="float: right">  <a href="https://web.archive.org/web/20130430191126/https://plus.google.com/112894606791267353638?prsrc=3" style="text-decoration:none;"><img src="https://web.archive.org/web/20130430191126im_/https://ssl.gstatic.com/images/icons/gplus-16.png" alt="" style="border:0;width:16px;height:16px;"/></a>    <form id="cref_iframe" action="https://web.archive.org/web/20130430191126/http://www.eprints.org/search/"> <input type="hidden" name="cref" value="http://www.eprints.org/search/cref_cse.xml"/> <input type="hidden" name="cof" value="FORID:9"/> <input type="text" name="q" size="25" class="google_cse_watermark" onfocus="this.style.backgroundImage='none'"/> <input type="submit" name="sa" value="Search" id="cref_submit"/> </form>   </div> <div style="clear: both"></div> </div> <h2>EPrints: "World's Best Practice for an institution commencing an institutional repository"</h2> <p><i>Steve Hitchcock, <a href="/web/20130430191126/http://www.eprints.org/community/">EPrints Community Manager</a>, 23rd November 2005</i></p> <p>Start any institutional repository (IR) with EPrints, recommends Professor Arthur Sale of the University of Tasmania (UTas), Australia. In a paper presented to institutions in New Zealand, Sale reports on the widely-used software packages for building IRs, favouring EPrints because of speed of set-up, ease of use, and minimal costs for running and maintaining a server. "It just works. No fuss. No maintenance. It's just too easy", Sale remarked in correspondence.</p> <p>Although others advocate more complex ICT-based approaches to creating an IR, Sale warns that this will involve more significant manpower costs, and may be unjustifiable. "Can people fly flags and ring bells over conquering Everest when it turns out to be Highgate Hill?"</p> <p>It is better to get up and running in a week or two, Sale argues, noting that: "All of the OAI-compliant software has the ability to do bulk transfers of the databases, should you wish to change in the future."</p> <p>Not that such a scenario is likely. EPrints, the original IR software in 2000, has an active and growing developer team, and with its recently launched Services (<a href="https://web.archive.org/web/20130430191126/http://www.eprints.org/services/">http://www.eprints.org/services/</a>) and Community (<a href="https://web.archive.org/web/20130430191126/http://www.eprints.org/community/">http://www.eprints.org/community/</a>) support is ready to respond quickly to the needs of users.</p> <p>Sale is not a passive observer of IR developments. Having been responsible for setting up the University of Tasmania's EPrints-based IR, he has written software add-ons, available for download, to provide authors with feedback on the usage of their papers in the IR.</p> <div class="pullquote_right"> "EPrints is quick to install, easy to configure, and needs minimal maintenance. Once installed, it simply works without fuss. There simply isn't a contest." </div> <h3>Software choice</h3> <p>From Sale, Arthur (2005) The Key Things to Know, University of Tasmania Eprints Repository, 16 November <a href="https://web.archive.org/web/20130430191126/http://eprints.comp.utas.edu.au:81/archive/00000223/">http://eprints.comp.utas.edu.au:81/archive/00000223/</a> </p> <blockquote> This is a no-contest decision when you look at it sensibly. There are really only two widely used packages: EPrints and DSpace. Fedora also enters the picture because ARROW has chosen to implement a sample repository based on it; otherwise it would be below the horizon of packages in common use. EPrints, DSpace and Fedora are all open source free software. </blockquote> <blockquote> All comply with OAI-PMH protocols; all are supported by a source university or two (EPrints in the UK by Southampton University, DSpace by MIT in the USA, and Fedora by the University of Virginia & Cornell University in the USA). The cost of the ARROW Fedora adaptation has not been announced, but it involves a commercial front-end from VLTS so there may be some cost. All of these three software solutions are viable. </blockquote> <div class="pullquote_right"> "Institutions that want to develop other uses of their repository software, and which have the funds to devote to significant ICT support of complex packages should be prepared for more significant manpower costs." </div> <blockquote> <i>World’s Best Practice for an institution commencing an institutional repository is EPrints</i>. The software is quick to install, easy to configure, and needs minimal maintenance. Once installed, it simply works without fuss. Over a year, no maintenance has been required to the UTas server apart from updates. There simply isn’t a contest. </blockquote> <blockquote> It is quite probable that if you choose an EPrints solution, you will not want to change in the foreseeable future. However, large institutions bigger than any Australian or New Zealand university, or institutions that want to develop other uses of their repository software, and which have the funds to devote to significant ICT support of complex packages, might contemplate DSpace or Fedora solutions. They should be prepared for more significant manpower costs. Both DSpace and Fedora are really <i>digital library</i> packages (not <i>institutional repository</i> packages) and require customization to provide IR (or indeed any) functionality. </blockquote> <blockquote> Regardless, I continue to recommend that the first repository any institution establishes should be an EPrints one as you can be up and running in a week or two. </blockquote> <p> Sale's paper is not just about choosing software. He gives practical advice on all aspects of setting up an IR, including how to seek high-level institutional support, and shows graphically the benefit of an institutionally-backed mandate, based on a Model Deposit Policy that he reproduces, for growing the content of an IR.<br> </p> <div class="pullquote_right"> "Keep the message simple: an IR is in the University's self-interest through increasing its research impact." </div> <p> According to Sale, the top reason for an institution to establish its own IR is increasing research impact, and positioning the institution relative to its competitors.<br> </p> <blockquote> Providing a refereed publication available for open access on the Internet increases the research impact of the publication. Citations are measured to increase by 50% to 250% depending on the discipline as compared with papers in the same journal but not online. It is the principal reason why universities are rapidly moving to establish open access repositories for their research output: it positions them better relative to their competitors. </blockquote> <p>Urging those leading campaigns for IRs to get the senior executive group (Vice-Chancellor, etc) to endorse the setting up of an EPrints archive, Sale provides a shorthand case for gaining their support:</p> <ul> <li>Emphasize the research impact: citations, meeting public accountability standards, knowing what happens to research, and contribution to knowledge dissemination.</li> <li>Emphasize the library getting into supporting the creation of research output.</li> <li>Keep the message simple: an IR is in the University’s self-interest through increasing its research impact.</li> </ul> <p>Sale, Arthur (2005) The Key Things to Know, University of Tasmania Eprints Repository, 16 November <a href="https://web.archive.org/web/20130430191126/http://eprints.comp.utas.edu.au:81/archive/00000223/">http://eprints.comp.utas.edu.au:81/archive/00000223/</a></p> <p><b>See also</b> <p>(this link added 25 September 2006) <p>Wyles, Richard, et al. <a href="https://web.archive.org/web/20130430191126/https://eduforge.org/docman/view.php/131/1062/Repository%20Evaluation%20Document.pdf"> Technical Evaluation of selected Open Source Repository Solutions</a>, Open Access Repositories in New Zealand (OARINZ) project, Christchurch Polytechnic Institute of Technology, v1.3, 13 September 2006 <br>"EPrints is the best candidate for a self-configuring solution for institutions wanting to set up and host their own repository." <p>(these links added 07 June 2006) <p>Stanger, Nigel and McGregor, Graham, <a href="https://web.archive.org/web/20130430191126/http://eprints.otago.ac.nz/274/">Hitting the ground running: building New Zealand抯 first publicly available institutional repository</a>, Discussion Paper 2006/07, Department of Information Science, University of Otago, Dunedin, New Zealand, 09 March 2006 <br>"What is so remarkable about the Otago IR? First, its speed of implementation at minimal cost is certainly worth noting, especially for other institutions that are considering an IR. ... we used the open source GNU EPrints repository building software, because it was widely used, well-supported, inexpensive and would not lock us into specific technologies or vendors" <p>Singh, Sukhdev and Pandita, Naina, <a href="https://web.archive.org/web/20130430191126/http://openmed.nic.in/1108/">Building the open access self-archiving repository for the bio-medical sciences at National Informatics Centre</a>, OpenMED@NIC, 10 November 2005, also in National Convention of Medical Library Association of India, Bangalore, 07-09 November 2005 <br>"EPrints is comparatively mature and easier to install, customize and maintain." <p>Sponsler, Ed, and Van de Velde, Eric F., <a href="https://web.archive.org/web/20130430191126/http://www.arl.org/sparc/pubs/enews/aug01.html#6">Eprints.org Software: A Review</a>, SPARC E-News, August-September 2001 <br>"EPrints is a powerful and inexpensive solution for sharing scholarly works with the world" <p><b>Add your own testimonial</b> using this <a href="https://web.archive.org/web/20130430191126/http://www.eprints.org/community/blog/index.php?/archives/98-Seeking-EPrints-testimonials.html">blog entry</a>. <p>For <b>some additional background</b> to this news story, see <p><a href="https://web.archive.org/web/20130430191126/http://www.eprints.org/community/blog/index.php?/archives/53-IR-software-correcting-some-misunderstandings.html">IR software: correcting some misunderstandings</a>, EPrints Insiders blog, December 2, 2005 <div id="ep_org_footer"> Copyright © 2011-2012 <a href="https://web.archive.org/web/20130430191126/http://www.soton.ac.uk/">University of Southampton, UK</a> </div> </body> </html>