GETTING STARTED
SearchAssist Overview
SearchAssist Introduction
Onboarding SearchAssist
Build your first App
Glossary
Release Notes
What's new in SearchAssist
Previous Versions

CONCEPTS
Managing Sources
Introduction
Files
Web Pages
FAQs
Structured Data 
Connectors
Introduction to Connectors
SharePoint Connector
Confluence Cloud Connector
Confluence Server Connector
Zendesk Connector
ServiceNow Connector
Salesforce Connector
Azure Storage Connector
Google Drive Connector
Dropbox Connector
Oracle Knowledge Connector
DotCMS Connector
RACL
Virtual Assistants
Managing Indices
Introduction
Index Fields
Traits
Workbench
Introduction to Workbench
Field Mapping
Entity Extraction
Traits Extraction
Keyword Extraction
Exclude Document
Semantic Meaning
Snippet Extraction
Custom LLM Prompts
Index Settings
Index Languages
Managing Chunks
Chunk Browser
Managing Relevance
Introduction
Weights
Highlighting
Presentable
Synonyms
Stop Words
Search Relevance
Spell Correction
Prefix Search
Custom Configurations
Personalizing Results
Introduction
Answer Snippets
Introduction
Extractive Model
Generative Model
Enabling Both Models
Simulation and Testing
Debugging
Best Practices and Points to Remember
Troubleshooting Answers
Answer Snippets Support Across Content Sources
Result Ranking
Facets
Business Rules
Introduction
Contextual Rules
NLP Rules
Engagement
Small Talk
Bot Actions
Designing Search Experience
Introduction
Search Interface
Result Templates
Testing
Preview and Test
Debug Tool
Running Experiments
Introduction
Experiments
Analyzing Search Performance
Overview
Dashboard
User Engagement
Search Insights
Result Insights
Answer Insights

ADMINISTRATION
General Settings
Credentials
Channels
Team
Collaboration
Integrations
OpenAI Integration
Azure OpenAI Integration
Custom Integration
Billing and Usage
Plan Details
Usage Logs
Order and Invoices

SearchAssist APIs
API Introduction
API List

SearchAssist SDK

HOW TOs
Use Custom Fields to Filter Search Results and Answers
Add Custom Metadata to Ingested Content
Write Painless Scripts
Configure Business Rules for Generative Answers

Semantic Meaning

Semantic analysis is the technique to understand the meaning and interpretation of words, signs, and sentence structure.

SearchAssist’s Index pipeline supports a Semantic Meaning stage. This stage uses Deep Neural Network algorithms to create embeddings of free text and saves them in a dense vector field. These embeddings are used to rank the documents by semantic relevance. The dense vectors are then indexed in the ElasticSearch and similarity is obtained between the user’s query vector and the indexed content vector.

You can:

  • Add multiple semantics to be analyzed from the source field.
  • Define a condition for the semantic meaning stage. The semantics from only the documents that satisfy the given condition would be analyzed.
  • Re-order or delete semantic meaning rules.
  • Simulate the changes before saving them.

Ensure to Train your app each time you make changes to any index configuration. This builds the index based on the updated configurations.

Configuration

To configure semantic meaning, follow the below steps:

  1. Click the Indices tab on the top.
  2. On the left pane, under the Index Configuration section, click Workbench.
  3. On the Workbench (Index Configuration) page, on the Stages column, click the + icon.
  4. On the right column, select Semantic Meaning from the Stage Type drop-down list.
  5. Enter a name in the Stage Name field.
  6. Enter a condition in the Condition field. You can add multiple conditions using the AND/OR connectors. Documents that satisfy the condition will be executed as part of the stage. See below for details.
  7. Select the field you want to extract Semantic Meaning from as Source Field.
  8. Define where you want to store the extracted Semantic Meaning as Target Field. This field is created by the application.
  9. Choose a model from the Choose Model drop-down list. See below for details.
  10. Click Simulate to verify the configurations. The simulator displays the Source and the number of documents to which the mapping was applied, and the result. You can change the Source (if not mentioned in the condition) and the number of documents.
  11. Once done, click Save Configuration on the top-right.

Models

The following models are supported:

  • Universal Sentence Encoder – It encodes text into high-dimensional vectors that are used for semantic similarity.
  • Sentence Transformers – It is a framework for sentence and text embeddings.
  • InferSent – It is a sentence embedding method that provides semantic sentence representations.

Conditions

Condition is of the following format: ctx.fieldtype==value or ctx.fieldtype!=value. The field_name can be obtained from the Fields table under Index Configuration.

For example, ctx.contentType=="web" to restrict the extraction to the content from a web source.

Semantic Meaning

Semantic analysis is the technique to understand the meaning and interpretation of words, signs, and sentence structure.

SearchAssist’s Index pipeline supports a Semantic Meaning stage. This stage uses Deep Neural Network algorithms to create embeddings of free text and saves them in a dense vector field. These embeddings are used to rank the documents by semantic relevance. The dense vectors are then indexed in the ElasticSearch and similarity is obtained between the user’s query vector and the indexed content vector.

You can:

  • Add multiple semantics to be analyzed from the source field.
  • Define a condition for the semantic meaning stage. The semantics from only the documents that satisfy the given condition would be analyzed.
  • Re-order or delete semantic meaning rules.
  • Simulate the changes before saving them.

Ensure to Train your app each time you make changes to any index configuration. This builds the index based on the updated configurations.

Configuration

To configure semantic meaning, follow the below steps:

  1. Click the Indices tab on the top.
  2. On the left pane, under the Index Configuration section, click Workbench.
  3. On the Workbench (Index Configuration) page, on the Stages column, click the + icon.
  4. On the right column, select Semantic Meaning from the Stage Type drop-down list.
  5. Enter a name in the Stage Name field.
  6. Enter a condition in the Condition field. You can add multiple conditions using the AND/OR connectors. Documents that satisfy the condition will be executed as part of the stage. See below for details.
  7. Select the field you want to extract Semantic Meaning from as Source Field.
  8. Define where you want to store the extracted Semantic Meaning as Target Field. This field is created by the application.
  9. Choose a model from the Choose Model drop-down list. See below for details.
  10. Click Simulate to verify the configurations. The simulator displays the Source and the number of documents to which the mapping was applied, and the result. You can change the Source (if not mentioned in the condition) and the number of documents.
  11. Once done, click Save Configuration on the top-right.

Models

The following models are supported:

  • Universal Sentence Encoder – It encodes text into high-dimensional vectors that are used for semantic similarity.
  • Sentence Transformers – It is a framework for sentence and text embeddings.
  • InferSent – It is a sentence embedding method that provides semantic sentence representations.

Conditions

Condition is of the following format: ctx.fieldtype==value or ctx.fieldtype!=value. The field_name can be obtained from the Fields table under Index Configuration.

For example, ctx.contentType=="web" to restrict the extraction to the content from a web source.