Skip to content

Commit 8ba329a

Browse files
authored
Merge pull request #176640 from laujan/update-concept-custom
update signature detection
2 parents 67a5e7a + 3c97e99 commit 8ba329a

File tree

5 files changed

+27
-8
lines changed

5 files changed

+27
-8
lines changed

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

Lines changed: 27 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ manager: nitinme
77
ms.service: applied-ai-services
88
ms.subservice: forms-recognizer
99
ms.topic: conceptual
10-
ms.date: 10/07/2021
10+
ms.date: 10/16/2021
1111
ms.author: lajanuar
1212
recommendations: false
1313
---
@@ -20,8 +20,7 @@ Form Recognizer uses advanced machine learning technology to detect and extract
2020

2121
* **Composed models**. A composed model is created by taking a collection of custom models and assigning them to a single model that encompasses your form types. When a document is submitted to a composed model, the service performs a classification step to decide which custom model accurately represents the form presented for analysis.
2222

23-
:::image type="content" source="media/analyze.png" alt-text="Screenshot: Form Recognizer tool analyze-a-custom-form window.":::
24-
23+
:::image type="content" source="media/analyze-studio.png" alt-text="Screenshot: Form Recognizer tool analyze-a-custom-form window.":::
2524

2625
## What is a custom model?
2726

@@ -31,7 +30,7 @@ A custom model is a machine learning program trained to recognize form fields wi
3130

3231
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.
3332

34-
## Try Form Recognizer Studio (Preview)
33+
## Form Recognizer Studio (Preview)
3534

3635
* Form Recognizer studio is available with the preview (v3.0) API.
3736

@@ -40,13 +39,13 @@ With composed models, you can assign multiple custom models to a composed model
4039
> [!div class="nextstepaction"]
4140
> [Try Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio/customform/projects)
4241
43-
## Try Form Recognizer Sample labeling tool
42+
## Sample Labeling tool
4443

4544
You can see how data is extracted from custom forms by trying our Sample Labeling tool. You'll need the following:
4645

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

49-
* 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.
48+
* 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.
5049

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

@@ -74,8 +73,8 @@ In the Form Recognizer UI:
7473
* The total size of the training data is 500 pages or less.
7574
* If your PDFs are password-locked, you must remove the lock before submission.
7675
* For unsupervised learning (without labeled data):
77-
* data must contain keys and values.
78-
* keys must appear above or to the left of the values; they can't appear below or to the right.
76+
* Data must contain keys and values.
77+
* Keys must appear above or to the left of the values; they can't appear below or to the right.
7978

8079
> [!TIP]
8180
> **Training data**
@@ -102,6 +101,26 @@ In the Form Recognizer UI:
102101

103102
* Explore our [**REST API (preview)**](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v3-0-preview-1/operations/AnalyzeDocument) to learn more about the preview version and new capabilities.
104103

104+
### Try signature detection
105+
106+
1. Build your training data set.
107+
108+
1. Navigate to the [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio) and select **Custom form** under Custom models:
109+
110+
:::image type="content" source="media/label-tool/select-custom-form.png" alt-text="Screenshot: Form Recognizer Studio select custom form.":::
111+
112+
1. Follow the workflow to create a new project:
113+
114+
1. Follow the Custom model input requirements.
115+
116+
1. Create a label with the type **Signature**.
117+
118+
1. Label your documents. For signature fields, using region labeling is recommended for better accuracy.
119+
120+
:::image type="content" source="media/label-tool/signature-label-region-too.png" alt-text="Screenshot: Label signature field.":::
121+
122+
Once your training set has been labeled, you can train your custom model and use it to analyze documents. The signature fields will specify whether a signature was detected or not.
123+
105124
## Next steps
106125

107126
* Complete a Form Recognizer quickstart:
103 KB
Loading
30.9 KB
Loading
255 KB
Loading
188 KB
Loading

0 commit comments

Comments
 (0)