The Samvera Community's Annual Report for 2017. This report may be of particular interest as it explains the reasons for the change of name from the 'Hydra Project'.
A plenary presentation at Hydra Connect 2016 advertised thus and An update on recent progress on the Hydra in a Box project, including work related to product development for the repository and metadata aggregation components, development of the hosted service, development and infrastructural decisions, and community engagement. A video of this session is available at the 'Related URL' below.
For the past few years I've been distributing a survey to gauge usage of Sufia (and, this year, CurationConcerns) and to get a sense of what direction the community wants the components to go in. I'd like to report back to you all on what the latest data says, and share a rough roadmap for 2016-2017. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
A presentation given at Samvera Connect 2017 described thus and A presentation that reflects on the learnings and accomplishments of the Hydra-in-a-Box project, the 30-month effort by Stanford Libraries, DuraSpace, and the Digital Public Library of America with funding from the IMLS.
A presentation given at Samvera Connect 2017 described thus and In this session we will give a quick background of Hyrax and offer a status update on current Hyrax work including the 2.0.0 release and the new testing process for releases. We will also discuss our early plans for the 2.x series of releases including updates on Collection Extensions work, Valkyrie sprints, plans for new Analytics features, and other potential work in the 2.x series. Last, we’ll talk broadly about roadmapping for Hyrax and what we might expect from Hyrax 3.0.0 and beyond.
In 2006, Stanford Libraries built the Stanford Digital Repository (SDR). The system has served us well—thirteen years later, SDR contains over 2.0 million objects (~500 terabytes of content). We built SDR using open-source software (including Samvera, Fedora, and Blacklight) and an additional ~300,000 lines of custom code. We believe it is among the largest and most complex repository systems in research libraries, and yet the challenges we face are common. We have grown SDR to a point where it is extremely difficult for us to sustain. Some of our foundational technologies are not only aging but are beyond end-of-life. Meanwhile, we are challenged to continue offering a valuable, performant, highly-available repository service to our stakeholders. Over the past two years, we have analyzed the factors complicating sustainability, that work has led to operational changes that improve the current state and a plan for sustaining repository development combining open-source and custom software. Our presentation highlights the reasons SDR became unsustainable and shares areas where we have made improvements and where we go next. We believe the lessons we have learned are widely applicable to institutions that develop their own repository solutions., and A presentation at Samvera Connect 2019 described thus