A presentation given at the joint meeting of the Fedora UK and Ireland, and the Fedora EU User Groups on 8th December 2009 in Oxford. The presentation describes the 'simple yet flexible' approach of the Hydra partners.
Powerpoint presentation given at Open Repositories 2009 (OR09) in Atlanta, GA, 20 May 2009 describing the different workflow strategies being developed in the Hydra Project.
Between April 2005 and March 2009, the e-Services Integration Group at the University of Hull undertook two Joint Information Systems Committee (JISC)-funded projects, RepoMMan and REMAP. The RepoMMan tool developed a browser-based interface through which a user could interact with a private digital repository space to support the development of their works-in-progress. It went on to look at the processes involved in publishing such works to a public-facing repository and to investigate the possibility of generating metadata for the published object automatically. The follow-on REMAP Project implemented the publishing process and also investigated how triggers might be embedded in the objects that were created that would help with management and possible preservation of the object over time. The work of RepoMMan and REMAP has now been taken up in an international collaboration, the Hydra Project, which seeks to develop a repository-enabled "Scholars' Workbench". This will be a highly flexible system that will provide a search and discovery interface for a Fedora repository and that can be configured to provide interactive workflows around it for pre-publication development of materials and their post-publication management.
This article centres on the recently completed REMAP Project undertaken at the University of Hull, which has been a key step toward realising a larger vision of the role a repository can play in enabling and supporting digital content management for an institution. The first step was the Joint Information Systems Committee (JISC)-funded RepoMMan Project that the team undertook between 2005 and 2007. The second step has been the REMAP Project itself, a key component of a university's information management. In this vision the institutional repository provides not only a showcase for finished digital output, but also a workspace in which members of the University can, if they wish, develop those same materials." This remains the case but with REMAP we added in notions of records management and digital preservation (RMDP) once the materials were placed in the repository. Thus the repository can play a key part throughout the lifetime of the content. It turns out that others share this vision of repository-enabled management over the full lifecycle of born-digital materials, a concept that some are calling the "scholar's workbench". (Others are calling it the "scholars' workbench", Hull uses the Fedora repository software, its development is undertaken by the not-for-profit organisation Fedora Commons. Hull will also be working with King's College London on the CLIF project to December 2010, work that will run in parallel with and complement Hydra. In the Ariadne article describing the work of RepoMMan we wrote, "The vision at Hull was, and is, of a repository placed at the heart of a Web Services architecture, the community has not yet decided quite where the apostrophe belongs!), and JISC-funded again, this second two-year project further developed the work that RepoMMan had started. The third step, more of a leap maybe, is a three-year venture (2008-11), the Hydra Project, being undertaken in partnership with colleagues at Stanford University, the University of Virginia and Fedora Commons
A webinar given by Tom Cramer for the DuraSpace 'Hot Topics' series in 2012. A recording of the webinar is available by following the 'Related URL' link below.
• No single institution can resource the development of a full range of digital content management solutions on its own, …yet each needs the flexibility to tailor solutions to local demands and workflows. • No single system can provide the full range of repository‐based solutions for a given institution’s needs, *…yet sustainable solutions require a common repository infrastructure The Hydra project has tested out these assumptions and reports in this presentation the outcomes from applying them to the work undertaken. The paper was delivered as a 'Prezi' presentation which can be found by following the 'Related URL' link below., The proposal for this presentation at the Open Repositories conference in 2011 begins, and The Hydra project is a digital repository initiative started in 2008 that originally brought together three institutions (Stanford University, the University of Virginia and the University of Hull) and DuraSpace, with a common identified need to provide a flexible means for managing and delivering a wide range of digital content types. The project has since investigated and worked towards a reusable framework for multipurpose, multifunction, multi‐institutional repository‐enabled solutions. Two previously identified assumptions have underpinned the work
A presentation at the Open Repositories conference in 2014. There are those who perceive that implementing, running and maintaining a Fedora-based digital repository is a daunting task suited only to institutions with a significant team of developers and support staff. This paper offers a different perspective. The University of Hull in the UK, the Rock and Roll Hall of Fame and Museum in Cleveland, Ohio, and the Chinese Historical Society of Southern California (CHSSC) provide three case studies of Hydra-based repositories that are centred on a single developer working with small, limited or no support. This talk will compare and contrast their experiences and explain why the developers concerned feel that creating and maintaining these successful repositories has been worth their time and effort.
A lightning talk at Samvera Virtual Connect 2016. The talk was in two parts with the second given by Matthew Phillips of Durham University. Unfortunately, his slide deck is missing from the archive.
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 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
//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
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
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
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.
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
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 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
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 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 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.
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 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.
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 presentation at Hydra Connect 2015 about integrating RDF with Hydra for discoverability and presentation. Trey Pendragon, at the time, was known as Trey Terrell.
A poster describing a possible workflow for using the open source software Archivematica to provide preservation functionality alongside the University of Hull's Hydra repository. Prepared for Hydra Connect 2015 in Minneapolis, MN, September 2015
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