Introduction
Our strategy is to make the customer’s data more alive by offering insights into their data. For example, offer a summary of a document, a list of named entities, and a sentiment analysis. The /wiki/spaces/CS/pages/4652335105, which offers a wide range of analyses, is an example of this. Additionally, we want these insights to be integrated into the front end, specifically in the context of a single object.
Connector
Module
Insights are added to MediaHaven by activating new Module Plugins of the category “Insights”. The corresponding connector then delivers the insights of the object by analyzing the object during ingest and returning the insight(s) after the analysis has been completed.
Metadata
The results of the analysis can also be optionally persisted as metadata by configuring the custom properties of the Module Plugins. See https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4652335133/Insights+Connector+Contract#Configuration for more information.
Schematic
To realize this, we will create a new category of connectors called “Insights”. In the sketch below there are two flows
In the ingest workflow, that requests the insights connector to analyze the object and (a)synchronously waits for the analysis to complete (drawn as the steps A-B-C-D)
The end user that requests and receives insights into their document (drawn as the steps 1-2-…-6)
The asynchronous webhook handling is not part of the current POC, and instead, a simpler polling approach is followed during ingest.
Contract
https://mediahaven.atlassian.net/wiki/spaces/CS/pages/4652335133/Insights+Connector+API+contract