Difference between revisions of "Data Sources Specification"
(→Overview) |
(→Key features) |
||
| Line 10: | Line 10: | ||
: Full-text retrieval, Multidimensional Range queries and Spatiotemporal search functionality | : Full-text retrieval, Multidimensional Range queries and Spatiotemporal search functionality | ||
| − | ;Unification of heterogenous Data and different IR | + | ;Unification of heterogenous Data and different IR facilities |
: Using the | : Using the | ||
Revision as of 19:58, 2 March 2012
Contents
Overview
The Data Sources Subsystem constitutes the framework we provide in order to integrate heterogeneous data from different providers in our Information Retrieval process. Using an Indexing Layer and the OpenSearch standard, Data Sources framework provides fast access and direct connection to the information hosted in the heterogeneous environment.
Key features
- Indexing Layer for advanced IR functionality
- Full-text retrieval, Multidimensional Range queries and Spatiotemporal search functionality
- Unification of heterogenous Data and different IR facilities
- Using the
Design
Philosophy
This is the rationale behind the design. An example will be provided.
Architecture
The main software components forming the subsystem should be identified and roughly described. An architecture diagram has to be added here. A template for the representation of the architecture diagram will be proposed together with an opensource tool required to produce it.
Deployment
Usually, a subsystem consists of a number of number of components. This section describes the setting governing components deployment, e.g. the hardware components where software components are expected to be deployed. In particular, two deployment scenarios should be discussed, i.e. Large deployment and Small deployment if appropriate. If it not appropriate, one deployment diagram has to be produced.
Large deployment
A deployment diagram suggesting the deployment schema that maximizes scalability should be described here.
Small deployment
A deployment diagram suggesting the "minimal" deployment schema should be described here.
Use Cases
The subsystem has been conceived to support a number of use cases moreover it will be used to serve a number of scenarios. This area will collect these "success stories".
Well suited Use Cases
Describe here scenarios where the subsystem proves to outperform other approaches.
Less well suited Use Cases
Describe here scenarios where the subsystem partially satisfied the expectations.
