Avalon will demonstrate how an initial plan to re-architect Avalon Media System utilizing the Hyrax stack has paired with efforts to ensure greater sustainability of both Avalon and Samvera as framework and community. Following that goal, the past year the Avalon team has made terrific strides toward the development of Avalon 7, in part through community collaborative work with Hyrax and Samvera teams. Additionally, we'll cover work aimed at preservation and scaled hosting of Avalon, as well as a range of activities including IIIF development for audiovisual media, collaborations with Avalon users, new features such as OHMS integration, our participation in community interest and working groups, and our efforts at outreach to find and assist new and potential users. A video recording of this session is available at the 'Related URL' below. and Presentation to delegates at Samvera Connect 2018 described thus
A presentation at Connect 2018 updating delegates on the recommendations of Samvera's Governance Working Group. A video recording of this session is available at the 'Related URL' below.
A presentation updating delegates at Samvera Connect 2018 about work on the Valkyrie gem. A video recording of this session is available at the 'Related URL' below.
An update to delegates at Samvera Connect 2018 about Samvera's Hyrax software. A video recording of this session is available at the 'Related URL' below.
We will present our use case for and development of a GraphQL API in Figgy, our Valkyrie-based digital collections management application. We'll give a brief summary of GraphQL itself, demo an in-broswer query tool called graphiql, and show how we used the graphql gem to quickly develop and deploy a GraphQL API endpoint. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
This presentation will provide an overview of the needs of the American Archive of Public Broadcasting, challenges and successes of building a custom application based on Hyrax and Avalon, features developed both within the application and as re-usable components, and how to represent PBCore metadata in a Samvera application. The American Archive of Public Broadcasting (AAPB), founded by the Corporation for Public Broadcasting, is currently a joint venture between WGBH and the Library of Congress. It is a collection of digital audiovisual content created for public media distribution, requiring an adaptable technical infrastructure that can support close collaborations with organizations of varying technical and institutional capacity. The critical component for this is the Archival Management System (AMS), the entry point through which contributors’ descriptive, technical, and preservation metadata is ingested into the AAPB collection and where all metadata is managed and improved through cataloging by AAPB staff and interns. With plans of moving to a new system, hopefully one with a more active opensource community around it, the AAPB determined that the best path forward was to build the tool on Avalon and within the Samvera community. In 2017, the AAPB was awarded a grant by the Mellon Foundation to do just this, and the AMS 2.0 development project began in December of 2017 and is slated for completion by the beginning of 2019. AAPB is working with AVP and Indiana University as part of the development team. At the same time the project was starting, Avalon made the decision to move to Hyrax for Avalon 7. That changed the starting point and scope for the AMS 2.0 development plan, which is now to build a custom application on a Hyrax base creating features in tandem with the Avalon team. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus
Fedora, the flexible, extensible, open source repository platform for managing, preserving, and providing access to digital content, is a key component of most Samvera implementations. Fedora 4.x, the latest version of Fedora, has been in production since 2015, and since then the real-world experience of the community’s use cases has clarified Fedora’s role in supporting preservation and access in the context of large collections and performance at scale. This understanding led to an effort to formally specify the Fedora application programming interface (API) that provides a stable layer of abstraction between clients and repository instances. In this way, alternate back-end implementations suited for specific user cases can all expose the same core services to repository clients. This initiative will allow the Fedora project to adapt to technological change more easily over time while insulating clients from changes in the underlying implementation. This presentation will provide an overview of the the API specification effort, including current status, motivations, and benefits, with a particular focus on the relevance to Samvera. A brief survey of alternate implementations will provide context for the different use cases that will be enabled by the specification. This will be of interest to current and future Fedora implementers looking for an update on the current status and technical roadmap of the project. A video recording of this session is available at the 'Related URL' below. and A presentation given at Samvera Connect 2018 described thus