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: workshops/Module 7.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -2,7 +2,7 @@
2
2
3
3
In the past modules, we focused on indexing content from unstructured sources such as PDF's. Often, there is a lot of data that exists in structured data sources such as Azure SQL or Cosmos DB which could benefit from the ability to perform full-text search. The advantage here, is that unlike unstructured data such as PDF's, the data has already been structured so we can make use of this through faceting and filtering. Yet, still there is often text content that can benefit from "enrichment".
4
4
5
-
In the below module you will take a set of purely anonymized patient data (patient name, address, notes, etc) and index it into Azure Search. Just like in the previous module, we will leverage the Custom Skill to extract diseases from the patient notes and then create a resulting application to search the patient information.
5
+
In the below module you will take a set of purely anonymized patient data (patient name, address, notes, etc) and index it into Azure Cognitive Search. Just like in the previous module, we will leverage the Custom Skill to extract diseases from the patient notes and then create a resulting application to search the patient information.
6
6
7
7
## SQL Database Connection Information
8
8
@@ -20,7 +20,7 @@ Here is what the data looks like:
20
20
21
21

22
22
23
-
## Indexing Content into Azure Search
23
+
## Indexing Content into Azure Cognitive Search
24
24
25
25
Just as we did in Module 3, we will leverage Postman to create the Data Source, Skillset, Indexer and Index to hold the data. You could alternatively use the Portal, however, you will not be able to configure the Custom Skill for extracting diseases as the ability to do this in not yet available in the portal.
26
26
@@ -300,7 +300,7 @@ Body:
300
300
Replace the [searchservice] with your search service and use your admin api key in the header.
301
301
Note: The below skillset leverages a pre-existing Azure Function (https://diseaseextraction.azurewebsites.net/api/custom-search?code=HXS0y4rEoQZ9p55A7wqybSeYFmYP6Lruna8y8HoAGu3kNSoLf80XWw==) to extract the diseases. You can use this as-is or change to the one you created in the previous module.
302
302
303
-
You will also need to update the [Cognitive Services Key] with a valid Cognitive Services Key (that was created in the same region as your Azure Search service).
303
+
You will also need to update the [Cognitive Services Key] with a valid Cognitive Services Key (that was created in the same region as your Azure Cognitive Search service).
0 commit comments