Skip to content

Commit e0ab313

Browse files
committed
resolve links
1 parent f18cf7a commit e0ab313

File tree

4 files changed

+15
-15
lines changed

4 files changed

+15
-15
lines changed

articles/applied-ai-services/form-recognizer/how-to-guides/build-a-custom-classifier.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -45,7 +45,7 @@ Once you've put together the set of forms or documents for training, you need to
4545

4646
The Form Recognizer Studio provides and orchestrates all the API calls required to complete your dataset and train your model.
4747

48-
1. Start by navigating to the [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio). The first time you use the Studio, you need to [initialize your subscription, resource group, and resource](../quickstarts/try-form-recognizer-studio.md). Then, follow the [prerequisites for custom projects](../quickstarts/try-form-recognizer-studio.md#additional-prerequisites-for-custom-projects) to configure the Studio to access your training dataset.
48+
1. Start by navigating to the [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio). The first time you use the Studio, you need to [initialize your subscription, resource group, and resource](../quickstarts/try-form-recognizer-studio.md). Then, follow the [prerequisites for custom projects](../quickstarts/try-form-recognizer-studio.md#added-prerequisites-for-custom-projects) to configure the Studio to access your training dataset.
4949

5050
1. In the Studio, select the **Custom classification model** tile, on the custom models section of the page and select the **Create a project** button.
5151

articles/applied-ai-services/form-recognizer/how-to-guides/build-a-custom-model.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -43,19 +43,19 @@ Follow these tips to further optimize your data set for training:
4343

4444
## Upload your training data
4545

46-
Once you've put together the set of forms or documents for training, you'll need to upload it to an Azure blob storage container. If you don't know how to create an Azure storage account with a container, following the [Azure Storage quickstart for Azure portal](../../../storage/blobs/storage-quickstart-blobs-portal.md). You can use the free pricing tier (F0) to try the service, and upgrade later to a paid tier for production.
46+
Once you've put together the set of forms or documents for training, you need to upload it to an Azure blob storage container. If you don't know how to create an Azure storage account with a container, following the [Azure Storage quickstart for Azure portal](../../../storage/blobs/storage-quickstart-blobs-portal.md). You can use the free pricing tier (F0) to try the service, and upgrade later to a paid tier for production.
4747

4848
## Video: Train your custom model
4949

50-
* Once you've gathered and uploaded your training dataset, you're ready to train your custom model. In the following video, we'll create a project and explore some of the fundamentals for successfully labeling and training a model.</br></br>
50+
* Once you've gathered and uploaded your training dataset, you're ready to train your custom model. In the following video, we create a project and explore some of the fundamentals for successfully labeling and training a model.</br></br>
5151

5252
> [!VIDEO https://www.microsoft.com/en-us/videoplayer/embed/RE5fX1c]
5353
5454
## Create a project in the Form Recognizer Studio
5555

5656
The Form Recognizer Studio provides and orchestrates all the API calls required to complete your dataset and train your model.
5757

58-
1. Start by navigating to the [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio). The first time you use the Studio, you'll need to [initialize your subscription, resource group, and resource](../quickstarts/try-form-recognizer-studio.md). Then, follow the [prerequisites for custom projects](../quickstarts/try-form-recognizer-studio.md#additional-prerequisites-for-custom-projects) to configure the Studio to access your training dataset.
58+
1. Start by navigating to the [Form Recognizer Studio](https://formrecognizer.appliedai.azure.com/studio). The first time you use the Studio, you need to [initialize your subscription, resource group, and resource](../quickstarts/try-form-recognizer-studio.md). Then, follow the [prerequisites for custom projects](../quickstarts/try-form-recognizer-studio.md#added-prerequisites-for-custom-projects) to configure the Studio to access your training dataset.
5959

6060
1. In the Studio, select the **Custom models** tile, on the custom models page and select the **Create a project** button.
6161

@@ -78,23 +78,23 @@ The Form Recognizer Studio provides and orchestrates all the API calls required
7878

7979
## Label your data
8080

81-
In your project, your first task is to label your dataset with the fields you wish to extract.
81+
In your project, your first task is to label your dataset with the fields you wish to extract.
8282

83-
You'll see the files you uploaded to storage on the left of your screen, with the first file ready to be labeled.
83+
The files you uploaded to storage are listed on the left of your screen, with the first file ready to be labeled.
8484

8585
1. To start labeling your dataset, create your first field by selecting the plus (➕) button on the top-right of the screen to select a field type.
8686

8787
:::image type="content" source="../media/how-to/studio-create-label.png" alt-text="Screenshot: Create a label.":::
8888

8989
1. Enter a name for the field.
9090

91-
1. To assign a value to the field, choose a word or words in the document and select the field in either the dropdown or the field list on the right navigation bar. You'll see the labeled value below the field name in the list of fields.
91+
1. To assign a value to the field, choose a word or words in the document and select the field in either the dropdown or the field list on the right navigation bar. The labeled value is below the field name in the list of fields.
9292

9393
1. Repeat the process for all the fields you wish to label for your dataset.
9494

9595
1. Label the remaining documents in your dataset by selecting each document and selecting the text to be labeled.
9696

97-
You now have all the documents in your dataset labeled. If you look at the storage account, you'll find a *.labels.json* and *.ocr.json* files that correspond to each document in your training dataset and a new fields.json file. This training dataset will be submitted to train the model.
97+
You now have all the documents in your dataset labeled. The *.labels.json* and *.ocr.json* files correspond to each document in your training dataset and a new fields.json file. This training dataset is submitted to train the model.
9898

9999
## Train your model
100100

@@ -173,21 +173,21 @@ Follow these tips to further optimize your data set for training.
173173

174174
## Upload your training data
175175

176-
When you've put together the set of form documents that you'll use for training, you need to upload it to an Azure blob storage container. If you don't know how to create an Azure storage account with a container, follow the [Azure Storage quickstart for Azure portal](../../../storage/blobs/storage-quickstart-blobs-portal.md). Use the standard performance tier.
176+
When you've put together the set of form documents for training, you need to upload it to an Azure blob storage container. If you don't know how to create an Azure storage account with a container, follow the [Azure Storage quickstart for Azure portal](../../../storage/blobs/storage-quickstart-blobs-portal.md). Use the standard performance tier.
177177

178-
If you want to use manually labeled data, you'll also have to upload the *.labels.json* and *.ocr.json* files that correspond to your training documents. You can use the [Sample Labeling tool](../label-tool.md) (or your own UI) to generate these files.
178+
If you want to use manually labeled data, upload the *.labels.json* and *.ocr.json* files that correspond to your training documents. You can use the [Sample Labeling tool](../label-tool.md) (or your own UI) to generate these files.
179179

180180
### Organize your data in subfolders (optional)
181181

182-
By default, the [Train Custom Model](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/TrainCustomModelAsync) API will only use documents that are located at the root of your storage container. However, you can train with data in subfolders if you specify it in the API call. Normally, the body of the [Train Custom Model](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/TrainCustomModelAsync) call has the following format, where `<SAS URL>` is the Shared access signature URL of your container:
182+
By default, the [Train Custom Model](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/TrainCustomModelAsync) API only uses documents that are located at the root of your storage container. However, you can train with data in subfolders if you specify it in the API call. Normally, the body of the [Train Custom Model](https://westus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1/operations/TrainCustomModelAsync) call has the following format, where `<SAS URL>` is the Shared access signature URL of your container:
183183

184184
```json
185185
{
186186
"source":"<SAS URL>"
187187
}
188188
```
189189

190-
If you add the following content to the request body, the API will train with documents located in subfolders. The `"prefix"` field is optional and will limit the training data set to files whose paths begin with the given string. So a value of `"Test"`, for example, will cause the API to look at only the files or folders that begin with the word "Test".
190+
If you add the following content to the request body, the API trains with documents located in subfolders. The `"prefix"` field is optional and limits the training data set to files whose paths begin with the given string. So a value of `"Test"`, for example, causes the API to look at only the files or folders that begin with the word *Test*.
191191

192192
```json
193193
{

articles/applied-ai-services/form-recognizer/label-tool.md

Lines changed: 2 additions & 2 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: how-to
10-
ms.date: 03/03/2023
10+
ms.date: 06/23/2023
1111
ms.author: lajanuar
1212
monikerRange: 'form-recog-2.1.0'
1313
---
@@ -280,7 +280,7 @@ With Model Compose, you can compose up to 200 models to a single model ID. When
280280

281281
## Analyze a form
282282

283-
Select the Analyze icon from the navigation bar to test your model. Select source 'Local file'. Browse for a file and select a file from the sample dataset that you unzipped in the test folder. Then choose the **Run analysis** button to get key/value pairs, text and tables predictions for the form. The tool applies tags in bounding boxes and reports the confidence of each tag.
283+
Select the Analyze icon from the navigation bar to test your model. Select source *Local file*. Browse for a file and select a file from the sample dataset that you unzipped in the test folder. Then choose the **Run analysis** button to get key/value pairs, text and tables predictions for the form. The tool applies tags in bounding boxes and reports the confidence of each tag.
284284

285285
:::image type="content" source="media/analyze.png" alt-text="Screenshot: analyze-a-custom-form window":::
286286

articles/applied-ai-services/form-recognizer/whats-new.md

Lines changed: 1 addition & 1 deletion
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: whats-new
10-
ms.date: 05/23/2023
10+
ms.date: 06/23/2023
1111
ms.author: lajanuar
1212
monikerRange: '>=form-recog-2.1.0'
1313
ms.custom: references_regions

0 commit comments

Comments
 (0)