Blogs by Ashwin

  Create Your Azure AI Language Project Your Azure AI Language project can be created in one of two ways. Language Studio will offer to build a language service for you if you begin using it without first creating one in the Azure portal. Using the Azure portal to construct your language service is the most flexible approach to start an Azure AI Language project. You can add unique features if you select this option. When constructing your language service, choose the custom feature that you will use to generate a custom text classification. Using this procedure, you will also connect the language service to a storage account. You can go straight to the Language Studio from the language service's overview pane after the resource has been deployed. After that, you can start a brand-new, unique text classification project. Train Your Classification Model It requires recognized data to be trained, just like any other AI model. In order for the model to be tested, it must see examples ...

  Custom Text Classification Skill You can map a text passage to various user-defined classes using custom text classification. To automatically determine a book's genre, for instance, you could train a model on the synopsis included on the back cover. You then add a genre facet to your online store search engine using that defined genre. You need to consider the following to enrich a search index using a custom text classification model: Store your documents so they can be accessed by Language Studio and Azure AI Search indexers. Create a custom text classification project. Train and test your model. Create a search index based on your stored documents. Create a function app that uses your deployed trained model. Update your search solution, your index, indexer, and custom skillset. Store Your Data Language Studio and Azure AI Services both provide access to Azure Blob storage. The easiest option is to select Container as the container must be available, although private container...

  Introduction By extracting more information from the source data, you can significantly enhance an index using Azure AI Search's predefined skills. However, there can be times when you have certain data extraction requirements that call for some bespoke functionality and cannot be satisfied by the established abilities. For example: Integrate the Form Recognizer service to extract data from forms Consume an Azure Machine Learning model to integrate predicted values into an index Any other custom logic Custom skills can be implemented as web-hosted services (like Azure Functions) that enable the necessary interface for integration into a skillset in order to support these scenarios. Define Custom Skill Schema The expected structure for input and output data that is required by abilities in an Azure AI Search skillset must be implemented by your custom skill. Input Schema A JSON structure with a record for every document to be handled is defined by the input schema for a custom ski...

  Apply Filtering and Sorting Users frequently like to filter and order query results according to field values in search solutions. Both of these features are supported by Azure AI Search via the search query API. Filtering Results You can apply filters to queries in two ways: By including filter criteria in a simple search expression. By providing an OData filter expression as a $filter parameter with a full syntax search expression. You can apply a filter to any filterable field in the index. Filtering With Facets When presenting users with filtering criteria based on field values in a result set, facets are a helpful tool. They function best when a field contains a limited number of discrete values that can be shown in the user interface as options or links. In order to use facets, you must first define the facetable fields for which you wish to extract the potential values. Sorting Results The query process's relevancy score is used by default to rank the results, with the hig...

  Understand The Indexing Process For every indexed entity, a document is created as part of the indexing process. An enrichment pipeline produces the documents repeatedly during indexing, combining enriched fields retrieved by cognitive skills with metadata from the data source. You can think of each indexed document as a JSON structure, which initially consists of a document with the index fields you have mapped to fields extracted directly from the source data. You can set up the indexer to extract image data from documents in the data source and add each image to a collection called normalized_images. You can use the collection of photographs as an input for skills that extract information from image data by normalizing the image data in this manner. Every talent adds fields to the document. For instance, a skill that determines the language used in a document may store its result in a language field. The document is structured hierarchically, and the skills are applied to a sp...

  Introduction Each of the several parts that make up an AI search solution is crucial to the extraction, enrichment, indexing, and querying of data. Data Source The majority of search solutions begin with a data source that has the information you are looking for. Azure AI Search is compatible with a variety of data sources, including: Unstructured files in Azure blob storage containers. Tables in Azure SQL Database. Documents in Cosmos DB. Azure AI Search can pull data from these data sources for indexing. Alternatively, applications can push JSON data directly into an index, without pulling it from an existing data store. Skillset You may index the data taken from the data source in a simple search solution. The data source determines the information that can be extracted. For example, while indexing data in a database, the fields in the database tables may be extracted. Similarly, when indexing a collection of documents, the text content of the document many be extracted along...