9 25-12 DuraSpace Hot Topics, Slides, Introduction to Hydra

  • 1,625 views
Uploaded on

“Introduction to Hydra,” presented by Tom Cramer, Chief Technology Strategist, Stanford University Libraries will introduce the capabilities of the Hydra suite of solutions, as well as delve into both …

“Introduction to Hydra,” presented by Tom Cramer, Chief Technology Strategist, Stanford University Libraries will introduce the capabilities of the Hydra suite of solutions, as well as delve into both the technical framework and community frameworks underpinning the project.

Tuesday, September 25, 2012

More in: Education , Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
1,625
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
36
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Hot Topics: The DuraSpace Community Webinar Series Series Three: “Get a Head on Your Repository with Hydra End-to-End Solutions” Curated by Tom CramerSeptember 25, 2012 Hot Topics: DuraSpace Community Webinar Series
  • 2. Using the Webinar Platform• 2-way audio for all participants is muted• We’ll utilize the Chat Window for the Q&A portion or you may use it if you are having technical difficulties• You may type your question here & hit ‘enter’September 25, 2012 Hot Topics: DuraSpace Community Webinar Series
  • 3. Webinar 1: Introduction to Hydra Presented by: Tom Cramer, Chief Technology Strategist at Stanford University LibrariesSeptember 25, 2012 Hot Topics: DuraSpace Community Webinar Series
  • 4. GET A HEAD ON YOUR REPOSITORY Tom Cramer Chief Technology Strategist Stanford University Libraries
  • 5. What Is 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 ➭ If you want to go fast, go alone. If you want to go far, go together.
  • 6. Fundamental Assumption #1 No 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.
  • 7. For Instance… ETD General Purpose Digitization Deposit Institutional Workflow System Repository SystemSimple Complex - Generally a - Heterogeneous - Potentially single PDF file types hundreds of files - Simple, - Simple to type per object prescribed complex objects - Complex, workflow - One- or two-step branching workflow - Streamlined UI workflow - Sophisticated for depositors, - General purpose operator (back reviewers & user interfaces office) interfaces readers
  • 8. Hydra Heads: Emerging Solution Bundles Institutional Repositories University of Hull University of Virginia Penn State University Images Northwestern University (Digital Image Library)
  • 9. Hydra Heads: Emerging Solution Bundles Archives & Special Collections Stanford University University of Virginia Rock & Roll Hall of Fame Media Indiana University Northwestern University Rock & Roll Hall of Fame WGBH
  • 10. Hydra Heads: Emerging Solution Bundles Workflow Management (Digitization, Preservation) Stanford University University of Illinois – Urbana-Champagne Northwestern University Exhibits Notre Dame
  • 11. Hydra Heads: Emerging Solution Bundles ETDs Stanford University University of Virginia Etc. (Small) Data everyone…
  • 12. Fundamental Assumption #2 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.
  • 13. Hydra Philosophy -- Community • An open architecture, with many contributors to a common core • 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 • “If you want to go fast, go alone. If you want to go far, go together.” One body, many heads
  • 14. Community • Conceived & executed as a collaborative, open source effort from the start • Initially a joint development project between Stanford, Univ of Virginia, and Univ of Hull • Close collaboration with DuraSpace / Partnership with MediaShelf, LLC • Complementary strengths and expertise
  • 15. Hydra Partners 12 10 8 6 4 2 0 OR09 OR10 OR11 OR12 OR = Open Repositories Conference
  • 16. University of Virginia, 2008LibDevConX^3, Stanford, 2012: (Hydranauts and Fellow Travelers)
  • 17. Community Hydra Steering Group - small coordinating bodyModel - collaborative roadmapping (tech & community) Currently - DuraSpace - resource coordination - Hull - governance of the "tech core" - MediaShelf and Hydra Framework - Stanford - community mtce. & growth - Virginia Hydra Partners Hydra Developers - shape and direct work - define tech architecture - commission "Heads" - code devleopment - functional requirements - integration & release & specs - UI design & spec Committers - Documentation - Training Contributors - Data & content models Founders - "User groups" Tech. Users- Duraspace - Hull - Stanford - UVa
  • 18. Managing the Community • Founding partners have an MoU governing how the community is managed • Subsequent partners have signed up to this MoU through a partner agreement addendum • Requirements of Partners • Use the software • Contribute to the project • Collaborate with other partners • Commit to collectively advancing the project and the community • Funding / payment is NOT required
  • 19. Hydra Partners… …are individuals, institutions, corporations or other groups that have committed to contributing to the Hydra community; they not only use the Hydra technical framework, but also add to it in at least one of many ways: code, analysis, design, support, funding, or other resources. Hydra Partners collectively advance the project and the community for the benefit of all participants.https://wiki.duraspace.org/display/hydra/Hydra+Community+Framework
  • 20. Code Licensing • All Hydra code is available under Apache License, Version 2.0 • All code commitments are being managed through Contributor License Agreements • Individual – so each developer is clear about what they are contributing • Corporate – so each institution is clear about what it is contributing • Code contributors maintain ownership of their IP • And grant a non-exclusive license to the project and its users
  • 21. Sustainability No animals were harmed in the making of this film.
  • 22. Job Postings
  • 23. If You Want To Go Fast… …go alone. …use Hydra?• Notre Dame deployed a video cataloging head in 6 weeks, from scratch• Ohloh.net stats (as of July 2012) • 16 regular contributors in last 12 months (26 in total) • Top 10% of open source teams • ~8 person years of development
  • 24. Hypatia Development – 8 week sprint 80/20 – 8 Weeks of Development https://github.com/projecthydra/hypatia/graphs/impact
  • 25. Hydra-based Applications at StanfordETD’s – Electronic Theses SALT – Self-Archiving EEMs – Everyday& Dissertations Legacy Toolkit Electronic Materials Argo – Repository Reporting Hypatia – Archives & and Management Special Collections
  • 26. Hydra Philosophy -- Technical • Tailored applications and workflows for different content types, contexts and user interactions • A common repository infrastructure • Flexible, atomistic data models • Modular, “Lego brick” services • Library of user interaction widgets • Easily skinned UI One body, many heads
  • 27. Shared, Primitive Functions • Deposit Plus • Manage Authentication – Edit Objects Authorization – Set Access Workflow • Search • Browse • Deliver
  • 28. Content Framework • Key to enabling re-use of Hydra repository solutions is a common baseline to how objects are structured • Objects must include rights metadata • Objects must include a statement of what content models the objects adhere to • That’s it! • The Hydra community has developed some basic building block content models (the Lego brick approach) • Combine and/or extend these to meet your needs
  • 29. Technical Framework - Components • Fedora provides a durable repository layer to support object management and persistence • Solr, provides fast access to indexed information • Blacklight, a Ruby on Rails plugin that sits atop solr and provides faceted search & tailored views on objects • Hydra Head, a Ruby on Rails plugin that provides create, update and delete actions against Fedora objects
  • 30. Blacklight for Repositories • Repository-agnostic, feature-rich, content- aware, turnkey access interface for repositories • Aggregate content from multiple repositories, with links back to source systems • Vibrant, multi-institutional, open source community on its own • Can be used independently, or as the first component of, Hydra
  • 31. CRUD in Repositories Create/Submit/Edit Search/View (CUD) (R) Repository/ Persistent Storage
  • 32. CRUD in Repositories Create/Submit/Edit Search/View (CUD) (R) Repository/ Persistent Storage
  • 33. Major Hydra Components hydra-head Blacklight Rails Plugin (Read Only) (R) (CUD) Solrizer Fedora Solr
  • 34. A Note on Ruby on Rails• Rapid application development for web applications: “Convention over configuration” – 10x productivity• Supportable: MVC (Model-View-Controller) and Rails framework make code well-structured, predictable• Testable: Rspec and Cucumber give powerful, automatable, testing tools• Learnable: Stanford went from 1 to 8 Ruby savvy developers in one year (no new hires) – 1 week learning curve to basic proficiency
  • 35. 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
  • 36. Best Practices in Development• Agile, user-centric development process• Test driven development & continuous integration• Take a light touch when dealing with big topics: “working software wins”• Distributed version control, github & public software repositories• Rotating release managers for components• Weekly “stand up” meeting w/ JIRA• Daily chats in IRC• Documentation
  • 37. So What is Hydra?• Framework for generating Fedora front-end applications w/ full CRUD functionality• That follows design pattern with common componentry and platforms – Fedora, Ruby on Rails, Solr, Blacklight• That supports distinct UI’s, content types, workflows, and policies
  • 38. So What is Hydra?• And a growing community of institutions and developers committed to framework and collaboration – Not grant-based – Distributed – Robust – Open
  • 39. Connect • http://www.projecthydra.org • Weekly developer calls: • Mondays 8:30 AM California time • Email list: hydra-tech@googlegroups.com • IRC: chat.freenode.net #projecthydra • Quarterly Hydra Partner meetings • Annual HydraCamp • Next Up: 8-12 October ’12, Penn State
  • 40. Hydra Webinar #2Case Studies in Repository ApplicationsTuesday, October 16 @ 11 AM EDT• Richard Green, University of Hull &• Rick Johnson, University of Notre Dame Hydra Webinar #3 A Deep Dive into the Hydra Technology Stack Tuesday, October 30 @ 11 AM EDT Matt Zumwalt, MediaShelf
  • 41. http://projecthydra.org
  • 42. Questions? Tom Cramer Stanford University tcramer@stanford.eduSeptember 25, 2012 Hot Topics: DuraSpace Community Webinar Series