Merge pull request #788 from laujan/branch-3

merge branch three to release branch

Author: v-dirichards

articles/ai-services/.openpublishing.redirection.ai-services.json

@@ -233,7 +233,7 @@
     {
       "source_path_from_root": "/articles/ai-services/document-intelligence/concept-insurance-card.md",
       "redirect_url": "/azure/ai-services/document-intelligence/concept-health-insurance-card",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/ai-services/document-intelligence/concept-w2.md",
@@ -248,7 +248,7 @@
     {
       "source_path_from_root": "/articles/ai-services/document-intelligence/language-support.md",
       "redirect_url": "/azure/ai-services/document-intelligence/language-support-ocr",
-      "redirect_document_id": true
+      "redirect_document_id": false
     },
     {
       "source_path_from_root": "/articles/ai-services/document-intelligence/quickstarts/includes/v3-csharp-sdk.md",
@@ -557,7 +557,7 @@
     },
     {
       "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom-generative.md",
-      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/custom-generative-extraction",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-generative-extraction",
       "redirect_document_id": true
     },
     {
@@ -604,6 +604,116 @@
       "source_path_from_root": "/articles/ai-services/document-intelligence/managed-identities-secured-access.md",
       "redirect_url": "/azure/ai-services/document-intelligence/authentication/managed-identities-secured-access",
       "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-contract.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/contract",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-general-document.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/general-document",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-health-insurance-card.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/health-insurance-card",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-id-document.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/id-document",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-invoice.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/invoice",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-receipt.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/receipt",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-retrieval-augmented-generation.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/concept/retrieval-augmented-generation",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-tax-document.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/tax-document",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-add-on-capabilities.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/concept/add-on-capabilities",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-business-card.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/prebuilt/business-card",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-composed-models.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/composed-models",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom-classifier.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-classifier",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom-label-tips.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-label-tips",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom-label.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-labels",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom-lifecycle.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-lifecycle",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom-neural.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-neural",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom-template.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-template",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-custom.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/train/custom-model",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/concept-query-fields.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/concept/query-fields",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/language-support-ocr.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/language-support/ocr",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/language-support-prebuilt.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/language-support/prebuilt",
+      "redirect_document_id": true
+    },
+    {
+      "source_path_from_root": "/articles/ai-services/document-intelligence/language-support-custom.md",
+      "redirect_url": "/azure/ai-services/document-intelligence/language-support/custom",
+      "redirect_document_id": true
     }
 
   ]

articles/ai-services/document-intelligence/concept/accuracy-confidence.md

@@ -131,4 +131,4 @@ For **dynamic tables**, the levels are meant to build on top of each other, so t
 ## Next step
 
 > [!div class="nextstepaction"]
-> [Learn more about custom models](../concept-custom.md)
+> [Learn more about custom models](../train/custom-model.md)

articles/ai-services/document-intelligence/concept-add-on-capabilities.md renamed to articles/ai-services/document-intelligence/concept/add-on-capabilities.md

@@ -18,18 +18,18 @@ monikerRange: '>=doc-intel-3.1.0'
 # Document Intelligence add-on capabilities
 
 ::: moniker range="doc-intel-4.0.0"
-[!INCLUDE [preview-version-notice](includes/preview-notice.md)]
+[!INCLUDE [preview-version-notice](../includes/preview-notice.md)]
 
-**This content applies to:** ![checkmark](media/yes-icon.png) **v4.0 (preview)** | **Previous versions:** ![blue-checkmark](media/blue-yes-icon.png) [**v3.1 (GA)**](?view=doc-intel-3.1.0&preserve-view=tru)
+**This content applies to:** ![checkmark](../media/yes-icon.png) **v4.0 (preview)** | **Previous versions:** ![blue-checkmark](../media/blue-yes-icon.png) [**v3.1 (GA)**](?view=doc-intel-3.1.0&preserve-view=tru)
 :::moniker-end
 
 :::moniker range="doc-intel-3.1.0"
-**This content applies to:** ![checkmark](media/yes-icon.png) **v3.1 (GA)** | **Latest version:** ![purple-checkmark](media/purple-yes-icon.png) [**v4.0 (preview)**](?view=doc-intel-4.0.0&preserve-view=true)
+**This content applies to:** ![checkmark](../media/yes-icon.png) **v3.1 (GA)** | **Latest version:** ![purple-checkmark](../media/purple-yes-icon.png) [**v4.0 (preview)**](?view=doc-intel-4.0.0&preserve-view=true)
 :::moniker-end
 
 :::moniker range="doc-intel-3.1.0"
 > [!NOTE]
