Merge pull request #98004 from diberry/luis-only-old-portal

[Cogsvcs] LUIS - not updating tutorials - old portal only

Author: v-albemi

articles/cognitive-services/LUIS/includes/old-portal-only.md

@@ -0,0 +1,17 @@
+---
+title: include file
+description: include file
+services: cognitive-services
+author: diberry
+manager: nitinme
+ms.custom: seodec18
+ms.service: cognitive-services
+ms.subservice: luis
+ms.topic: include
+ms.custom: include file
+ms.date: 12/05/2019
+ms.author: diberry
+---
+
+> [!NOTE]
+> This article applies to the existing LUIS portal only. Do not use this article with the preview LUIS portal. The same apps are available in both portals.

articles/cognitive-services/LUIS/luis-tutorial-composite-entity.md

@@ -9,30 +9,30 @@ ms.custom: seodec18
 ms.service: cognitive-services
 ms.subservice: language-understanding
 ms.topic: tutorial
-ms.date: 10/14/2019
+ms.date: 12/05/2019
 ms.author: diberry
 ---
 
 # Tutorial: Group and extract related data
 In this tutorial, add a composite entity to bundle extracted data of various types into a single containing entity. By bundling the data, the client application can easily extract related data in different data types.
 
-The purpose of the composite entity is to group related entities into a parent category entity. The information exists as separate entities before a composite is created. 
+The purpose of the composite entity is to group related entities into a parent category entity. The information exists as separate entities before a composite is created.
 
 The composite entity is a good fit for this type of data because the data:
 
-* Are related to each other. 
+* Are related to each other.
 * Use a variety of entity types.
 * Need to be grouped and processed by client app as a unit of information.
 
-[!INCLUDE [Waiting for LUIS portal refresh](./includes/wait-v3-upgrade.md)]
+[!INCLUDE [Only valid with current portal](includes/old-portal-only.md)]
 
 **In this tutorial, you learn how to:**
 
 <!-- green checkmark -->
 > [!div class="checklist"]
 > * Import example app
 > * Create intent
-> * Add composite entity 
+> * Add composite entity
 > * Train
 > * Publish
 > * Get intents and entities from endpoint
@@ -49,22 +49,22 @@ The composite entity is a good fit for this type of data because the data:
 
 ## Composite entity
 
-In this app, the department name is defined in the **Department** list entity and includes synonyms. 
+In this app, the department name is defined in the **Department** list entity and includes synonyms.
 
-The **TransferEmployeeToDepartment** intent has example utterances to request an employee be moved to a new department. 
+The **TransferEmployeeToDepartment** intent has example utterances to request an employee be moved to a new department.
 
 Example utterances for this intent include:
 
 |Example utterances|
 |--|
 |move John W. Smith to the accounting department|
 |transfer Jill Jones from to R&D|
- 
-The move request should include the department name, and the employee name. 
+
+The move request should include the department name, and the employee name.
 
 ## Add the PersonName prebuilt entity to help with common data type extraction
 
-LUIS provides several prebuilt entities for common data extraction. 
+LUIS provides several prebuilt entities for common data extraction.
 
 1. Select **Build** from the top navigation, then select **Entities** from the left navigation menu.
 
@@ -82,11 +82,11 @@ LUIS provides several prebuilt entities for common data extraction.
 
 1. Select **TransferEmployeeToDepartment** from the intents list.
 
-1. In the utterance `place John Jackson in engineering`, select the personName entity, `John Jackson`, then select **Wrap in composite entity** in the pop-up menu list for the following utterance. 
+1. In the utterance `place John Jackson in engineering`, select the personName entity, `John Jackson`, then select **Wrap in composite entity** in the pop-up menu list for the following utterance.
 
     ![Screenshot of selecting wrap composite in drop down dialog](./media/luis-tutorial-composite-entity/hr-create-composite-entity-1.png)
 
-1. Then immediately select the last entity, `engineering` in the utterance. A green bar is drawn under the selected words indicating a composite entity. In the pop-up menu, enter the composite name `TransferEmployeeInfo` then select enter. 
+1. Then immediately select the last entity, `engineering` in the utterance. A green bar is drawn under the selected words indicating a composite entity. In the pop-up menu, enter the composite name `TransferEmployeeInfo` then select enter.
 
     ![Screenshot of entering composite name in drop down dialog](./media/luis-tutorial-composite-entity/hr-create-composite-entity-2.png)
 
