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
//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