Added semanticSimilarity, extractArticleInfo analytics endpoint, many backend changes
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 theEventRegistry.getNewsSourceUri
andEventRegistry.suggestNewsSources
.
Changed
- changed params in the GetCounts and GetCountsEx classes.
EventRegistry.suggestNewsSources()
andEventRegistry.getNewsSourceUri()
now also acceptsdataType
parameter, which is by default ["news", "pr"]. It determines what kind of data sources to include in the generated suggestions.QueryArticles
andQueryArticlesIter
classes now supports additional parameterdataType
that determines what type of data should be returned. By default, the value isnews
. For now it can also bepr
or an array with both values.
Removed
- Removed the RequestEventArticleUris, RequestArticlesUriList, RequestEventsUriList due to backend changes. Use the equivalent *UriWgt* version of the classes.
- Removed RequestArticlesUrlList class since it is not supported anymore.
- Removed
QueryArticles.addRequestedResult()
,QueryEvents.addRequestedResult()
,QueryArticle.addRequestedResult()
,QueryEvent.addRequestedResult()
, andQuery.clearRequestedResults()
. As before, a single result type can be requested per call so the methods are not usable. UsesetRequestedResult()
methods. - Data model change: We removed the
id
property from different returned data objects. Although the documentation clearly stated that the property is for internal use only, users commonly used the property, which caused potential issues.