Category Archives: Migration

Posts about Meaningcloud’s migration.

Text Classification 2.0: Migration Guide

We’ve recently published a new version of our Text Classification API, which comes hand in hand with a new version of the Classification Models Customization console.

In both these new versions, the main focus is on user models. We know how important it is to easily define the exact criteria you need, so the new classification API supports a new type of resource, the one generated by the Classification Model Customization Console 2.0.

In this post, we will talk about how to migrate to these new versions if you are currently using the old ones. Text Classification 1.1 and Classification Models 1.0 will be retired on 15/Sep/2020. Continue reading →

MeaningCloud Release: VoC vertical pack upgrade

In the latest MeaningCloud update, we have published a new upgrade for our Voice of the Customer vertical pack. This update has two significant changes:

  • We’ve added a new domain to the four we already supported: telecommunications. This domain is huge and has a vast amount of unstructured data available and ready to be analyzed. You can check out the categories for this new model in the documentation.
  • We’ve refactored the models we already provided. Most of this refactorization has been done under-the-hood, but there are some categories that have changed names, either to give a more intuitive idea of what they refer to or to narrow down the criteria.
MeaningCloud release

Continue reading →

The Text Proofreading API moves to Stilus

Even since the very beginnings of MeaningCloud, we have offered a Text Proofreading API in Spanish which allow you to standardize and ensure the quality of your contents through spelling, grammar and style proofreading.

Stilus logo

On the 2nd of April, we will definitely move this API and its functionality to Stilus, an application where we take advantage of the functionality provided by the API and show everything you can do with it.

To those of you who currently use it, the migration process can be done in three easy steps:

  1. Register at Stilus.
  2. Contact us at support telling us about your volume requirements and which Stilus user would use the API. We will inform you of the conditions and tell you how to subscribe to the API.
  3. Once you have subscribed, you will only have to change the API endpoint and the key parameter value in your integration, and you will be all set to keep using the Text Proofreading API.

If you’d rather use directly the text proofreading functionality online or from Word, check out all the ways in which you can use Stilus!

MeaningCloud Release: new Language Identification API and more

As we recently advanced, during these last few months we have been working on new functionality. We are planning to start releasing it over the next few months.

In the latest release of MeaningCloud we have included some of this functionality:

Continue reading →

Sentiment Analysis 2.1: Migration guide

We have released a new version of our sentiment analysis API, Sentiment Analysis. In Sentiment Analysis 2.1:

  • We’ve changed how the sentiment model is sent in order to enable the use of custom sentiment models across all the APIs that support sentiment analysis.
  • Support to analyze documents and URLs has been added.
  • A configurable interface language has been added to improve multilingual analyses.

As you would see, this is a minor version upgrade, so the migration process will be fast and painless. In this post, we explain what you need to know to migrate your applications from Sentiment Analysis 2.0 to Sentiment Analysis 2.1.
Continue reading →

Lemmatization, PoS, Parsing 2.0: Migration guide

We have released a new version of our core linguistic analyzer: Lemmatization, PoS and Parsing. In Lemmatization, PoS and Parsing 2.0:

  • More analysis possibilities have been included to allow you to combine a complete morphosyntactic analysis with other types of analysis such as Sentiment Analysis and Topics Extraction.
  • Configuration options have been changed to provide more flexibility in the analyses and to make the options available more understandable.
  • We’ve refactored our code to:
    • Improve the quality of the concepts/keywords extraction.
    • Make easier and more flexible the use and traceability of user dictionaries.
    • Give the possibility of obtaining a more complex integrated analysis to give flexibility in complex scenarios where the standard output is not enough.
  • A new type of topic has been added, quantity expressions, to cover a specific type of information that was hard to obtain with previous versions.
  • Some fields in the output have been modified, either to give them more appropriate names or to make them easier to use and understand.
  • Some use modes have been retired as the information provided was redundant with what a morphosyntactic analysis already gives.

All these improvements mean the migration process is not as fast as it would be with a minor version. These are the things you need to know to migrate your applications from Lemmatization, PoS and Parsing 1.2 to Lemmatization, PoS and Parsing 2.0.
Continue reading →

Topics Extraction 2.0: Migration guide

We have released a new version of our information extraction API, Topics Extraction. In Topics Extraction 2.0:

  • The topics extracted have been reordered to extract information in a more coherent way.
  • Configuration options have been changed to provide flexibility in the analyses and to make the options available more understandable.
  • We’ve refactored our code with two short-term goals in mind:
    • Improving the quality concepts/keywords extraction.
    • Making easier and more flexible the use of user dictionaries.
  • A new element has been added, quantity expressions to cover a specific type of information that was hard to obtain with previous versions.
  • Some fields at the output have been modified, either to give them more appropriate names or to make them easier to use and understand.
  • A configurable interface language has been added to improve multilingual analyses.

