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
Smart Hibernation

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

Weights

Weights are used to boost the search relevance of a field. Assign weightage to your fields as per your business rules and requirements and fine-tune the search results accordingly.  

For example, if a user queries for information and SearchAssist finds related information on both a web page and an FAQ page, the weightage assigned to fields related to FAQs and web pages will decide what content will the user see on the top. Let’s say the faq_content field is assigned a weight of 6 and page_content is assigned a weightage of 4, then the FAQ results will appear higher in the search results list before the web results.

Each field is assigned a weight value between 0 and 10. Increasing the field’s weight increases its relevance. By default, weights are defined only for the pre-defined fields. When you add a new index field, mark it as Searchable and assign a weight to it.  

Weights assigned to the fields are relative to each other. A field with a weightage of 7 will be considered more relevant than a field with a weightage of 5.

Note: Weight along with other parameters like results ranking, business rules, etc. affect the results and the order in which they are shown to the users. 

To view, add or edit the weightage assigned to various fields, go to the Search Settings under the Indices tab and click on Weights. By default, it shows the list of system-defined fields and their weightage. 

If you modify the weightage of any of the existing fields, it is automatically updated. You can use the delete icon in each row to delete the respective field. 

To add a new field and assign it a weightage, click the Add searchable field link on the top right corner. Note that a weightage can be assigned only to the searchable fields. Select the field, assign a weight to it and click Add. If the field is not defined yet, go to the Index Fields and add a new searchable field before assigning the weight. 

SearchAssist also gives the option to reset the weights assigned to the system-defined fields. This can be specifically useful to go back to the initial state when testing with weights to fine-tune results. To do so, click the Reset to Default link on the top of the page and click Continue.

Weights

Weights are used to boost the search relevance of a field. Assign weightage to your fields as per your business rules and requirements and fine-tune the search results accordingly.  

For example, if a user queries for information and SearchAssist finds related information on both a web page and an FAQ page, the weightage assigned to fields related to FAQs and web pages will decide what content will the user see on the top. Let’s say the faq_content field is assigned a weight of 6 and page_content is assigned a weightage of 4, then the FAQ results will appear higher in the search results list before the web results.

Each field is assigned a weight value between 0 and 10. Increasing the field’s weight increases its relevance. By default, weights are defined only for the pre-defined fields. When you add a new index field, mark it as Searchable and assign a weight to it.  

Weights assigned to the fields are relative to each other. A field with a weightage of 7 will be considered more relevant than a field with a weightage of 5.

Note: Weight along with other parameters like results ranking, business rules, etc. affect the results and the order in which they are shown to the users. 

To view, add or edit the weightage assigned to various fields, go to the Search Settings under the Indices tab and click on Weights. By default, it shows the list of system-defined fields and their weightage. 

If you modify the weightage of any of the existing fields, it is automatically updated. You can use the delete icon in each row to delete the respective field. 

To add a new field and assign it a weightage, click the Add searchable field link on the top right corner. Note that a weightage can be assigned only to the searchable fields. Select the field, assign a weight to it and click Add. If the field is not defined yet, go to the Index Fields and add a new searchable field before assigning the weight. 

SearchAssist also gives the option to reset the weights assigned to the system-defined fields. This can be specifically useful to go back to the initial state when testing with weights to fine-tune results. To do so, click the Reset to Default link on the top of the page and click Continue.