Customization via System Settings
The overall purpose of System Settings for Global Search is to provide administrators with the flexibility to configure the behavior and display of the Global Search functionality. These settings allow users to customize the search experience, control the visibility of certain features, and optimize the search parameters according to their specific requirements. These settings can be configured from Administration > System Settings > Global Search tab.
disable.sourcecode.search
Enable/disable the Source Code search in Global Search.
Parameters:
The default value is False.
If set to True, the Source Code search results get disabled in the Global search.
If set to False, the Source Code Search results are displayed in the Global Search.
search.es.searchcontext
Show/Hide object types from search criteria. Based on search criteria objects are displayed in the search results page.
Parameters:
Available object types: All, tables, oetopic, files, reports, apis, schema, codes, data attributes, glossary, service requests, help & resources question wall
Enter the selected object names in the field provided. If left blank then only the All tab is displayed.
search.es.pagination.count
Specify the maximum number of records to be added in an index while running the advanced job to fetch from local DB to Elasticsearch. Supports: Min - 5000, Max - 10000.
Parameters:
The default value is 5000.
Enter the value in the field provided.
es.search.dropdown.disabled
Configure to enable or disable the quick view data dropdown in Elasticsearch-based search results.
Parameters:
The default value is False.
If set to True, the quick view data dropdown is disabled in the search results.
If set to False, the quick view data dropdown is enabled and visible in the search results.
search.es.active.filters
This configuration specifies the active filters used on the Global Search page to refine search results. Each filter corresponds to a specific attribute of the search items, allowing users to narrow down results based on various criteria:
Parameters:
The below filter sections are considered essential for effective search. It is recommended to use these filters, although users can remove some filters if they do not match their requirements.
Connection, Schema, Glossary, TableType, Folder, Report Group, Term Status, Data Quality Index, Service Request Status, Question Wall, Additional Information, Created Date.
search.es.governancerole.filters.optional
This configuration specifies the Governance Roles filters used on the Global Search page to refine search results.
Parameters:
Owner, Steward, Custodian, Governance Role 4, Governance Role 5, Governance Role 6.
search.es.dataobjects.filters.optional
This configuration specifies additional filters for Data Objects, which can be used on the Global Search page to refine search results.
Parameters:
Certifications, API Group, Ratings, Popularity, Report Type.
index.max.result.window
If Elasticsearch is enabled, this configuration specifies the maximum number of records returned in a single search request in the Data Catalog’s data objects.
The default is 10,000.
Parameters:
Maximum value is 10,000
Minimum value is 1
es.datacatalog.grid.mysql.fallback.force
Configure to fetch the records of the Data Catalog from the database or Elasticsearch.
The default value is false.
Parameters:
If set to true, the Data Catalog will be fetched from the database.
If set to false, the Data Catalog will be fetched from the Elasticsearch.
es.datacatalog.filter.size
Configure to show the filter size of the catalog objects in a page. The default value is 100.
Parameters:
Maximum value is 100
Minimum value is 20
catalog.es.oetp.additional.ops.allowed
If Elasticsearch is enabled, configure to enable the Advanced Filter option in the Data Catalog.
The default value is true.
Parameters:
If set to true, the Advanced Filter option is enabled.
If set to false, the Advanced Filter option is disabled.
additional.sorting.options
Configure to enable sorting of search results based on object types with the highest number of service requests. Only object types linked to Access Request types are considered.
Parameters:
The default value is false.
custom.search.requirements
Configure custom tuning of relevance scoring for search results via JSON Configuration.
Parameters:
The default value is {"level1": 500, "level2": 300, "level3": 50}.
The listed system settings need to be configured under the supervision of senior-level administrators.
search.score.use.synonym
Configure the Synonym (Configure Synonyms for Search) Score in the Relevance score formula to determine the most relevant search results. The relevance score is calculated based on three components: the Elasticsearch score, the popularity score, and the synonym score (if configured).
Parameters:
If set to True, the search results calculation includes the Synonym score.
If set to False, the search results calculation excludes the Synonym score. Relevance score calculation depends solely on the Elasticsearch score and the settings configured for the Popularity score.
globalsearch.match.type
This configuration defines the matching type strategy used by the Global Search functionality to determine how search queries are analyzed against document fields:
best_fields: This type is used when the match is to be optimized for precision. It searches across multiple fields, scoring each field's match and returning the highest score. Best used when you know the field that should give the best match.
most_fields: Utilizes when the match is optimized for recall. It searches across multiple fields, adding the scores of each match to potentially increase overall relevance scores. Ideal for broad queries where any field could contain the user's query.
cross_fields: Analyzes multiple fields as a single combined field, increasing relevance for queries that span multiple fields. This is beneficial for searches expected to have multiple terms across different fields.
Jobs to Manage Index
The OvalEdge System Administrator must execute an Advanced Job named "Advanced Job for Indexing into ElasticSearch" during the tool's initial installation. Subsequently, as new data is crawled into the system, the indexing into Elasticsearch is automated.
Copyright © 2025, OvalEdge LLC, Peachtree Corners, GA USA
Last updated
Was this helpful?