Here is one way to organize the tasks for our October deadline.
sds - Sail Data Services, the java servlet that is used by wise to handle sail, there is a lot of overlap between this and the curnit microportal
MP - Micro Portal, Stephen's portal
PLR - Pas Learner Runtime, the java client application used by learners.
- Portal
- Learner Data
- sds receive learner data
- sds send learner data
- sds store data
- sds provide access to do reporting queries
- sds workgroup agents
- wise user id map
- wise workgroup agent map
- Offering
- wise awareness of curnits in sds
- sds curnit url management ui
- wise awareness of offerings in sds
- wise hand off to sds jnlp
- Reporting
- MP reports from sds
- Client side reports from sds (grading tool)
- Learner Data
- PLR
- Bugs in selected curnits
- greyed out navigation
- Note ui
- autoscrolling nav
- webrenderer mac issues - quicktime... or jdic mac
- startup speed
- New features in selected curnits
- integrate OTrunk if needed for selected curnit
- web step that adds session info to url
- flash state saving
- temporary discussion step
- Clientside Deployment
- mac jnlp cache issue
- href on jnlp element or not, no-cache or not, save jnlp on desktop?
- wiped computers each night
- multiple users one computer
- offline
- Bugs in selected curnits
- Authoring
- Authoring content management.
- curnit versioning
- seperate pods from curnit in cms to support multiple curnits with different order
- server to hold curnits or pods, authentication?, simply use confluence?
- Authoring tool
- deleting steps
- saved data format of curnit
- use wise for authoring?
- moving steps
- order of steps separated
- Authoring content management.