Difference between revisions of "SRU Facilities"
From Gcube Wiki
(→Introduction) |
|||
| Line 11: | Line 11: | ||
*Providing gCube datasources to others: | *Providing gCube datasources to others: | ||
**gCube SearchSystem can be used by others | **gCube SearchSystem can be used by others | ||
| + | |||
| + | |||
| + | In order to utilize the above benefits we have developed the following components: | ||
| + | *an SRU consumer service that is used in order to exploit external SRU providers | ||
| + | *an SRU adapter service for RDBMSs that is used in order to provide SRU capabilities to RBMSs | ||
| + | *an SRU adapter service for SearchSystem that is used in order to provide SRU capabilities to gCube SearchSystem | ||
Revision as of 13:24, 17 July 2014
Introduction
The SRU components have been created in the context of the Federated Search[link to wiki page]. Federated Search has the following benefits:
- Search space is expanded as new datasources come in
- The complexity of search and index to the datasource providers
By enabling Federated Search gCube can benefit by:
- Getting more external sources:
- External providers that comply with SRU can be used directly as external datasources
- External providers that do not comply with SRU can be used indirectly as external datasources through SRU Adapters
- Providing gCube datasources to others:
- gCube SearchSystem can be used by others
In order to utilize the above benefits we have developed the following components:
- an SRU consumer service that is used in order to exploit external SRU providers
- an SRU adapter service for RDBMSs that is used in order to provide SRU capabilities to RBMSs
- an SRU adapter service for SearchSystem that is used in order to provide SRU capabilities to gCube SearchSystem
