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
We’ve all heard that the biggest challenges offer the best rewards. But we don’t always know how to tackle the large complex challenges that come our way. As a software engineer, I believe that learning how to break down projects and tasks is the most important skill we can have. In this talk, I will discuss some strategies that I have used to analyze, organize, and manage the projects that I have worked on. But don’t worry if you’re not a software engineer, these strategies can be applied to more than just software, including your personal and career goals.
and we often need to make localized adjustment(s) to address either an underlying bug or to extend existing behavior. The code-base has places for configuration, but sometimes that might not be enough. Join me on a foray into how you can make the Ruby/Rails changes you need now and not make things (too much worse) for your future self and others. and The Samvera stack is deep
10 PM PDT. Join the team behind the new Hyrax Analytics features for a sneak peek at the nearly-final interface for the analytics dashboard for collections and works, as well new reporting functionality! We'll show you exports, show pages, and graphs galore for Google Analytics and open source provider Matomo., Presentation from Samvera Connect 2021 on October 20, 2021 from 11, and 40 AM - 12
Advancing Hyku, funded by Arcadia, a charitable fund of Lisbet Rausing and Peter Baldwin Shared Research Repository, hosted by British Library Hyku for Consortia, funded by Institute of Museum and Library Services and Leads from Hyku projects in various stages (active implementation, nearing launch, and ramping up) gathered for a lively panel session at Samvera Connect 2021. We started with brief updates on work done this past year across our projects on prioritizing community features. Included were discussion about what works in local installations, what works (and doesn’t) when contributing code back to the community core, and how we collaborate across projects in formal (shared Hyku Roadmap, meetings, documentation) and informal (Slack, email, telepathy?!?) ways. We ended the panel with an open call for community input on future community Hyku development priorities. Projects represented
Keyword:
2021, Samvera Connect, and Hyku
Creator:
Holt, llkay, Basford, Jenny, Hurford, Amanda, and Ramsey, Ellen Catz
This presentation the slide deck for a lightning talk given at Samvera Connect 2021 (online). It discusses strategies for adopting patterns for developing Hyrax plugins.
Keyword:
Hyrax Plugin Patterns Architecture Event Bus Bulkrax Callbacks
