Yes! Another Blacklight mapping plugin! This one is super cool with features like performant Solr clustering, indexing multiple types of geometry (bounding boxes and points!) This is an audio recording of the session. and A lightning talk presentation at Hydra Connect 2016 described thus
Keyword:
Blacklight, Connect 2016, Hydra, and Lightning talk
Using Sufia 7 as a reference model, what does the path for depositing a new item into a Hydra/PCDM based repository look like from an end-user, code, console, solr, and fedora perspective, A presentation given at Hydra Connect 2016 described thus, show the upload of new digital content via the Sufia UI and show each step of the data flow in the Browser, rails console, and Fedora. Walk through derivative generation and show the various PCDM relationships being built at each stage. Then add a new user collection, and walk through the same flows as a work is added to a collection, and what gems are in play, what does the data look like from a ruby developer perspective, what is persisted in Fedora and Solr - how does it all relate to PCDM? A video of this session is available at the 'Related URL' below.
Keyword:
Connect 2016, Hydra, Portland Common Data Model (PCDM), and Sufia
Migrating a Fedora 3-based Hydra repository to Fedora 4 can be a major undertaking. This panel will bring together representatives from multiple institutions that either are planning for, are in the midst of, or have completed such a migration. Depending on where they are in the migration process, panelists will talk about their plans for migration, techniques used or expected to be used, obstacles anticipated or encountered, how problems were addressed, and migration outcomes. It is hoped that the presentations and discussion will be useful to other Hydra sites planning such a migration. A video of this session is available at the 'Related URL' below. and A presentation given at Hydra Connect 2016 described thus
Keyword:
Fedora, Connect 2016, Hydra, and Migration
Subject:
Hydra Project
Creator:
Coble, Jim, Wead, Adam, Hardesty, Juliet L, and Friscia, Mike
Follow-up to last year's presentation about Columbia's Hyacinth editor. Lots of changes / progress since the last presentation. Many TODOs have been TODONE. Hyacinth is a metadata editor, batch Fedora ingest tool and content publishing application that is becoming more and more integrated into our digitization, cataloging and front-end presentation workflows. Built on top of Hydra, but not Blacklight, with a JavaScript-and-AJAX-heavy front-end for many search/editing features. Currently Fedora 3, but hopefully moving toward Fedora 4 early next year. Still under development with additional planned features. I'd love to present and get feedback. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016 described thus
The Hydra-in-a-Box team in conjunction with Princeton has added IIIF image and presentation API support to Hydra. Come see how we're going farther together with open APIs. A video of this session is available at the 'Related URL' below. and A lightning talk presentation given at Hydra Connect 2016 described thus
Keyword:
International Image Interoperability Framework (IIIF), Connect 2016, Hydra in a Box, Hydra, and Lightning talk
We encountered big performance hurdles with our Sufia6 based application HydraNorth, and this is a quick overview of tools we used to help us monitoring and profiling the performance of our application, and restoring sanity to our team. A video of this session is available at the 'Related URL' below. and A lightning talk presentation given at Hydra Connect 2016 described thus
An overview of the Jisc Research Data Management Shared Service initiative in the UK, looking to establish a set of infrastructural components that academic institutions can combine to provide an overall RDM solution. Hydra has been shortlisted as one of the repository components that an initial group of pilot institutions can use. A video of this session is available at the 'Related URL' below. and A lightning talk presentation at Hydra Connect 2016 described thus
Keyword:
Connect 2016, Research data management, Jisc, Hydra, and Lightning talk
A presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, provide an update on progress to date, At the University of Alberta Libraries we are currently developing a Digital Asset Management System (‘Hydra North’, built on Hydra and Fedora 4) to bring all of our digital assets into one platform for discovery, access and preservation. The metadata underlying these repositories has been created according to many standards (DC, MODS, EAD, etc.) and varies in level of fullness and overall quality. We find ourselves at a ‘metadata crossroads’ as we attempt to bring this disparate metadata together. We see a solution in a move to RDF and the application of the principles of linked data. In this presentation we will discuss some of the initial questions we asked ourselves as we tried to fully grasp what the move to RDF and linked data would mean for our existing metadata, provide concrete examples of the thought processes and workflows involved in moving from existing non-RDF metadata to RDF, based on the principles of linked data, outline some of the decisions we made along the way, and why, and what the impact has been, and reflect on lessons learned and outline next steps.
Keyword:
Metadata, Resource Description Framework (RDF), Hydra, Open Repositories 2015, and Fedora
A proposal for a presentation given at the Open Repositories conference in 2015 held in Indianapolis described thus, One of the many successes of the Hydra community is the fundamental notion from which its name is derived—the concept of many interfaces (“heads”) over top of a single repository (the “body”). The recent release of Fedora 4, with its internal RDF-centric model, has spurred efforts for a community-wide model of collections and works, such that the heads can be sure that the body will behave as they expect it to. That model has been designed and vetted by the Hydra community, and its architecture and initial implementations will be presented in this paper. [Note, and the subject of this proposal has since become known as the 'Portland Common Data Model'.]
Keyword:
Community, Data model, Resource Description Framework (RDF), Hydra, Portland Common Data Model (PCDM), Open Repositories 2015, and Fedora
Subject:
Hydra Project
Creator:
Stroop, Jon, Sanderson, Rob, and Cowles, Esmé
Contributor:
University of California San Diego, Princeton University, and Stanford University
however, library enduring commitments in print and current operations, and complex campus organizations often hinder libraries¹ ability to quickly respond to the data needs of the academy. Notre Dame¹s investment in research was recently reinforced by the university¹s approval of the expansion of ten disciplines, such as computational data, adult stem cell research, and nuclear physics. There is much needed support for research data on campus. The Hesburgh Libraries has been building an institutional digital repository since winter 2012. To respond to the trending needs, the Libraries switched gears to a user-centered and agile approach to develop data curation and access services since June 2013. Our goal remains to accept all scholarly outputs (text, images, video and audio), but with an imminent emphasis on research support. Our strategy is to grow our data curation services and our user base simultaneously, and to build success stories to drive adoptions along the way. Early adopters were identified with the help of our subject librarians, and they determined the most critical baseline features for the Libraries to develop. We also leveraged Hydra open source solutions and collaborated with Northwestern University, Indiana University, and the University of Virginia to create a new community shared Institutional Repository (IR) system. We have worked with our early adopters to pilot features since summer. We plan to launch an early access release by November 2013 and a full rollout by April 2014. We will share our development philosophy to overcome resource shortages to meet high demands on research support, our strategy to reach and develop our user base and roadmap, our insights on faculty¹s needs on research support, and our methodology to leverage and contribute to open source tools. A quick demo of our curation tool will be provided at the end of the session. and A presentation to the CNI Members' Meeting in December 2013. This session provides Notre Dame¹s experience as a case study to provision research data curation and access services. Managing research outputs becomes a tall order of many universities, given their determined agenda to pursue research excellence. In a world of increasingly data-intensive research, data is rising as a critical component of scholarly communication, often mandated by granting agencies. Data curation, preservation, and access are paramount to university academic mission, and academic and research libraries are some of the few entities of the universities that carry such functions
Keyword:
Fedora, Collaboration, Architecture, Research data management, Hydra, ORCID, Community, and DuraSpace