In previous versions of the Qlik Web Connectors, the MeaningCloud API was accessible through the Sentiment and Text Analytics Connector.
Ways to access your data
To access your
Loading data from tables
|Sentiment||Use this table to fetch a single sentiment score for the full text.|
The table returns the following information:
|Shows the status of the API call.||
|model||Shows the extraction model and language. The extraction model is always general.||
|score_tag||Shows the global sentiment score of the text.||
|agreement||Shows the agreement of sentiment among the parts of the text.||
|subjectivity||Shows whether the text is subjective or objective.||
|confidence||Shows the confidence of the sentiment analysis.||Integer from 0-100.|
|irony||Shows whether the text was analyzed as ironic.||
|length||Shows the character length of the text.||Integer|
Using the Sentiment table to get sentiment data for comments
The most effective way to use the
When you load data with a script like the one above, you should see one table called MeaningCloudConnector_Sentiment that has all of the MeaningCloud sentiment fields plus the two columns from the original data table. The original table that is used to pass data into the RegEx engine should not be available in Qlik Sense.
Working with the MeaningCloud API quota limits
The Qlik Web Connectors use the
Reference - MeaningCloud developer documentation
You can refer to the MeaningCloud API documentation to learn more about the requirements and restriction imposed by the MeaningCloud API.
You have exceeded the API limits that are imposed on the Qlik Web Connectors by one of the MeaningCloud APIs.
To reduce the impact of reaching the API rate limits, develop your app with the following in mind:
- Extract only the data you need.
- Reload one MeaningCloud-based application at a time.
- Ensure that loops in your script that make API calls will not result in infinite loops.