The query of agent will be based on the data of the dataset configured in this step, and the user can customize the scope of the dataset queried by the agent, so that the agent can be better applied to the current business. This article provides you with configuration guidance related to creating datasets that agents can query when configuring an Intelligent Analysis Agent.
The current agent's data source configuration supports two data sources:
This article describes the activity details for configuring an agent data source based on a created dataset; see DataWind for creating a data source based on a chart Chart Configuration.
Before configuring the data source of the agent, you need to create the corresponding data as a dataset of the DataAgent to complete the data preparation operation. For details, please refer to Data Preparation Overview.
After entering the agent management configuration page, click "Data and Knowledge" in the left navigation bar. After entering the data source configuration page, you can start the configuration of the dataset in the "Dataset" tab.
As of version 3.17, adding a dataset and initializing will enable dataset vectorization by default, see below for details Dataset initialization.
You can click "Add Dataset" on the page to add the dataset you have permission for.
warning
The Intelligent Analysis Agent provides you with the function of "Optimizing Dataset Configuration". You can upload some questions and the AI will give you suggestions for dataset configuration. When using this function,
Breakdown | Key points |
|---|---|
Configuration purpose | The semantic model can reset the user-oriented semantics of the data set names, fields and other information on the basis of the data set, mainly to help the model better understand what data is contained in the data set and what the business semantics of these fields are, so as to improve the accuracy of the agent's automatic selection of data sets and Q & A. |
Precautions |
|
Click Config Model on the Dataset Configuration page.
Click "Set basic model information" to add a name, description, and features to the semantic model.
The relevant parameter configuration instructions are as follows:
Parameter | Configuration instructions |
|---|---|
Semantic model name | Support user-defined semantic model names. If not specified, they will be synchronized with the dataset name by default. |
Semantic model description | Support users to add descriptions to the semantic model. If not specified, it will be synchronized with the dataset description by default. |
Feature | The feature values of the semantic model are used to define the key characteristics that distinguish the current dataset from other datasets. Users can use commas and carriage returns to separate multiple values. warning
|
After the field list of the current dataset, click the "Configure" button of a field to enter the semantic model configuration interface of the corresponding field.
Fields of different data types involve some differences in the configuration parameters, which are described below.
General configuration parameters
Parameter | Configuration instructions |
|---|---|
Agent field name | The user can customize the agent field name. When the description at the time of query is this name, the agent will preferentially use this field for query. When empty, it is consistent with the field name of the dataset. |
Field name synonym | The user can set one or more synonyms for the field name, and when the description of the query is in these synonyms, the agent will preferentially use the field for query. Multiple synonyms are separated by commas or carriage returns. |
Field description | The user can add a description of the agent field to help understand the field, which is consistent with the field description of the dataset when empty. |
Default recall | If "Default Recall" is checked, this field will be passed to the large model as a prompt word each time a question is asked. |
Text class field-specific configuration parameters
Parameter | Configuration instructions |
|---|---|
Field value recall | Text class fields turn on the field value recall button by default, you can close it on demand, and the field value will not be recalled after closing. |
Field value blacklist | Field values that do not want to be recalled |
High frequency field value description | For high-frequency text fields, the field meaning range can be configured. The configuration example is as follows. |
Numerical class field-specific configuration parameters
Parameter | Configuration instructions |
|---|---|
Default calculation method | In the drop-down box, select the default calculation method for field values of the numeric class. Current support: sum, count, count differently, mean, maximum, minimum. |
Enables fields that require the use of a semantic model.
You can search to open the semantic model configuration content of the required fields in the dataset one by one, or click "Batch Open Status" at the bottom of the field list to open the semantic model configuration of all fields in the dataset.
Breakdown | Key points |
|---|---|
Configuration purpose | The agent supports configuring a knowledge base for the dataset, and users can add some industry slang, inaccurate or ambiguous expressions, etc., to the knowledge base, so that the large model can better understand the user's questions. |
Precautions | Dataset editing or above permissions are required to add. |
Click on the Associated Knowledge" of the dataset configuration to enter the knowledge management configuration page.
Click "Knowledge Base Configuration" to configure parameters such as matching degree preset and recall upper limit of the knowledge base.
The relevant parameter configuration instructions are as follows:
Parameter | Configuration instructions |
|---|---|
Match threshold | Adjust the vector matching degree between business terms and problems, with a minimum of 0 and a maximum of 1, indicating an accurate match. |
Upper limit of knowledge recall | Control the maximum number of one-time recall knowledge in the current dataset to avoid the interference of too much recall knowledge on the large model. |
Click "Add Knowledge" to add more knowledge to the knowledge base.
The knowledge of a dataset can usually be used to describe a data range after combining data set fields. The relevant parameter configuration instructions and examples are as follows:
Parameter | Configuration instructions | Configuration example |
|---|---|---|
Business term | Business terms such as specific nouns, slang, and names of common terms, when the recall rule is "follow the knowledge base configuration", the business term will be used as a keyword to recall the piece of knowledge. | For example, for a crowd profile dataset, when you need to disassemble the crowd field by group profile:
|
Conjunction | It is used to connect business terms and descriptions, including "representation" and "none" connectors. The function of connectors is mainly to make the whole sentence smoother, and whether connectors are needed can be determined according to the smoothness of previewing the whole sentence knowledge. | |
Explain | The definition, interpretation, etc. of input knowledge are the core parts of knowledge, and the description of knowledge needs to be accurate and easy to understand to help the large model understand more accurately. For example, the description of the business term "search performance caliber" is "Definition: orders/traffic are counted in searches". | |
Synonym | Synonyms of business terms serve the same purpose as business terms. For example, the synonyms of age distribution include age profile, age composition, and age structure. | |
Preview | You can check whether the overall knowledge is smooth through the preview. This is the knowledge that is ultimately given to the model, including the concatenation of business terms, connectors, and descriptions. | |
Recall rule | Includes following knowledge base configuration, default recall, and custom rules.
| |
Participate in the recall of field names | Field name recall refers to the current knowledge, whether to participate in field recall, the way to participate is to recall according to the field name in the knowledge. For example, the name of knowledge: sales represents sales and profit margins. Then the knowledge participates in the recall, and the two fields of sales and profit margin will be recalled. | |
Participate in recall field value | Field value recall refers to the current knowledge, whether to participate in the field recall, the way to participate is to recall according to the field value in the knowledge. For example, the name of knowledge: Douyin, watermelon, Jinri Toutiao. If this knowledge participates in the recall, the field "Product Name" will be recalled according to the values of Douyin, Watermelon, Jinri Toutiao, etc. |
The user clicks "Filter Configuration" to enter the dataset filtering configuration interface, and can filter the dataset data used by the agent according to the dimension field or indicator field in the dataset.
Set the filter criteria for the dataset used by the agent, and users can use dimension filtering, metric filtering, or date filtering based on the desired data situation.
Filter criteria | Applicable scenario | Operation guidance |
|---|---|---|
Dimension filter | The data needs to be filtered by dimension field to distinguish between dimension and metric field pairs, seeDimensions and Metrics. | |
Metric filter | The data needs to be filtered according to the indicator fields, and the distinction between dimensions and indicator fields is referred to in Dimensions and Metrics. | |
Date filter | Data needs to be filtered by date type fields |
Click "Config Readiness" to enter the configuration dataset ready interface. You can set the synchronization date and time for dataset readiness. After setting, click "Save".
Starting with the 3.5.0 release, direct import of semantic models and knowledge base configurations for other agents is supported. When you add a dataset to an agent and configure the semantic model and knowledge base of the dataset, if you need to use the same dataset when creating a new agent later, and the field semantic model and knowledge base of the dataset are similar to the previous configuration, you can directly import the corresponding configuration into the newly created agent.
warning
After completing the dataset configuration, you can view the data set initialization status in the list and view the enabled status of each data set in scenarios such as smart quizzes, in-depth research, etc.
After adding a dataset, the system automatically initializes the dataset and performs data set vectorization automatically. During the initialization process or after the initialization is completed, you can click the status column "Initializing" or "Completed" status, click "View Details", and jump to the initialization configuration page to view the configuration details.
The example of the initialization configuration interface is as follows:
Dataset initialization also has two states: incomplete and failed. You can try the initialization configuration again according to the interface prompts:
After the initialization of the dataset is completed, the vectorization of the dataset is turned on by default. If the subsequent dataset does not need to be used by the current agent query, you can click "Completed" in the status column, jump to the initialization configuration page, and turn off the vectorization.
After closing, the configuration of the dataset is preserved, but subsequent use of the agent will no longer query the data in the corresponding dataset.
After the dataset is created, Intelligent Data Query and In-depth Research are turned on by default, and you can turn on/off the corresponding switches on demand in the list.
tip