activesolution / cognitivecms Goto Github PK

This is a proposal to enable a new feature in CognitiveCMS that would give instant enrichment to the editors as soon as they add an asset in WordPress (instead of having to wait for the pipeline to process which is the current setup). This is a big change in the foundation of this solution.

Our proposed solution is the following:

• Remove the plugin dashboard page

• Remove current Cognitive Search pipeline implementation

• Add a new web api project that will replicate the current functionality by calling the Cognitive Services directly with the purpose to enrich a text or an image with tags

• Enriched tags need to be fetched from web api endpoint that is connected to Azure Search, instead of being saved locally

• Adjust the deployment project script to setup all the necessary resources

The workflow would be following - The editor uploads an image (or adds a page) to WordPress. This triggers CognitiveCMS enrichment process and the following steps occur:

1. Upload the image to Azure Blob Storage

2. Call the web api with the url to the uploaded blob

3. The web api calls all the cognitive services and the enriched data is saved to Azure Search Index

The suggested solution would support only text and images, and smaller number of Cognitive Services to improve performance.

One alternative we considered was to call the existing pipeline to start it manually. However, that will not provide instant feedback and the end-user will not know when the assets have been reindexed.

This is a proposal to enable a new feature in CognitiveCMS that would enable real-time whitelist/blacklist functionality. This is dependent on #1.

Our proposed solution is the following:

Add a text-area for both whitelist and blacklist in WordPress plugin settings page. The requirement would be that you can have only one list with keywords, the other one will be disabled since it makes no sense having both whitelist and blacklist at the same time.

The lists should be saved in blob storage.

Add to the web api from #1 where Azure Search results should be exposed and filters applied. This is to enable real-time whitelist/blacklist changes.