Hydramata Project Refresh March 10, 2014Hydramata Project Refresh1
Why are We Here Again? January 22, 2014Hydra Connect 20142
Where We Started March 10, 2014Hydramata Project Refresh3
Our World is Different: Mixed Content and Formats March 10, 2014Hydramata Project Refresh4
Mixed Landscape ETD Statistical Data Image Data Article March 10, 2014Hydramata Project Refresh5 Video
Shifting Needs March 10, 2014Hydramata Project Refresh6
Sustain through Community … DATA CURATION EXPERTS March 10, 2014Hydramata Project Refresh7 Hydramata IndianaNorthwesternDCENotre DameCincinnatiVirginia
Faith and Commitment March 10, 2014Hydramata Project Refresh8
In Sync March 10, 2014Hydramata Project Refresh9
Curate Gem Mixed Architecture March 10, 2014Hydramata Project Refresh10
Why a Name Change? Shared IR: – Are we sharing code or infrastructure? Curate – Mixed reviews as it means something different to everyone – While a large focus, our vision stretches beyond both curation of work and traditional IR March 10, 2014Hydramata Project Refresh11
Our Vision Refreshed Flexible Configurations Modularity Extensibility Wide Format Support Support IR use cases Swappable Viewers, Workflows Other Integrations March 10, 2014Hydramata Project Refresh12
Hydramata A set of separate hydra-based automata, “hydramata”, that can be combined to form a single Hydra Head. Each hydramaton can be mixed and matched with other hydramata to provide wide format support tailored to fit your institutional or digital repository needs. March 10, 2014Hydramata Project Refresh13
Transformation March 10, 2014Hydramata Project Refresh14
March 10, 2014Hydramata Project Refresh15
Renewed Focus Links to institutional priorities and schedules Balance between Sprint and Release Planning More concrete release timelines and roadmap March 10, 2014Hydramata Project Refresh16
Release Schedule April 15: Red Green Refactor July 1: Transformation and Scale November 1: TBD (Video, Exhibits, etc?) March 10, 2014Hydramata Project Refresh17
April Release: Red Green Refactor Prepare for Refactoring Create Stable Release Candidate moving us form Red to Green Before refactoring we need our code clean and stable with an improved user interface, expanded testing, improved metadata, and free of major bugs. Therefore, this release will be focused on creating a stable release candidate that moves us from Red to Green to be ready for refactoring in the next release. March 10, 2014Hydramata Project Refresh18
July Release: Transformation and Scale Begin transforming and refactoring our single gem architecture into one that better fits our vision of a pluggable framework, and build in more scale of managing content. Where to further focus is being prioritized and discussed among the PD’s and PO’s. March 10, 2014Hydramata Project Refresh19
Institutional Release Focus April 15 – ND - Production Beta Update – UC - Baseline for Early Adopters Release – IU - First sandbox deployment for library staff – UVa - Test and analysis for further work July 1 – NU – Research Scholarship Release 0.5 – ND – 3 rd Beta Release – Uva – Beta for Research Data – UC – Second Beta Release – IU Piolot Deployment for Research Data November 1 – Uva – Expanded beta for Research Data – NU – 1.0 Production Release – ND – Full Campus Launch – IU – Expanded Data and Early Adopter Pilot – UC – Production Release March 10, 2014Hydramata Project Refresh20
Other Changes Increased testing – Welcome to Chris DeLuca who will act as the QA Lead starting March 17th! March 10, 2014Hydramata Project Refresh21
Questions ? March 10, 2014Hydramata Project Refresh22