v2.2.0
Changed
-
Breaking change: When exporting annotations as JSON, the "features" that the annotator entered are no longer nested under
label
(#347). Where previously the export would have been{ "features": { "label": { "field1": "value1" } } }
it is now
{ "features": { "field1": "value1" } }
-
Include details of failed annotations in export formats (#399)
- When exporting annotation data from projects (both via the web UI and using the command line tool),
each document includes details of which users rejected, timed out or aborted annotation of
that document, as well as the annotation data from the users who completed the document successfully.
This can be useful for the project manager to identify documents that are particularly difficult
to annotate, perhaps suggesting that the annotation guidelines need to be extended or clarified.
- When exporting annotation data from projects (both via the web UI and using the command line tool),
Fixed
- Upgraded a number of third-party dependencies to close various vulnerabilities (#397)
- Fixed several issues relating to the export of annotated data (#377)
- Added an explicit setting for "no email security", as an alternative to the implicit setting when the relevant environment variable is omitted. This is because the implicit setting was lost on upgrades, whereas an explicit "none" will be preserved (#402)