@@ -98,23 +98,23 @@ LUIS provides several prebuilt entities for common data extraction.
 
 1. In each example utterance, select the left-most entity that should be in the composite. Then select **Wrap in composite entity**.
 
-1. Select the last word in the composite entity then select **TransferEmployeeInfo** from the pop-up menu. 
+1. Select the last word in the composite entity then select **TransferEmployeeInfo** from the pop-up menu.
 
-1. Verify all utterances in the intent are labeled with the composite entity. 
+1. Verify all utterances in the intent are labeled with the composite entity.
 
-## Train the app so the changes to the intent can be tested 
+## Train the app so the changes to the intent can be tested
 
 [!INCLUDE [LUIS How to Train steps](../../../includes/cognitive-services-luis-tutorial-how-to-train.md)]
 
 ## Publish the app so the trained model is queryable from the endpoint
 
 [!INCLUDE [LUIS How to Publish steps](../../../includes/cognitive-services-luis-tutorial-how-to-publish.md)]
 
-## Get intent and entity prediction from endpoint 
+## Get intent and entity prediction from endpoint
 
 1. [!INCLUDE [LUIS How to get endpoint first step](../../../includes/cognitive-services-luis-tutorial-how-to-get-endpoint.md)]
 
-2. Go to the end of the URL in the address and enter `Move Jill Jones to DevOps`. The last querystring parameter is `q`, the utterance query. 
+2. Go to the end of the URL in the address and enter `Move Jill Jones to DevOps`. The last querystring parameter is `q`, the utterance query.
 
     Since this test is to verify the composite is extracted correctly, a test can either include an existing sample utterance or a new utterance. A good test is to include all the child entities in the composite entity.
 
