Outline timetable
The timetable below is indicative only and shows how the first versions of Hydra, intended for use by the partners - not for public release - might develop. Public versions of the software will probably be released in stages, some time behind their adoption by the project partners.
2009
9 January 2009: Specification of core Hydra client ![]()
30 January 2009: Set of design mock-up pages complete ![]()
April 2009:
A 'pre-alpha' demonstrator is up and running
which shows proof-of-concept for the proposed Hydra technology stack. In the next months this will be expanded into a Fedora 3.2 Hydra client which copes with:
- creation, editing, admin, access support
- management of sets (collections) and display
- rich search (Blacklight)
- temporary AuthZ using Ruby functions
- specific support for Electronic Theses & Dissertations (but not just that)
- range of tested content models with SDefs/SDeps
- must create sustainable objects
18-21 May OR09 conference: presentations about Hydra ![]()
- public launch of this wiki space

May 2009 Blacklight available for testing with Hydra objects in partners ![]()
June/July 2009 First code available to public?
July/August 2009: Production ready system available to partners for new academic year for the ETD Hydra head and possibly simple objects
- delayed for a number of reasons including a fairly major change to parts of the Hydra spec and awaiting security components - now estimated late fall.
September 2009 Proof-of-concept demonstration site available for search and discovery interface ![]()
- this is Hull's take on what it might look like; the eventual interface provided 'out-of-the-box' will be configurable in a fairly straightforward fashion
2010/2011
more detail will be added to this section nearer the time
Q4 2009 / Q1 2010 First public release?
Configurable end-to-end workflows
Personal repository space
- support for rollback
- support for sharing/co-ownership
- support for multiple, simultaneous publish
- support for multiple user profiles (same person in multiple roles, projects...) and proxy users
Automated support for records management and digital preservation