Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Importing a taxonomy for keyword-based topic detection

Updated on July 5, 2022

After you create a topic model, import a taxonomy that contains defined topics and keywords for topic detection. Based on the keywords, topic detection assigns topics to the analyzed piece of text.

Before you begin:
  1. Create a .csv, .xls, or .xlsx file with defined topics and corresponding keywords. For more information, see Requirements and best practices for creating a taxonomy for rule-based classification analysis.
  2. Create a keyword-based topic model by specifying the model name, language, and corresponding ruleset. For more information, see Setting up a keyword-based topic model.
  1. In the Taxonomy workspace, click ActionsImport.
  2. In the Import taxonomy dialog box, click Choose file, and then select the .csv or .xlsx taxonomy file.
  3. Click Import.
  4. To detect child topics only when the corresponding parent topic is detected, for the parent topic, select the Match child topics only if the current topic matches check box.
  5. Optional: To test your taxonomy, select ActionsTest.
    Tip: Always test your taxonomy on a number of text samples to determine whether it accurately assigns topics. Depending on the results, you might refine your taxonomy, for example, by increasing the number of Should words to accommodate additional use cases, or by adding Not words to help differentiate between similar categories.
  6. Save the taxonomy by clicking Save.
    You can use the taxonomy as part of a machine learning topic model or directly in Text Analyzers to perform keyword-based topic detection.
Result: Your model is now available in the Models workspace.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us