You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Jörn Kottmann (JIRA)" <de...@uima.apache.org> on 2010/12/02 15:24:11 UTC

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

     [ https://issues.apache.org/jira/browse/UIMA-1875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jörn Kottmann resolved UIMA-1875.
---------------------------------

    Resolution: Fixed

Issue is solved. Its now possible to display features under the actual annotation text.
Smaller improvements will follow after 2.3.1 is released.
Minor issues remaining are:
- Rendering speed (enabling it is slow for long documents with hundreds of tokens)
- Overlaps when feature text is longer than annotation
- Feature text size, feature text color and overhang should be configurable
- End of line tag placement might be improved

Issue will be closed after feedback from Philip has been received.

> 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
>            Assignee: Jörn Kottmann
>             Fix For: 2.3.1SDK
>
>         Attachments: CasEditor-TagDrawingStrategy.tiff, CasEditor-TagDrawingStrategyOverlap.tiff
>
>
> 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.  

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