Data Sources Specification

Overview

The Data Sources Subsystem constitutes the framework we provide in order to integrate heterogeneous data from different providers in our Information Retrieval(IR) 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

Unification of heterogenous Data and different IR capabilities

Using the CQL standard, different gCube IR providers that host data with diverse representations and semantics, can be involved the overall IR process.

Indexing Layer for advanced IR functionality

Full-text retrieval, Multidimensional Range queries and Spatiotemporal search functionality

Access to the information hosted by external Providers

External providers can provide their results during the IR process through the OpenSearch standard.

Design

Philosophy

The Data Sources framework is implemented in order to:

• simplify the integration of different IR providers in the gCube IR framework, using the appropriate standards.
• provide Replication and High Availability through a distributed architecture.
• exploit the information and IR capabilities of external providers.

Architecture

The Data Sources framework is composed by the Index and OpenSearch Systems. The architecture is depicted in the following figure:

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.