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
  • Thanks Craig.

    The only question is how to find out that document is un-managed in M-Files. For users would be important to have a link to that "un-managed" object in M-files where user can select the class manually. As I mentioned we have tried the API but could not find out "un-managed" documents. But perhaps, this is by design because those documents are not seen in the vault yet. Still wondering why user could see un-managed document in the client but this information is not accessible over API. If this would be seen through API, this part could be automated and we could create assignments for those specific un-managed documents.

    But definitely quite clear now.

    Best regards,
    Dejan
Reply
  • Thanks Craig.

    The only question is how to find out that document is un-managed in M-Files. For users would be important to have a link to that "un-managed" object in M-files where user can select the class manually. As I mentioned we have tried the API but could not find out "un-managed" documents. But perhaps, this is by design because those documents are not seen in the vault yet. Still wondering why user could see un-managed document in the client but this information is not accessible over API. If this would be seen through API, this part could be automated and we could create assignments for those specific un-managed documents.

    But definitely quite clear now.

    Best regards,
    Dejan
Children
No Data