You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

Description

The Fedora-Kepler Integration demonstration project is an investigation of methods of interaction between the Kepler Scientific Workflow Engine and a Fedora Commons Repository.

It is recommended that you read the Kepler product analysis page before continuing. It will provide a basic understanding on Kepler terminology and the issues encountered.

The Fedora-Kepler investigation was performed by Rick Moore for Fedora Commons and the Cornell University Library. Funding for this project was provided under a grant from the Mellon Foundation.

Project Components

Fedora Digital Repository

The project used Fedora Repository V3.2.1, released May 8, 2009. It is available from Fedora Commons at http://www.fedora-commons.org/software/current.

Kepler Scientific Workflow

Kepler is a java-based application for building and executing scientific workflows. It is a product of the Kepler Project originated by UC Davis, UC Santa Barbara, and UC San Diego. A detailed analysis of Kepler is available on the Kepler Scientific Workflow Engine page. That page also contains information on downloading Kepler and navigating it's documentation maze.

JyFedoREST

JyFedoREST is a Jython package for creating and managing objects in a Fedora Repository. It is a minimal Jython wrapper around V3.2.1 of the Fedora REST API. It is described in detail on it's own project page.

FCRepoKepler package

FCRepoKepler is a Jython package containing a few helper classes that make life easier when developing actors for Kepler. The project page contains complete documentation of the classes available in the package.

Test Case - REST API

Several actors and workflows were developed to test Fedora's REST API from within Kepler. They are described in detail on the REST API Tests page.

Test Case - DataSTAR

DataSTAR is a Cornell Library initiative aimed at providing a staging archive for scientific data that is to be shared among several collaborators, both within the Cornell community and external to it.The actors and workflows developed for this part of the project are descibed in detail on the DataSTAR Use Case page.

  • No labels