Page tree
Skip to end of metadata
Go to start of metadata

What is the Enterprise Search UI?


For search and big data analytics projects, the Enterprise Search UI is composed of a collection of search engine-independent technology assets. These can help improve search development for repeatable use cases, accelerate project timelines, and reduce overall project costs. The Enterprise Search UI provides an optimized architecture for search and big data applications.

The Enterprise Search UI provides an end-to-end search system featuring:

  • Content acquisition and processing?
  • Search?
  • User interfaces
    • End user?
    • Administration?
    • Business?

What does the Enterprise Search UI do?

  1. Checks all applications and runs the plugins.

  2. Provide links.

  3. Use a dedicated thesaurus (including definitions, concepts, query, and help documentation).

Why??

  • Fill in the gaps in Open Source search engine platforms?

  • Create a working system in days (not weeks)?

  • Show business value quickly

Text  ↔  Concept

a. Publish thesaurus

      • to a file
      • (export) to Mongo DB

b. File name (thesaurus.txt) download and publish


An End-to-End Search System


Deploy on-premise or in the cloud or a hybrid

You can choose from the available components. The end-to-end total solution includes content acquisition & processing and search with:

  • The end user interface includes full source code for search-based applications.
  • A "pluggable" administration / business user interface so administrators can install, administer components, run health checks, and manage servers. The business user can access a thesaurus editor, best bets, and formula weightings.

The search stack contains open source and commercial components

You can create a search solution that is customized to your specific requirements. This reduces your solution time-to-delivery and your long term total cost of ownership. Create a working system in days (instead of weeks).

Open Source Components & ST Assets


Open Source Components 

  • Search engine - Elasticsearch
  • Node.JS application server - for the API
  • MongoDB - for the Staging Repository, user data, and management
  • Angular.JS & Bootstrap interface - for end users


ST Assets

  • Aspire - for content acquisition and processing
  • Staging Repository - for content reprocessing, index-time joins, and enrichments
  • Query Processing Language - for query processing

Optional

  • Premium connectors