|
Tag: Redirect target changed |
| (23 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| This is a placeholder for an article on an upcoming new feature in version 2024.
| | #Redirect [[AI Search and the Search Page]] |
| | |
| | |
| Azure AI Search Setup Notes
| |
| * Microsoft's Azure AI Search documentation is found here:
| |
| * https://learn.microsoft.com/en-us/azure/search/
| |
| | |
| | |
| Basic Setup
| |
| # Create an Azure AI Search Service | |
| #* The following article from Microsoft instructs users how to create a Search Service.
| |
| #* https://learn.microsoft.com/en-us/azure/search/search-create-service-portal
| |
| #** FYI: When setting up the Search Service, you will need to add a "query key" as well. This is needed for the next step.
| |
| #** FYI: Copy or write down the URL for the next step as well.
| |
| # Add an "AI Search" Repository Option to the Grooper Repository's root node.
| |
| #* You will need the URL and Query Key (API Key) from AI Search service in Azure.
| |
| # Add an Indexing Behavior on a Content Model in Grooper.
| |
| #* Documents must be classified before they can be indexed. Only Document Types/Content Types inheriting an Indexing Behavior are eligible for indexing.
| |
| # Create the search index by right-clicking the Content Model and selecting "Search > Create Search Index"
| |
| #* This creates the search index in Azure. Without the search index created, documents can't be added to an index.
| |
| # Index documents in one of the following ways:
| |
| #* Manually, one document at a time by right-clicking the document and using the "Add to Index" command.
| |
| #* Using an Execute activity in a Batch Process to apply the "Add to Index" command to all documents in a Batch.
| |
| #* Running the Grooper Indexing Service to index documents automatically in the background.
| |
