Fedora is the flexible, extensible, open source repository platform that commonly underlies Samvera implementations. Fedora provides a number of core services that Samvera already uses, such as CRUD operations, versioning, and fixity, and several new, potentially useful extended services have been introduced within the last year. The API Extension Framework provides a means of binding services to repository objects in order to extend the functionality of Fedora, while the Import/Export Utility makes it easier to get content into and out of Fedora in standardized formats and packages. This workshop will introduce both of these new services and discuss how they might be used in the context of Samvera. Participants will also have an opportunity to try them out via hands-on exercises in combination with a virtual machine. and A workshop given at Samvera Connect 2017 described thus
Keyword:
Fedora, Samvera, Workshop, Import/export, and Connect 2017
Subject:
Samvera Community
Creator:
Woods, Andrew
Contributor:
Birkland, Aaron, DuraSpace, and Johns Hopkins University
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