You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/cognitive-services/form-recognizer/concept-business-cards.md
+17-20Lines changed: 17 additions & 20 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,39 +15,40 @@ ms.author: pafarley
15
15
16
16
# Business card concepts
17
17
18
-
Azure Form Recognizer can analyze and extract key value pairs from business cards using one of its prebuilt models. The Business Card API combines powerful Optical Character Recognition (OCR) capabilities with our Business Card Understanding model to extract key information from business cards in English. It extracts personal contact info, company name, job title, and more. The Prebuilt Business Card API is publicly available in the Form Recognizer v2.1 preview.
18
+
Azure Form Recognizer can analyze and extract contact information from business cards using one of its prebuilt models. The Business Card API combines powerful Optical Character Recognition (OCR) capabilities with our Business Card Understanding model to extract key information from business cards in English. It extracts personal contact info, company name, job title, and more. The Prebuilt Business Card API is publicly available in the Form Recognizer v2.1 preview.
19
19
20
20
## What does the Business Card API do?
21
21
22
22
The Business Card API extracts key fields from business cards and returns them in an organized JSON response.
23
23
24
24

25
25
26
-
### Fields Extracted:
27
-
* Contact Names
28
-
* First Name
29
-
* Last Name
30
-
* Company Names
26
+
### Fields extracted:
27
+
28
+
* Contact names
29
+
* First names
30
+
* Last names
31
+
* Company names
31
32
* Departments
32
-
* Job Titles
33
+
* Job titles
33
34
* Emails
34
35
* Websites
35
36
* Addresses
36
-
* Phone Numbers
37
-
* Mobile Phones
37
+
* Phone numbers
38
+
* Mobile phones
38
39
* Faxes
39
-
* Work Phones
40
-
* Other Phones
40
+
* Work phones
41
+
* Other phones
41
42
42
-
The Business Card API also returns all recognized text from the Business Card. This OCR output is included in the JSON response.
43
+
The Business Card API can also return all recognized text from the Business Card. This OCR output is included in the JSON response.
The [Analyze Business Card](https://westcentralus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1-preview-1/operations/AnalyzeBusinessCardAsync) takes an image or PDF of a business card as the input and extracts the values of interest and text. The call returns a response header field called `Operation-Location`. The `Operation-Location` value is a URL that contains the Result ID to be used in the next step.
51
+
The [Analyze Business Card](https://westcentralus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1-preview-1/operations/AnalyzeBusinessCardAsync) takes an image or PDF of a business card as the input and extracts the values of interest. The call returns a response header field called `Operation-Location`. The `Operation-Location` value is a URL that contains the Result ID to be used in the next step.
51
52
52
53
|Response header| Result URL |
53
54
|:-----|:----|
@@ -59,19 +60,16 @@ The second step is to call the [Get Analyze Business Card Result](https://westce
59
60
60
61
|Field| Type | Possible values |
61
62
|:-----|:----:|:----|
62
-
|status | string | notStarted: The analysis operation has not started. |
63
-
||| running: The analysis operation is in progress. |
64
-
||| failed: The analysis operation has failed. |
65
-
||| succeeded: The analysis operation has succeeded. |
63
+
|status | string | notStarted: The analysis operation has not started.<br /><br />running: The analysis operation is in progress.<br /><br />failed: The analysis operation has failed.<br /><br />succeeded: The analysis operation has succeeded.|
66
64
67
-
When the **status** field has the **succeeded** value, the JSON response will include the business card understanding and text recognition results. The business card understanding result is organized as a dictionary of named field values, where each value contains the extracted text, normalized value, bounding box, confidence and corresponding word elements. The text recognition result is organized as a hierarchy of lines and words, with text, bounding box and confidence information.
65
+
When the **status** field has the **succeeded** value, the JSON response will include the business card understanding and optional text recognition results, if requested. The business card understanding result is organized as a dictionary of named field values, where each value contains the extracted text, normalized value, bounding box, confidence and corresponding word elements. The text recognition result is organized as a hierarchy of lines and words, with text, bounding box and confidence information.
68
66
69
67

70
68
71
69
### Sample JSON output
72
70
73
71
See the following example of a successful JSON response:
74
-
The "readResults" node contains all of the recognized text. Text is organized by page, then by line, then by individual words. The "documentResults" node contains the business-card-specific values that the model discovered. This is where you'll find useful key/value pairs like the first name, last name, company name and more.
72
+
The "readResults" node contains all of the recognized text. Text is organized by page, then by line, then by individual words. The "documentResults" node contains the business-card-specific values that the model discovered. This is where you'll find useful contact information like the first name, last name, company name and more.
75
73
76
74
```json
77
75
{
@@ -392,4 +390,3 @@ The Business Card API also powers the [AIBuilder Business Card Processing featur
392
390
- Learn about the [Form Recognizer REST API](https://westcentralus.dev.cognitive.microsoft.com/docs/services/form-recognizer-api-v2-1-preview-1/operations/AnalyzeBusinessCardAsync)
Copy file name to clipboardExpand all lines: articles/machine-learning/data-science-virtual-machine/reference-deprecation.md
-15Lines changed: 0 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -46,18 +46,3 @@ Existing DSVM provisioned images in your subscription will continue to operate a
46
46
>
47
47
> ARM templates that have not been updated with the new DSVM image details will fail to to deploy after the retirement date.
48
48
49
-
## Mitigating upcoming retirements
50
-
51
-
In this section, we discuss mitigation to upcoming retirements.
52
-
53
-
### Upgrade Windows 2016 DSVM
54
-
55
-
In order to migrate a data disk from your existing Windows 2016 DSVM to a Windows 2019 DSVM, take the following steps:
56
-
57
-
1. Create a new Windows 2019 DSVM, following the instructions shown [here](./provision-vm.md#create-your-dsvm).
58
-
1. Detach existing data disks from your Windows 2016 image using [these instructions](../../virtual-machines/windows/detach-disk.md).
59
-
1. Attach the disk from the previous step to your Windows 2019 image using [these instructions](../../virtual-machines/windows/attach-disk-ps.md#attach-an-existing-data-disk-to-a-vm).
60
-
61
-
### Upgrade Ubuntu 16.04 DSVM
62
-
63
-
We recommend upgrading existing Ubuntu 16.04 DSVMs to the [Ubuntu 18.04 DSVM edition](./dsvm-ubuntu-intro.md).
@@ -558,5 +558,5 @@ Contributions and suggestions for Azurite are welcome. Go to the Azurite [GitHub
558
558
559
559
## Next steps
560
560
561
-
-[Use the Azure storage emulator for development and testing](storage-use-emulator.md) documents the legacy Azure storage emulator, which is being superseded by Azurite.
561
+
-[Use the Azure Storage Emulator for development and testing](storage-use-emulator.md) documents the legacy Azure Storage Emulator, which is being superseded by Azurite.
562
562
-[Configure Azure Storage connection strings](storage-configure-connection-string.md) explains how to assemble a valid Azure Storage connection string.
Copy file name to clipboardExpand all lines: articles/time-series-insights/time-series-insights-update-query-data-csharp.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ ms.custom: seodec18
18
18
This C# example demonstrates how to query data from the [Gen2 Data Access APIs](https://docs.microsoft.com/rest/api/time-series-insights/reference-data-access-overview) in Azure Time Series Insights Gen2 environments.
19
19
20
20
> [!TIP]
21
-
> View Gen2 C# code samples at [https://github.com/Azure-Samples/Azure-Time-Series-Insights](https://github.com/Azure-Samples/Azure-Time-Series-Insights/tree/master/gen1-sample/csharp-tsi-gen1-sample).
21
+
> View Gen2 C# code samples at [https://github.com/Azure-Samples/Azure-Time-Series-Insights](https://github.com/Azure-Samples/Azure-Time-Series-Insights/tree/master/gen2-sample/csharp-tsi-gen2-sample).
22
22
23
23
## Summary
24
24
@@ -66,7 +66,7 @@ Alternatively, add each package using [NuGet 2.12+](https://www.nuget.org/). For
66
66
67
67
## C# sample code
68
68
69
-
Please refer to the [Azure Time Series Insights](https://github.com/Azure-Samples/Azure-Time-Series-Insights/blob/master/gen1-sample/csharp-tsi-gen1-sample/Program.cs) repo to access the C# sample code.
69
+
Please refer to the [Azure Time Series Insights](https://github.com/Azure-Samples/Azure-Time-Series-Insights/tree/master/gen2-sample/csharp-tsi-gen2-sample) repo to access the C# sample code.
0 commit comments