Hydra at OR2011

Thank you Building the Hydra together Enhancing Repository Provision through Multi-Institution Collaboration Isolated institutions alone in the repository wilderness Hull, Virginia, Stanford Each looking to manage and share digital content They met in the town of Fedora (now twinned with DSpace across the river) Brought together by the Grand Vizier, Thorny Staples, then of Fedora Commons Identified a common aim A reusable framework for multipurpose, multifunction, multi‐institutional repository‐enabled solutions. Hydra wiki - https://wiki.duraspace.org/display/hydra/ Hydra website - http://projecthydra.org A 3-year quest, initially, started in September 2008 Each partner working together towards their own view(s) of the Hydra built on a common foundation No single institution can resource the development of a full range of digitalcontent management solutions on its own, …yet each needs the flexibility to tailor solutions to local demands and workflows. No single system can provide the full range of repository‐based solutions for a given institution’s needs, …yet sustainable solutions require a common repository infrastructure One body, many heads Provisions None, other than what we could bring ourselves MediaShelf Make it easy for others to join the quest Safety in numbers Each can bring their own insights and capabilities Multiple routes to getting involved Not the first to make this journey Our journey has passed by other repository environments Pools of Solomon © The Fitzwilliam Museum. Some strong, some not so stable Many using up lots of resource Seeking clarity from a pooled, common approach Three tools crafted to guide our way Philosophy and governance Technical framework Project infrastructure Other presentations at OR Hydra 24x7 (case studies and developer practice) - Friday, 3:30pm, Room 202 Hydra Framework: Open Source Collaboration in Action - Friday, 4:45pm, Room 202 Philosophy and governance Ease repository interaction through Hydra head with relevant functionality Address a wide range of digital content use cases Ensure sustainability through wide adoption Initial quest started from town of Fedora ... but outcomes could inform quests from other starting points Hydra Steering University of Hull University of Virginia Stanford University DuraSpace Hydra Partners University of Notre Dame Northwestern University Hydra Adopters: Indiana University Glasgow Caledonian University UIUC Hydra Design * Define Functional Objectives & supporting, high-level technical objectives * (Shape and) Fund work * Define conceptual models * Define Data Models & Content Models, providing samples * Provide Sample Data * Share design patterns & Management techniques * UI Design & Spec * End-user Documentation * End-user Training * Maintain consistency of User Experience * Quality Assurance Hydra Developer * Define Technical Architecture * Coordinate development of common functionality * Implement Data & Content Models * Define & Enforce Development Practices * Code Development * Integration & Release * Developer & Deployment Documentation * Developer & Sys Admin Training Hydra Partners are individuals, institutions, corporations or other groups that have committed to contributing to the Hydra community; they not only use the Hydra technical framework, but also add to it in at least one of many ways: code, analysis, design, support, funding, or other resources. Hydra Partners collectively advance the project and the community for the benefit of all participants. Technical framework to be continued... Data model Technical stack Keep it simple Except spudnuts and curry A baseline from which others can develop Model for common metadata Model for generic simple content Model for static images Model for JPEG2000 images Model for parents Model for sets Don't call it a content model! Atomistic v. compound modelling Fedora c-modelling Hydra Ruby modelling Code available via GitHub Active contributor/Hydra developer community Reference implementation based on Ruby on Rails Hydra GitHub - https://github.com/projecthydra/ Ohloh analysis 25 regular contributors in past 12 months Contributions amount to over $7.5 million worth of effort Top 2% of current open source teams Why Ruby? Rapid application Testable environment MVC model supports well-structured approach Hydra provides a core basis upon which others can build (travel?), assured that they are developing in a way that others find useful in their own environments. Hydra provides a data model that can be used by others, avoiding the need to establish individual models on each occasion. Hydra continues to provide software that others can, and have, used to address local needs, and allowing them to focus on these needs as a priority over the underlying infrastructure. The partners are guided by the governance that will allow them to further contribute at the appropriate level or area of interest. Hydra is informed by a community of users that can provide mutual support in both development and use of the repository solutions that emerge. Legal partnership Consortium agreement Code licensing (Apache) We have gone far because we have travelled together We have caught glimpses of the Hydra on our journey Many have been mirages We now have a good sight of the Hydra Many have seen it in their own way But the quest goes on And Partners are continuing to work together and principles MediaShelf Rock and Roll Hall of Fame 15 heads either done or in progress Video repository and head set up in 4-6 weeks at Notre Dame from scratch Doing the quest because we want to starting with community The next 12 months Follow-up with known adopters of the software Formalise partnership model Quarterly meetings Promote developer infrastructure Roll out new heads into production Hull Institutional Repository Hydra head Notre Dame Atrium exhibition Hydra head University of Virginia open access Hydra head Northwestern image cropping Hydra head Stanford Everyday Electronic Materials (EEMs) Hydra head Stanford ETD Hydra head Stanford SALT Hydra head