Skip to content

Commit 2719908

Browse files
Merge pull request #225824 from aahill/studio-format
Text format update for conversational features
2 parents 55bcd7e + 1e6f16a commit 2719908

File tree

4 files changed

+34
-3
lines changed

4 files changed

+34
-3
lines changed

articles/cognitive-services/language-service/language-studio.md

Lines changed: 25 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -57,6 +57,31 @@ When you're ready to use Language Studio features on your own text data, you wil
5757

5858
4. Select **Done**. Your resource will be created, and you will be able to use the different features offered by the Language service with your own text.
5959

60+
61+
### Valid text formats for conversation features
62+
63+
> [!NOTE]
64+
> This section applies to the following features:
65+
> * [PII detection for conversation](./personally-identifiable-information/overview.md)
66+
> * [Conversation summarization](./summarization/overview.md?tabs=conversation-summarization)
67+
68+
If you're sending conversational text to supported features in Language Studio, be aware of the following input requirements:
69+
* The text you send must be a conversational dialog between two or more participants.
70+
* Each line must start with the name of the participant, followed by a `:`, and followed by what they say.
71+
* Each participant must be on a new line. If multiple participants' utterances are on the same line, it will be processed as one line of the conversation.
72+
73+
See the following example for how you should structure conversational text you want to send.
74+
75+
*Agent: Hello, you're chatting with Rene. How may I help you?*
76+
77+
*Customer: Hi, I tried to set up wifi connection for Smart Brew 300 espresso machine, but it didn't work.*
78+
79+
*Agent: I’m sorry to hear that. Let’s see what we can do to fix this issue.*
80+
81+
Note that the names of the two participants in the conversation (*Agent* and *Customer*) begin each line, and that there is only one participant per line of dialog.
82+
83+
:::image type="content" source="./media/language-studio-conversation-example.png" alt-text="A screenshot showing an example conversation input in Language Studio." lightbox="./media/language-studio-conversation-example.png":::
84+
6085
## Clean up resources
6186

6287
If you want to clean up and remove a Cognitive Services subscription, you can delete the resource or resource group. Deleting the resource group also deletes any other resources associated with it.
282 KB
Loading

articles/cognitive-services/language-service/personally-identifiable-information/how-to-call-for-conversations.md

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: nitinme
88
ms.service: cognitive-services
99
ms.subservice: language-service
1010
ms.topic: how-to
11-
ms.date: 05/10/2022
11+
ms.date: 01/31/2023
1212
ms.author: jboback
1313
ms.reviewer: bidishac
1414
---
@@ -35,6 +35,9 @@ Currently the conversational PII preview API supports all Azure regions supporte
3535

3636
## Submitting data
3737

38+
> [!NOTE]
39+
> See the [Language Studio](../language-studio.md#valid-text-formats-for-conversation-features) article for information on formatting conversational text to submit using Language Studio.
40+
3841
You can submit the input to the API as list of conversation items. Analysis is performed upon receipt of the request. Because the API is asynchronous, there may be a delay between sending an API request, and receiving the results. For information on the size and number of requests you can send per minute and second, see the data limits below.
3942

4043
When using the async feature, the API results are available for 24 hours from the time the request was ingested, and is indicated in the response. After this time period, the results are purged and are no longer available for retrieval.
@@ -59,7 +62,7 @@ When you get results from PII detection, you can stream the results to an applic
5962

6063
1. Go to your resource overview page in the [Azure portal](https://portal.azure.com/#home)
6164

62-
2. From the menu on the left side, select **Keys and Endpoint**. You will need one of the keys and the endpoint to authenticate your API requests.
65+
2. From the menu on the left side, select **Keys and Endpoint**. You'll need one of the keys and the endpoint to authenticate your API requests.
6366

6467
3. Download and install the client library package for your language of choice:
6568

articles/cognitive-services/language-service/summarization/how-to/conversation-summarization.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ manager: nitinme
88
ms.service: cognitive-services
99
ms.subservice: language-service
1010
ms.topic: how-to
11-
ms.date: 09/26/2022
11+
ms.date: 01/31/2023
1212
ms.author: jboback
1313
ms.custom: language-service-summarization, ignite-fall-2021, event-tier1-build-2022, ignite-2022
1414
---
@@ -40,6 +40,9 @@ There's another feature in Azure Cognitive Service for Language named [document
4040

4141
## Submitting data
4242

43+
> [!NOTE]
44+
> See the [Language Studio](../../language-studio.md#valid-text-formats-for-conversation-features) article for information on formatting conversational text to submit using Language Studio.
45+
4346
You submit documents to the API as strings of text. Analysis is performed upon receipt of the request. Because the API is [asynchronous](../../concepts/use-asynchronously.md), there may be a delay between sending an API request and receiving the results. For information on the size and number of requests you can send per minute and second, see the data limits below.
4447

4548
When you use this feature, the API results are available for 24 hours from the time the request was ingested, and is indicated in the response. After this time period, the results are purged and are no longer available for retrieval.

0 commit comments

Comments
 (0)