Changelog - 2.35.0
Released on
Release notes
- New
search_inparameter inanalyze/datasetroute with the precomputed workflow. Allows to define if the documents extraction has to be done by searching entity keywords in the title and/or in the text. Not available withner-linkingworker. - New
entity_volume_sentenceindicator available in theanalyze/{id}/timeseries/{hash}/downloadroute. - New
extractedparameter for thedocuments/translateroute. - A new pending status has been introduced for precomputed instances.
- Chinese and Japanese languages are now handled by the precomputed workflow.
Comments
-
Use the
search_inparameter on theanalyze/datasetwith{"precompute": true}route to choose if the extraction must be done on title, text or both.- Example:
{"search_in": ["title"]}The extraction will be done on entities' keywords only on title.{"search_in": ["text"]}The extraction will be done on entities' keywords only on text.{"search_in": ["title", "text"]}The extraction will be done on entities' keywords on title and text.
- Example:
-
A new indicator
entity_volume_sentenceis now available when retrieving the timeseries for a given analysis. This indicator represents the volume of sentences where the entity of interest is matched for the aggregation period. -
A new parameter
extractedhas been added to the translate route to retrieve a precise version of a document. This date must be the exact date of extraction. If this field is absent, the most recent document will be used. -
Using the POST
analyze/statusroute and a valid instance id, you can now receive a new statuspending. This means your instance is in queue and will be processed. -
The
languagesparameter of thedataset/routenow supportsjapaneseandchineselanguages.