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
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
Ubiquity repositories, which are based on Hyku, are designed to be highly scalable, highly reliable and quick to deploy in the cloud. In this presentation we will outline the technical architecture we have implemented, along with the challenges faced. These include scalability, security, cost-efficiency, performance, reliability, resilience, portability, delivery pipelines for code deployment, error reporting, testing and localization. We will also discuss our approach ensuring we remain on the most recent stable branch of the platform and contributing our code back to the community. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Collaboration, Architecture, Samvera, API, Customization, Connect 2020, Hyrax, and Hyku
one size would not fit all for our campus archives, library, and museum, and community needs above all. In this presentation, team members will talk about the past two years of experimentation, development, and conversation around how to connect our community to our cultural heritage collections through multiple integrations, both human and technological. At a high-level, we’ll discuss our technical architecture that uses legacy applications like ArchivesSpace, an aging Fedora repository, and a decades-old museum database together with the IIIF framework and open-source GatsbyJS. And perhaps more importantly, we’ll outline the cross-departmental team structure that has developers talking to museum curators, library cataloguers, archivists, and everyone in between. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording., The University of Notre Dame has taken a modular approach to building a new digital collections platform-integrating existing applications and connecting the people that manage and use them across the library, archives, and art museum. We began with two assumptions, and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Architecture, Samvera, Workflow, Connect 2020, Metadata, and Digital collections
Elixir, Phoenix, React, GraphQL, PostgreSQL, Elasticsearch, Amazon Web Services, Docker and Terraform. This presentation will focus on describing why we chose this path and the decisions and tradeoffs we've made along the way, along with a brief demonstration of our current state. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording., Northwestern University Libraries has been building a "green field" digital repository application since June 2019, code-named "Meadow". Our goal in building Meadow is to provide an internal tool to ingest, modify and publish digital resources to an API that drives our user-facing digital collections frontend. Meadow's development roadmap has focused on complementing NUL's existing production workflows and implementing best practices in digital preservation in a cloud-based environment. Meadow is built with a several languages, tools, and frameworks including, and A presentation given at Samvera Connect 2020 On-line described thus
Keyword:
Architecture, Samvera, Workflow, Connect 2020, Metadata, and Preservation
A presentation given at Samvera Connect 2020 On-line (originally titled 'Cloud storage service uploads for a Valkyrie repository') and described thus and This presentation aims to outline and discuss attempts throughout 2019 and 2020 to integrate an early pre-release of the BrowseEverything 2.0 component for supporting Google Drive file uploads into a Samvera repository. While this shall be restricted in scope for cases which were specific to the Princeton University Library and a Valkyrie-based repository Figgy, the hope is to encourage discussions regarding obstacles which were encountered and to aim to generalize the solutions which were discovered in this integration. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording.
Keyword:
Cloud services, Architecture, Samvera, Valkyrie, and Connect 2020
* Understand what Samvera is and how to participate * Understand how to use Samvera * Understand the value of Samvera Samvera is a community, a set of tools, and a collection of ready-to run and hosted applications to help build a digital repository for your institution. The community drives the specification and development of sustainable open source technology and honing best practices for managing digital content. This workshop will provide an on-boarding and general entrée to the Samvera community and solutions for non-coders. The first part will provide an overview of Samvera solutions, hosting options and the community – what is it, why is it different? It will showcase applications solving a diverse set of needs and organizations, and discuss the how the community at large works to enable these. The second part will give a general technical overview designed for a non-technical audience. The resources needed to maintain and contribute to a hosted or custom Samvera solution will be discussed, resources that exist to get started will be highlighted plus how to contribute to the community technically and non-technically. The final part will discuss value and how to pitch Samvera and get institutional support. It will discuss the advantages of being part of the community and how that strengthens the sustainability of the tools, the applications, and the community overall. The 'Related URL' below links to a YouTube video of the presentation. and Samvera Connect 2020 was a virtual, rather than face-to-face, conference because of the COVID-19 pandemic. This presentation would normally have been given as a workshop with some hands-on participation in the middle. The session was described thus
Keyword:
Community, Governance, Architecture, Connect 2020, Samvera, Workshop, and Repository