-> Add-on capabilities are available within all models except for the [Business card model](concept-business-card.md).
+> Add-on capabilities are available within all models except for the [Business card model](../prebuilt/business-card.md).
 :::moniker-end
 
 :::moniker range=">=doc-intel-3.1.0"
@@ -58,7 +58,7 @@ For `2024-07-31-preview` release and later, the Read model supports searchable P
 
 > [!NOTE]
 >
-> * Not all add-on capabilities are supported by all models. For more information, *see* [model data extraction](concept-model-overview.md#model-analysis-features).
+> * Not all add-on capabilities are supported by all models. For more information, *see* [model data extraction](../model-overview.md#model-analysis-features).
 >
 > * Add-on capabilities are currently not supported for Microsoft Office file types.
 
@@ -759,19 +759,19 @@ The `ocr.barcode` capability extracts all identified barcodes in the `barcodes`
 
 | **Barcode Type**   | **Example**   |
 | --- | --- |
-| `QR Code` |:::image type="content" source="media/barcodes/qr-code.png" alt-text="Screenshot of the QR Code.":::|
-| `Code 39` |:::image type="content" source="media/barcodes/code-39.png" alt-text="Screenshot of the Code 39.":::|
-| `Code 93` |:::image type="content" source="media/barcodes/code-93.gif" alt-text="Screenshot of the Code 93.":::|
-| `Code 128` |:::image type="content" source="media/barcodes/code-128.png" alt-text="Screenshot of the Code 128.":::|
-| `UPC (UPC-A & UPC-E)` |:::image type="content" source="media/barcodes/upc.png" alt-text="Screenshot of the UPC.":::|
-| `PDF417` |:::image type="content" source="media/barcodes/pdf-417.png" alt-text="Screenshot of the PDF417.":::|
-| `EAN-8` |:::image type="content" source="media/barcodes/european-article-number-8.gif" alt-text="Screenshot of the European-article-number barcode ean-8.":::|
-| `EAN-13` |:::image type="content" source="media/barcodes/european-article-number-13.gif" alt-text="Screenshot of the European-article-number barcode ean-13.":::|
-| `Codabar` |:::image type="content" source="media/barcodes/codabar.png" alt-text="Screenshot of the Codabar.":::|
-| `Databar` |:::image type="content" source="media/barcodes/databar.png" alt-text="Screenshot of the Data bar.":::|
-| `Databar` Expanded |:::image type="content" source="media/barcodes/databar-expanded.gif" alt-text="Screenshot of the Data bar Expanded.":::|
-| `ITF` |:::image type="content" source="media/barcodes/interleaved-two-five.png" alt-text="Screenshot of the interleaved-two-of-five barcode (ITF).":::|
-| `Data Matrix` |:::image type="content" source="media/barcodes/datamatrix.gif" alt-text="Screenshot of the Data Matrix.":::|
+| `QR Code` |:::image type="content" source="../media/barcodes/qr-code.png" alt-text="Screenshot of the QR Code.":::|
+| `Code 39` |:::image type="content" source="../media/barcodes/code-39.png" alt-text="Screenshot of the Code 39.":::|
+| `Code 93` |:::image type="content" source="../media/barcodes/code-93.gif" alt-text="Screenshot of the Code 93.":::|
+| `Code 128` |:::image type="content" source="../media/barcodes/code-128.png" alt-text="Screenshot of the Code 128.":::|
+| `UPC (UPC-A & UPC-E)` |:::image type="content" source="../media/barcodes/upc.png" alt-text="Screenshot of the UPC.":::|
+| `PDF417` |:::image type="content" source="../media/barcodes/pdf-417.png" alt-text="Screenshot of the PDF417.":::|
+| `EAN-8` |:::image type="content" source="../media/barcodes/european-article-number-8.gif" alt-text="Screenshot of the European-article-number barcode ean-8.":::|
+| `EAN-13` |:::image type="content" source="../media/barcodes/european-article-number-13.gif" alt-text="Screenshot of the European-article-number barcode ean-13.":::|
+| `Codabar` |:::image type="content" source="../media/barcodes/codabar.png" alt-text="Screenshot of the Codabar.":::|
+| `Databar` |:::image type="content" source="../media/barcodes/databar.png" alt-text="Screenshot of the Data bar.":::|
+| `Databar` Expanded |:::image type="content" source="../media/barcodes/databar-expanded.gif" alt-text="Screenshot of the Data bar Expanded.":::|
+| `ITF` |:::image type="content" source="../media/barcodes/interleaved-two-five.png" alt-text="Screenshot of the interleaved-two-of-five barcode (ITF).":::|
+| `Data Matrix` |:::image type="content" source="../media/barcodes/datamatrix.gif" alt-text="Screenshot of the Data Matrix.":::|
 
 ::: moniker range="doc-intel-4.0.0"
 
@@ -1064,11 +1064,11 @@ For query field extraction, specify the fields you want to extract and Document
 
 * If you're processing a contract in the [Document Intelligence Studio](https://formrecognizer.appliedai.azure.com/studio/document), use the `2024-02-29-preview` or `2023-10-31-preview` versions:
 
-    :::image type="content" source="media/studio/query-fields.png" alt-text="Screenshot of the query fields button in Document Intelligence Studio.":::
+    :::image type="content" source="../media/studio/query-fields.png" alt-text="Screenshot of the query fields button in Document Intelligence Studio.":::
 
 * You can pass a list of field labels like `Party1`, `Party2`, `TermsOfUse`, `PaymentTerms`, `PaymentDate`, and `TermEndDate` as part of the `analyze document` request.
 
-   :::image type="content" source="media/studio/query-field-select.png" alt-text="Screenshot of query fields selection window in Document Intelligence Studio.":::
+   :::image type="content" source="../media/studio/query-field-select.png" alt-text="Screenshot of query fields selection window in Document Intelligence Studio.":::
 
 * Document Intelligence is able to analyze and extract the field data and return the values in a structured JSON output.
 
@@ -1119,7 +1119,7 @@ Invoice number: 34278587
 
 > [!div class="nextstepaction"]
 > Learn more:
-> [**Read model**](prebuilt/read.md) [**Layout model**](concept-layout.md)
+> [**Read model**](../prebuilt/read.md) [**Layout model**](../prebuilt/layout.md)
 
 > [!div class="nextstepaction"]
 > SDK samples:

articles/ai-services/document-intelligence/concept/analyze-document-response.md

@@ -19,7 +19,7 @@ In this article, let's examine the different objects returned as part of the `An
 
 ## Analyze document request
 
-The Document Intelligence APIs analyze images, PDFs, and other document files to extract and detect various content, layout, style, and semantic elements. The `Analyze` operation is an async API. Submitting a document returns an **Operation-Location** header that contains the URL to poll for completion. When an analysis request completes successfully, the response contains the elements described in the [model data extraction](../concept-model-overview.md#model-data-extraction).
+The Document Intelligence APIs analyze images, PDFs, and other document files to extract and detect various content, layout, style, and semantic elements. The `Analyze` operation is an async API. Submitting a document returns an **Operation-Location** header that contains the URL to poll for completion. When an analysis request completes successfully, the response contains the elements described in the [model data extraction](../model-overview.md#model-data-extraction).
 
 ### Response elements
 
@@ -54,7 +54,7 @@ The `Analyze` response for each API returns different objects. API responses con
 | **keyValuePairs**| Key-value pairs recognized by a pretrained model. The key is a span of text from the document with the associated value. | General document and Invoice models |
 | **documents**| Fields recognized are returned in the `fields` dictionary within the list of documents| Prebuilt models, Custom models.|
 
-For more information on the objects returned by each API, see [model data extraction](../concept-model-overview.md#model-data-extraction).
+For more information on the objects returned by each API, see [model data extraction](../model-overview.md#model-data-extraction).
 
 ## Element properties
 
@@ -167,7 +167,7 @@ When *output=figures* is specified during the initial `Analyze` operation, the s
 
 #### Sections
 
-Hierarchical document structure analysis is pivotal in organizing, comprehending, and processing extensive documents. This approach is vital for semantically segmenting long documents to boost comprehension, facilitate navigation, and improve information retrieval. The advent of [Retrieval Augmented Generation (RAG)](../concept-retrieval-augmented-generation.md) in document generative AI underscores the significance of hierarchical document structure analysis. The Layout model supports sections and subsections in the output, which identifies the relationship of sections and object within each section. The hierarchical structure is maintained in `elements` of each section.
+Hierarchical document structure analysis is pivotal in organizing, comprehending, and processing extensive documents. This approach is vital for semantically segmenting long documents to boost comprehension, facilitate navigation, and improve information retrieval. The advent of [Retrieval Augmented Generation (RAG)](../concept/retrieval-augmented-generation.md) in document generative AI underscores the significance of hierarchical document structure analysis. The Layout model supports sections and subsections in the output, which identifies the relationship of sections and object within each section. The hierarchical structure is maintained in `elements` of each section.
 
 ```json
 {