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
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
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
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
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.
Keyword:
Fedora, Avalon, Hydra, Open Repositories 2015, Metadata, and Resource Description Framework (RDF)
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
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
Keyword:
Fedora, Avalon, Digital collections, Hydra, Repository, Sustainability, Open Repositories 2015, Community, Digitization, Preservation, Workflow, and Archives
Subject:
Avalon Media System
Creator:
Frost, Hannah, Grants, Dunn, Jon, Rudder, Julie, Cane, Debs, and Durbin, Mike
Contributor:
Andrew W Mellon Foundation, University of Virginia, Stanford University, Northwestern University, and Indiana University
A proposal for a presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, One of the many successes of the Hydra community is the fundamental notion from which its name is derived—the concept of many interfaces (“heads”) over top of a single repository (the “body”). The recent release of Fedora 4, with its internal RDF-centric model, has spurred efforts for a community-wide model of collections and works, such that the heads can be sure that the body will behave as they expect it to. That model has been designed and vetted by the Hydra community, and its architecture and initial implementations will be presented in this paper. [Note, and the subject of this proposal has since become known as the 'Portland Common Data Model'.]
Keyword:
Community, Data model, Resource Description Framework (RDF), Hydra, Portland Common Data Model (PCDM), Open Repositories 2015, and Fedora
Subject:
Hydra Project
Creator:
Stroop, Jon, Sanderson, Rob, and Cowles, Esmé
Contributor:
University of California San Diego, Princeton University, and Stanford University
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
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
A poster given at the 2014 Open Repositories held in Helsinki. This poster will demonstrate the breadth of usage of the Hydra open repository solution within Europe, and highlight how the institutions using it have engaged with the Hydra community to establish their own repositories and fed into ongoing development. Readers will become aware of the use of Hydra within Europe, and how this relates to the Hydra project overall.
Keyword:
Community, Repository, Hydra, Blacklight, and Fedora
Subject:
Hydra Project
Creator:
Conrad, Anders, Wright, Nicola, Awre, Christopher L, Frost, Dermot, and Arambudo, Roger Guash
Contributor:
London School of Economics and Political Science, Trinity College Dublin, Royal Library, Copenhagen, Denmark, Theater Institute of Barcelona, and University of Hull
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 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.
The Hydra Project started in 2008 through a partnership between the University of Hull, the University of Virginia, Stanford University and Fedora Commons (now DuraSpace) to create tools that support use of the Fedora digital repository. Hull adopted the software outputs from this collaboration for its institutional repository in 2011 and remains an active Partner in the community, serving on the Steering Group and fostering development of the community and software in the UK and mainland Europe and The community now has 35 formal Partners and over 70 known adopters internationally. In June 2017 Hydra changed its name to Samvera, Icelandic for 'being together', to recognize the value gained from multiple institutions working together to create the underlying common basis upon which multiple different repository solutions have been implemented. Samvera can be adopted through a set of tools to develop your own repository (using a package called Hyrax as the starting point) and is also available as a complete repository solution, hosted or local, through the use of Hyku. The community has been at the heart of making Samvera a success, and will continue to underpin its future direction.
Update on the recent work to implement standards-based import/export functionality for Fedora 4, working on importing and exporting Bags for migrating between Fedora repositories, and backing up to and restoring from preservation services such as APTrust, Archivematica, etc. and A lightning talk presentation at Hydra Connect 2016, described thus
Keyword:
Fedora, Connect 2016, Hydra, Import/export, and Lightning talk
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 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
Blacklight, Fedora, Collaboration, Connect #2 (Fall 2014), Hydra, and Community
Subject:
Hydra Project
Creator:
Arambudo, Roger Guash, Awre, Christopher L, Conrad, Anders, Frost, Dermot, and Wright, Nicola
Contributor:
Trinity College, Dublin, Ireland, Theatre Institute of Barcelona, Royal Library, Copenhagen, Denmark, London School of Economics and Political Science, and University of Hull
A brief update on the current state of Fedora 4, followed by a high-level feature discussion for managers and a hands-on test drive for developers. and A workshop given at Hydra Connect #2 described thus
Keyword:
Fedora, Connect #2 (Fall 2014), Hydra, and Workshop
