uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Philip Ogren <phi...@ogren.info>
Subject 2 questions - Re: [jira] Updated: (UIMA-1875) ability to visualize and quickly update/add values to primitive features
Date Thu, 02 Dec 2010 04:41:43 GMT
Hi Jörn,

I decided that I would try building the latest code for the CasEditor 
and take a look at your recent changes and poke around the code a bit.  
I was able to checkout the uima code with subversion, build it with 
maven, and import the projects into eclipse.  Now I'm not sure what to 
do next.  Do you use the Eclipse PDE when you are experimenting with the 
Cas Editor plugin - or do you restart eclipse after copying the new 
version of the plugin to your plugins directory?  Any hints about this 
would be great.  I don't now remember my other question - must be 
getting late!

Thanks,
Philip

On 12/1/2010 5:14 PM, 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 updated UIMA-1875:
> --------------------------------
>
>      Fix Version/s: 2.3.1SDK
>
>> 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.


Mime
View raw message