A presentation at Samvera Connect 2019, originally titled "Samvera Stack Overview", described thus and Samvera can be a daunting stack for newcomers. This presentation is designed to give developers and community members the common definitions and descriptions of the Samvera stack at the application and framework level. Framework topics include discussions around Rails, Sidekiq, Data Stores, Fedora, Solr, Blacklight, etc. While application level topics include discussions around Avalon, Hyrax, Hyku, etc. At the end of the presentation, attendees will have a greater understanding of Samvera's components and how they interact and come together to create a Samvera application.
Federal law requires a standard of accessibility on any project that receives federal funds. Creating accessible applications is also socially responsible, and implementing these practices can help us set better expectations as community leaders. In a community dedicated to preservation and providing access to to a broad range of assets, accessibility standards should be a priority. We'll explain audits and certification levels, as well as accessibility features that could provide significant value to digital repositories. Using Hyku as an example, a developer will demonstrate practices that are easy to incorporate into the dev process, as well as demo practical examples. and A presentation at Samvera Connect 2019, originally titled "Accessibility Audits & Upgrades in Samvera", described thus
A presentation at Samvera Connect 2019 described thus and Agile is an approach to software development that emphasizes team collaboration, continual planning, continual learning, and incremental delivery versus delivering everything at the end, perfectly and all at once. This talk aims to give a high level overview of Agile development and how the academic community could benefit from being more agile. We will cover the 4 core values and 12 principles upon which Agile was founded. We will also cover Agile's most widely used frameworks, Scrum, as a specific use case. We will go over Scrum's roles, events, artifacts, and the rules of how to play this highly collaborative game.
Organizations seeking Samvera solutions may have an internal development team, yet find they require external supplemental developers due to internal resource limitations or to bridge a specific technical knowledge gap. Collaborating among divided internal/external teams can be be a productive way of reaching goals within committed timelines, but also has its challenges. We present case studies of Samvera projects that utilized external development resources, highlighting the effects on productivity and budget. We'll also share advice on ways to effectively integrate and maximize a partnership with external developers, including the benefits of their unique experience. Discussion will include effective collaboration tools and other tips to ensure a successful implementation. and A presentation at Samvera Connect 2019 described thus
Keyword:
Collaboration, Project management, Connect 2019, and Samvera
Many institutions need to import, export, and migrate data in bulk, and the ability to do this easily should be a fundamental service offered by any repository. For Hyrax, there are a range of home-grown and community solutions focused on specific use cases but there are no easily reusable community solutions. That’s starting to change and we’d like to talk about our specific experience building ‘Bulkrax’ and ‘Zizia’, two bulk import-export engines for Hyrax. This talk will outline the current status of our two projects, covering the design and approach taken, alongside features such as OAI-PMH import, and CSV import and export. We'll also talk about where Bulkrax and Zizia are going in the near future. We’ll show how each can be adopted, configured, and extended to meet local use cases, and how these projects are meeting the requirements set out by 2018’s ‘Batch Import-Export Working Group’. We’ll also discuss how best to move forward as a community around this issue, This will mean developing not only software but also shared community practice for managing the flow of bulk metadata from legacy systems and digitization projects into Samvera repositories., and A presentation at Samvera Connect 2019 described thus
As most Hyrax adopters know, Hyrax offers a basic set of metadata properties that it assigns to each new work type. Most adopters will extend that set, to a greater or lesser degree, adding new properties, defining vocabularies and terms lists, and setting other constraints and requirements. Adding new metadata is a complicated process in Hyrax, and there are various ways in which developers have worked to streamline things (eg. scooby snacks, dog biscuits and archetypes). But before we even get to customising a Hyrax application, metadata librarians and developers must collaborate on specifying the metadata requirements. With no community machine-readable approach to defining those requirements, misunderstandings are common, and can be costly. With a machine-readable specification for metadata, metadata librarians could accurately specify requirements and developers could validate and codify those into applications. That’s where the Machine-readable Metadata Modeling Specification (M3) steps in. The specification is the output of the M3 Working Group and is nearing its version 1.0 release. This presentation will provide a walkthrough of the specification, show how to construct and validate a new M3 profile, and illustrate the benefits of M3 for both metadata specialists and developers. and A presentation at Samvera Connect 2019 described thus