A combined slide deck of the short reports from Interest and Working Groups at Hydra Connect 2015. Archivists Interest Group Digital Preservation Interest Group Geospatial Interest Group Hydra GIS Data Modeling Working Group Metadata Working Group Page Turner Interest/Working Group Service Management Interest Group User Experience Interest Group Web Presence Interest Group
A presentation at Hydra Connect 2015 about integrating RDF with Hydra for discoverability and presentation. Trey Pendragon, at the time, was known as Trey Terrell.
A lightning talk at Samvera Virtual Connect 2016. The talk was in two parts with the second given by Matthew Phillips of Durham University. Unfortunately, his slide deck is missing from the archive.
A presentation at the Open Repositories conference in 2014. There are those who perceive that implementing, running and maintaining a Fedora-based digital repository is a daunting task suited only to institutions with a significant team of developers and support staff. This paper offers a different perspective. The University of Hull in the UK, the Rock and Roll Hall of Fame and Museum in Cleveland, Ohio, and the Chinese Historical Society of Southern California (CHSSC) provide three case studies of Hydra-based repositories that are centred on a single developer working with small, limited or no support. This talk will compare and contrast their experiences and explain why the developers concerned feel that creating and maintaining these successful repositories has been worth their time and effort.
A presentation given at the Open Repositories conference in 2009. Part of the proposal reads and Repositories have proven themselves as powerful tools for managing digital content in many different contexts. But experience has also shown that there are real, practical limits in trying to extend a single repository solution to meet the manifold needs of most institutions for their full range of digital content and use cases. Relatively narrow and inflexible application front ends can be used to create single-purpose repository-powered solutions, but they do not lend themselves to being quickly and easily repurposed to meet variations in content type or user interactions. There is a clear business need for a flexible, reusable application framework that can support the rapid development of multiple systems tailored to distinct needs, but powered by a common underlying repository. Recognizing this common need, Stanford University, the University of Hull and the University of Virginia are collaborating on “Project Hydra”, a three-year effort to create an application and middleware framework that, in combination with an underlying Fedora repository, will create a reusable environment for running multifunction, multipurpose repository-powered solutions. This presentation will provide demonstrations of the work done to date, including of the prototype ETD application, as well as the set of content models and disseminators that the project has defined so far. The presentation will also present links to the project’s publicly accessible documentation and open source code, as well as solicit the constructive input from community members who may be interested in the project or its outcomes.
A presentation given at the Open Repositories conference in 2010. In part, the proposal reads and While repositories provide obvious benefits in hosting and managing content, it is equally clear that there is no “one size fits all” solution to the range of digital asset management needs at a typical institution, much less across institutions. A system that supports the submission, approval and dissemination of electronic theses and dissertations, for example, has demonstrably different requirements than a digitization workflow solution, an e-science data repository, or media preservation and access system. There is a clear need in the repository community to readily develop and deploy content-, domain-, and institution-specific solutions that integrate the flexibility and richness of customized applications and workflows with the underlying power of repositories for content management, access and preservation. This paper will provide an overview of Hydra’s philosophy, architecture, and components, as well as demonstrations of various Hydra installations. The paper will also provide a progress report on Hydra development to date and its overall roadmap, as well as provide observations on the successes and challenges of community-based development of shared repository solutions.
• No single institution can resource the development of a full range of digital content management solutions on its own, …yet each needs the flexibility to tailor solutions to local demands and workflows. • 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 The Hydra project has tested out these assumptions and reports in this presentation the outcomes from applying them to the work undertaken. The paper was delivered as a 'Prezi' presentation which can be found by following the 'Related URL' link below., The proposal for this presentation at the Open Repositories conference in 2011 begins, and The Hydra project is a digital repository initiative started in 2008 that originally brought together three institutions (Stanford University, the University of Virginia and the University of Hull) and DuraSpace, with a common identified need to provide a flexible means for managing and delivering a wide range of digital content types. The project has since investigated and worked towards a reusable framework for multipurpose, multifunction, multi‐institutional repository‐enabled solutions. Two previously identified assumptions have underpinned the work
A webinar given by Tom Cramer for the DuraSpace 'Hot Topics' series in 2012. A recording of the webinar is available by following the 'Related URL' link below.
Powerpoint presentation given at Open Repositories 2009 (OR09) in Atlanta, GA, 20 May 2009 describing the different workflow strategies being developed in the Hydra Project.
A presentation given at the joint meeting of the Fedora UK and Ireland, and the Fedora EU User Groups on 8th December 2009 in Oxford. The presentation describes the 'simple yet flexible' approach of the Hydra partners.
A presentation given to the joint meeting of the Fedora UK and Ireland, and Fedora EU User Groups on 8th December 2009 in Oxford. The presentation was part of the 'scholars workbench' strand.
A short presentation given at the Repository Fringe 2013, held in Edinburgh on 1-2 August 2013. A video recording is available at the 'Related URL' below.
A presentation on the use of Hydra for the management of datasets at the JISC Managing Research Data / DCC Institutional Engagement workshop on components for data management, held at the National College, Nottingham, on 24-25th October 2012. This presentation was given on 24th October within the strand on 'Data repositories and storage', alongside talks on the use of DataStage with DSpace at University of Hertfordshire, and on the use of CKAN at the University of Lincoln.
As part of the Mellon-funded AIMS project, the Universities of Virginia, Hull, Stanford and Yale have spent the last two years exploring the ramifications and distinct requirements of born digital archival materials in libraries. This presentation focuses on the partners’ research and prototyping of tools, infrastructure and workflows necessary to provide an end-to-end environment for born digital archival materials.
A webinar given by Matt Zumwalt for the DuraSpace 'Hot Topics' series in 2012 (scheduled for Oct 30, 2012, but recorded separately due to Superstorm Sandy) A recording of the webinar is available by following the 'Related URL' link below.
A webinar given by Rick Johnson and Richard Green for the DuraSpace 'Hot Topics' series in 2012. A recording of the webinar is available by following the 'Related URL' link below.
A presentation given at the London School of Economics and Political Science on 22nd November 2012. The meeting brought together a number of institutions from the UK (and some from Europe more widely) interested in the potential of Hydra. The presentation was one of a number describing the then current use of Hydra in the UK.
A presentation given at the London School of Economics and Political Science on 22nd November 2012. The meeting brought together a number of institutions from the UK (and some from Europe more widely) interested in the potential of Hydra. The presentation was one of a number describing the then current use of Hydra in the UK.
A presentation given at the London School of Economics and Political Science on 22nd November 2012. The meeting brought together a number of institutions from the UK (and some from Europe more widely) interested in the potential of Hydra. The presentation was one of a number describing the then current use of Hydra in the UK.
A presentation given at the London School of Economics and Political Science on 22nd November 2012. The meeting brought together a number of institutions from the UK (and some from Europe more widely) interested in the potential of Hydra. The presentation was one of a number describing the then current use of Hydra in the UK.
A presentation given at the London School of Economics and Political Science on 22nd November 2012. The meeting brought together a number of institutions from the UK (and some from Europe more widely) interested in the potential of Hydra. The presentation was one of a number describing the then current use of Hydra in the UK.
The Royal Library was very fast to adapt the emerging web technologies in the mid 1990’s. The web was used as an integrated part of digitization projects, resulting in a number of specially tailored web sites for various types of content, manuscripts, images, literary texts, journal articles, etc. Each project and type of material would typically result in its own data model, metadata format, workflow, and a database/repository that was tightly coupled with the web application. In later years, as the throughput on the digitization production lines has increased, more automated ways of dissemination have been developed. However this has not been able to fundamentally replace the tendency to building silos around different types of content. Being both national and university library, we can expect that in the future accessioned material will largely be born digital. In order to handle this situation, we have decided to start implementing an integrated digital library infrastructure, covering all aspects of digital collection building and management. The assumptions are that some metadata will be shared between all types of digital materials, and that the main steps in a digital object life-cycle will be common for all object types. In my presentation I am going to show how we are building a technical infrastructure in support of this, using building blocks such as Hydra, Fedora Commons, Solr, and Blacklight. I will also be touching on the organizational side of the project, focusing on the challenges to both IT people and collections staff in this process of change., and A presentation to the EOD Conference held at the National Library of Technology, Prague, Czech Republic, 17-18 October 2013. Abstract
however, library enduring commitments in print and current operations, and complex campus organizations often hinder libraries¹ ability to quickly respond to the data needs of the academy. Notre Dame¹s investment in research was recently reinforced by the university¹s approval of the expansion of ten disciplines, such as computational data, adult stem cell research, and nuclear physics. There is much needed support for research data on campus. The Hesburgh Libraries has been building an institutional digital repository since winter 2012. To respond to the trending needs, the Libraries switched gears to a user-centered and agile approach to develop data curation and access services since June 2013. Our goal remains to accept all scholarly outputs (text, images, video and audio), but with an imminent emphasis on research support. Our strategy is to grow our data curation services and our user base simultaneously, and to build success stories to drive adoptions along the way. Early adopters were identified with the help of our subject librarians, and they determined the most critical baseline features for the Libraries to develop. We also leveraged Hydra open source solutions and collaborated with Northwestern University, Indiana University, and the University of Virginia to create a new community shared Institutional Repository (IR) system. We have worked with our early adopters to pilot features since summer. We plan to launch an early access release by November 2013 and a full rollout by April 2014. We will share our development philosophy to overcome resource shortages to meet high demands on research support, our strategy to reach and develop our user base and roadmap, our insights on faculty¹s needs on research support, and our methodology to leverage and contribute to open source tools. A quick demo of our curation tool will be provided at the end of the session. and A presentation to the CNI Members' Meeting in December 2013. This session provides Notre Dame¹s experience as a case study to provision research data curation and access services. Managing research outputs becomes a tall order of many universities, given their determined agenda to pursue research excellence. In a world of increasingly data-intensive research, data is rising as a critical component of scholarly communication, often mandated by granting agencies. Data curation, preservation, and access are paramount to university academic mission, and academic and research libraries are some of the few entities of the universities that carry such functions
Diving into the Technology of Hydramata". and A presentation to the Fedora Interest Group track at the 2014 Open Repositories held in Helsinki. As in the heading of the proposal, this was originally offered under the title "Extending the Hydra Head to Create a Pluggable, Extensible Architecture
In the past year, the major groundwork has been laid for repository systems to support ORCID identifiers. DSpace, Hydra, and EPrints all have support for storing and managing ORCIDs. However, we are still in the early stages of ORCID adoption. Only a small fraction of repository content is annotated with ORCIDs, and most end-users have not yet realized any benefit from the features based on ORCID. This panel will bring together representatives of major repository systems to relate the current status of ORCID implementations, discuss plans for future work, and identify shared goals and challenges. The panelists will discuss how ORCID support provides practical benefits both to repository staff and end-users, with a focus on features that exist now or will exist in the next year. and Slides from a panel session given at the Open Repositories conference in 2015 held in Indianapolis described thus
Open source software isn’t really free. This might seem obvious to some, but there are many members of open source communities that consume rather than contribute, Slides from a panel session given at the Open Repositories conference in 2015 held in Indianapolis described thus, and they use the software but are either unwilling or unable to engage with the community to write code, submit use cases, create documentation, or do any of the other things that make an open source project a success. Fortunately, things don't have to be this way. Over the past two years, the Fedora project has undertaken a great effort to revitalize not only the software but the community itself. By maintaining open, transparent communication, soliciting use cases, development, and testing from community members, and establishing a clear project governance structure, we have laid the groundwork for a successful community source project. At the same time, the Islandora and Hydra communities have pursued similar strategies to build and sustain their own communities and the broader Fedora community. This panel will feature a discussion on the recent successes of the Fedora community and future plans to continue raising the level of community engagement and project ownership.
At the Digital Collections and Archives (DCA) at Tufts University we have designed, built, and integrated our archival collection management system and repository’s administrative interface to facilitate ingesting archival objects into our Fedora based repository. This 24x7 session briefly explores the assumptions and functional requirements we have used to guide this development work. The DCA’s unique position as an archives that is one of the key stakeholders and users of the Tufts institutional repository has enabled us to meet this integration challenge. The session describes how the integration of our archival collection management system and our repository relies on the ability to flexibly move metadata from one system to another. and A lightning talk given at the Open Repositories conference in 2015 held in Indianapolis described thus
To offer an interface for the library’s digital collections and archives, Yale Library has adopted the hydra stack for what are currently 3 access interfaces, findit, an application currently supporting 9 special collections and containing approximately 700k object, the Henry Kissinger Papers which when complete will contain approximately 1.7m images, and the Yale Indian Papers Project, a small collection of approximately 2k objects . This presentation summarizes key customizations and features including ingest, contextual navigation, fulltext search, image and transcript viewing, and ongoing work with authentication and authorization. and A lightning talk given at the Open Repositories conference in 2015 held in Indianapolis described thus
A presentation given at the Open Repositories conference in 2015 held in Indianapolis, described thus, Fedora, Hydra, Solr, and Blacklight. Called “Ichabod,” this tool has allowed us to ingest, normalize, and enrich metadata from diverse systems of record and make it consumable by our main discovery tool, which is powered by the Ex-Libris product Primo. We developed Ichabod using the Agile methodology and involving developers from three distinct NYU Libraries groups. The software will lay the groundwork for future innovation in the areas of metadata management and discovery for repository content. The relationships we established have already made it possible for a similar collaboration arrangement on two other projects, with more to come in the future., and From DSpace to Drupal, NYU has a variety of systems to ingest and display curated digital content. To make this content discoverable centrally, we developed a tool for metadata ingest, transformation, and discovery based on a popular open-source software stack
A panel presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus and Partnerships for shared repositories offer the promise of repository services at a decreased cost due to shared infrastructure and staff. In practice, reduced costs for shared repositories often require tradeoffs in security or access for the shared system. Staff working in a shared system may be geographically distributed or may work for different institutions with different priorities and reporting lines. Effective use of shared services requires thoughtful communication and tools that help maintain consistency and prevent conflicts when multiple people work in the same system. In this panel, shared repository service managers for multisite Islandora installations and a Hydra partnership will discuss methods for distributing system access and communicating with staff who work at our parent organizations, partner institutions, and third-party vendors. Each panelist will discuss the methods used so that distributed staff can have the level of access necessary to use the repository’s unique functions, while also ensuring that widely distributed system access doesn’t result in data loss or system failures.
Indiana University and Northwestern University, in collaboration with nine partner institutions, recently completed the last year of a three-year IMLS-funded effort to build the Avalon Media System, an open source solution for managing and providing access to digital audio and video collections, based on Fedora and the Hydra repository software development framework. As the Avalon platform reaches maturity, several institutions are in the process of implementing Avalon both to replace current time-based media access solutions and to support new use cases. In addition, new funding from the Andrew W. Mellon Foundation will support continued work to develop new features, grow and provide support for the community of adopters, and move Avalon towards organizational and financial sustainability. This panel will bring together project leaders from Indiana and Northwestern, along with Avalon community members at the University of Virginia and Stanford University, to share experiences of implementing Avalon at their institutions, integrating Avalon with other local systems, and supporting Avalon to enable a variety of use cases in research, teaching, and learning. Panel members will also discuss future development plans and provide a preview of how the project intends to transition from a grant-supported endeavor to a community-sustained solution. and Slides for a panel presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus
A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, provide an update on progress to date, At the University of Alberta Libraries we are currently developing a Digital Asset Management System (‘Hydra North’, built on Hydra and Fedora 4) to bring all of our digital assets into one platform for discovery, access and preservation. The metadata underlying these repositories has been created according to many standards (DC, MODS, EAD, etc.) and varies in level of fullness and overall quality. We find ourselves at a ‘metadata crossroads’ as we attempt to bring this disparate metadata together. We see a solution in a move to RDF and the application of the principles of linked data. In this presentation we will discuss some of the initial questions we asked ourselves as we tried to fully grasp what the move to RDF and linked data would mean for our existing metadata, provide concrete examples of the thought processes and workflows involved in moving from existing non-RDF metadata to RDF, based on the principles of linked data, outline some of the decisions we made along the way, and why, and what the impact has been, and reflect on lessons learned and outline next steps.
Indiana University Bloomington Libraries is involved in two new projects to digitize and store content and related metadata. Each of these projects presents unique challenges. We want to use the same technology stack for both, however, so we are choosing Fedora as a storage mechanism, with Hydra-based Sufia as a repository front end. We will discuss our decision, show advantages of this Hydra/Fedora framework, and discuss advantages of moving to Fedora 4. We will also contrast this framework with the way we might have approached these projects in the past with previous versions of Fedora and before Sufia or Hydra were options. and A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus
A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus and Avalon Media System requires support for complex structure and modular descriptive metadata management. Use cases and examples will examine options for Avalon in Fedora such as the RDF data model in Fedora 4, static XML datastreams, and external data stores to determine which path best fits structural and descriptive metadata needs for time-based media.
Using Sufia 7 as a reference model, what does the path for depositing a new item into a Hydra/PCDM based repository look like from an end-user, code, console, solr, and fedora perspective, A presentation given at Hydra Connect 2016 described thus, show the upload of new digital content via the Sufia UI and show each step of the data flow in the Browser, rails console, and Fedora. Walk through derivative generation and show the various PCDM relationships being built at each stage. Then add a new user collection, and walk through the same flows as a work is added to a collection, and what gems are in play, what does the data look like from a ruby developer perspective, what is persisted in Fedora and Solr - how does it all relate to PCDM? A video of this session is available at the 'Related URL' below.
New to Samvera? Welcome! We understand how steep the learning curve may seem when getting started. Samvera 101 is an introductory presentation that will cover fundamental principles with a sampling of common topics and definitions used within the Samvera stack and community. Framework topics include discussions around, Rails, Sidekiq, Data Stores, Fedora, Solr, Blacklight, etc. While application level topics include discussions around, Avalon, Hyrax, Hyku, etc. Like a prerequisite class, this talk is designed to prepare developers and community members for success! Attendees will leave having a greater understanding of Samvera's components and how they come together to create a Samvera application. The 'Related URL' below links to a YouTube recording with closed captioning., and A presentation given at Samvera Connect 2020 On-line described thus
A presentation given at Hydra Connect #2 described thus and Some have the impression that running a Hydra system requires a significant team of developers. In fact, there are a number of institutions running Hydra that are "one-developer shops". This talk will explore the pros and cons.