CURRENT

Interface programming priorities until Wed May 14, 2008:

• Keeping with the goal of Getting Sara's use case up and running:

• Get some kind of Decision tree display, whether static or active, working consistently in Search by Example.

• Display the kind of error where no features are returned. Andrew already handles the situation where Amit returns an actual error.

• Allow reloading of previous Search by Example results that have been saved. This will really help with demos.

OLD:

Chicago Hackfest: 2/9 

Focus should remain on making detail design decisions so that implementors have clear direction.  Focus  remain on the "search by example" i.e. Sara's use case needs.

We reviewed the design as of 2/9 (before the Chicago hackfect) and identified problems with workflow and ability to save and recall your work at all steps.
The design was revised with paper mockups and Milena is doing the detailed screen designs

• revised all screens (see paper mockups)
• After the select project, the next screen now allows users not only to select a toolset but also to select one of the existing project "files" i.e. workset, intermediate data or results to go directly to that phase.
• need revised project manager design with "avanced management functions":  rename, delete, copy, export.   Export will allow to export results to CVS, or export a workset to a different project, or eventually publish a training set or classification...
• make sure all screens show the shared "Search" and "Display options" buttons