<commit_before># Change Log

## [v8.1.0]() (2018-06-10)

**Added**
- added `blog` data type. Various methods in `EventRegistry` class accept it, such as `suggestNewsSources()`, `suggestSourcesAtPlace()` and `getNewsSourceUri()`.

**Updated**
- `QueryArticlesIter.initWithComplexQuery()` now accepts also the `dataType` parameter (by default `news`).

**Removed**
- Removed the parameter `articleBatchSize` from `QueryArticlesIter.execQuery` since it was not useful. We are always returning the maximum number of results that can be obtained with a single query.


## [v8.0]() (2018-04-10)

**Added**
- Text analytics: added `Analytics.semanticSimilarity` API call. It can be used to determine how semantically related two documents are. The documents can be in the same or different languages.
- Text analytics: added `Analytics.extractArticleInfo` API call. It provides functionality to extract article title, body, date, author and other information from the given URL.
- `dataType` parameter when searching for articles. Event Registry is now separating collected content by data type. The possible values for data type are "news", "pr" (for PR content) and "blogs" (we will start indexing and providing blog content shortly). The dataType parameter can be set in the QueryArticles and QueryArticlesIter classes as well as in the `EventRegistry.getNewsSourceUri` and `EventRegistry.suggestNewsSources`.

**Changed**
- changed params in the GetCounts and GetCountsEx classes.
- `EventRegistry.suggestNewsSources()` and `EventRegistry.getNewsSourceUri()` now also accepts `dataType` parameter, which is by default ["news", "pr"]. It determines what kind of data sources to include in the generated suggestions.
- `QueryArticles` and `QueryArticlesIter` classes now supports additional parameter `dataType` that determines what type of data should be returned. By default, the value is `news`. For now it can also be `pr` or an array with both values.
<commit_msg>updated changelog<commit_after># Change Log


## [v8.2.0]() (2018-06-29)

**Added**
- added `TopicPage` class. It can be used to create a topic by specifying keywords, concepts, sources, ... as well as their weights. You can specify a threshold and receive only articles and events that match enough specified conditions to reach the required weight. Alternatively you can simply sort the results by relevance and get the top ranked results that are most related to your topic page. See `TopicPageExamples.py` file for examples on how to use the topic pages.
- added named entity extraction endpoint to `Analytics`. Call `Analytics.ner(text)` to extract named entities.

**Updated**
- sentiment analysis now supports two models - vocabulary based as well as a model using neural networks. Choose the model by specifying the `method` parameter. Possible values for it are `vocabulary` (vocabulary based sentiment analysis, default) or `rnn` (neural networks based model).


## [v8.1.0]() (2018-06-10)

**Added**
- added `blog` data type. Various methods in `EventRegistry` class accept it, such as `suggestNewsSources()`, `suggestSourcesAtPlace()` and `getNewsSourceUri()`.

**Updated**
- `QueryArticlesIter.initWithComplexQuery()` now accepts also the `dataType` parameter (by default `news`).

**Removed**
- Removed the parameter `articleBatchSize` from `QueryArticlesIter.execQuery` since it was not useful. We are always returning the maximum number of results that can be obtained with a single query.


## [v8.0]() (2018-04-10)

**Added**
- Text analytics: added `Analytics.semanticSimilarity` API call. It can be used to determine how semantically related two documents are. The documents can be in the same or different languages.
- Text analytics: added `Analytics.extractArticleInfo` API call. It provides functionality to extract article title, body, date, author and other information from the given URL.
- `dataType` parameter when searching for articles. Event Registry is now separating collected content by data type. The possible values for data type are "news", "pr" (for PR content) and "blogs" (we will start indexing and providing blog content shortly). The dataType parameter can be set in the QueryArticles and QueryArticlesIter classes as well as in the `EventRegistry.getNewsSourceUri` and `EventRegistry.suggestNewsSources`.

**Changed**
- changed params in the GetCounts and GetCountsEx classes.
- `EventRegistry.suggestNewsSources()` and `EventRegistry.getNewsSourceUri()` now also accepts `dataType` parameter, which is by default ["news", "pr"]. It determines what kind of data sources to include in the generated suggestions.
- `QueryArticles` and `QueryArticlesIter` classes now supports additional parameter `dataType` that determines what type of data should be returned. By default, the value is `news`. For now it can also be `pr` or an array with both values.

{'fraction_non_alphanumeric': 0.08333333333333333, 'fraction_numerical': 0.010905349794238683, 'mean_word_length': 5.114465408805032, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '7503122', 'n_tokens_mistral': 1279, 'n_tokens_neox': 1209, 'n_words': 634}