Overview of content related to 'video' http://www.ariadne.ac.uk/taxonomy/term/171/all?article-type=&term=&organisation=&project=&author=chris%20awre&issue= RSS feed with Ariadne content related to specified tag en Hydra UK: Flexible Repository Solutions to Meet Varied Needs http://www.ariadne.ac.uk/issue70/hydra-2012-11-rpt <div class="field field-type-text field-field-teaser-article"> <div class="field-items"> <div class="field-item odd"> <p><a href="/issue70/hydra-2012-11-rpt#author1">Chris Awre</a> reports on the Hydra UK event held on 22 November 2012 at the Library of the London School of Economics.</p> </div> </div> </div> <p>Hydra, as described in the opening presentation of this event, is a project initiated in 2008 by the University of Hull, Stanford University, University of Virginia, and DuraSpace to work towards a reusable framework for multi-purpose, multi-functional, multi-institutional repository-enabled solutions for the management of digital content collections [<a href="#1">1</a>]. An initial timeframe for the project of three years had seen all founding institutional partners successfully implement a repository demonstrating these characteristics.&nbsp; Key to the aims of the project has always been to generate wider interest outside the partners to foster not only sustainability in the technology, but also sustainability of the community around this open source development.&nbsp; Hydra has been disseminated through a range of events, particularly through the international Open Repositories conferences [<a href="#2">2</a>], but the sphere of interest in Hydra has now stimulated the holding of specific events in different countries: Hydra UK is one of them.</p> <p>The Hydra UK event was held on 22 November 2012, kindly hosted by the Library at the London School of Economics.&nbsp; Representatives from institutions across the UK, but also Ireland, Austria and Switzerland, came together to learn about the Hydra Project, and to discuss how Hydra might serve their digital content collection management needs.&nbsp; 29 delegates from 21 institutions were present, representing mostly universities but also the archive, museum and commercial sectors.&nbsp; Five presentations were given on Hydra, focusing on the practical experience of using this framework and how it fits into overall system architectures, and time was also deliberately given over to discussion of more specific topics of interest and to allow delegates the opportunity to voice their requirements.&nbsp; The presentations were:</p> <ul> <li>Introduction to Hydra</li> <li>Hydra @ Hull</li> <li>Hydra @ Glasgow Caledonian University</li> <li>Hydra @ LSE</li> <li>Hydra @ Oxford</li> </ul> <h2 id="Introduction_to_Hydra">Introduction to Hydra</h2> <p>Chris Awre from the University of Hull gave the opening presentation.&nbsp; The starting basis for Hydra was mutual recognition by all the founding partners that a repository should be an enabler for managing digital content collections, not a constraint or simply a silo of content.&nbsp; Digital repositories have been put forward and applied as a potential solution for a variety of use cases over the years, and been used at different stages of a content lifecycle.&nbsp;</p> <p style="text-align: center; "><img alt="LSE Library (Photo courtesy of Simon Lamb, University of Hull.)" src="http://ariadne-media.ukoln.info/grfx/img/issue70-hydra-2012-11-rpt/figure1-hydra-rpt-lse-library.jpg" style="width: 178px; height: 178px;" title="LSE Library (Photo courtesy of Simon Lamb, University of Hull.)" /></p> <p style="text-align: center; "><strong>Figure 1: LSE Library</strong><br /><small>(Photo courtesy of Simon Lamb, University of Hull.)</small></p> <p>To avoid producing a landscape of multiple repositories all having to be managed to cover these use cases, the Hydra Project sought to identify a way in which one repository solution could be applied flexibly to meet the requirements of different use cases. The idea of a single repository with multiple points of interaction came into being – Hydra – and the concept of individual Hydra ‘head’ solutions.</p> <p>The Hydra Project is informed by two main principles:</p> <ul> <li>No single system can provide the full range of repository-based solutions for a given institution’s needs,<br />o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; …yet sustainable solutions require a common repository infrastructure.</li> <li>No single institution can resource the development of a full range of solutions on its own,<br />o&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; …yet each needs the flexibility to tailor solutions to local demands and workflows.</li> </ul> <p>The Hydra Project has sought to provide the common infrastructure upon which flexible solutions can be built, and shared.</p> <p>The recognition that no single institution can achieve everything it might want for its repository has influenced the project from the start. &nbsp;To quote an African proverb, ‘If you want to go fast go alone, if you want to go far, go together’. Working together has been vital.&nbsp; To organise this interaction, Hydra has structured itself through three interleaving sub-communities, the Steering Group, the Partners and Developers, as shown by Figure 2.</p> <p style="text-align: center; "><img alt="Figure 2: Hydra community structure" src="http://ariadne-media.ukoln.info/grfx/img/issue70-hydra-2012-11-rpt/hydra-community-structure-v4.jpg" style="width: 661px; height: 506px;" title="Figure 2: Hydra community structure" /></p> <p style="text-align: center; "><strong>Figure 2: Hydra community structure</strong></p> <!-- <p style="text-align: center; "><img alt="Figure 2: Hydra community structure" src="http://ariadne-media.ukoln.info/grfx/img/issue70-hydra-2012-11-rpt/figure2-hydra-community-structure.jpg" style="width: 640px; height: 490px;" title="Figure 2: Hydra community structure"></p><p style="text-align: center; "><strong>Figure 2: Hydra community structure</strong></p> --><!-- <p style="text-align: center; "><img alt="Figure 2: Hydra community structure" src="http://ariadne-media.ukoln.info/grfx/img/issue70-hydra-2012-11-rpt/figure2-hydra-community-structure.jpg" style="width: 640px; height: 490px;" title="Figure 2: Hydra community structure"></p><p style="text-align: center; "><strong>Figure 2: Hydra community structure</strong></p> --><p>The concept of a Hydra Partner has emerged from this model of actively working together, and the project has a Memorandum of Understanding (MoU) process for any institution wishing to have its use of, and contribution and commitment to Hydra recognised.&nbsp; Starting with the original four partners in 2008, Hydra now has 11 partners, with two more in the process of joining.&nbsp; All have made valuable contributions and helped to make Hydra better.&nbsp; Hydra partnership is not the only route to involvement, though, and there are many in the Hydra developer community who are adopters of the software, but who have not reached a stage where partnership is appropriate.</p> <p>The technical implementation of Hydra was supported through early involvement in the project by MediaShelf, a commercial technical consultancy focused on repository solutions.&nbsp; All Hydra software is, though, open source, available under the Apache 2.0 licence, and all software code contributions are managed in this way.&nbsp; The technical implementation is based on a set of core principles that describe how content objects should be structured within the repository, and with an understanding that different content types can be managed using different workflows.&nbsp; Following these principles, Hydra could be implemented in a variety of ways: the technical direction taken by the project is simply the one that suited the partners at the time.</p> <p>Hydra as currently implemented is built on existing open source components, and the project partners are committed to supporting these over time:</p> <ul> <li>Fedora: one of the digital repository systems maintained through DuraSpace [<a href="#3">3</a>]</li> <li>Apache Solr: powerful indexing software now being used in a variety of discovery solutions [<a href="#4">4</a>]</li> <li>Blacklight: a next-generation discovery interface, which has its own community around it [<a href="#5">5</a>]</li> <li>Hydra plugin: a collection of components that facilitate workflow in managing digital content [<a href="#6">6</a>]</li> <li>Solrizer: a component that indexes Fedora-held content into a Solr index</li> </ul> <p>These components are arranged in the architecture shown in Figure 3.</p> <p style="text-align: center; "><img alt="Figure 3: Hydra architecture" src="http://ariadne-media.ukoln.info/grfx/img/issue70-hydra-2012-11-rpt/figure3-hydra-architecture-v4.jpg" style="width: 543px; height: 258px;" title="Figure 3: Hydra architecture" /></p> <p style="text-align: center; "><strong>Figure 3: Hydra architecture</strong></p> <!-- <p style="text-align: center; "><img alt="Hydra architecture" src="http://ariadne-media.ukoln.info/grfx/img/issue70-hydra-2012-11-rpt/architecture.png" style="width: 547px; height: 262px;" title="Hydra architecture"></p><p style="text-align: center; "><strong>Hydra architecture</strong></p> --><!-- <p style="text-align: center; "><img alt="Hydra architecture" src="http://ariadne-media.ukoln.info/grfx/img/issue70-hydra-2012-11-rpt/architecture.png" style="width: 547px; height: 262px;" title="Hydra architecture"></p><p style="text-align: center; "><strong>Hydra architecture</strong></p> --><p>A common feature of the last three components in the list above is the use of Ruby on Rails as the coding language and its ability to package up functionality in discrete ‘gems’.&nbsp; This was consciously chosen for Hydra because of its agile programming capabilities, its use of the MVC (Model–View–Controller) structure, and its testing infrastructure.&nbsp; The choice has been validated on a number of occasions as Hydra has developed.&nbsp; However, it was noted that other coding languages and systems could be used to implement Hydra where appropriate.&nbsp; This applies to all the main components, even Fedora.&nbsp; Whilst a powerful and flexible repository solution in its own right, Fedora has proved to be complex to use: Hydra has sought in part to tap this capability through simpler interfaces and interactions.</p> <p></p><p><a href="http://www.ariadne.ac.uk/issue70/hydra-2012-11-rpt" target="_blank">read more</a></p> issue70 event report chris awre bbc bodleian libraries california digital library duraspace glasgow caledonian university jisc london school of economics sakai stanford university university of hull university of oxford university of virginia hydra jisc information environment remap project apache api archives authentication cataloguing collection development content management data data management data set digital archive digital library digital preservation digital repositories dissemination eprints fedora commons framework google maps infrastructure institutional repository licence metadata multimedia open source preservation repositories research ruby search technology sharepoint software solr streaming video vle Thu, 13 Dec 2012 19:24:07 +0000 lisrw 2411 at http://www.ariadne.ac.uk