[ 
https://issues.apache.org/jira/browse/CTAKES-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13455979#comment-13455979
 ] 

Troy Bleeker commented on CTAKES-7:
-----------------------------------

Could you point to the documentation you think needs to be rewritten? The 
latest release has "A very basic intro to what cTakes is, what cTakes does, and 
how somebody can use it" via the mechanisms shipped with it. There is no GUI 
outside of UIMA yet.
                
> Pre-Migration- Update/Migrate current cTAKES documentation
> ----------------------------------------------------------
>
>                 Key: CTAKES-7
>                 URL: https://issues.apache.org/jira/browse/CTAKES-7
>             Project: cTAKES
>          Issue Type: Task
>    Affects Versions: 2.6-incubating
>            Reporter: Pei Chen
>            Assignee: Joern Kottmann
>             Fix For: 3.0-incubating
>
>   Original Estimate: 1,344h
>  Remaining Estimate: 1,344h
>
> Update/Migrate current cTAKES documentation
>                 Oy.  As somebody who popped into this world recently I 
> recommend that documentation not be “updated”, but rather rewritten. My 
> opinion on this is that it can be redone with Pei’s new gui as a starting 
> point.  A very basic intro to what cTakes is, what cTakes does, and how 
> somebody can use it via the gui.  After that the document can be structured 
> upon the layout of the gui; top-down, left-right: corpus, AEs, pipelines, 
> etc.   Obviously a lot of the current documentation can be plugged in here 
> and there, but we need to massage it enough that readers don’t feel like 
> they’ve hit a square peg that came out of left field.  Also obvious is that 
> the gui is still evolving and the first bit of documentation will need to 
> evolve with it.  SPF

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to