This presentation will focus on Northwestern University and Indiana University’s continued work toward a sustainable model for support, maintenance, and development of the Avalon Media System - an open-source, Samvera-based repository for audio and video jointly developed since 2011. Over the last two years, the team has focused on widening engagement with and commitment to the Samvera and IIIF communities as well as developing wider developer interest by re-basing the product on top of Hyrax and developing a modular architecture. and A proposal and presentation given at the Open Repositories conference in Hamburg, Germany, in 2019, described thus
Keyword:
Grants, International Image Interoperability Framework (IIIF), Avalon, Samvera, Open Repositories 2019, Sustainability, and Hyrax
Subject:
Avalon Media System
Creator:
Dunn, Jon, Schober, David, and Steans, Ryan
Contributor:
Andrew W Mellon Foundation, Indiana University, Samvera, Institute of Museum and Library Services, and Northwestern University
- Large ingestion of 4 gig tifs with derivates and preservation checks (10k works) in ~ 1 hour - 5k batch metadata updates ~5 minutes - Round trip spreadsheet update (5k records in 5 minutes) - Preservation dashboard / verification - Local authority creation and updates This presentation will discuss the process, what we learned, and how it relates to the Samvera community at large. and On St. Patrick's Day NU went live with our new digital collection repository and asset management tool prioritizing speed of ingestion and metadata updates. We reframed the problem by working with end-users to look closely at workflows and prioritize solutions rather than any specific technology. The resulting application ecosystem is extremely budget friendly and the architecture supports
Heavily inspired by QA, "Authoritex" is a Hex package for querying any controlled vocabulary or set of authority terms that NUL developed for use within our Elixir ecosystem. We'll go through quick overview of Authoritex and how it fits into our repository ingest application "Meadow" and our broader strategy for handling controlled terms and authorities. The 'Related URL' below links to a video recording of the session. The video has closed captioning. and A lightning talk (seven minute) presentation given at Samvera Connect 2020 On-line described thus
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 described thus, using a recent major batch update feature as a case study. We’ll explore how our approach allowed us to stay connected to our users and helped keep our development team in sync. Finally, we’ll reflect on what we’ve found most successful in this approach as well as stumbling blocks we encountered along the way. The 'Related URL' below links to beginning of this presentation in the day's YouTube recording., and Over the past year, NUL dev team has implemented and refined a workflow for modular development of repository applications. It starts with addressing a specific user need or problem. Using design-thinking techniques, we next generate visual solutions through rudimentary wire framing, white boarding sessions and architecture discussions. We then move to API design and mocking before starting development with two teams working independently, from the API, outwards. This presentation will demonstrate the iterative approach in action
Keyword:
Workflow, Connect 2020, Samvera, User experience, and API
Forking this Github starter project spins up a webpack React dev environment, along with some tools and commands to bundle your React component to share via NPM. An alternative to Create React App, the project configuration was developed with the aim of exporting and sharing with other React apps in the wild. The video recording of this segment is available at the 'Related URL' below.
The Governance Working Group was chartered by Partners thus, A one-page summary of the discussion, documentation, and feedback to-date related to the various governance models under consideration. * Synthesis, This step will be shepherded by Steering, as the proposed model will also be assessed for legal, licensing, and MOU implications prior to further community review. * Proposal, Development of a draft governance proposal and incremental steps to implementation if appropriate * Community Input, Circulation of the final proposal for potential adoption at a Spring/Summer 2018 partner meeting, The Governance working group is a small group chartered by the community to help synthesize and formalize the various governance discussions and documents currently underway. The scope of the Samvera Governance Working Group’s deliverables will be, Circulation of the above to Partners, stakeholders, and the Steering group for review, comment, and change requests to the proposal * Legal Review, * Context, A revised governance proposal based on community, stakeholder, & legal feedback * Community Review, and A summary of the themes and issues that the community hopes to address by refining existing or adopting new governance practices and structures. Ideally identifies key differences and decision points between the models provided for evaluation and current model. This combined context and synthesis documents should be approximately 750-1500 words (1-3 pages) in length * Draft
Keyword:
Governance, Interest and Working Groups, and Samvera
University of Michigan, Data Curation Experts, Northwestern University, DuraSpace, Emory University, Princeton University, Indiana University, and Cornell University
A lightning talk at Samvera Virtual Connect 2019 described thus and Avalon Media System is upgrading it's UI component for handling structural metadata editing for an audio or visual work. The user can select and organize timespans in an AV work by manually typing bounding times and titles, or by interacting with a visual representation of the waveform. Technologies used are Peak.js and ReactJS.
Keyword:
Metadata, Lightning talk, Virtual Connect 2019, Avalon, Samvera, and User experience
Northwestern University Libraries is currently running Samvera applications in production. Three of these are developed, maintained, and managed by the Repository & Digital Curation workgroup, * Arch, an Institutional Repository, based on Hyrax 2.4.1 * AVR, Northwestern's audiovisual repository, based on Avalon 6.3 * DONUT, the staff-facing ingest interface for the digital object repository, based on Hyrax 2.4.1 In developing and deploying these applications, we have encountered (and mostly overcome) numerous stumbling blocks relating to performance, scalability, customization, and assumptions about the deployment environment and infrastructure on which the apps will run. While we have found it possible to shoehorn the Samvera stack (as it exists today) into our Amazon Web Services cloud-based deployment environment, we have also started to investigate the rewards and compromises involved in taking a cloud-first approach to our next generation of tools. We have identified several basic tenets for this approach so far, * If AWS offers a native Software-as-a-Service (SaaS) solution for a particular problem, use it (e.g., choose ElasticSearch/Cloud Search over Solr) * Avoid virtual server instances that run 24x7 waiting for requests/work * Do not assume there is a local filesystem to work with * Optimize startup time so that units of work can be spawned and killed as needed * Constantly assess and reassess every unit of work for scalability, repeatability, and idempotence * Keep data portable and code adaptable, but don't over-stress about vendor lock-in In this presentation, members of the Repository Development & Administration Team will present on lessons learned from 7 years of working with Samvera, Avalon, and Hyrax, what the future holds for our next round of in-house development, and the opportunities & compromises our cloud-first approach creates regarding our use of and contributions to the larger Samvera community., and A presentation at Samvera Virtual Connect 2019 described thus
Keyword:
Cloud services, Samvera, and Virtual Connect 2019
Subject:
Samvera Community
Creator:
Klein, Michael B
Contributor:
Quinn, Brendan, Schober, David, Arling, Adam, Shaw, Karen, and Northwestern University