| Literature DB >> 17760972 |
Kathrin Klee1, Rebecca Ernst, Manuel Spannagl, Klaus F X Mayer.
Abstract
BACKGROUND: Apollo, a genome annotation viewer and editor, has become a widely used genome annotation and visualization tool for distributed genome annotation projects. When using Apollo for annotation, database updates are carried out by uploading intermediate annotation files into the respective database. This non-direct database upload is laborious and evokes problems of data synchronicity.Entities:
Mesh:
Year: 2007 PMID: 17760972 PMCID: PMC2001201 DOI: 10.1186/1471-2105-8-320
Source DB: PubMed Journal: BMC Bioinformatics ISSN: 1471-2105 Impact factor: 3.169
Figure 1Apollo web service adapter overview. To load data into Apollo the Apollo GUI calls the web service adapter GUI, which calls the web service adapter. The web service adapter invokes the web service client that communicates with the web service. The web service is deployed on an in house server that directly accesses the database. The database returns the information of interest to the web service and the web service returns it to the web service adapter. The web service returns the information as a GameXML formatted String and the GAME-XML adapter transforms the information into Apollo readable format. Subsequent the information can be loaded from the web service adapter into the Apollo main window. To write data back into the database or in a flat file the web service adapter receives the information as CurationSet from Apollo. This CurationSet will be send to the GAME-XML adapter to retrieve a GameXML formatted string, which can be transferred to the web service. The web service directs the information into the database or in a dedicated flat file.