Forum Discussion
Files getting classified in syntex training files but not in SharePoint library
Hi, I'm having some trouble with some files in SharePoint not getting classified, with some appearing to not even get put through the classification process. The files are being scanned in batche...
Hi Shane_Lambert,
have you found a solution to the problem? I am currently facing a similar issue.
One Sharepoint Document Library. Two Classification models, which classify incoming documents into two groups. However, sometimes the classification happens with a large delay (several days) and sometimes no classification happens at all.
Unfortunately, diasbling both models from the library and enabling again did not help.
2 Weeks ago everything went flawlessly.
Any advice or help is highly appreciated.
After running into this issue hundreds of times while working with syntex, I've found that syntex models seem to be running their own OCR on files when you train them, which seems to be a lot better than other OCRs that I've tried with my current project. However, as far as I can tell, models don't run their own OCR when classifying files in SharePoint libraries. This leads to models classifying files differently when training vs in a SharePoint library.
That being said, I have no clue how to fix this. I would love to have syntex just apply its own OCR on all files, regardless of location, but I haven't found a good way to do that. At this point, I would also take it the other way around (having syntex not apply any OCR and just use ours) but I also haven't found a way to do that.
- I've had similar issues and not sure the cause. You've tried all the tricks I tried and then some including republishing the models. Some files just seem to refuse to be classified even though the models identify them flawlessly.
Thank you for the quick reply! That is really unfortunate...
We get around this issue for now, by adding another "custom" column to classify the document type by hand. And adding a rule that if there is a classification date, override the "custom" column. Otherwise, it can still be classified by hand.
However in my opinion this issue is a deal-breaker in using syntex as of now.
