Adding Fast Rules Resources

A Semantic > Resources interface is available in the Business Console to easily configure your fast rules needs.

This task shows you how to:

Create fast rules resources in the Administration Console

Before you begin: This procedure explains how the Exalead CloudView administrator creates fast rules resources in the Administration Console so that they can be edited in the Business Console.
  1. Go to Index > Data Processing > Semantic Processors.
  2. Drag the Fast Rules processor to the list of current processors, and expand its configuration panel.
  3. Click Create new next to Resource directory.
  4. Enter the name of your fast rules resource, for example, myfastrules.

    Note: For more details on its configuration, see Fast Rules Matcher (Rule-Based) in the Exalead CloudView Configuration Guide.

  5. Click Save and Apply.

    Your new fast rules resource shall now be available in the Business Console, under Semantic > Resources.

Configure a fast rule resource

  1. In Semantic > Resources, select a fast rules resource from the list of Resources.
    • If the semantic resource is not available in the list, click the Refresh button.
    • If the semantic resource is in the list but you get an error message, check with your Exalead CloudView Administrator. When a new resource is created, the changes must be applied to the configuration before being able to edit the resource.
  2. Click Add category and specify matching and/or exception rules for this category.
    1. Language, restrict the match to a specific language or accept xx (N/A) (for all languages).
    2. Query, type the query that should generate or not the annotation, for example, we may want to create a match rule that will match Paris if it is not used in the expression “Paris Hilton” or “Paris Texas”.
    3. Do not forget to prefix your queries by the context (the meta) on which the rule applies to. For example, we could write the following match rule: text: "Paris" BUTNOT text: "Paris Hilton" or a match rule and one or more exception rules as in the following screenshot, but always specifying to search within the text context.