[jira] Commented: (UIMA-1875) ability to visualize and quickly update/add values to primitive features

["Jörn Kottmann (JIRA)" <de...@uima.apache.org>]

    [ https://issues.apache.org/jira/browse/UIMA-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12935814#action_12935814 ] 

Jörn Kottmann commented on UIMA-1875:
-------------------------------------

The line spacing can be set on the StyledText with a call to StyledText.setLineSpacing(int).

It seems possible to implement an annotation style which retrieves a feature from
an annotation, and draws it over or under the the annotation text. The field could
have one of primitive types.





> ability to visualize and quickly update/add values to primitive features
> ------------------------------------------------------------------------
>
>                 Key: UIMA-1875
>                 URL: https://issues.apache.org/jira/browse/UIMA-1875
>             Project: UIMA
>          Issue Type: New Feature
>          Components: CasEditor
>            Reporter: Philip Ogren
>
> I spent a bit of time evaluating the CAS Editor recently and have the following suggestion.  It is common to have annotation tasks in which adding a primitive value to a annotation feature happens frequently.  Here's one common annotation task - part-of-speech tagging.  Usually, the way this task is performed is a part-of-speech tagger is run on some data and a part-of-speech tag is added as a string value to a feature of a token type.  The annotator's task is then to look at the part-of-speech tags and make sure they look right and fix the ones that aren't.  However, the only way to see the part-of-speech tag is by clicking on the token annotation in the text and view the value of the feature in the editor view.  This makes the tool really unusable for this annotation task.  What would be really nice is to be able to display the part-of-speech tags above or below the tokens so that the linguist can scan the sentence with its tags and quickly find the errors.  
> There are a number of other annotation tasks that have similar requirements.  For example, named entities usually have category labels which would be nice to display.  Word sense disambiguation data is also similar.  
> On a related note - I have noticed that filling the value of e.g. a feature of type string is really hard to do if it does not yet have a value.  The problem is that it requires extremely precise mouse movements to activate the cursor in the empty text field.  This is very tiresome for situations in which the text is not pre-annotated automatically.  

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.