All these improvements mean the migration process is not as fast as it would be with a minor version. In this post, we explain what you need to know to migrate your applications from Topics Extraction 1.2 to Topics Extraction 2.0.
Continue reading →

Sentiment Analysis 2.0: Migration guide

We have released a new version of one of our more popular APIs: Sentiment Analysis. In Sentiment Analysis 2.0:

  • The rules used for defining polarity terms have been greatly improved, adding new operators and making the models used much more flexible, which in turn leads to better results.
  • Sentiment analysis is now done at more levels, allowing to identify more complex syntactic structures and to obtain more detailed information about how the polarity is expressed.
  • More configuration options have been added related to the morphosyntactic analysis over which the sentiment analysis is carried out.
  • The architecture of the service has changed, leading to a tenfold improvement in the response time.
  • An integration with the Lemmatization, PoS and Parsing API has been added in order to ease the way of creating applications that use the information provided by both APIs.
  • Dictionary customization has been fully integrated in order to get out the most out of its functionality.

All these improvements mean the migration process is not as fast as it would be with a minor version. These are the things you need to know to migrate your applications from Sentiment Analysis 1.2 to Sentiment Analysis 2.0.
Continue reading →

Migrate from Textalytics: Spellchecker and Language Analysis API

We have just published and updated in MeaningCloud two of the functionalities that were still pending to migrate from Textalytics.

  • Automatic text proofreading checks spelling, grammar and style in your texts for several languages: Spanisn, English, French and Italian.
  • Full language analysis including lemmatization, Part of Speech tagging and syntactic analysis also for several languages. For this API besides English, Spanish, French and Italian we have also Portuguese and Catalan available.

Textalytics users can access MeaningCloud using the same email and password they already had. If you do not remember your password, you can reset and generate a new password.

Developers using Textalytics’ Spell, Grammar and Style Proofreading API or Lemmatization, POS and Parsing API

If you are a user of the following functionalities and want to migrate to MeaningCloud, you can do it already. You only have to:

  1. Update the access point, since the request and response format does not change. Both HTTP and HTTPS endpoints are available.
    API Textalytics MeaningCloud
    Spell, Grammar and Style Proofreading 
    https://textalytics.com/core/stilus-1.2
    		 
    http://api.meaningcloud.com/stilus-1.2
    Lemmatization, POS and Parsing API 
    http://textalytics.com/core/parser-1.2
    		 
    http://api.meaningcloud.com/parser-1.2
  2. Check your license key in MeaningCloud and make sure that you use the correct (and only) license as the value of the parameter ‘license key’ on all requests. You can copy your license key either from the Licenses section in the Account menu, or from the developers home.

As always, if you have doubts or find any other problem, do not hesitate to write us to support@meaningcloud.com. Nevertheless, in order to ensure a smooth transition for client applications all the Textalytics’ API endpoints will be operational until June 1st, 2015.

Textalytics users: how to migrate your application to MeaningCloud

Textalytics users can access MeaningCloud using the same email and password they already had. If you do not remember your password, you can reset and generate a new password.

Meaningcloud’s API authentication as well as accounting have been simplified. It now requires a single license key for all APIs and  consumption is accounted in number of requests. In order to ensure a smooth transition for client applications all the Textalytics’ API endpoints will be operational until June 1st, 2015.

Developers that use the APIs of Textalytics

If you are a user of the following functionalities and want to migrate to MeaningCloud, you can do it already. You only have to:

  1. Update the access point, since the request and response format does not change. Both HTTP and HTTPS endpoints are available.
    API Textalytics MeaningCloud
    Sentiment Analysis 
    http://textalytics.com/core/sentiment-1.2
    		 
    http://api.meaningcloud.com/sentiment-1.2
    Topics Extraction 
    http://textalytics.com/core/topics-1.2
    		 
    http://api.meaningcloud.com/topics-1.2
    Text Classification 
    http://textalytics.com/core/class-1.1
    		 
    http://api.meaningcloud.com/class-1.1
    Language Identification 
    http://textalytics.com/core/lang-1.1
    		 
    http://api.meaningcloud.com/lang-1.1
  2. Check your license key in MeaningCloud and make sure that you use the correct (and only) license as the value of the parameter ‘license key’ on all requests. You can copy your license key either from the Licenses section in the Account menu, or from the developers home.

For the users of the remaining APIs, you will be informed over the next few weeks.

Users of the Textalytics Add-in for Excel

If you use the Textalytics add-in for Excel and want to upgrade to MeaningCloud:

  1. Uninstall the Textalytics Add-in for Excel.
    1. Open Control Panel > Programs > Programs and Features.
    2. Select the Textalitics add-in for Excel from the list of programs and click the Uninstall button
  2. Download the new version of MeaningCloud add-in for Excel which already contains the updated access points.
  3. Install the new version.
  4. Configure your license key to start analyzing texts.