Grooper 21.00.0082 is available as of 12-12-2023! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.00.0044 is available as of 06-20-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Grooper 23.1.0022 is available as of 07-05-2024! Check the Downloads Discussion for the release notes and to get the latest version.
Options
Documents not meeting MinimumSimilarity getting Classified
![strotelli](https://us.v-cdn.net/6030453/uploads/userpics/328/n0EWX6VJ1QYCZ.jpg)
I have documents that should end up unclassified after the classification step. When i test them they show up as a 0% match to any other document type, however when they are run through classification they end up with a document type.
0
Best Answer
-
Options
GrooperGuru Posts: 481 admin
Couple thoughts here... First, do they always end up as the same doc type or do they end up assigned to different doc types? If the same, I would suspect that you have defined a Default Doc Type on your Content Model. If different, I would then ask if you are running classification using a service or through manual task processing. The Classification service can retain old versions of the content model. So if you've been actively training classification, the service may not see the latest and greatest changes you've made. At some point in 2.6, we added a feature to force the Classification service to get changes automatically without having to be restarted. It is a setting named Model Refresh Interval, and you configure it in the classification step of the batch process. The setting is described as follows:
"The interval (in seconds) at which content model information will be refreshed from the repository. WARNING: if set to 0 this feature will be disabled, and Content Model information will not be updated until the service(s) are restarted."Matt Harrison
Product Manager
mharrison@bisok.com5