Diff for /loncom/TODO between versions 1.81 and 1.86

version 1.81, 2001/04/24 23:29:38 version 1.86, 2001/05/17 17:39:42
Line 23  XMLPARSE Line 23  XMLPARSE
     + deregister()      + deregister()
     + register need to take care of overloading, and deregister needs to unload      + register need to take care of overloading, and deregister needs to unload
     + answer target - for simple display of correct answer for a problem      + answer target - for simple display of correct answer for a problem
       * <m> tag needs to do variable evaluation before tth-ing the string, also 
     add eval="nothing" to turn this off.
       * convert the rest to use get_param
   
 CAPARESPONSE.C  CAPARESPONSE.C
    !+ pass back the reason (Y)     !+ pass back the reason (Y)
Line 34  RUN.pm Line 37  RUN.pm
 EDIT INTERFACE  EDIT INTERFACE
     + undo (Y)      + undo (Y)
     + delete (Y)      + delete (Y)
     + insert (Y)      * insert (getting there) (Y)
     + add more tags (Y)      c add more tags (Y)
     & make it easier to add plain textfield stype entries (Y)      & make it easier to add plain textfield stype entries (Y)
     + have textfield style entries protect against bad data (</parserlib> in       + have textfield style entries protect against bad data (</parserlib> in 
  the parserlib textfiled (Y)   the parserlib textfiled (Y)
Line 46  HOMEWORK Line 49  HOMEWORK
    !+ create <stringresponse> <formularesponse>(Y)     !+ create <stringresponse> <formularesponse>(Y)
    !+ <rbresponse> <oresponse> need to restore last submitted response (Y)     !+ <rbresponse> <oresponse> need to restore last submitted response (Y)
     + <rbresponse> <oresponse> hints need to work (Y)      + <rbresponse> <oresponse> hints need to work (Y)
       * <rb/i/o response> break if name isn't spcified (Y)
     & all response types need to be verified about what they do after the       & all response types need to be verified about what they do after the 
       answer date (Y)        answer date (Y)
     + view problem as specific student (Y)      + view problem as specific student (Y)
Line 54  HOMEWORK Line 58  HOMEWORK
     * <essayresponse> needs to protect input / output      * <essayresponse> needs to protect input / output
   
 /ADM/GRADES  /ADM/GRADES
     + search for students (Y)      * show list of multiple students if multiple match (Y)
     & find domain of student (Y)      * allow specifying the domain (Y)
     + handle ambiguous case (Y)      + handle ambiguous case (Y)
     + back to homework link (Y)      + back to homework link (Y)
     + handle extra fields (Y)      + handle extra fields (Y)
Line 114  RAT Line 118  RAT
     + need to be able to evaluate conditions in lonuserstate      + need to be able to evaluate conditions in lonuserstate
     + need to be able to set conditions in RAT client (G)      + need to be able to set conditions in RAT client (G)
     * "finish" resource non-editable      * "finish" resource non-editable
     + "finish" resource when empty causes the serever to through "noidea" when   
         trying to use Next or Back buttons  
     * unescaped colons in resource titles      * unescaped colons in resource titles
     * timeouts seen at Ohio U  
   
 PUBLISHER  PUBLISHER
     * needs to devalidate spreadsheets in problem publishing (G)      * needs to devalidate spreadsheets in problem publishing (G)
     +?does HTML to XHTML cleanup job      +?does HTML to XHTML cleanup job
     + co-author role respected  
   
 VERIFICATION OF CONTENT  
     c have TA's do homework (G)  
     c verify internal page links  (G)   Large Chunks of funtionality that need work:
     c verify applets (G)  
     c do homeworks from home/computer labs (G)  - Statistics
     c be always at least two weeks ahead in homework   - Simple
    - resource analysis class/system wide
    - resource correlation course wide
    - other stats from CAPA
    - Complex
    - foil level analysis/correlation measures
    - derandomized foils analysis
    - have/view reason student selected a foil
    - resource quality, how good is a resource
   
   - Messaging
    - crtical messages
    - email gateways into/out of the system
    - handle more types of communication
          - stu <-> stu
          - ins <-> stu
          - ins -> class/section
          - messages seeded with data from spreadsheet
          - chat / whiteboard / bbs
          - "round robin" feedback handling
   
   - Grading
    - simple grading needs cleaning up (see Guy's TODO list)
    - survey data extraction ( stat complex could handle most of
     this)
    - essay / shortanswer
    - instructor / autoget all/none
    - team based submission
    - peer graded
    - peer suggest grade
   
   - homework engine
    - new parm - mode -> homework/exam/survey controls response
     renderings / awards and solved status
    - edit interface / clone other problem
    - math stuff
    - validating <part> and multiple <*response> works as
     advertised
    - handling previous answers correctly
    - CAPA problems 
    - <imageresponse> need Java applet
    - <randomlabel> 
   
   - metadata
    - implement new method of handling what a problem stores
   
   - RAT
    - set parms / choose parts
    - set conditions
    - language for conditions
    - browse link
    - some kind of non-anti-save
   
   - Publish
    - review step
    - coauthor role
    - permisions / locking
    - retrieve diff
    - auto thumbnail / convert images
   
   - printing
    - tex target (CGI / daemon?)
   
   - Remote Control
    - instructor remote (MyDesk?)
    - evaluate this quality control feedback
    - level up / down
   

Removed from v.1.81  
changed lines
  Added in v.1.86


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>