Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The VIVO and Fedora FEDORA communities have recognized their potential complementarity for some time, as is natural given the origins of both in the library community. These discussions have typically focused either on ways Fedora could complement a typical VIVO or in return on how VIVO could complement a typical Fedora repository.

  • The Datastar project from 2008-2010 at Cornell illustrated the use case of Fedora complementing VIVO by providing a repository for storing datasets uploaded to Fedora through VIVO. A customized VIVO provided an editing and discovery interface for dataset metadata, while Fedora provided repository functions for the dataset itself, such as support for dataset download and versioning.
  • Institutional repositories such as UR Research at the University of Rochester sometimes feature pages for the researchers themselves, in addition to repository collections and resources, to support browsing by researcher and to provide an extra incentive for uploading content. While not powered by either Fedora or VIVO, UR Research illustrates another straightforward use case for Fedora-VIVO interoperability.

With the rapid growth of the The Hydra community Project and the transition from Fedora 3 to Fedora 4 and with its greater emphasis reliance on RDF there new opportunities for closer connections between VIVO and Fedora, both at the Vitro (software only) and VIVO (software plus ontology plus ontology-related customizations to Vitrocustomization) levels.

A number of platforms could potentially be involved:

  • Sufia
  • Blacklight
  • Apache Solr
  • Apache Camel
  • W3C Linked Data Platform
  • Linked Data for Libraries use cases

Children Display