You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by Philip Ogren <ph...@ogren.info> on 2010/12/02 05:41:43 UTC
2 questions - Re: [jira] Updated: (UIMA-1875) ability to visualize
and quickly update/add values to primitive features
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.
Re: 2 questions - Re: [jira] Updated: (UIMA-1875) ability to visualize
and quickly update/add values to primitive features
Posted by Jörn Kottmann <ko...@gmail.com>.
Did that work for you ? Could you test the tag style on your project ?
The issue should be closed soon, since we want to go for the next RC
tomorrow.
Thanks,
Jörn
On 12/2/10 2:45 PM, Jörn Kottmann wrote:
> Now you should be able to just start the Cas Editor as eclipse
> application.
> For example right click its plugin.xml file and select "Debug As" ->
> Eclipse Application.
>
> There is a new drawing style in the properties called "TAG", select it
> for an annotation
> and set the feature to your tag feature.
>
> Jörn
>
> On 12/2/10 5:41 AM, Philip Ogren wrote:
>> 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.
>>
>
Re: 2 questions - Re: [jira] Updated: (UIMA-1875) ability to visualize
and quickly update/add values to primitive features
Posted by Jörn Kottmann <ko...@gmail.com>.
Now you should be able to just start the Cas Editor as eclipse application.
For example right click its plugin.xml file and select "Debug As" ->
Eclipse Application.
There is a new drawing style in the properties called "TAG", select it
for an annotation
and set the feature to your tag feature.
Jörn
On 12/2/10 5:41 AM, Philip Ogren wrote:
> 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.
>
2nd question
Posted by Philip Ogren <ph...@ogren.info>.
I thought of my other question - but decided it was the sort of question
I should post to the uima users instead of asking you directly.
On 12/1/2010 9:41 PM, Philip Ogren wrote:
> 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.
>