[LON-CAPA-dev] Future Directions for 2.6 Results

[Guy Albertelli II]

Hi All,

So the main thrusts that seemed to be desired where:

   - we need to find where we need to go,
     need more of a wide spread pull survey
     from existing people and from the wider
     community to identify missing items, or
     finish/polish that needs applying
   
   - username migration 
       - better overall user management

   - try to get a design
       - need to define 'categories of pages'
       - pick a designer
       - apply the design

   - WYSIWYG needs serious fixing

   - kill "Update Display" on lonindexer

   - fine grained cloning choices

   - more homework!


---- old results from previous meeting copied below-----
 3A > 3B > 4A > 6 > 4B > 1 > 2 > 5A >> 5B
(category definitions below)

Fe -> Felicia
Gu -> Guy
Ge -> Gerd
Gr -> Overall Group
St -> Stuart

Finish off:
St - Groups PORT spaces links from Users PORT space

3A:
Gu - continue usability -> separtation of layers

3B:
Gu - implementing results existing study
     (some efforts need to be made at interpreting the results)
Gu - implement accessibility changes

4A:
Gu - domain trust settings -> take a look at what it entails


6:
Gr - Code cleanup? Documentation? Comments?

4B:


2:
St - collborative student submissions
St - Lock-down extrenal send of COMs as per dated COM


1:
St - simple problem plagerism
Gu - Parameters for Show answers in homework
Gu - conditionals - stop punishing the student
Gu - tag to formalize and simplify the process of getting information
     from the user that is later used in the HW


----Decoupled from release schedule:---
 3B:

 - need to get started on a 'overall review' of uer interface and
   decide on some html/design style guides

 4B:
 - better built demo domain?
 - Camtasia training session help files for things that 
   people want help for

------ not for 2.4 ------
 - better 'snapshot' of what a student has done in a course
    (problems done.. posts made.. mails sent... login times...)
 - &generate_incorrects()
 - Discussion groups (similar to Angel) where a Group
   really is a course with everything just renamed.
   (complications occur relating to permissions and
    definitons)

 - Setting up an on-line Discussion/Essay course    2
 - domain # scale issue?
 - making it easier to change usernames

 - multiclick image response (2.4?)
 - easier assigned seating for exam mode
 - DC -> choose any author
 - /OR - <sr> --- <o/r/m/rb/r> --- xml style on this
 - UTF support in printing
 - plagrisms check on more than pure text
 - instructor specified units
 - <drawimage> print support
 - .rights in source avail
 - QTI
 - Ability to add problems to sequences from text/csv
   file 5

 - Lon-capa time in menu mode somehow...


----- Categories ------

1. strengthen our strengths
   - more problem types 
   - improving existing types
   - better control over flipping on/off new features

2. attract new users with new features
  A. softer sciences
      - groups
      - wiki
      - discussion (more info about?)
      - more like moodle 
  C. BT & QTI (money)
  
3. usability enhancements
   A. better seperation between 
      presentation/application layers
   B. - streamlining existing interfaces
      - easier learning curve
      - grant for CC analysis
   C. improved interface for students

4. systemwide growth enhancements
  A. - domain browse/search
     - domain grouping
     - domain trust settings
     - domain configuration info
  B. - ease of installation/maintenance
     - syncing to existing university systems
     - better demo?

5. Standards support
   A. supporting authoring use of external standards
        - SCORM RTE
        - QTI (seems more important to international
               users?)
   B. supporting exporting of existing resource /
      data into standards
        - OSPI
        - OKI/Sakai

6. General Code Maintenace / Documentation

-- 
guy@albertelli.com   0-7-0-6-27,137