Slides from the Getting to the Repository of the Future Workshop held on Wednesday 31st July 2013 at Repository Fringe 2013. The workshop was led by Chris Awre, University of Hull, and Balviar Notay, JISC.
2. Three parts
• What is Hydra – and why?
• State of the Hydrasphere
• Hydra@Hull update
Repository Fringe - Hydra | 2 August 2013 | 2
3. Hydra
Change the way you think about Hull | 7 October 2009 | 2
• A collaborative project between:
– University of Hull
– University of Virginia
– Stanford University
– Fedora Commons/DuraSpace
– MediaShelf LLC
• Unfunded (in itself as a project)
– Activity based on identification of a common need
• Aim to work towards a reusable framework for multipurpose,
multifunction, multi-institutional repository-enabled
solutions
• Timeframe - 2008-11 (but now extended indefinitely)
Text Repository Fringe - Hydra | 2 August 2013 | 3
4. Fundamental Assumption #1
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.
No single institution can resource the development of a full
range of solutions on its own,
…yet each needs the flexibility to tailor
solutions to local demands and workflows.
Fundamental Assumption #2
Repository Fringe - Hydra | 2 August 2013 | 4
6. Hydra software
• Fedora
– All Hydra partners are Fedora users
• Solr
– Very powerful indexing tool, as used by…
• Blacklight
– Prior development at Virginia (and now Stanford/JHU) for
OPAC
– Adaptable to repository content
• Ruby
– Agile development / excellent MVC / good testing tools
• Ruby gems
– ActiveFedora, Opinionated Metadata, Solrizer, etc.
Repository Fringe - Hydra | 2 August 2013 | 6
7. Fedora and Hydra
• Fedora can be complex in enabling its flexibility
• How can the richness of the Fedora system be enabled
through simpler interfaces and interactions?
– The Hydra project has endeavoured to address this, and
has done so successfully
– Not a turnkey, out of the box, solution, but a toolkit that
enables powerful use of Fedora’s capabilities through
lightweight tools
• Principles can also be applied to other repository environments
• Hydra ‘heads’
– Single body of content, many points of access into it
Repository Fringe - Hydra | 2 August 2013 | 7
8. Hydra partners and users
Repository Fringe - Hydra | 2 August 2013 | 8
0
5
10
15
20
25
30
OR09 OR10 OR11 OR12 OR13
OR = Open Repositories Conference
13. One Body, Many Heads…
ETDs
(Theses)
Books,
Articles
Images
Audio-
Visual
Research
Data
Maps
& GIS
Docu-
ments
Scalable, Robust, Shared
Management and
Preservation Services
Repository Fringe - Hydra | 2 August 2013 | 13
14. Four Key Capabilities
1. Support for any kind of record or metadata
2. Object-specific behaviors
– Books, Articles, Images, Music, Video, Manuscripts, etc.
3. Tailored views for domain or discipline-specific materials
4. Easy to augment & over-ride with local modifications
Repository Fringe - Hydra | 2 August 2013 | 14
15. Adapt to the content
UKCoRR – Hydra | 9 November 2012 | 15
16. Hydra@Hull
Committee papers
Theses
Dissertations
Exam papers
Student handbooks
E-prints/journal articles
Audio recordings
Open educational resources
Datasets
University policies, procedures and regulations
Digitised content
Strategy documents
LecturesImages
Books
Repository Fringe - Hydra | 2 August 2013 | 16
17. Hydra@Hull - upgrade
Repository Fringe - Hydra | 2 August 2013 | 17
Based on latest Hydra software, version 6, and Bootstrap design
18. Seven strategic Hydra priorities
1. Develop solution bundles
2. Develop turnkey applications
3. Grow the Hydra vendor ecosystem
4. Codify a scalable training framework to fuel
community growth
5. Develop a documentation framework
6. Ensure the technical framework allows code
sharing
7. Refresh and intensify the community ties
Repository Fringe - Hydra | 2 August 2013 | 18
19. Thank you
Chris Awre – c.awre@hull.ac.uk
Hydra at Hull – http://hydra.hull.ac.uk
Hydra Project – http://projecthydra.org