One Body, Many Heads for Repository-Powered Digital Content Applications Hydra Europe Symposium, Trinity College, Dublin, 7 th April 2014 Chris Awre Head.

One Body, Many Heads for Repository-Powered

Digital Content Applications

Hydra Europe Symposium, Trinity College, Dublin, 7th April 2014

Chris AwreHead of Information ManagementLibrary and Learning Innovation

University of Hull(with thanks to Tom Cramer for some of the

slides)

Hydra• A collaborative project between:

– University of Hull– University of Virginia– Stanford University– Fedora Commons/DuraSpace– MediaShelf LLC

• Aim to work towards an open source reusable framework for multipurpose, multifunction, multi-institutional repository-enabled solutions

• Timeframe - 2008-11 (but now extended indefinitely)

Why?

• All were, and are, Fedora users• Fedora can be complex in enabling its

flexibility• How can the richness of the Fedora system be enabled through simpler interfaces and interactions?

• Hydra has sought to address this, and has done so

successfully• Enabling powerful use of Fedora’s

capabilities through lightweight tools• Principles can also be applied to other

repository environments, e.g., UC San Diego

Multipurpose, multifunction, multi-institutional approach

• A repository should be an enabler, not a constraint

• A repository should be usable at different stages in the lifecycle of the content

• A repository should be capable of providing, or integrating, functionality to suit the management needs of the content

• A repository should not be a silo within one institution (or one part of one institution)

Fundamental Assumption #1No 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

Hydra

• A robust repository fronted by feature-rich, tailored applications and workflows (“heads”) • One body, many heads

• Collaboratively built “solution bundles” that can be adapted and modified to suit local needs.

• A community of developers and adopters extending and enhancing the core

HydraHydra

http://projecthydra.org

Hydra is a repository solution

• Hydra has been implemented as a flexible repository solution, to meet a variety of needs• Hydra has demonstrated that it can be used for a variety of use cases• Hydra is in use on both sides of the Atlantic• Solution bundles have been developed, and others are planned

ScholarSphere

Avalon

Hydramata

Hydra use cases

• Institutional repository• Images• Audiovisual• Datasets• Geodata• Archives and digital preservation• Exhibits• Workflow management / repository administration

Repository-Powered ApproachETDs

(Theses)

Books, Article

s

Images

Audio-Visual

Research Data

Maps & GIS

Docu-ments

Digital Repository

Scalable, Robust, Shared Management

and Preservation Services

Hydra is a community

• Open source projects without a community risk withering away• Hydra started as a collaborative community, and the benefit of this has guided the project throughout• Everyone is encouraged to contribute what they can• Communities within a community• Managers• Developers• Archivists

• Training is key to facilitating engagement

“If you want to go fast, go alone. If you want to go far, go together”

(African proverb)

Hydra partners and users

OR09 OR10 OR11 OR12 OR130

5

10

15

20

25

30

OR = Open Repositories Conference

Hydra is a technical framework

• Hydra applications are made up from a collection of components• These can be adapted and developed to suit

local requirements• All of them can be used, or some of them

• Hydra software enables solutions to be created over Fedora• Community collaboration on common solutions• Collaborative and interactive component management

CRUD in Repositories

CRUD in Repositories

CRUD in Repositories

http://github.com/projecthydra

Hydra is open source software

• Hydra is available under the Apache 2 licence• Code contributions are made under a Code Licensing Agreement• Individual and corporate

• Akin to ‘community source’ approach• Open source software developed on a broad basis, not individually

• Mechanism in place for accepting component contributions

Philosophies

• Building a framework, not an application (variation is part of the plan)

• Opinionated software• Invest time & resources into

collaborative community (face time!)• Trainings & workshops• Openness, transparency (code, designs,

discussions)• Commit to contributing back to core• Design for re-use

Eight strategic priorities

1. Develop solution bundles2. Develop turnkey applications3. Grow the Hydra vendor ecosystem4. Codify a scalable training framework

to fuel community growth5. Develop a documentation framework6. Ensure the technical framework

allows code sharing7. Refresh and intensify the community

ties8. Marketing and communication for

expansion

http://projecthydra.org

http://wiki.duraspace.org/display/hydra