Known Issues with Automatic Term Assignment

Resolving The Problem

Upgrade to Information Server 11.7.0.1 to fix any of the below items except 2.

For 11.7.0.0 there might be a workaround depending on the observed behavior and error message:

1. When running discovery with term assignment on more than 30,000 assets term assignment may fail due to an internal size limitation. In this case we recommend to break down the discovery task into smaller subtasks with less than 30,000 assets each.
2. There is no way to enable the detection of term assignment candidates but prevent the creation of term assignments. Removing the assignment threshold sets it to the default of 0.8. To minimize the number of assignments that are created set the assignmentTreshold to 1.0.
3. The linguistic matching service has a fixed candidateThreshold of 0.4 that is independent of the candidate threshold set on the ODF configuration. There is currently no way to change this.
4. An entry categoryScope = "" in the ODF configuration causes analysis to fail. To disable the category scope feature remove this entry from the ODF configuration.

Example:

Wrong (causes failure):
{
 "capabilities": {
   "com.ibm.iis.odf.capabilities.TermAssignment": {
     "softLimit": 0,
     "hardLimit": 100,
     "candidateThreshold": 0.4,
     "assignmentThreshold": 0.8,
     "categoryScope": ""
   }
 },
"services"...
}

Correct:
{
 "capabilities": {
   "com.ibm.iis.odf.capabilities.TermAssignment": {
     "softLimit": 0,
     "hardLimit": 100,
     "candidateThreshold": 0.4,
     "assignmentThreshold": 0.8
   }
 },
"services"...
}