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.
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.
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 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.
A presentation given at Samvera Connect 2019 described thus and This presentation will cover the initial work to move the University of Michigan’s Deep Blue Documents repository from DSpace to Hyrax on Samvera and also merge it with the U-M data repository, Deep Blue Data, which is already on Hyrax. Deep Blue contains more than 120,000 items and has been around on DSpace since 2006. The Deep Blue Data repository started in 2016. Presenters will discuss steps taken so far to migrate and merge the repositories, including creating a minimum viable product (MVP) list, testing migration, addressing challenges so far, collaborating between IT and service providers, and determining next steps.
This session will be a brief introduction to the Hydra community, and a 35,000ft view of Hydra technically. It is an opportunity for people new to Hydra to get some context around what we are about and, hence, the rest of the conference! and An introductory presentation at Hydra Connect 2016, described thus
A presentation given at Hydra Connect #2 described thus and Some have the impression that running a Hydra system requires a significant team of developers. In fact, there are a number of institutions running Hydra that are "one-developer shops". This talk will explore the pros and cons.
A presentation given at Hydra Connect #2, advertised as "is Fedora 4 a good option for my needs?" and described thus and This session will discuss some of the features that are new in Fedora 4 that will undoubtedly send dazzles up the Hydra stack.
A presentation given at Hydra Connect #2 described thus and Our first year of developing a Hydra-based institutional repository yielded many surprises, frustrations, and eureka moments. We will tell you what we wish someone had told us about the Hydra community, Rails applications, System/Stack deployment, and Developer collaboration.
Do you ever wonder what working groups exist in the Hydra community or what topics are being discussed or how to spark a discussion or a working group? We are proposing a framework for interest groups and working groups which has proven effective in other successful communities toward raising awareness, connecting members with common interests, spawning action oriented working groups and making time at face to face meetings in support of both "percolating" ideas and heads down work. Join us to explore how this framework can further empower our community. and A presentation at Hydra Connect #2 described thus
A combined slide deck of the short reports from Interest and Working Groups at Hydra Connect 2015. Archivists Interest Group Digital Preservation Interest Group Geospatial Interest Group Hydra GIS Data Modeling Working Group Metadata Working Group Page Turner Interest/Working Group Service Management Interest Group User Experience Interest Group Web Presence Interest Group
A presentation at Hydra Connect 2015 about integrating RDF with Hydra for discoverability and presentation. Trey Pendragon, at the time, was known as Trey Terrell.
The keynote address at the Hydra Connect 2016 conference advertised thus and This presentation aims to present opportunities for collaboration between current Hydra members and The Daniel Cosío Villegas library at El Colegio de México (COLMEX) as well as other Mexican institutions that are interested in making a Mexican-based Hydra users group. COLMEX has been actively planning the implementation of a Hydra-based repository. Given that COLMEX has a significant presence in various digital libraries and repositories interest groups in Mexico, we have taken the opportunity promote Hydra as an alternative, not only with the hopes of promoting the project but to find local partners that might be interested in collaborating. We hope that we might find international partners who will help to spur initiatives through various means of evangelizing, helping support efforts, and perhaps coming down to Mexico to visit. In this manner we can help Hydra become a truly global initiative and one which considers north-south collaborations especially those outside the English-speaking world.
A plenary presentation at Hydra Connect 2016 advertised thus and An update on recent progress on the Hydra in a Box project, including work related to product development for the repository and metadata aggregation components, development of the hosted service, development and infrastructural decisions, and community engagement. A video of this session is available at the 'Related URL' below.
This annual report on the Hydra Project will provide a synopsis of the project’s current state from a high level perspective, including recent developments and important trends in adoption and activiity, the technical framework, the community framework, major projects and milestones, and where we may be going in the near future. With so much activity in so many different parts of the project, this session is a chance to take a step back from the many trees to survey the whole forest of the HydraSphere. A video of this session is available at the 'Related URL' below. (Very Low Audio for half of this and then just regular Low Audio - max out volume with headphones to hear) and The 'State of the HydraSphere' address given at Hydra Connect 2016, advertised thus
A presentation given at Hydra Connect 2016, described thus and In the UK, the Universities of York and Hull are looking at Archivematica's place in a research data pipeline. The two universities have slightly different use cases but share the desire to put research (and likely other) content through Archivematica on its way to the repository thus giving us a solid base for long-term preservation. We are both now in the third phase of a joint project to build proof-of-concepts to illustrate how Hydra and Archivematica can work together to manage and preserve research data. Since our project began, Jisc have launched an ambitious UK national research data shared service where a range of suppliers offer systems in different lots. Both Hydra / Fedora and Islandora / Fedora are part of the the ‘research repository’ lot of the service and the work of York and Hull has heavily informed the ‘preservation’ lot, with Archivematica one of the systems on offer. This presentation will describe the proof-of-concept work done by Hull and York, and will provide an overview of the new Jisc service.
A presentation at Hydra Connect 2016 described thus and A review of available APIs and services for identifying, and either manually or automatically loading, open source online content into a local IR. Grey areas, policy questions, challenges and opportunities. A video of this session is available at the 'Related URL' below.
A report of Michigan's early-stage investigation into building a Hydra publihing platform, which will eventually include support for fully-encoded text with an eye towards migrating level-4 TEI texts from DLXS and possibly including EPUB 3. and A lightning talk presentation at Hydra Connect 2016, described thus
A brief walk through on concerns related to monitoring and alerting a production Hydra stack. An recording of this session is available at the 'Related URL' below. Unfortunately, although it is technically a video, the slides do not show on the recording. and A lightning talk presentation at Hydra Connect 2016, described thus
When the Library of Congress was recently attacked, we noticed an important part of our workflow ground to a halt - XML schema validation had failed. We've developed a gem that allows for schema mirroring and offline validation/rspec testing, which we hope might be of use to others. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, described thus
A lightning fast overview of free or cheap, cool and useful Ruby and Rails web sites, blogs, podcasts, videos, and users groups for new and not-so-new Hydra developers. I'll talk fast, but don't worry, I'll post the links on-line before the talk. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, 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.
The Boston Public Library has long been a Fedora 3 Commons system and we are heavily invested in that backend. After waiting to see how Fedora 4 Commons develops and with some recent internal debate, our "next gen" repository solution is going in a different direction. This will be a (perhaps) controversial talk as to why and how we came to this conclusion. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016, 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 will be a half-day, hands-on workshop covering data modeling primarily in RDF. We hope to bring a diverse group of Hydra community members together to learn, discuss, and build out examples that will inform Hydra community best practices for data modeling. This modeling work will be taught in the context of helping Hydra and Fedora development, metadata, and interoperability efforts. We will discuss how model uses a number of standards, and demo the different ways to represent models. We will compare and contract data modeling with metadata standards/profiles. We will walk through modeling efforts around PCDM and its place in our work and community - this workshop will not focus on PCDM alone (this is not a PCDM or RDF workshop). We want this workshop to bring together, develop and engage a larger corps of data modelers in the Hydrasphere. and A workshop delivered at Hydra Connect 2016, described thus
A presentation given at Samvera Connect 2017 described thus and The Accessibility and Samvera presentation will cover an intro to web accessibility , general accessibility of Samvera applications, tools and resources for evaluation, educating ourselves and making accessibility a part of development from the start.
A presentation given at Samvera Connect 2017 described thus and A presentation that reflects on the learnings and accomplishments of the Hydra-in-a-Box project, the 30-month effort by Stanford Libraries, DuraSpace, and the Digital Public Library of America with funding from the IMLS.
A presentation given at Samvera Connect 2017 described thus and In this session we will give a quick background of Hyrax and offer a status update on current Hyrax work including the 2.0.0 release and the new testing process for releases. We will also discuss our early plans for the 2.x series of releases including updates on Collection Extensions work, Valkyrie sprints, plans for new Analytics features, and other potential work in the 2.x series. Last, we’ll talk broadly about roadmapping for Hyrax and what we might expect from Hyrax 3.0.0 and beyond.
Want to move beyond a simple autocomplete field for controlled vocabularies? Want a more accurate selection process? We will look at a Hyrax demo app that uses questioning authority to search linked data authorities and extracts multiple predicate values from search results to provide additional context in a lookup table to help with the selection process from a controlled vocabulary. The presentation will include direct access to OCLC Fast, locally cached access to Library of Congress and GeoNames, as well as others. and A presentation given at Connect 2017 originally advertised as "Lookup with Context to select metadata values from a controlled vocabulary" and described thus
A presentation given at Connect 2017 described thus and The University of Cincinnati recently migrated our Scholar@UC application from Sufia 7.3 to Hyrax 1.0. We will discuss our process and the special circumstances we had to deal with.
Flexible approaches to grouping things in the repository" and described thus, An introduction to the Hyrax 2.1 Collections which include collections extensions, once known as Display Sets. This implementation adds the ability to define collection types with various settings to meet the many use cases for collections from user collections to exhibits. We'll also look at how these play nicely with Admin Sets., and A presentation given at Connect 2017 advertiosed under the title "Collections Extensions and Admin Sets
A presentation given at Connect 2017 described thus and Presentation on a gem for Hyrax models and authorities, which provides a central place for creating models for different types of works. Each new model draws on a central pot of properties to declare the set of properties needed to fully describe the particular work. The gem already exists and has sample models for journal article, thesis and more. In this presentation we will work through the process of defining a new model and then using that model in a Hyrax application. The idea behind the gem is to make it easier for developers to deploy new models, and provide a place for metadata folks to jointly define re-usable models.
A presentation given at Connect 2017 described thus and How can presentation layers in Hyrax applications be extended to fit local needs? This session will showcase two front-end implementations of Hyrax for institutional repositories and discuss design decisions we made for specific use-cases.
A presentation given at Connect 2017 described thus and With so many Samvera metadataists managing similar objects and collections, can we get a handle on the metadata we have and what we share with the community? This session will introduce the idea behind the Documentation Project from the Samvera Metadata Interest Group and will consider what we're saying about our objects, how we're expressing it, and how best to move this work forward to provide suitable context for what we do or don't want our MAPS to look like as we document our work within Samvera.
A presentation given at Connect 2017 described thus and Princeton University Library has spent the last two years developing Plum as a staff-only ingest platform for books, manuscripts, geo-spatial data, and archived ephemera. This talk would go through a history of the design goals, the successes we've had, the problems we've run into, and a look into the future.
A presentation given at Connect 2017 described thus, it’s not fun to have an ingest fail overnight and spend the morning tracking down why. Programmatically testing and validating digital object metadata prior to ingest helps us avoid these failures. The metadata itself is managed by Git and stored in GitHub, Several years ago UCSB incorporated Git/GitHub and JIRA into our metadata management and batch ingest workflows. Since then we’ve looked at repurposing other development tools to provide lightweight and automated solutions to problems we often face. One is that we rely primarily on batch ingests when adding content to our Samvera repository. As a result it’s especially important for the metadata to be error-free, and this allows us to run automated checks against any changes using Jenkins and some custom libraries we’ve written for validating CSV and MODS metadata. In this session, we will provide an overall of our current ingest preparation workflow and the tools we are using, and will discuss some of the benefits that have come out of this collaborative effort.
A presentation given at Connect 2017 described thus, Michigan's Research Data Repository has been in production since Feb 2016. Presentation on experiences and challenges of transitioning from Sufia to Hyrax, and adding new features and running the service over the past year.
A presentation given at Connect 2017 described thus and Over the past 5 years ScholarSphere has been released 100 times. We will look back at those 100 releases to categorize the releases. I will then share lessons that I have learned through the process of releasing ScholarSphere.
A presentation given at Connect 2017 described thus and In this presentation, we present Fedora 4’s performance in different use cases. These use cases are the most general use cases that were developed by the Fedora 4 performance team. We compare the performance between different versions of Fedora 4 and demonstrate the improvement between these versions. We will also describe the procedures of these performance experiments and demonstrate the software we use (Ansible, AWS, and JMeter). Our performance experiments are conducted in the AWS ecosystem, and we use an R graph tool to visualize the JMeter result. With the AWS grant, we can do many different performance experiments in many scales. Moreover, it is easy to repeat and verify the performance results using AWS. The Fedora 4 performance team wants to know more about the Samvera community’s interests related to the Fedora 4 performance. We plan to gather more use cases from the Samvera community, including middleware such as Solr, Camel, and Fuseki, etc. We can investigate, explore issues, and continue enhancing the future of Fedora 4.