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.
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
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
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
A presentation at the Open Repositories conference held in Hamburg, Germany, during 2019, described thus and The University of Houston (UH) Libraries, in partnership and consultation with numerous institutions, was awarded an IMLS National Leadership/Project Grant to support the creation of the Bridge2Hyku (B2H) Toolkit. Contents migration from proprietary systems to open source repositories remains a barrier for many institutions due to lack of tools, tutorials, and documentation. The B2H Toolkit, which includes migration strategies and use cases as well as tools for transitioning from CONTENTdm to Hyku, acts as a comprehensive resource to facilitate the repository migration process. This presentation will start with background information on the ecosystems, workflows, and tools, collectively known as the Bayou City Digital Asset Management System (BCDAMS), implemented at the UH Libraries. The presenters will then move to the key phases that make up the IMLS funded B2H Toolkit project plan. The presenters will also discuss how the project engages and strengthens the open source Samvera Community (formerly Hydra Community) around Hyku by leveraging our collective expertise through strategic collaboration. They will finally discuss sustainability and promotion of the B2H toolkit.
over 150,000 items in total. The University of Hull is contributing to the long-term legacy of the year through the development of a digital archive to capture, record and make available the material generated. This has been undertaken through the combination of a repository, using Samvera’s Hyrax, with related tools, A presentation at the Open Repositories 2019 conference in Hamburg, Germany, described thus, Hull in the UK was awarded the title of UK City of Culture for 2017. Over 2,800 events, attracting a total of 5.3 million people, took place over the course the year, a vast cultural undertaking. This cultural celebration generated many digital, and physical, artefacts, from the business documents of the organising company through to models of works by artists and data from evaluation of the impact of the year, and Archivematica for preservation processing, Box as an interim store, CALM for archives cataloguing, and Blacklight for presentation and discovery – each doing what they do best and being combined to best overall effect. This presentation will describe the work to create this infrastructure in partnership with a repository vendor, CoSector, and consider the ways in which the architecture, now completed, can be applied to other use cases, both archival and repository-related, beyond the specific one for which it was built.
Hyrax, now with around 50 active repositories, Samvera is an open source repository system with a growing user base. Since launch, two Samvera flavours have emerged, The Samvera Hyku system, focusing on how it's being developed to meet expectations of the British Library’s project The successes and challenges for the Library, our users and partners of developing a shared repository service. The workshop aims to be useful for both business/repository managers and repository system colleagues. We aim to pitch it at a level that makes it accessible for the ‘simply interested and not too technical’ but with enough detail to provide genuine insight into the potential of Samvera Hyku. After introductory presentations, the audience will divide to focus on the two areas above, with the chance to dig into the detail and throw questions at our expert presenters., The proposal for a workshop given at the Open Repositories conference in 2019 described thus, and and more recently Hyku, specifically designed to support multiple repositories on a single instance. By June 2019, the British Library will be reaching the end of a pilot project to develop shared repository services using Hyku as the central platform for itself and four partners, British Museum, Tate, National Museums Scotland and MOLA (Museum of London Archaeology). This workshop will cover
Agenda, with linked presentations and notes, for the Samvera Partner Meeting held at Indiana University - Purdue University Indianapolis (IUPUI) 29-30 April, 2019.
Program, and links to subsequent notes, for the Samvera Europe Group meeting held 14th December, 2017, at the London School of Economics and Political Science.
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.
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
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.
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
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'.]
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.
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
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
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.
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
Course syllabus for the Hydra Camp held at Princeton University Libraries, 26-29 August, 2014. The goal of Hydra Camp is to introduce new developers to the skills and tools they will need to successfully build Hydra based digital repository solutions. There’s a lot of ground to cover and you won’t walk out at the end of the week a complete expert, but we hope we’ll have provided you enough of a scaffolding to jump-start your own work and keep learning like the rest of us. We hope that the topics covered at Hydra Camp provide enough breadcrumbs that you’ll have a good idea where to start looking once you get home and start digging into problems on your own!
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.
A workshop given at the 2014 Open Repositories held in Helsinki. The Hydra for Managers workshop will enable repository managers and curators of digital collections to learn about the Hydra Project, encompassing both the community and the technical development. Focusing on the community primarily, topics covered will include an exploration of how Hydra fits local use cases, how to work with Hydra as a repository, and how to engage with the community to serve local needs and the sustainability Hydra going forward. The workshop will run for 90 minutes and will comprise a mixture of presentations and time to discuss questions raised by attendees. The workshop will be led by established Hydra Partners with different perspectives on using Hydra from differently-sized institutions.