The current user interface consists of two
We describe each phase in turn.
1 employs the following autonomous Web Services:
KEGG find (K-Find) Web Service: It takes the term and
species parameter and call the find webservice provided by the KEGG
which then returns the list of matching records.
NCBI e-search (N-eSearch) Web Service.
It also takes the term and species and retrieves the matching
record list by using the URL retrieval in XLM format.
results of these two web services are combined using Sangam’s internal
Web Services. These are:
Branch, Iterator, IUnion, and Join.
The plan that consists of these operators along with the
autonomous Web Services is as follows:
Services provide the following functionalities.
user employs an interface to specify those DNAs (from KEGG) and Proteins
(from NCBI) of interest. This
list is submitted to Phase 2 of the system, which employs the following
external Web Services:
KEGG Get (K-Get) webservice: It uses the Get webservice
supported by KEGG to returned the detailed information about all the
records by the users
NCBI eFetch (N-eFetch) webservice: It uses the eFetch URL
utility provided by the NCBI to get the information of all the selected
records in the XML format.
Once again, phase 2 employs Sangam’s internal
Web Services as glue to combine these autonomous Web Services together.
In addition to the autonomous webservices used in Phase1, Phase 2 uses
one more autonomous webservice called Project.
Project Operator (P):
it is placed in between the Branch and Iterator webservice so that it
filters out record-ids irrelevant for the particular branch (e.g. in the
above diagram P2 will filter out all the records returned by K-Find