Skip to content

Commit 95473be

Browse files
committed
add images update conceptuals
1 parent 770b101 commit 95473be

File tree

3 files changed

+47
-47
lines changed

3 files changed

+47
-47
lines changed

articles/applied-ai-services/form-recognizer/concept-custom.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -28,15 +28,15 @@ A custom model is a machine learning program trained to recognize form fields wi
2828

2929
## What is a composed model?
3030

31-
With composed models, you can assign multiple custom models to a composed model called with a single model ID. This is useful when you have trained several models and want to group them to analyze similar form types. For example, your composed model may include custom models trained to analyze your supply, equipment, and furniture purchase orders. Instead of manually trying to select the appropriate model, you can use a composed model to determine the appropriate custom model for each analysis and extraction.
31+
With composed models, you can assign multiple custom models to a composed model called with a single model ID. It is useful when you have trained several models and want to group them to analyze similar form types. For example, your composed model may include custom models trained to analyze your supply, equipment, and furniture purchase orders. Instead of manually trying to select the appropriate model, you can use a composed model to determine the appropriate custom model for each analysis and extraction.
3232

3333
## Try Form Recognizer
3434

3535
See how data is extracted from your specific or unique documents using custom models. You'll need the following:
3636

3737
* An Azure subscription—you can [create one for free](https://azure.microsoft.com/free/cognitive-services/)
3838

39-
* A [Form Recognizer instance](https://ms.portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) in the Azure portal. You can use the free pricing tier (`F0`) to try the service. After your resource deploys, click **Go to resource** to get your API key and endpoint.
39+
* A [Form Recognizer instance](https://ms.portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) in the Azure portal. You can use the free pricing tier (`F0`) to try the service. After your resource deploys, select **Go to resource** to get your API key and endpoint.
4040

4141
:::image type="content" source="media/containers/keys-and-endpoint.png" alt-text="Screenshot: keys and endpoint location in the Azure portal.":::
4242

@@ -47,17 +47,17 @@ See how data is extracted from your specific or unique documents using custom m
4747
4848
1. On the Form Recognizer Studio home page, select **Custom form**.
4949

50-
1. Under **My Projects** select **+ Create a project**.
50+
1. Under **My Projects**, select **+ Create a project**.
5151

5252
1. Complete the **project details** fields.
5353

54-
1. **Configure the service resource**.
54+
1. **Configure the service resource**.
5555

5656
1. Add your **Storage account** and **Blob container** to **Connect your training data source**.
5757

5858
1. **Review and create** your project.
5959

60-
1. A set of sample documents have been provided for you to build and test your custom model.
60+
1. A set of sample documents has been provided for you to build and test your custom model.
6161

6262
> [!div class="nextstepaction"]
6363
> [Try Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio/customform/projects)
@@ -126,7 +126,7 @@ In the Form Recognizer UI:
126126

127127
1. Navigate to the [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio) and select **Custom form** under Custom models:
128128

129-
:::image type="content" source="media/label-tool/select-custom-form.png" alt-text="Screenshot: Form Recognizer Studio select custom form.":::
129+
:::image type="content" source="media/label-tool/select-custom-form.png" alt-text="Screenshot: Form Recognizer Studio select a custom form page.":::
130130

131131
1. Follow the workflow to create a new project:
132132

articles/applied-ai-services/form-recognizer/concept-invoice.md

Lines changed: 35 additions & 35 deletions
Original file line numberDiff line numberDiff line change
@@ -84,48 +84,48 @@ You will need an invoice document. You can use our [sample invoice document](htt
8484

8585
|Name| Type | Description | Standardized output |
8686
|:-----|:----|:----|:---:|
87-
| CustomerName | string | Invoiced customer| |
88-
| CustomerId | string | Customer reference ID | |
89-
| PurchaseOrder | string | Purchase order reference number | |
90-
| InvoiceId | string | ID for this specific invoice (often "Invoice Number") | |
91-
| InvoiceDate | date | Date the invoice was issued | yyyy-mm-dd|
92-
| DueDate | date | Date payment for this invoice is due | yyyy-mm-dd|
93-
| VendorName | string | Vendor name | |
94-
| VendorAddress | string | Vendor mailing address| |
95-
| VendorAddressRecipient | string | Name associated with the VendorAddress | |
96-
| CustomerAddress | string | Mailing address for the Customer | |
97-
| CustomerAddressRecipient | string | Name associated with the CustomerAddress | |
98-
| BillingAddress | string | Explicit billing address for the customer | |
99-
| BillingAddressRecipient | string | Name associated with the BillingAddress | |
100-
| ShippingAddress | string | Explicit shipping address for the customer | |
101-
| ShippingAddressRecipient | string | Name associated with the ShippingAddress | |
102-
| SubTotal | number | Subtotal field identified on this invoice | integer |
103-
| TotalTax | number | Total tax field identified on this invoice | integer |
104-
| InvoiceTotal | number (USD) | Total new charges associated with this invoice | integer |
105-
| AmountDue | number (USD) | Total Amount Due to the vendor | integer |
106-
| ServiceAddress | string | Explicit service address or property address for the customer | |
107-
| ServiceAddressRecipient | string | Name associated with the ServiceAddress | |
108-
| RemittanceAddress | string | Explicit remittance or payment address for the customer | |
109-
| RemittanceAddressRecipient | string | Name associated with the RemittanceAddress | |
110-
| ServiceStartDate | date | First date for the service period (for example, a utility bill service period) | yyyy-mm-dd |
111-
| ServiceEndDate | date | End date for the service period (for example, a utility bill service period) | yyyy-mm-dd|
112-
| PreviousUnpaidBalance | number | Explicit previously unpaid balance | integer |
87+
| CustomerName | String | Invoiced customer| |
88+
| CustomerId | String | Customer reference ID | |
89+
| PurchaseOrder | String | Purchase order reference number | |
90+
| InvoiceId | String | ID for this specific invoice (often "Invoice Number") | |
91+
| InvoiceDate | Date | Date the invoice was issued | yyyy-mm-dd|
92+
| DueDate | Date | Date payment for this invoice is due | yyyy-mm-dd|
93+
| VendorName | String | Vendor name | |
94+
| VendorAddress | String | Vendor mailing address| |
95+
| VendorAddressRecipient | String | Name associated with the VendorAddress | |
96+
| CustomerAddress | String | Mailing address for the Customer | |
97+
| CustomerAddressRecipient | String | Name associated with the CustomerAddress | |
98+
| BillingAddress | String | Explicit billing address for the customer | |
99+
| BillingAddressRecipient | String | Name associated with the BillingAddress | |
100+
| ShippingAddress | String | Explicit shipping address for the customer | |
101+
| ShippingAddressRecipient | String | Name associated with the ShippingAddress | |
102+
| SubTotal | Number | Subtotal field identified on this invoice | Integer |
103+
| TotalTax | Number | Total tax field identified on this invoice | Integer |
104+
| InvoiceTotal | Number (USD) | Total new charges associated with this invoice | Integer |
105+
| AmountDue | Number (USD) | Total Amount Due to the vendor | Integer |
106+
| ServiceAddress | String | Explicit service address or property address for the customer | |
107+
| ServiceAddressRecipient | String | Name associated with the ServiceAddress | |
108+
| RemittanceAddress | String | Explicit remittance or payment address for the customer | |
109+
| RemittanceAddressRecipient | String | Name associated with the RemittanceAddress | |
110+
| ServiceStartDate | Date | First date for the service period (for example, a utility bill service period) | yyyy-mm-dd |
111+
| ServiceEndDate | Date | End date for the service period (for example, a utility bill service period) | yyyy-mm-dd|
112+
| PreviousUnpaidBalance | Number | Explicit previously unpaid balance | Integer |
113113

114114
### Line items
115115

116116
Following are the line items extracted from an invoice in the JSON output response (the output below uses this [sample invoice](media/sample-invoice.jpg))
117117

118118
|Name| Type | Description | Text (line item #1) | Value (standardized output) |
119119
|:-----|:----|:----|:----| :----|
120-
| Items | string | Full string text line of the line item | 3/4/2021 A123 Consulting Services 2 hours $30.00 10% $60.00 | |
121-
| Amount | number | The amount of the line item | $60.00 | 100 |
122-
| Description | string | The text description for the invoice line item | Consulting service | Consulting service |
123-
| Quantity | number | The quantity for this invoice line item | 2 | 2 |
124-
| UnitPrice | number | The net or gross price (depending on the gross invoice setting of the invoice) of one unit of this item | $30.00 | 30 |
125-
| ProductCode | string| Product code, product number, or SKU associated with the specific line item | A123 | |
126-
| Unit | string| The unit of the line item, e.g, kg, lb etc. | hours | |
127-
| Date | date| Date corresponding to each line item. Often it is a date the line item was shipped | 3/4/2021| 2021-03-04 |
128-
| Tax | number | Tax associated with each line item. Possible values include tax amount, tax %, and tax Y/N | 10% | |
120+
| Items | String | Full string text line of the line item | 3/4/2021 A123 Consulting Services 2 hours $30.00 10% $60.00 | |
121+
| Amount | Number | The amount of the line item | $60.00 | 100 |
122+
| Description | String | The text description for the invoice line item | Consulting service | Consulting service |
123+
| Quantity | Number | The quantity for this invoice line item | 2 | 2 |
124+
| UnitPrice | Number | The net or gross price (depending on the gross invoice setting of the invoice) of one unit of this item | $30.00 | 30 |
125+
| ProductCode | String| Product code, product number, or SKU associated with the specific line item | A123 | |
126+
| Unit | String| The unit of the line item, e.g, kg, lb etc. | Hours | |
127+
| Date | Date| Date corresponding to each line item. Often it is a date the line item was shipped | 3/4/2021| 2021-03-04 |
128+
| Tax | Number | Tax associated with each line item. Possible values include tax amount, tax %, and tax Y/N | 10% | |
129129

130130
The invoice key-value pairs and line items extracted are in the `documentResults` section of the JSON output.
131131

articles/applied-ai-services/form-recognizer/concept-layout.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Layouts - Form Recognizer
33
titleSuffix: Azure Applied AI Services
4-
description: Learn concepts related to layout analysis with the Form Recognizer API - usage and limits.
4+
description: Learn concepts related to Layout API analysis with Form Recognizer APIusage and limits.
55
author: laujan
66
manager: nitinme
77
ms.service: applied-ai-services
@@ -14,7 +14,7 @@ recommendations: false
1414

1515
# Form Recognizer layout model
1616

17-
Azure the Form Recognizer Layout API extracts text, tables, selection marks, and structure information from documents (PDF, TIFF) and images (JPG, PNG, BMP). It enables customers to take documents in various formats and return structured data representations of the documents. It combines an enhanced version of our powerful [Optical Character Recognition (OCR)](../../cognitive-services/computer-vision/overview-ocr.md) capabilities with deep learning models to extract text, tables, selection marks, and document structure.
17+
Azure the Form Recognizer Layout API extracts text, tables, selection marks, and structure information from documents (PDF, TIFF) and images (JPG, PNG, BMP). The layout model combines an enhanced version of our powerful [Optical Character Recognition (OCR)](../../cognitive-services/computer-vision/overview-ocr.md) capabilities with deep learning models to extract text, tables, selection marks, and document structure.
1818

1919
***Sample form processed with [Form Recognizer Sample Labeling tool](https://fott-2-1.azurewebsites.net/) layout feature***
2020

@@ -28,11 +28,11 @@ Azure the Form Recognizer Layout API extracts text, tables, selection marks, and
2828

2929
## Try Form Recognizer
3030

31-
See how layout data, including tables, check boxes, and text is extracted from forms and documents using the Form Recognizer Studio or our Sample Labeling tool. You'll need the following:
31+
See how data, including tables, check boxes, and text, is extracted from forms and documents using the Form Recognizer Studio or our Sample Labeling tool. You'll need the following:
3232

3333
* An Azure subscription—you can [create one for free](https://azure.microsoft.com/free/cognitive-services/)
3434

35-
* A [Form Recognizer instance](https://ms.portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) in the Azure portal. You can use the free pricing tier (`F0`) to try the service. After your resource deploys, click **Go to resource** to get your API key and endpoint.
35+
* A [Form Recognizer instance](https://ms.portal.azure.com/#create/Microsoft.CognitiveServicesFormRecognizer) in the Azure portal. You can use the free pricing tier (`F0`) to try the service. After your resource deploys, select **Go to resource** to get your API key and endpoint.
3636

3737
:::image type="content" source="media/containers/keys-and-endpoint.png" alt-text="Screenshot: keys and endpoint location in the Azure portal.":::
3838

@@ -43,7 +43,7 @@ See how layout data, including tables, check boxes, and text is extracted from f
4343
4444
***Sample form processed with [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio/layout)***
4545

46-
:::image type="content" source="media/studio/sample-layout.png" alt-text="Screenshot: layout processing in Form Recognizer Studio.":::
46+
:::image type="content" source="media/studio/sample-layout.png" alt-text="Screenshot: document processing in Form Recognizer Studio.":::
4747

4848
1. On the Form Recognizer Studio home page, select **Layout**
4949

@@ -58,7 +58,7 @@ See how layout data, including tables, check boxes, and text is extracted from f
5858
5959
### Sample Labeling tool
6060

61-
You will need a form document. You can use our [sample form document](https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/master/curl/form-recognizer/sample-layout.pdf).
61+
You'll need a form document. You can use our [sample form document](https://raw.githubusercontent.com/Azure-Samples/cognitive-services-REST-api-samples/master/curl/form-recognizer/sample-layout.pdf).
6262

6363
1. On the Sample Labeling tool home page, select **Use Layout to get text, tables, and selection marks**.
6464

0 commit comments

Comments
 (0)