This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Intelligent services

Hi all,

I am somehow confused with all these different intelligent services that partially do the same and partially built on top of each other.
So if I understand correctly, Smart Classifier and Smart Metadata are cloud-based services with a essence of knowledge graph and I assume some AI learning capabilities.

On the other side, there is Discovery and Information Extractor (Text Analytics and Matcher). My understanding of Discovery service is that it enforce classification of documents and properties based on configuration and rules and that not really work with concept of suggestions. Also it needs Smart Classifier for categorization (which means 2 licences) and is dependent to cloud service as well.
Information Extractor seems to be the only service which works on-premise without need of cloud services. Is my understanding so far right?

I am wondering if Information Extractor services can be used with documents coming through connectors to suggest users class and properties during promotion process. Could they be configured in a way when people bring documents from "outside" and just drop them to M-Files that these services suggest class and properties for dropped document? Somehow all documentation explains cases that these services run periodically in backend and need their time for processing. It is not clear if they would support such on-demand cases. Of course, if possible, this would help users a lot not to always need to provide all metadata by themselves.

Thanks for thoughts and clarifications.

Dejan
Parents
  • The difference between managed an unmanaged documents lies in the fact that managed documents have been registered as objects in the database whereas unmanaged objects are only indexed. They exist in the index but not in the database. Users can see them in their user interface because Views are configured to show indexed documents even though they are not objects in the database. If the API only works on the database it will not be able to show documents that only exist in the index.
Reply
  • The difference between managed an unmanaged documents lies in the fact that managed documents have been registered as objects in the database whereas unmanaged objects are only indexed. They exist in the index but not in the database. Users can see them in their user interface because Views are configured to show indexed documents even though they are not objects in the database. If the API only works on the database it will not be able to show documents that only exist in the index.
Children
No Data