Richard Eckart de Castilho

**Describe the bug** When there are multiple recommenders for different features of a single layer, it can lead to multiple "no label" suggestions being rendered - one for each feature....

**Describe the bug** The fields `document`, `user` and `project` in `AnnotationDocument` should not be nullable. **Please complete the following information:** - Version and build ID: 38.1

**Is your feature request related to a problem? Please describe.** We currently have no document structure tree for HTML files. This is somewhat related also to a bug where annotations...

**Describe the bug** Undo does not seem to affect the retained suggestion info. **To Reproduce** Steps to reproduce the behavior: 1. Enable retaining suggestion info in a multi-value string feature...

**Is your feature request related to a problem? Please describe.** Link-feature auto-merging is currently only supported for span features. However, document-level layers also support adding link features. **Describe the solution...

**Describe the refactoring action** Remove unused recommender declarations when removing an annotation with retained recommender info. **Expected benefit** No unused data left in the CAS.

Recommendations for label-less annotations and feature-less layers

4

Currently, the recommenders only learn from annotations that have features and these features must have values. Sometimes, I just want to quickly make some annotations, e.g. quickly mark named entities,...

**What's in the PR** - Introduced Annotation class with default begin/end 0 - Update reference data accordingly - Fixed several issues with sorting/ordering annotations **How to test manually** * No...

**Is your feature request related to a problem? Please describe.** All our CAS data inherits only from FeatureStructure - we have no Annotation type - despite UIMA having that. **Describe...

**Describe the refactoring action** Add more type annotations. **Expected benefit** More type-safety. Better linting.