How can we include user experience [UX] best practices in Hydra's core development work? How can UX experts contribute effectively to the Hydra project? How can we ensure that decisions around elements that affect the user experience are based on good evidence? Through case studies and facilitated discussion, this panel will seek to demonstrate and explore how to better integrate end-user feedback into the Hydra development stream. Dave McCallum from the University of Oregon explores issues of accessibility and the user experience. Jenn Colt from Cornell University and Sonya Betz from the University of Alberta will facilitate an active discussion around building UX into Hydra development workflows, and will ask participants to suggest strategies for including real users and their feedback in design and development decisions. The second presentation is available at the 'Related URL' below. An audio recording of the session is available for download below. and A presentation given at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Hydra, and User experience
Subject:
Hydra Project
Creator:
Betz, Sonya, Colt, Jenn, and McCallum, David
Contributor:
Cornell University, University of Oregon, and University of Alberta
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
Keyword:
Metadata, Workflow, Architecture, Hydra, Open Repositories 2015, Blacklight, Digital collections, Fedora, and Solr
Subject:
Hydra Project
Creator:
Pechekhonova, Ekaterina, Harper, Corey, Kassel, Carol, and Lovins, Daniel
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
Keyword:
Architecture, Repository, Curate gem, Hydra, Hydramata, Fedora, Import/export, Technology, Research data management, and Open Repositories 2014
Subject:
Hydra Project
Creator:
Johnson, Rick and Newman, Linda
Contributor:
University of Notre Dame and University of Cincinnati
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.
Keyword:
Grants, DLF Forum 2011, Hydra, and Archives
Subject:
Hydra Project
Creator:
Dushay, Naomi, Meloni, Julie, Cramer, Tom, Olson, Michael, and Daigle, Bradley
Contributor:
Yale University, Andrew W Mellon Foundation, University of Virginia, and Stanford University
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.
Keyword:
Community, Open Repositories 2010, Architecture, Repository, and Hydra
Subject:
Hydra Project
Creator:
Sadler, Bess, Sigmon, Tim, Mene, Willy, Green, Richard A, Staples, Thornton, McRae, Lynn, Cramer, Tom, and Awre, Christopher L
Contributor:
University of Hull, DuraSpace, University of Virginia, and Stanford University
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.
Keyword:
Open Repositories 2009, Collaboration, Repository, and Hydra
Generalizing from discussions within the GIS Data Modeling Working Group, this talk aims to address the potential benefits and risks involved in attempting to integrate Vagrant Boxes (virtual machine images) into software development and service deployment life cycles. An audio recording of the session is available for download below. and A lightning talk presentation at Hydra Connect 2016, described thus
Keyword:
Deployment, Connect 2016, Hydra, and Lightning talk
Subject:
Hydra Project
Creator:
Griffin, James
Contributor:
Lafayette College Libraries and GIS Data Modeling Working Group
The session focuses on open approaches to sharing geospatial metadata. We will discuss issues around standard requirements, appropriate linked data predicates, using linked data for placenames and gazetteers, participating in organizations and networks for sharing like OpenGeoMetadata, and identifying available tools and resources. An audio recording of the session is available for download below. and A panel presentation at Hydra Connect 2016, described thus
Keyword:
Geodata, Connect 2016, Hydra, and Linked data
Subject:
Hydra Project
Creator:
Durante, Kim, Battista, Andrew, Hardy, Darren, Griffin, James, Reed, Jack, and Barnett, Chris
I will show the data model migration from Sufia 6 to Sufia PCDM we used for ScholarSphere. In addition I will the outline major design decisions we made along the way. Then we will look at the tools in Sufia for migration of data from Sufia 6 to Sufia PCDM. I will include examples of extending the functionality for people who have extended the basic Sufia 6 model. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016, described thus
Keyword:
Connect 2016, Hydra, Portland Common Data Model (PCDM), and Sufia
A recap of the group's recommendations for the upcoming (now released) Sufia 7 – thoughts on the diverse needs of the community and the result, What worked, what didn't work, how to approach it next time. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016, described thus
Keyword:
Interest and Working Groups, Connect 2016, Hydra, User experience, and Sufia
A presentation at Hydra Connect 2016, described thus and The Hydra stack is large and complex, getting a handle on what's causing a specific slowdown can be difficult. This session would recommend some tools, strategies, and places to look for improving the performance of your application. An audio recording of the session is available for download below.
A presentation at Hydra Connect 2016 described thus and A follow-up to our presentation at Hydra Virtual Connect to show the progress we've made on Opaquenamespace.org. We'll discuss how we are using Git and github as our master-copy for RDF graphs, and using Blazegraph and the triplestore-adapter gem for our operational datastore. An audio recording of the session is available for download below.
Keyword:
Resource Description Framework (RDF), Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Wick, Ryan, Gum, Josh, and Sato, Linda
Contributor:
University of Oregon Libraries and Oregon State University Libraries and Press
Using Hydra to manage and present cultural heritage resources raises a set of interesting challenges that are beyond the scope of the traditional institutional repository. These include more complex data models, elaborate and varied workflows, richer descriptive metadata, support for more and varied controlled vocabularies, the requirement to manage larger objects comprised of larger files and multiple derivatives, support for IIIF, and a desire for richer viewing environments in general. In this presentation we will discuss these challenges and highlight examples and implementations that have gone ‘beyond the repository’. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016 described thus
Keyword:
International Image Interoperability Framework (IIIF), Connect 2016, Workflow, Hydra, and Metadata
Subject:
Hydra Project
Creator:
Allinson, Julie and Stroop, Jon
Contributor:
Princeton University Library and University of York
Highlight the contributions many Hydra institutions are making towards Fedora as a way to advance their Hydra environments, as exemplars of how the two projects are symbiotic. An audio recording of the session is available for download below., A presentation at Hydra Connect 2016 described thus, Advance a Hydra platform statement on the importance of supporting Fedora in general, Generate awareness of the role client platforms play in shaping Fedora development, Generate awareness of the role Fedora plays in the Hydra stack, Fedora provides an essential foundational layer to the Hydra Stack that may seem opaque to many in the Hydra Community. Recent community discussions have highlighted the technical and community relationship between Hydra and Fedora, the value proposition of Fedora, and Fedora's role in an institution's broader preservation strategy. As the Hydra Community continues to thrive, the intersection of the larger repository community and role with these technologies is an important community rallying area. This session is intended to, and Discuss methods for approaching development of features along the Hydra and Fedora stack continuum
Keyword:
Fedora, Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Cramer, Tom, Estlund, Karen, and Armintor, Benjamin
A presentation at Hydra Connect 2016 described thus and This case study will address the initial decisions and reasons for switching to Hydra, prototyping for launch of Hydra head, metadata cleanup and asset migration, final quality review, and lessons learned. An audio recording of the session is available for download below.
Keyword:
Case study, Connect 2016, Hydra, and Migration
Subject:
Hydra Project
Creator:
Simic, Julia, Wick, Ryan, Mellinger, Margaret, and Sato, Linda
Contributor:
University of Oregon Libraries and Oregon State University Libraries
GeoConcerns is a plugin to CurationConcerns for managing geospatial resources in a repository (http, A presentation at Hydra Connect 2016 described thus, and //geoconcerns.github.io). This presentation will give an overview and demonstration of GeoConcerns’ features and PCDM-based data model. In addition, we will discuss the code base and future development work such as integration with Sufia. An audio recording of the session is available for download below.
Keyword:
Geodata, Connect 2016, Hydra, and Portland Common Data Model (PCDM)
A presentation at Hydra Connect 2016 described thus, In this presentation, we will present a software development and deployment process that we have developed at Virginia Tech. We have used this procedure to develop several Hydra projects for University Libraries services at Virginia Tech and have also used it to conduct interviews for Ruby and Rails developers. We implemented a central vagrant box to facilitate the development and deployment processes. Using this vagrant box gives us many benefits, and 1. Code immediately. Our software engineers can focus on coding without worrying about software installation. 2. Unified development environment. All developers do their work in the same, consistent development environment. 3. Development of multiple projects simultaneously. Developers can work on multiple projects in parallel, switching between project environments in just a few minutes. 4. Minimal differences between development environments and production environment. After we finish implementation, we can quickly deploy our applications into a cloud environment (e.g. AWS and OpenStack) that is highly consistent with our development environments. We will present and demonstrate our hands-on experience on how we use a single vagrant box with different GitHub repositories to develop multiple Hydra applications in detail, including Sufia, GeoBlacklight, Fedora, Solr, Vagrant, AWS, and OpenStack. An audio recording of the session is available for download below.
Archiving Research Data into Hydra through the Open Science Framework (OSF) - A look at initial work of Notre Dame and Johns Hopkins to archive research projects from the OSF into Fedora and Hydra repositories, and first implementation of a Fedora Research Object Model. This plugs into a service offering of the Center for for Open Science, OSF for Institutions (OSF4I). ND/JHU version will be initial support for OSF Fedora Archiving Add-on in the OSF as part of OSF4I offering. We hope to start discussion around next steps for other Hydra institutions to use this along with OSF4I to allow them support to archive research data from the OSF into their own Hydra/Fedora repository. An audio recording of the session is available for download below. and A presentation given at Hydra Connect 2016 described thus
In the UK, the Universities of York and Hull are looking at Archivematica's place in a research data pipeline. The two universities have slightly different use cases but share the desire to put research (and likely other) content through Archivematica on its way to the repository thus giving us a solid base for long-term preservation. We are both now in the third phase of a joint project to build proof-of-concepts to illustrate how Hydra and Archivematica can work together to manage and preserve research data. Since our project began, Jisc have launched an ambitious UK national research data shared service where a range of suppliers offer systems in different lots. Both Hydra / Fedora and Islandora / Fedora are part of the the ‘research repository’ lot of the service and the work of York and Hull has heavily informed the ‘preservation’ lot, with Archivematica one of the systems on offer. This presentation will describe the proof-of-concept work done by Hull and York, and will provide an overview of the new Jisc service. An audio recording of the session is available for download below. and A presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Archivematica, Workflow, Hydra, and Preservation
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.
Keyword:
Connect 2016, Hydra, Portland Common Data Model (PCDM), and Sufia
Migrating a Fedora 3-based Hydra repository to Fedora 4 can be a major undertaking. This panel will bring together representatives from multiple institutions that either are planning for, are in the midst of, or have completed such a migration. Depending on where they are in the migration process, panelists will talk about their plans for migration, techniques used or expected to be used, obstacles anticipated or encountered, how problems were addressed, and migration outcomes. It is hoped that the presentations and discussion will be useful to other Hydra sites planning such a migration. A video of this session is available at the 'Related URL' below. and A presentation given at Hydra Connect 2016 described thus
Keyword:
Fedora, Connect 2016, Hydra, and Migration
Subject:
Hydra Project
Creator:
Coble, Jim, Wead, Adam, Hardesty, Juliet L, and Friscia, Mike
Follow-up to last year's presentation about Columbia's Hyacinth editor. Lots of changes / progress since the last presentation. Many TODOs have been TODONE. Hyacinth is a metadata editor, batch Fedora ingest tool and content publishing application that is becoming more and more integrated into our digitization, cataloging and front-end presentation workflows. Built on top of Hydra, but not Blacklight, with a JavaScript-and-AJAX-heavy front-end for many search/editing features. Currently Fedora 3, but hopefully moving toward Fedora 4 early next year. Still under development with additional planned features. I'd love to present and get feedback. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016 described thus
The Hydra-in-a-Box team in conjunction with Princeton has added IIIF image and presentation API support to Hydra. Come see how we're going farther together with open APIs. A video of this session is available at the 'Related URL' below. and A lightning talk presentation given at Hydra Connect 2016 described thus
Keyword:
International Image Interoperability Framework (IIIF), Connect 2016, Hydra in a Box, Hydra, and Lightning talk
We encountered big performance hurdles with our Sufia6 based application HydraNorth, and this is a quick overview of tools we used to help us monitoring and profiling the performance of our application, and restoring sanity to our team. A video of this session is available at the 'Related URL' below. and A lightning talk presentation given at Hydra Connect 2016 described thus
An overview of the Jisc Research Data Management Shared Service initiative in the UK, looking to establish a set of infrastructural components that academic institutions can combine to provide an overall RDM solution. Hydra has been shortlisted as one of the repository components that an initial group of pilot institutions can use. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Research data management, Jisc, Hydra, and Lightning talk
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
Keyword:
Fedora, Digital collections, Hydra, Archives, Open Repositories 2015, Sufia, and Metadata
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.
Keyword:
Metadata, Resource Description Framework (RDF), Hydra, Open Repositories 2015, and Fedora
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.
Keyword:
Fedora, Digital collections, Hydra, Vendors, Open Repositories 2015, Islandora, Documentation, Repository, and Training
Subject:
Hydra Project
Creator:
Dean, Robin, Estlund, Karen, and Herbert, John
Contributor:
University of Oregon Libraries, CO Alliance of Research Libraries, and LYRASIS
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
Keyword:
Workflow, Authorization, Lightning talk, Hydra, Open Repositories 2015, and Digital collections
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
Keyword:
Case study, Digital collections, Hydra, Repository, Archives, Open Repositories 2015, Lightning talk, and Metadata
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.
Keyword:
Community, Collaboration, Islandora, Hydra, Open Repositories 2015, and Fedora
Subject:
Hydra Project
Creator:
Ruest, Nick, Wilcox, David, and Cramer, Tom
Contributor:
York University, DuraSpace, and Stanford University
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
Keyword:
Metadata, DSpace, Hydra, Open Repositories 2015, and ORCID
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
Keyword:
Fedora, Collaboration, Architecture, Research data management, Hydra, ORCID, Community, and DuraSpace
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
Keyword:
Blacklight, Fedora, Architecture, Hydra, Metadata, and Solr
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.
Keyword:
Community, Architecture, Repository, Hydra, and Fedora
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.
Keyword:
Repository, Hydra, Fedora, and Collection management
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.
Keyword:
Fedora, Architecture, Hydra, Repository, Content models, and Metadata
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 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 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 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.
Keyword:
Research data management, Jisc, and Hydra
Subject:
Hydra Project
Creator:
Awre, Christopher L, Green, Richard A, and Lamb, Simon W
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 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 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.
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.
Keyword:
Case study, Workflow, and Hydra
Subject:
Hydra Project
Creator:
McRae, Lynn, Piazza, Nathan, Green, Richard A, and Open Repositories 2009
Contributor:
Fedora Commons, University of Virginia, Stanford University Libraries, Cramer, Tom, University of Hull, Sigmon, Tim, and Wayland, Ross
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.
• 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
Keyword:
Collaboration, Open Repositories 2011, Hydra, and Community
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.
Keyword:
Deployment, Case study, Hydra, and Open Repositories 2014
Subject:
Hydra Project
Creator:
Wead, Adam, Awre, Christopher L, Green, Richard A, Ng, Steven, and Lamb, Simon W
Contributor:
University of Hull, Chinese Historical Society of Southern California (CHSSC), and Rock and Roll Hall of Fame and Museum
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.
Keyword:
Research data management, Hydra, Virtual Connect 2016, and Lightning talk
Subject:
Hydra Project
Creator:
Allinson, Julie
Contributor:
University of York, Phillips, Matthew, and Durham University
This will be a half-day, hands-on workshop covering data modeling primarily in RDF. We hope to bring a diverse group of Hydra community members together to learn, discuss, and build out examples that will inform Hydra community best practices for data modeling. This modeling work will be taught in the context of helping Hydra and Fedora development, metadata, and interoperability efforts. We will discuss how model uses a number of standards, and demo the different ways to represent models. We will compare and contract data modeling with metadata standards/profiles. We will walk through modeling efforts around PCDM and its place in our work and community - this workshop will not focus on PCDM alone (this is not a PCDM or RDF workshop). We want this workshop to bring together, develop and engage a larger corps of data modelers in the Hydrasphere. and A workshop delivered at Hydra Connect 2016, described thus
Keyword:
Resource Description Framework (RDF), Connect 2016, Hydra, Portland Common Data Model (PCDM), Metadata, and Workshop
Subject:
Hydra Project
Creator:
Matienzo, Mark, Harlow, Christina, Johnson, Tom, and Hardesty, Juliet L
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
The Boston Public Library has long been a Fedora 3 Commons system and we are heavily invested in that backend. After waiting to see how Fedora 4 Commons develops and with some recent internal debate, our "next gen" repository solution is going in a different direction. This will be a (perhaps) controversial talk as to why and how we came to this conclusion. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
A lightning talk presentation at Hydra Connect 2016, described thus and Hydra applications can interact with a number of backing services (Fedora, Solr, Redis, job runners, etc). Using Docker to run these services locally can potentially simplify the development environment and reduce on-boarding time. A video of this session is available at the 'Related URL' below.
A lightning fast overview of free or cheap, cool and useful Ruby and Rails web sites, blogs, podcasts, videos, and users groups for new and not-so-new Hydra developers. I'll talk fast, but don't worry, I'll post the links on-line before the talk. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
When the Library of Congress was recently attacked, we noticed an important part of our workflow ground to a halt - XML schema validation had failed. We've developed a gem that allows for schema mirroring and offline validation/rspec testing, which we hope might be of use to others. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
A brief walk through on concerns related to monitoring and alerting a production Hydra stack. An recording of this session is available at the 'Related URL' below. Unfortunately, although it is technically a video, the slides do not show on the recording. and A lightning talk presentation at Hydra Connect 2016, described thus
A report of Michigan's early-stage investigation into building a Hydra publihing platform, which will eventually include support for fully-encoded text with an eye towards migrating level-4 TEI texts from DLXS and possibly including EPUB 3. and A lightning talk presentation at Hydra Connect 2016, described thus
Keyword:
Connect 2016, Hydra, and Lightning talk
Subject:
Hydra Project
Creator:
Morse, Jeremy
Contributor:
Andrew W Mellon Foundation, Penn State University Press, Northwestern University Press, Indiana University Press, and Michigan Publishing, University of Michigan Library
A presentation at Hydra Connect 2016 described thus and A review of available APIs and services for identifying, and either manually or automatically loading, open source online content into a local IR. Grey areas, policy questions, challenges and opportunities. A video of this session is available at the 'Related URL' below.
Keyword:
Open access, Connect 2016, and Hydra
Subject:
Hydra Project
Creator:
Newman, Linda
Contributor:
Horton, Glen, Konecny, Mark, University of Cincinnati, and Van Mil, James
A presentation given at Hydra Connect 2016, described thus and In the UK, the Universities of York and Hull are looking at Archivematica's place in a research data pipeline. The two universities have slightly different use cases but share the desire to put research (and likely other) content through Archivematica on its way to the repository thus giving us a solid base for long-term preservation. We are both now in the third phase of a joint project to build proof-of-concepts to illustrate how Hydra and Archivematica can work together to manage and preserve research data. Since our project began, Jisc have launched an ambitious UK national research data shared service where a range of suppliers offer systems in different lots. Both Hydra / Fedora and Islandora / Fedora are part of the the ‘research repository’ lot of the service and the work of York and Hull has heavily informed the ‘preservation’ lot, with Archivematica one of the systems on offer. This presentation will describe the proof-of-concept work done by Hull and York, and will provide an overview of the new Jisc service.
Keyword:
Fedora, Connect 2016, Workflow, Hydra, and Archives