Skip to content

Commit 290ec1e

Browse files
committed
edits
1 parent 8543d2f commit 290ec1e

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

articles/search/search-get-started-portal-image-search.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@ You need three Azure resources and some sample image files to complete this walk
2424
> [!div class="checklist"]
2525
> + Azure Storage to store image files as blobs
2626
> + Azure AI services multiservice account, used for image vectorization and Optical Character Recognition (OCR)
27-
> + Azure AI Search for image vectorization during indexing and queries
27+
> + Azure AI Search for indexing and queries
2828
2929
Sample data consists of image files in the [azure-search-sample-data](https://github.com/Azure-Samples/azure-search-sample-data/tree/main/unsplash-images) repo, but you can use different images and still follow this walkthrough.
3030

@@ -104,7 +104,7 @@ In this step, you can also apply AI to extract text from images. The wizard uses
104104

105105
Two more outputs appear in the index when OCR is added to the workflow:
106106

107-
+ First, the "chunk" field is populated with an OCR-generated string of any text in the image.
107+
+ First, the "chunk" field is populated with an OCR-generated string of any text found in the image.
108108
+ Second, the "text_vector" field is populated with an embedding that represents the "chunk" string.
109109

110110
The inclusion of plain text in the "chunk" field is useful if you want to use relevance features that operate on strings, such as [semantic ranking](semantic-search-overview.md) and [scoring profiles](index-add-scoring-profiles.md).
@@ -137,23 +137,23 @@ The inclusion of plain text in the "chunk" field is useful if you want to use re
137137

138138
1. Select **Create** to run the wizard. This step creates the following objects:
139139

140-
+ Data source connection to blob storage.
140+
+ An indexer that drives the indexing pipeline.
141141

142-
+ Index with vector fields, text fields, vectorizers, vector profiles, vector algorithms. You can't modify the default index during the wizard workflow. Indexes conform to the [2024-05-01-preview REST API](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2024-05-01-preview&preserve-view=true).
142+
+ A data source connection to blob storage.
143143

144-
+ Skillset with the following five skills:
144+
+ An index with vector fields, text fields, vectorizers, vector profiles, vector algorithms. You can't modify the default index during the wizard workflow. Indexes conform to the [2024-05-01-preview REST API](/rest/api/searchservice/indexes/create-or-update?view=rest-searchservice-2024-05-01-preview&preserve-view=true).
145+
146+
+ A skillset with the following five skills:
145147

146148
+ [OCR skill](cognitive-search-skill-ocr.md) recognizes text in image files.
147149
+ [Text Merger skill](cognitive-search-skill-textmerger.md) unifies the various outputs of OCR processing.
148150
+ [Text Split skill](cognitive-search-skill-textsplit.md) adds data chunking. This skill is built into the wizard workflow.
149151
+ [Azure AI Vision multimodal](cognitive-search-skill-vision-vectorize.md) is used to vectorize text generated from OCR.
150152
+ [Azure AI Vision multimodal](cognitive-search-skill-vision-vectorize.md) is called again to vectorize images.
151153

152-
+ Indexer with field mappings and output field mappings.
153-
154154
## Check results
155155

156-
Search explorer accepts text, vectors, and images as query inputs. You can drag or select an image into the search area, and it will be vectorized for search. Search Explorer vectorizes your image and sends the vector as a query input to the search engine. Image vectorization assumes that your index has a vectorizer definition, which **Import and vectorize data** creates from your inputs.
156+
Search Explorer accepts text, vectors, and images as query inputs. You can drag or select an image into the search area. Search Explorer vectorizes your image and sends the vector as a query input to the search engine. Image vectorization assumes that your index has a vectorizer definition, which **Import and vectorize data** creates based on your embedding model inputs.
157157

158158
1. In the Azure portal, under **Search Management** and **Indexes**, select the index your created. An embedded Search Explorer is the first tab.
159159

@@ -171,7 +171,7 @@ Search explorer accepts text, vectors, and images as query inputs. You can drag
171171

172172
1. Try other query options to compare search outcomes:
173173

174-
+ Hide vectors for more readable results.
174+
+ Hide vectors for more readable results (recommended).
175175
+ Select a vector field to query over. The default is text vectors, but you can specify the image vector to exclude text vectors from query execution.
176176

177177
## Clean up

0 commit comments

Comments
 (0)