Databases

Various projects and researchers use Taverna to access, collate and manipulate data from databases:

eFamily

The eFamily project was designed to integrate the information contained in five major protein databases. The project developed webservices to allow the calculation of results based upon the content of several databases, and upon annotation of the data.

The project made use of Taverna workflows to integrate the webservices, both those provided by the eFamily project and those developed externally.

Publications

Some details of this work are given in the http://www.allhands.org.uk/2004/proceedings/papers/211.pdf eFamily: Bridging Sequence and Structure by Finn et al.

EMBRACE

EMBRACE is the European Model for Bioinformatics Research And Community Education (EMBRACE). It consists of a large number of partners throughout Europe

The objective of EMBRACE is to draw together a wide group of experts throughout Europe who are involved in the use of information technology in the biomolecular sciences.
The EMBRACE Network of Excellence will optimise informatics and information exploitation by pure and applied biological scientists in both the academic and commercial sectors.

The University of Manchester is a member of the EMBRACE project, and the Taverna Workbench has been adopted by EMBRACE as its workflow system of choice.

The suitability of Taverna Workbench has been confirmed by its use in several test cases:

The tGRAP work is described in the document The reincarnation of the tGRAP database by Vroling.

Use of Taverna allows the members of EMBRACE to have ready access to the existing bioinformatics services and also to the myGrid team’s expertise in this area. Correspondingly, the members of EMBRACE represent a diverse group of users with different backgrounds and infrastructure.

omixed

omixed is a “customisable storage system for scientific data, completely managed via web services”. Its developers have written a Taverna 1.7.x plugin to allow users to access data.

The plugin “provides two endpoints giving full control of omixed resources. The first endpoint, known as the server endpoint, is designed for most users who want to browse, download, or add to or modify existing resources. The second point, known as the admin endpoint, is designed for administrators to create and delete resources, assign schema to them, and modify user privileges.”