Difference between revisions of "Search Orchestrator"
From Gcube Wiki
(→Search Orchestrator) |
(→Search Orchestrator) |
||
| Line 1: | Line 1: | ||
== Search Orchestrator == | == Search Orchestrator == | ||
| − | The Search Orchestrator is the entry point for the information retrieval services provided in a gCube infrastructures. Implemented as a gCube web service, it is responsible for applying each stage in the chain of stages that compose the query answering process. The first stage in this chain, is the parsing of a submitted query. [http://www.loc.gov/standards/sru/specs/cql.html Contextual Query Language] parsing is performed by the [[gCQLParser]]. | + | The Search Orchestrator is the entry point for the information retrieval services provided in a gCube infrastructures. Implemented as a gCube web service, it is responsible for applying each stage in the chain of stages that compose the query answering process. The first stage in this chain, is the parsing of a submitted query. [http://www.loc.gov/standards/sru/specs/cql.html Contextual Query Language] parsing is performed by the [[gCQLParser]]. Then a number of predefined preprocessors will be applied to the CQL query tree, resulted from the parsing stage. Preprocessors can apply static rules to rewrite the query in an equivalent form, or enhance the query for semantic and personalization purposes. The next stage comprizes the planning phase. |
Revision as of 13:29, 22 July 2011
Search Orchestrator
The Search Orchestrator is the entry point for the information retrieval services provided in a gCube infrastructures. Implemented as a gCube web service, it is responsible for applying each stage in the chain of stages that compose the query answering process. The first stage in this chain, is the parsing of a submitted query. Contextual Query Language parsing is performed by the gCQLParser. Then a number of predefined preprocessors will be applied to the CQL query tree, resulted from the parsing stage. Preprocessors can apply static rules to rewrite the query in an equivalent form, or enhance the query for semantic and personalization purposes. The next stage comprizes the planning phase.
