Tahir Naveed
Feb 14, 2020
(2 votes)

Using Microsoft cognitive services to improve content sentiments

In this blog post, I will describe how we have utilised Microsoft cognitive services (Text Analytics API) to analyse content before a content author publishes it so it can be rewritten in a more positive tone. The Text Analytics API uses a machine learning classification algorithm to generate a sentiment score between 0 and 1. Scores closer to 1 indicate positive sentiment, while scores closer to 0 indicate negative sentiment.

Content author will be encourged to rewrite content if a score closer to zero is returned - the idea is to make sure our content conveys the message in a postive manner.

A working example can be seen below and all the code is in github.

The basic steps are as follows

  1. Create a Microsoft azure account and subscribe to Microsoft cognitive services. You will need the end point and a key. A detail documentation can be found here
  2. Create a plugin (button) in tinymce
    1. The button when clicked will call a server side web api and pass the tinymce content alongwith via an ajax call.
  3. Create a server side web api controller to process content
    1. This controller will receive the content from tinymce and will call microsoft cognitive services to analyse sentiments of the content

Visual studio solution architecture:

  1. Use visual studio extension to create basic episerver alloy vinealla website.
  2. Install the following nuget packages
    1. install-package Microsoft.AspNet.WebApi
      1. You will need to configure some basic routes ( see the working example)
    2. install-package Microsoft.Azure.CognitiveServices.Language.TextAnalytics
      1. You will need to configure Cognitive services in Azure portal and then copy/paste the key in the sample

Once it is configured, the backend code is all setup.

For front end code, I have utilised yomen TinyMCE Plugin Generator to generate a tinymce plugin. More documentation can found here. Simple code to add a button to tinymce editor which when clicked will made an ajax call to backend web api and show the result to end use.

(Please note the code share is a basic example of making it all work together and it is not production ready code)

Feb 14, 2020


Please login to comment.
Latest blogs
Fixing Optimizely Content Syncing/Caching Issues on the DXP pre CMS.Core 12.13.0

Hi all, With our recent deployments to the DXP for .NET 6 projects (one a new build and one an upgrade) our clients had raised issues where there...

Scott Reed | Mar 23, 2023

Handle hostnames, schedule jobs and role access when synchronizing content

The Environment Synchronizer module helps you to set your environment into a known state after synchronizing databases between environments. In thi...

Ove Lartelius | Mar 23, 2023 | Syndicated blog

4 tips and tricks for Hangfire on Optimizely CMS

Here are four useful tricks I always apply to any site where I use Hangfire (code included).

Stefan Holm Olsen | Mar 21, 2023 | Syndicated blog

The new LinkItem property in Optimizely CMS, and why it matters

In the past, we have used different tricks to achieve this. Now, the LinkItem property is finally built-in in Optimizely CMS 12!

Tomas Hensrud Gulla | Mar 20, 2023 | Syndicated blog

A day in the life of an Optimizely Developer - Vertical Slicing in CMS12

There is such a vast choice these days in how you can build a website, aside from all of the different programming languages out there, there are...

Graham Carr | Mar 20, 2023

Tag Helpers in CMS 12

Microsoft introduced the TagHelper back in the primordial soup of ASP.NET vNext which became .Net 5, then .NET Core then .Net 5 you know the drill…...

MartinOttosen | Mar 20, 2023