--- title: "Data collection" slug: "clovastudio-scenario" tags: ["CLOVA Studio"] updated: 2026-09-17T09:33:50Z published: 2026-09-17T09:33:50Z canonical: "guide.ncloud-docs.com/clovastudio-scenario" stale: true --- > ## Documentation Index > Fetch the complete documentation index at: https://guide.ncloud-docs.com/llms.txt > Use this file to discover all available pages before exploring further. # Data collection Available in Classic and VPC Data collection is the process through which the model thinks and examines to provide appropriate answers to the user's questions. Through collecting and reviewing data, you can edit your model's thought process. ## Data collection screen The data collection screen is configured as follows: ![clovastudio-scenario_main_ko.png](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/clovastudio-scenario_main_en(2).png?sv=2026-02-06&spr=https&st=2026-11-01T19%3A27%3A27Z&se=2026-11-01T20%3A27%3A27Z&sr=c&sp=r&sig=p7qnbyOheAXe5UIx9dugxXOWTcSuVtsz%2FKarRHY8lFs%3D) | Item | Description | | --- | --- | | ① Data collection area | Area where you set the values for data collection and run the process - **Model/version**: select a language model or version to use - **Skill**: selected skill set and list of skills included in the version. You can only use skills whose task status is "completed" - **Setting > call option**: run a user query to assign a specific value for calling API - **Setting > response format**: check response format specified for skill set - **User query**: enter user queries to collect. It will not be until you select a skill set that the field will be enabled. - **[→]** button: a button to execute Data collection | | ② Data collection area | Area where you review and collect the created data - **Query analysis**: user query analysis to choose which skill to use - **Skill call**: model's thought process to call an appropriate API - **Final response**: response processed based on call result | | ③ Feature buttons | - **[Load]** button: a button to recall the previously tasked scenario - **[Temporary save]** button: a button to save what has been done until now - **[Complete task]** button: a button to complete the work done to date. Only activated when the final answer has been created | ## Run data collection The following walks you through the model's thought and judgment process to handle user queries through data collection. To run data collection, follow these steps: 1. From the NAVER Cloud Platform console, click **Menu** > **All Services** > **AI Services** > **CLOVA Studio** in order. 2. From the **my product** menu, click the **[Go to CLOVA Studio]** button. 3. In CLOVA Studio, click the **Skill trainer** menu. 4. Click the skill set you want to collect data for. 5. Click the **Data collection** tab. 6. Set required information for data collection. - **Model/version**: select a language model or version to use. - **Skill**: list of skills included in the skill set. You can only use skills whose task status is "completed." - **Setting** > **Call option**: specify a value for API call for user queries. For more information on how to create a call option, see [create call option](/docs/en/clovastudio-scenario#%ED%98%B8%EC%B6%9C%EC%98%B5%EC%85%98%EC%9E%91%EC%84%B1). 7. Enter queries to collect in the **user query** area. 8. Click the **[→]** button. - The data collection steps are shown in order on the left side of the screen. - Click **[Suspend]** to suspend a specific step. Click **[Restart]** to restart the suspended task. Note You cannot edit **model/version** and **user query** after running data collection. If you need to edit the content, click **[Initialize]** to restart the task. The **[Initialize]** button is activated once data collection is completed. ## Review and edit data After running the data collection, if there is any inaccurate judgment from the model at each step, you can improve the response by manually editing the parameters to generate more accurate answers. To review and edit the collected data, follow these steps: 1. [Run data collection](/docs/en/clovastudio-scenario#%EB%8D%B0%EC%9D%B4%ED%84%B0%EC%88%98%EC%A7%91%EC%8B%A4%ED%96%89). 2. Check the skill call results after the query analysis. - For more information on each step, see [Data collection steps](/docs/en/clovastudio-scenario#%EB%8D%B0%EC%9D%B4%ED%84%B0%EC%88%98%EC%A7%91%EB%8B%A8%EA%B3%84). 3. Click **[Next]** at each step to proceed to the next. - For a new data collection, you can skip to the final response stage without clicking **[Next]**. 4. To edit your data, click a field, edit, and click **[Apply]** - Data creation is restarted for the next steps. 5. Check the final response and click **[Task completed]**. - To save the task for later use, click **[Temporary save]**. - The **[Task completed]** button appears after the final response is created. ## Load data You can load, review, and edit data you previously worked on. To load data, follow these steps: 1. From the NAVER Cloud Platform console, click **Menu** > **All Services** > **AI Services** > **CLOVA Studio** in order. 2. From the **my product** menu, click **[Go to CLOVA Studio]**. 3. In CLOVA Studio, click the **Skill trainer** menu. 4. Click a skill set. 5. Click the **Data collection** tab. 6. Click **[Load]** in the Run data collection area. 7. Check the temporarily saved task list. - You can search based on user queries from the top right of the Load window. - To check the data results, click **[⋮]** > **[View data]** from the list. - To delete a task, click **[⋮]** > **[Delete]** from the list. - The task status shows "completed" only when you click **[Complete task]** on the data task screen. 8. To edit the previous query task from the data collection screen, click **[Open]**. - The data collection screen appears, and you can continue to work on the previous queries. - You can also load the call option applied to the task. ## Data collection steps Data collection consists of query analysis, skill calls and final response, in order. The following describes the tasks run in each data collection step. ### Query analysis This is the step to decide which skill to use by analyzing user queries. Queries are classified by the call and mapped to relevant skills. If 2 or more queries are analyzed, 2 skill calls are made. ### Skill calls This step includes skill calls and the review of the model's thoughts. Skill calls are performed as many times as the number of queries classified during the query analysis step. Skill calls consist of 3 steps. - Step 1: querying API for the skill you want to call - **Call method**: model's thought process to find an API - **Call skill**: skill's model name - **API query details**: API Spec and Description for model of the skill - Step 2: checking the search results of the API query - **API search result**: model's thought process to call an API. Inferring the request variables (parameters) required for the API call - **Action**: API method. Only supports requests_get and requests_post - **Action input**: URL and parameters inferred by the model. Input fields differ depending on the action - If requests_get, action input field: API URL/parameter - If requests_post, action input field: API URL/parameter (key, value) - Click **[Add field]** to create an additional blank field - Click the ![i-clovastudio_reset.png](https://cdn.document360.io/6998976f-9d95-4df8-b847-d375892b92c2/Images/Documentation/i-clovastudio_reset.png?sv=2026-02-06&spr=https&st=2026-11-01T19%3A27%3A27Z&se=2026-11-01T20%3A27%3A27Z&sr=c&sp=r&sig=p7qnbyOheAXe5UIx9dugxXOWTcSuVtsz%2FKarRHY8lFs%3D) icon to delete the field - **Call result**: API call result - Step 3: organizing content based on the call result - **Thought**: model's thought process to organize the content of the call - **Result**: result of model creation Note In the case of requests_post, when creating a new parameter in the action input field, make sure it is not redundant with the key of an existing parameter. If there are duplicate keys, the API may not be called. ### Final response In this step, the final response is created and reviewed. After the creation of the final response, click **[Task completed]** to complete data collection. ## Creating call options By creating call options, you can fix a certain value for the header and body parameters for the API spec operation ID. To create a call option, follow these steps: 1. While [running data collection](/docs/en/clovastudio-scenario#%EB%8D%B0%EC%9D%B4%ED%84%B0%EC%88%98%EC%A7%91%EC%8B%A4%ED%96%89), click **[Call option]** of the **Setting** menu on the right side of the screen. - The **call option** window appears. 2. Enter the call option in JSON type in the call value input area. - Create it referring to the example format at the top of the screen. - For more information on call value input, see [Detailed call option](/docs/en/clovastudio-scenario#%EC%83%81%EC%84%B8%ED%98%B8%EC%B6%9C%EC%98%B5%EC%85%98). 3. Once the call value input is completed, click **[Apply]**. - If it fails to be applied, an error message is displayed. Re-edit the call value. Note - If you re-enter the **Data collection** menu after exiting it, the call options are initialized. - After collecting data with the call options applied, even if you click **[Initialize]**, your options are maintained. - If you load your previous task with the **[Load]** button, the call options applied to the task are loaded as well. ### Detailed call option It is information on the fields that can be written in the call option. The call options are applied in the order of operations field, baseOperation field, and then the user query. | Field | Data type | Description | | --- | --- | --- | | baseOperation | object | The call option is applied to all APIs registered within the skill set | | baseOperation.header | map | Fixed values to be added to the HTTP header of all APIs | | baseOperation.query | map | Fixed values to be added to the HTTP Query Parameter of all APIs | | baseOperation.requestBody | map | Fixed values to be added to the HTTP Request Body of all APIs | | operations | list | The call option is applied only to the specified Operation ID among the APIs registered within the skill set | | operations[].operationId | string | Assign operation ID you want to apply the call option to | | operations[].header | map | Fixed values to be added to the HTTP header of the API mapped to the assigned operation ID | | operations[].query | map | Fixed values to be added to the HTTP query parameter of the API mapped to the assigned operation ID | | operations[].requestBody | map | Fixed values to be added to the HTTP request body of the API mapped to the assigned operation ID |