Skip to content

Commit 42e4e85

Browse files
authored
Update concept-custom.md
1 parent f24300f commit 42e4e85

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

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

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -102,26 +102,6 @@ In the Form Recognizer UI:
102102

103103
* 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.
104104

105-
### Try signature detection
106-
107-
1. [**Build your training data set**](build-training-data-set.md#custom-model-input-requirements).
108-
109-
1. Navigate to the [**Form Recognizer sample labeling tool**](https://fott-preview-private.azurewebsites.net) and select **Use Custom to train a models with labels and get key value pairs**:
110-
111-
:::image type="content" source="media/label-tool/fott-use-custom.png" alt-text="Screenshot: FOTTtools selection of the custom option.":::
112-
113-
1. In the next window, select **New project**:
114-
115-
:::image type="content" source="media/label-tool/fott-new-project.png" alt-text="Screenshot: FOTTtools select new project.":::
116-
117-
1. Follow the [**Custom model input requirements**](build-training-data-set.md#custom-model-input-requirements).
118-
119-
1. Create a label with the type **Signature**.
120-
121-
1. **Label your documents**. For signature fields, using region labeling is recommended for better accuracy.
122-
123-
1. 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.
124-
125105
## Next steps
126106

127107
* Complete a Form Recognizer quickstart:

0 commit comments

Comments
 (0)