[
https://issues.apache.org/jira/browse/STANBOL-470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13194533#comment-13194533
]
Ali Anil Sinaci commented on STANBOL-470:
-----------------------------------------
This issue is resolved through the following features and improvements:
- Search logic has been implemented from scratch.
* Search engine pattern has been removed for document search.
* Content items are indexed through Solr cores. Therefore all search on the
content items are performed through Solr indexes.
* Search interface has been splitted into there different interfaces:
SolrSearch, RelatedKeywordSearch and FeaturedSearch.
* SolrSearch is compatible with SolrJ. That is, clients who have already
been using SolrJ can easily switch to SolrSearch API of Contenthub. As a result
of LDPath integration, additional methods exist in this interface to accept
LDPath program names (Solr core names). There is a single implementation of
this interface in Contenthub.
* RelatedKeywordSearch exposes a "search engine" pattern, but only to
search for related keywords. RelatedKeywordSearchManager is the manager to
handle several implementations of this interface (engines).
* In addition to the search results retrieved from SolrSearch, users can
now send their search keywords (query terms) to RelatedKeywordSearchManager to
retrieve related keywords from different sources. This can be performed as a
separate process from SolrSearch.
* RelatedKeywordSearch has been implemented by WordnetSearch,
OntologyResourceSearch and ReferencedSiteSearch. As their names indicate, they
look for related keywords within their resources. (WordnetSearch can be
excluded until the license issue is resolved or a new client library is used)
* FeaturedSearch combines the capabilities of SolrSearch and
RelatedKeywordSearch in case a client wants to retrieve all results (content
items and related keywords) from Contenthub search.
* FeaturedSearch provides a similar interface to SolrSearch with additional
methods. However, behaviour is different, it is "featured" in this
implementation.
* FeaturedSearch provides a special method: tokenizeEntities. This method
takes a query string and finds out whether there exists any entities in the
query or not. Based on the discovered entities, FeaturedSearch prepares Solr
queries in special formats to boost the results related with the entities.
However, this method should be improved to cover a massive number of possible
cases which can occur during keyword searches.
* FeaturedSearch provides special methods to ease the faceted search. Web
GUI of Contenthub makes use of this interface to enable faceted search.
> New search interface for Contenthub
> -----------------------------------
>
> Key: STANBOL-470
> URL: https://issues.apache.org/jira/browse/STANBOL-470
> Project: Stanbol
> Issue Type: New Feature
> Components: Content Hub
> Reporter: Ali Anil Sinaci
>
> SolrJ interface should be exposed so that Contenthub can easily be adopted by
> "already Solr users".
> Additional features of Contenthub should also be exposed for adopters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
