OR2013 Hydra for Managers
Following a brief clarification on the need for Hydra information tailored for current and prospective managers, we received the following calls for information. The format is a synthesis of the information Karen and I received but then organized for a wider Hydra partner discussion.
- Management Issues
- Framing the problem – Chris A indicates this is needed in order to show how Hydra can address needs.
- In addition to information for managers, different types of product owners, service providers, subject matter experts are in need information and they could be enrolled to contribute. - Claire Stewart
- We need something that describes how Hydra meets needs of core services for Libraries and how that complements core services of IT departments.
- What kind of resources & skills do we need?
- We want it all, how do we get started?
- How does Hydra facilitate the use of Fedora? Institutions have experience of Fedora being hard and resource intensive – how does Hydra address that?
- What is the balance of investment vs. return?
- How does this impact risk?
- What is the value proposition vs. Dspace or Islandora? What does it offer that is distinct from the others?
- Technology
- Hydra Core Documentation
- What do you get out of the box?
- What are the components and what purpose do they serve?
- How well does it inter operate or integrate with other systems and databases?
- Matrix of Heads
- Core Focus
- Basic functionality
- How they complement or interrelate with other heads
- What skills are needed to deploy?
- How much time is needed to configure & deploy?
- Minimum hardware requirements
- How/Where to start?
- "How do I leverage the best code of all the code?"
- Matrix of Gems
- Purpose
- Basic Functionality
- Example/Source Heads
- Hydra Core Documentation
- Dspace
- Some interest expressed in Hydra over Dspace
- What do we leave behind if we migrate away from Dspace
- Dspace has served us well but…
- Interested in more customizations
- Desire many heads with one body