@@ -180,7 +180,7 @@ LUIS provides several prebuilt entities for common data extraction.
     }
     ```
 
-   This utterance returns a composite entities array. Each entity is given a type and value. To find more precision for each child entity, use the combination of type and value from the composite array item to find the corresponding item in the entities array.  
+   This utterance returns a composite entities array. Each entity is given a type and value. To find more precision for each child entity, use the combination of type and value from the composite array item to find the corresponding item in the entities array.
 
 ## Clean up resources
 
@@ -197,7 +197,7 @@ LUIS provides several prebuilt entities for common data extraction.
 
 ## Next steps
 
-This tutorial created a composite entity to encapsulate existing entities. This allows the client application to find a group of related data in different datatypes to continue the conversation. A client application for this Human Resources app could ask what day and time the move needs to begin and end. It could also ask about other logistics of the move such as a physical phone. 
+This tutorial created a composite entity to encapsulate existing entities. This allows the client application to find a group of related data in different datatypes to continue the conversation. A client application for this Human Resources app could ask what day and time the move needs to begin and end. It could also ask about other logistics of the move such as a physical phone.
 
-> [!div class="nextstepaction"] 
-> [Learn how to add a simple entity with a phrase list](luis-quickstart-primary-and-secondary-data.md)  
+> [!div class="nextstepaction"]
+> [Learn how to add a simple entity with a phrase list](luis-quickstart-primary-and-secondary-data.md)

articles/cognitive-services/LUIS/tutorial-entity-roles.md

@@ -1,32 +1,32 @@
 ---
 title: "Tutorial: Contextual data with roles - LUIS"
 titleSuffix: Azure Cognitive Services
-description: Find related data based on context. For example, an origin and destination locations for a physical move from one building and office to another building and office are related. 
+description: Find related data based on context. For example, an origin and destination locations for a physical move from one building and office to another building and office are related.
 services: cognitive-services
 author: diberry
 manager: nitinme
 ms.custom: seodec18
 ms.service: cognitive-services
 ms.subservice: language-understanding
 ms.topic: tutorial
-ms.date: 10/14/2019
+ms.date: 12/05/2019
 ms.author: diberry
-#Customer intent: As a new user, I want to understand how and why to use roles on an entity. 
+#Customer intent: As a new user, I want to understand how and why to use roles on an entity.
 ---
 
 # Tutorial: Extract contextually related data from an utterance
 
-In this tutorial, find related pieces of data based on context. For example, an origin and destination locations for a transfer from one city to another. Both pieces of data may be required and they are related to each other.  
+In this tutorial, find related pieces of data based on context. For example, an origin and destination locations for a transfer from one city to another. Both pieces of data may be required and they are related to each other.
 
-A role can be used with any prebuilt or custom entity type, and used in both example utterances and patterns. 
+A role can be used with any prebuilt or custom entity type, and used in both example utterances and patterns.
 
-[!INCLUDE [Waiting for LUIS portal refresh](./includes/wait-v3-upgrade.md)]
+[!INCLUDE [Only valid with current portal](includes/old-portal-only.md)]
 
 **In this tutorial, you learn how to:**
 
 > [!div class="checklist"]
 > * Create new app
-> * Add intent 
+> * Add intent
 > * Get origin and destination information using roles
 > * Train
 > * Publish
@@ -53,9 +53,9 @@ A role should be used when the entity data to extract:
 
 1. [!INCLUDE [Start in Build section](../../../includes/cognitive-services-luis-tutorial-build-section.md)]
 
-1. Select **Create new intent**. 
+1. Select **Create new intent**.
 
-1. Enter `MoveEmployeeToCity` in the pop-up dialog box then select **Done**. 
+1. Enter `MoveEmployeeToCity` in the pop-up dialog box then select **Done**.
 
     ![Screenshot of create new intent dialog with](./media/tutorial-entity-roles/create-new-intent-move-employee-to-city.png)
 
@@ -81,24 +81,24 @@ The prebuilt entity, geographyV2, extracts location information, including city
 
 1. Select **Entities** from the left-side navigation.
 
-1. Select **Add prebuilt entity**, then select `geo` in the search bar to filter the prebuilt entities. 
+1. Select **Add prebuilt entity**, then select `geo` in the search bar to filter the prebuilt entities.
 
     ![Add geographyV2 prebuilt entity to app](media/tutorial-entity-roles/add-geographyV2-prebuilt-entity.png)
 1. Select the checkbox and select **Done**.
-1. In the **Entities** list, select the **geographyV2** to open the new entity. 
-1. Add two roles, `Origin`, and `Destination`. 
+1. In the **Entities** list, select the **geographyV2** to open the new entity.
+1. Add two roles, `Origin`, and `Destination`.
 
     ![Add roles to prebuilt entity](media/tutorial-entity-roles/add-roles-to-prebuilt-entity.png)
 1. Select **Intents** from the left-side navigation, then select the **MoveEmployeeToCity** intent. Notice the city names are labeled with the prebuilt entity **geographyV2**.
 1. In the first utterance of the list, select the origin location. A drop-down menu appears. Select **geographyV2** in the list, then follow the menu across to select **Origin**.
-1. Use the method from the previous step to mark all roles of locations in all the utterances. 
+1. Use the method from the previous step to mark all roles of locations in all the utterances.
 
 
-## Add example utterances to the None intent 
+## Add example utterances to the None intent
 
 [!INCLUDE [Follow these steps to add the None intent to the app](../../../includes/cognitive-services-luis-create-the-none-intent.md)]
 
-## Train the app so the changes to the intent can be tested 
+## Train the app so the changes to the intent can be tested
 
 [!INCLUDE [LUIS How to Train steps](../../../includes/cognitive-services-luis-tutorial-how-to-train.md)]
 
@@ -148,9 +148,9 @@ The prebuilt entity, geographyV2, extracts location information, including city
       ]
     }
     ```
-    
+
     The correct intent is predicted and the entities array has both the origin and destination roles in the corresponding **entities** property.
-    
+
 ## Clean up resources
 
 [!INCLUDE [LUIS How to clean up resources](../../../includes/cognitive-services-luis-tutorial-how-to-clean-up-resources.md)]
@@ -169,5 +169,5 @@ The prebuilt entity, geographyV2, extracts location information, including city
 
 This tutorial created a new intent and added example utterances for the contextually learned data of origin and destination locations. Once the app is trained and published, a client-application can use that information to create a move ticket with the relevant information.
 
-> [!div class="nextstepaction"] 
-> [Learn how to add a composite entity](luis-tutorial-composite-entity.md) 
+> [!div class="nextstepaction"]
+> [Learn how to add a composite entity](luis-tutorial-composite-entity.md)