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
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
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
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
