If a category has been in use, you should use extreme care deleting it. When you delete a category:

• If resources were categorized using the category, the association will be removed.
• Any policy that included the category may no longer have the expected results.
• Attestations involving the category may no longer work.
• Reports will no longer include data about the category.

If you choose to delete a category, you should ensure that the proper administrators are notified so that policies, attestations and reports can be modified as needed.

To delete a category

1. Select Governed Data | Taxonomy Manager | Categorizations.
2. Locate the row containing the taxonomy, and click Edit.
3. Select the category.
4. Click Delete.
5. In the confirmation dialog box, click Delete Category.

To delete a category using PowerShell

1. Determine the ID of the category you want to delete.
   See Finding a Taxonomy or Category ID using PowerShell for details.
2. Run the Remove-QCategory cmdlet, using the following mandatory parameters:
   1. ServerAddress
      Provide the name of the computer hosting the Data Governance server, and the port. Enter in the form computername:port number. The default port is 8723.
   2. CategoryId
      The ID of the category you want to delete.

Manual categorization requires very little set up, however it is not as powerful as automated categorization. Using manual categorization, business owners can apply categories to owned resources. Policies and attestations can be implemented, and information about categorization may appear in relevant view, reports and dashboards. The following steps should be taken:

• Activate classification in your deployment. For more information, see Activating Classification .
• Create taxonomies and add categories. For more information, see Creating Taxonomies.
• Publish your category. You can either publish a category available when you create it, or you can edit an existing category and publish it. For more information, see Creating a Category and Editing a Category.

For more information on manually categorizing resources, see Working With Manually Categorized Resources.

Contents

• An Overview of Rules
• How Rules Affect Categorization
• Writing XML Rules
• Managing Rules in the Classification System
• Associating Rules to Categories
• Testing and Reviewing Automated Classification
• Making a Category Available to the Automated System

You must have at least one live rule associated with a category before any automated categorization can take place.

Rules are the basis of automated categorization. A rule is the criteria that defines what a resource must contain in order to match the rule. Rules are expressed using custom XML files, and added to the automated system. A rule can be associated with more than one category.

For example, a rule might state that in order to match, a resource must contain both a credit card number and a credit card provider within 50 characters of each other. Another example might be that a resource must contain ten credit card numbers.

In addition to defining criteria, a rule also sets a match strength. Match strength is a numerical representation of how well the content matches the rule. The simplest implementation is to use the default match strength of one. For more information, see How Rules Affect Categorization and Advanced Rule Applications.

You can create a rule in developer mode, and test it before you implement it. Once you are satisfied that a rule has the desired results, you can associate it with categories.