Does writing or reviewing code make you stressed, fatigued, or anxious? In this session Glen will share the mindful approach he takes to writing and reviewing code at the University of Cincinnati Libraries. Mindfulness has been used to reduce stress and increase the quality of people's lives and it can be used during software development as well. Learn how being present in the moment, focusing, and empathizing with users can lead to a better product and actually be therapeutic for the developer. and A presentation at Samvera Connect 2019 described thus
A workshop delivered at Hydra Connect 2016, described thus, increasing familiarity with PCDM, contributing back to PCDM from the activities of the participants, and increasing participants’ familiarly and comfort with data models more broadly., and The Portland Common Data Model (PCDM) is a flexible shared, linked data-based domain model for representing complex digital objects. This workshop will review PCDM, its history, technical overview, recent developments, and Hydra-specific implementation considerations. The workshop will also include an interactive modeling session where users will employ use cases from their repositories (or provided samples) to model in PCDM. The goals of the workshop include
A recording of a presentation at Samvera Connect 2018 described thus and Panelists from Duke University, Indiana University, and the University of Michigan will share their experience of developing a Research Data Repository based on Hyrax 2. They will discuss what worked out-of-the-box, what was customized, future directions, lessons learned to date from working together, and contributing back to the Hyrax community. Institutions’ efforts include data migration, accessibility testing, branding, community outreach, curation workflows, and overcoming the challenges associated with large datasets. A video recording of this session is available at the 'Related URL' below.
//wiki.duraspace.org/display/hydra/Applied+Linked+Data+Working+Group, https, A workshop delivered at Hydra Connect 2016, described thus, and This workshop is all about techniques to use linked data within your Hydra based application. For example, autocomplete fields from a controlled vocabulary are nice... but what if you wanted to give more context to what users are selecting via things like alternative labels and broader / narrower concepts? How do you cache triples locally? How do do you publish your own controlled vocabulary for others to use? And what is the best way to make your RDF data harvestable by others? This workshop is based on work done by the Applied Linked Data working group
A panel presentation at Samvera Connect 2019 described thus and As a Hyrax application developer, setting up a development environment is well documented within the community. Simply go through the Github README, install the prerequisites, and the development environment is practically ready to roll. Setting up a Hyrax production environment? Now, that’s a different story. Once an application is ready for production, there are a number of important decision points and configuration options that are less well documented within the community. This session will highlight some of those configuration options and include a discussion about how we can move forward, as a community, in communicating, sharing, and documenting how the characteristics of a repository should be considered before setting up a Hyrax production environment.
At Stanford libraries we've run hundreds of virtual machines to support dozens of applications. We've found the cost and complexity of patching and maintaining these machines to be untenable. We believe that a serverless infrastructure is our future and so we are using AWS Fargate (Elastic Container Services) and Lambda architecture to reduce our maintenance burden. We will explain the AWS offerings in this space, explain how we can set up a simple distributed system, and point out pitfalls that we've experienced. and A video recording of a presentation at Samvera Connect 2018 described thus
For the past few years I've been distributing a survey to gauge usage of Sufia (and, this year, CurationConcerns) and to get a sense of what direction the community wants the components to go in. I'd like to report back to you all on what the latest data says, and share a rough roadmap for 2016-2017. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
This presentation will explore the development of Hyku for Open Educational Resources — openly licensed educational materials such as textbooks, quizzes, classroom activities, etc. — while capitalizing on Hyku's multi-tenancy and sharing of infrastructure across two large groups of libraries. The PALCI and PALNI consortia (representing libraries in Pennsylvania, New York, New Jersey, West Virginia and Indiana) have just received a two year IMLS National Leadership Grant to develop Hyku into a multi-tenant, consortia-based service capable of handling OER in addition to other institutional repository resource types. In addition to leveraging collective expertise through consortia, two new work types are being developed for OER and electronic thesis and dissertations. This presentation will focus on the first work type being developed for OER , describing the features and uses of these resources, how the new work type model is being developed, and examine why Hyku and the Open Source Software community is a great home for this project. and A presentation at Samvera Connect 2019 described thus
Update on the recent work to implement standards-based import/export functionality for Fedora 4, working on importing and exporting Bags for migrating between Fedora repositories, and backing up to and restoring from preservation services such as APTrust, Archivematica, etc. and A lightning talk presentation at Hydra Connect 2016, described thus
A presentation given at Samvera Connect 2018 described thus, Despite widespread interest in Hyrax, Samvera’s new flagship repository solution, there is a dearth of documentation about how to run a production instance. We’ll cover the lessons we’ve learned from a year of building and hosting Hyrax, including our new project checklist, logging and monitoring practices, and data migration paths. DCE has been hosting a Hyrax based ETD repository for Emory University for 12 months. We've made a lot of discoveries and improvements since we launched. We'll be sharing our learnings and best practices for running Samvera Based repositories including, and * Infrastructure as code (esp. ansible for configuration management) * Monitoring using open-source and commercial tools (nagios, ok computer, splunk, pingdom, honeybadger) * Maintenance, Upgrades, and Testing A video recording of this session is available at the 'Related URL' below.
This session will provide an overview of the strategies and tactics being used at Emory University Libraries for planning and management of Samvera based initiatives. An overview of our approaches to project, product, and system management will be presented with a focus on resource strategy related to people, teams and roles. An emphasis on new hires and leadership roles will be presented as well as the challenges faced when implementing new technologies, providing support for legacy systems and managing teams. We intend for the session to be an opportunity for attendees to also share their experiences and challenges in the areas of leadership and management. and A presentation at Samvera Connect 2019 described thus
A lightning talk presentation at Hydra Connect 2016, described thus and Hydra applications can interact with a number of backing services (Fedora, Solr, Redis, job runners, etc). Using Docker to run these services locally can potentially simplify the development environment and reduce on-boarding time. A video of this session is available at the 'Related URL' below.
Minimum Viable Product-Suite and Minimum Viable Preservation features in a new Samvera platform migration., A presentation given at Samvera Connect 2018 described thus, and The Emory Digital Library Program team will share a retrospective of their Discovery and Technical Design process for determining MVP2
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