Hi Jörn,
I spent about an hour last night trying to figure out how I could look
at the changes you recently committed to CAS Editor and made no
progress. I am able to compile the code with maven and have the
projects there in Eclipse - but I just don't know how to run the darn
thing. You don't have to spell it out for me - but if you could at
least point me to a good entry point for the Eclipse documentation that
would be really helpful. I looked at a bunch of tutorials and such and
couldn't find the bit I need.
Thanks,
Philip
On 12/3/2010 3:59 AM, Jörn Kottmann (JIRA) wrote:
[
https://issues.apache.org/jira/browse/UIMA-1875?page=com.atlassian..jira.plugin.system.issuetabpanels:all-tabpanel
]
Jörn Kottmann closed UIMA-1875.
-------------------------------
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.
