Options
  • Locked Locked
  • Replies 16 replies
  • Subscribers 11 subscribers
  • Views 756 views
  • Users 0 members are here
Related
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

dejan
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
  • Intelligence services aren't directly related to the promotion process. These are two distinct things, although they can work together.

    Promotion is the act of finding unmanaged content (content in other repositories) and augmenting it with metadata. This is typically a manual process. This metadata includes the class and any other properties that are either mandated by the class or that the user wishes to add. Once promoted, the file content continues to (primarily) live within the remote system but the object itself can be involved in M-Files processes such as workflows, notifications and assignments, have permissions applied to it, appear in views, etc.

    An intelligence service can suggest metadata for a given file. When the file is added to the vault, the intelligence services run to analyse the file content and provide suggestions on the property values that should be on the object. The user can choose any set of these to apply to the new object. The intelligence service runs if the document is dragged into the vault via the desktop client, uploaded via the web or mobile interfaces, or whether it's promoted from an external repository. Intelligence services can also be run via the M-Files APIs so you can retrieve the suggestions for a given file via script, for example.

    So, whilst intelligence services may be (and often are) kicked off by the promotion process, they are not directly related.

    The concept with Discovery is that it can automatically trawl external repositories, locate content that it deems should be promoted, and kick off the process. Where this blurs the line between promotion and intelligence services is that this can be used to promote content automatically without any user interaction, working with Smart Classifier or Information Extractor to identify content with PII, for example.

    Regards,

    Craig.
Reply
  • Intelligence services aren't directly related to the promotion process. These are two distinct things, although they can work together.

    Promotion is the act of finding unmanaged content (content in other repositories) and augmenting it with metadata. This is typically a manual process. This metadata includes the class and any other properties that are either mandated by the class or that the user wishes to add. Once promoted, the file content continues to (primarily) live within the remote system but the object itself can be involved in M-Files processes such as workflows, notifications and assignments, have permissions applied to it, appear in views, etc.

    An intelligence service can suggest metadata for a given file. When the file is added to the vault, the intelligence services run to analyse the file content and provide suggestions on the property values that should be on the object. The user can choose any set of these to apply to the new object. The intelligence service runs if the document is dragged into the vault via the desktop client, uploaded via the web or mobile interfaces, or whether it's promoted from an external repository. Intelligence services can also be run via the M-Files APIs so you can retrieve the suggestions for a given file via script, for example.

    So, whilst intelligence services may be (and often are) kicked off by the promotion process, they are not directly related.

    The concept with Discovery is that it can automatically trawl external repositories, locate content that it deems should be promoted, and kick off the process. Where this blurs the line between promotion and intelligence services is that this can be used to promote content automatically without any user interaction, working with Smart Classifier or Information Extractor to identify content with PII, for example.

    Regards,

    Craig.
Children
No Data




              

© M-Files Corporation 2024 | Privacy Policy