Hector
Hector
**Is your feature request related to a problem? Please describe.** Currently, complex attributes of entries (e.g. List, Dict) are not supported. "N/A" or "Complex Object" are being shown at the...
**Is your feature request related to a problem? Please describe.** Forte's new [pointer](https://github.com/asyml/forte/blob/master/forte/data/ontology/core.py#L427) objects standardize the connection between entries. Pointers can be the attributes of entires, the current Stave's main...
Two possible improvements in legend selection: 1. Select all/unselect all/reverse-select in legends 2. Radio selection of the attribute under a particular legend should follow its legends behavior
The current strategy of sending annotations to back end is done by sending over the whole data pack. This is quite a large network overhead. It is sufficient to send...
The full legend name follows a class name convention, thus two legends can be different but share the last segment of their names (e.g. company_a.Prodcut vs. company_b.Product). While showing the...
Some backend controls such as `All document` and `All users` currently appear on top of the page, they should be moved to a different view that is accessible by the...
Currently the database store a document and an ontology together in one table. Since most documents are sharing the ontology, they should be better stored in two tables.
We currently have constraints on the label that can be assigned to a link. Can we render attribute selection from the constraints instead of making users to type in a...
Currently, attributes are appeared as read only on the right side bar. Ability to edit and save these would be quite nice too.
Current ldc-to-xml converter do not give clear error message at some places. For example, when the "-o" option is not provided, it just throw NullPointerException: Exception in thread "main" java.lang.NullPointerException...