Italics are comments from the discussion at the September Strategic meeting
- in progress - Complete
Strategy 1: Develop A Full Suite of Solution Bundles
By OR13, Hydra will have catalyzed work beginning on a DSpace-equivalent Hydra head.
As at early April a number of Hydra partners are being approached by DSpace users seeking to know more about Hydra and how it might be a migration path for them. UVA, ND with others are speccing an IR/DR solution for themeselves that would address this point. More details here:
IR Solution Bundle Requirements Breakout
OR13 emphasised this interest
By OR14, a DSpace-equivalent Hydra head will be available to the community.
What are the intermediate steps to get there? Do we need to accelerate the process?
By end of 2013, Blacklight / Hydra users will have a robust & polished exhibits tool in Atrium (Omeka-equivalent)
Continuing needs and requirements gathering; date is unrealistic.
By end of 2013, Blacklight / Hydra users will have a demonstrated, replicable approach to presenting Finding Aids and archival collections (XTF-equivalent)
Date very optimistic. Recipes are out there but we haven't pulled them together into a solution. Yale has just posted a job for doing this process. Discussing with ArchiveSphere about collaboration.
By end of 2013, there will be viable heads / solution bundles for time-based media (Avalon), images (DIL), and administration (Argo).
Avalon 1.0.0 released May 2013. DIL code is not yet shared. DUL (Duke) may be a better admin than Argo which is too tied to Stanford. WGBH DAM is another candidate here.
Strategy 2: Develop Turnkey / Hosted Solutions
By end of 2013, Hydra will have fostered the beginnings of development of both hosted and turnkey Hydra solutions
Sufia. Avalon. (Turnkey is "install, minimal config, go!")
By OR14, there will be a Hydra turnkey application available to the community via at least one provider.
By OR14, there will be a Hydra hosted solution available to the community via at least one provider.
Maybe not OR14. AP Trust is looking at the possibility? DuraSpace? DCE?
Strategy 3: Grow the Vendor Ecosystem & Define the Vendor Community Structure
By end of 2013, Hydra will have X (x=3?) vendors in the ecosystem, performing consulting, training, integration, custom development, SAAS...
No way! But this would help with procurement processes.
By end of 2013, Hydra will have a defined structure with vendors that is symbiotic with the overall community.
Need the vendors first! A good product (like a DSpace equivlent) would be a lure. Should we have materials for trying to get vendors involved?
Strategy 4: Training Framework
By end of 2013, Hydra will have a training framework that includes a standard, shared Hydra curriculum, a method for offering onsite trainings at new adopters looking to launch quickly, and a way to deliver training multiple times a year at multiple locations (internationally).
Great progress here. Standard, high quality curriculum being delivered by DCE and also Hydra folks who have been through a TA stage.
Strategy 5: Documentation Framework
By end of 2013, Hydra will have a documentation framework that will define targeted audiences, information needs, initial development / infill of any gaps, and mechanisms (including resourcing strategies) to maintain the project's documentation base.
Hydra gem is part of this together with the promised documented upgrade path. Drew at WGBH is bringing a lot together.
Strategy 6: Technical Framework
By end of 2013, Hydra will have demonstrated robust code-sharing and reuse across heads and sites, and a technical core that facilitates this.
By end of 2013, Hydra will have investigated and framed its needs to provide maintenance support and continuity for deployed Hydra software (heads, gems), and identified approaches for meeting these support needs.
Hydra gem and the developing gemset is part of this. What else do we need?
By OR14, Hydra will have tested and adopted clear, proven methods for addressing needs for stable, supported software.
By LDCX^4, we will have CLA's on file from all contributors
By OR13, Hydra will have an updated and more polished articulation of its community principles, values, methods and benefits--the recipe that has defined the "hydra way" to date, and much of the project's success.
Added to agenda for June partners' meeting. Deferred to September with a suggestion that SG put up a "straw man" for discussion prior to that.
By OR13, Hydra will have more clearly defined the balance of roles between the Steering and Partners groups, promoting engagement, transparency, effectiveness and efficiency in community governance and administration
New definition of responsibilitiea approved at June 2013 meeting. Wiki and website changed to reflect these.
At OR13, Hydra will have a Hydra UG meeting as part of the official conference track.
Tried for it at OR13 but somehow it wasn't quite clear.
By end of 2013, Hydra will have established a framework for fostering & working with Solution Bundle communities.
eg: Sufia, Avalon, DIL, Hydra DAM. These will be sub-communities - need to be part of, or at least complementary with, the larger Hydra community. We need marketing soulution bundles.
By end of 2013, Hydra will have established a framework for fostering & structuring its relationship to vendors; this possibly includes registered service providers, endorsed events and products, etc.
Redundant until we get the vendors.
By end of 2013, Hydra will have defined an approach for coordinating development and support activities of partners across Europe, North America and Australasia
Summer 2013: European Partners having regular calls to discuss participation in coming conferences and seeding others with publicity materials.
(New 2013-06-27) By the end of 2013 Hydra will have established a mechanism for raising awareness at conferences etc where Hydra is not explicitly represented - eg publicity materials in delegate packs).
Bookmark (similar to OR12 bookmark) being distributed as "Conference Goodies" material for (European) conferences.