NEXT CALL: JULY 16nd  11:30 EST

Local: 265-8030 Toll Free: 877-265-8433

Interface programming update and priorities (July 9th 2008)

Lots of emails back and forth between Amit, Andrew, Stefan and Catherine, but No conf call today because of too few participants, overlapping meetings, delays, lions and bears...

•  Amit and Andrew have made progress on the task of getting results back to users even for large worksets (i.e. the size that Sara needs).  Not quite there yet, but should be soon.  Amit is close to having users get an email emailed telling them their analysis has completed. We now save toolset ID and the user's email along with a result.  Andrew still has to write the code to reload the result with its toolset, but that shouldn't take long. 

• The tree browser is still slow, but I've been working on an alternate collection browser, similar to the horizontal/column navigation in the OS X finder.  Since it only displays a part of the collection at a time, it seems to be a lot faster.  On a related note we re-discussed the need in the future to allow the workpart rating to be done in a tree-structure environment to provide context and allow rating of entire branches at once.

•  The highlight of features in the chunk viewer (i.e. showing where the feature appear in the text) is working now. WARNING: None of those changes are visible yet because auto-updating of the Monk website has been turned off while Amit and I finish up the new analysis and result calls.
• No action on the export (yet)

Interface programming update and priorities (July 2th 2008)

(late notes from Wednesday meeting, with one extra item from Monday's supper cell call )

July 2nd
Amit, Andrew, Catherine

We focused mostly on determining what the most critical tasks were to allow Sara to work on her use case without going thru Amit for everything.  That was:

>> for next week (and 2 weeks)<<
- Allow users to be notified by email when results are ready (to avoid problem that the browser times out). 
- Allow users/Sara to return to her project the new results are visible there, and can be opened, which launches the "search by example" toolset (and allow iterative work)
- Make the treebrowser work with big worksets (currently we cannot load Sara's workset, and noone else could create such a large workset).

- Allow export/save of results data on user local computer (so it can be loaded into other tools). [added today Monday by supercell as critical]

>>>Last week<<<
- Fixed a lot of Bugs on different parts of the tools
- Fixed the problem with "save as"
- More middleware calls work/exploration
- Created a second "search by Example toolset" to separate the more realiable pne from the experimental one

>>>Still delayed to the future<<<
- Look at what's gone wrong with Fisheye: Amit
- We need to fix the decision tree so that it doesn't crash the system.
It's currently out of the workbench: Amit
- The master tool needs to retain the window shape: Alejandro and Andrew
- Created a single tool header that includes the master tool selection:
Andrew and Alejandro (Kept from last week - more complex than expected)

NEXT CALL: JULY 9nd
Local: 265-8030 Toll Free: 877-265-8433

Interface programming priorities (MONK interface cell meeting minutes 08-05-28)

NEXT MEETING IS JUNE 11th

Past week - outcomes

• We can now save results in the workbench.
• The starting screen now provides an overview including results sets rather than just the list of toolsets.
• We can see the decision tree in the Search by Example toolset.
• We can support stemming and stopwords for Sara's use case, but not yet in the workbench.
• We started work on master tools.

Next week - plans

• Add some instructions to the top of the starting screen. This should say "Please choose a Workset, Results, or Toolset, then click "continue": Andrew
• The user should be able to name results: Amit and Andrew
• Retrieving results still needs to go in the workbench: Andrew
• Search by Example should produce three kinds of results and recentlyproduced only one kind: Amit will look into it
• Supporting stemming and stopwords for Sara's use case in the workbench: Andrew
• The master tool switching should be possible: Alejandro and Andrew
• We should remove the search box from the 3 pages when it does not work: Andrew
• We need to test the search functions: Catherine

Interface priorities (MONK interface cell meeting minutes) 08-05-21

Last week's accomplishments

• We have the calls for saving and retrieving results but not yet in the workbench.
• Amit briefed Catherine's student Romain on MONK, so that he can start to do an exploration phase for Tanya's use case.

Next week's plans

• We will add the calls for saving and retrieving results into the
  workbench: Andrew
• We need a link to these results. There is a sketch by Milena: Andrew will do this
• We want to see the decision tree, so we'll add it to the Search by Example toolset: Andrew
• Search by Example should produce three kinds of results and recently produced only one kind: Amit will look into it
• Supporting stemming and stopwords for Sara's use case: Amit
• Start work on master tools. There is a sketch: Alejandro and Andrew ______

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.

Some discussions and updates are listed in the demo script page

(see https://apps.lis.uiuc.edu/wiki/display/MONK/Current+demo+script

Also see notes are in THE APRIL HACKFEST PAGE

See https://apps.lis.uiuc.edu/wiki/display/MONK/April+08+Mini+Hackfest

Catherine & Andrew's Phone Call/Demo (3/27/2008)

Project Selection

• project list should refresh on project creation
• deleting project stops you from selecting other projects
• stop user from creating projects with same name
• ability to double click to launch project, (also disable text selection)

Project Page

• double click toolset to launch
• enter new workset name is unclear, change it

Toolset

• collection tree
  • hourglass for large node expansion
  • grey checkmark for node with only some child nodes checked
  • don't expand subnode on node check
  • when checking a node, check ALL child nodes
    • i.e. workset is always composed of the smallest granular workparts
• continue button to move to next step in the bottom right
• need consistent layout of components when moving between steps
  • keep chunk viewer at the right side
• should be able to save workset at workset selection step
  • either add save button to collection tree browser or add workset manager to first step
• workset manager
  • change to tree grid (eventually)
  • remove project combo (it's already been selected)

Catherine's Feedback (3/21/2008)

In Projects page: 

A double click should open the project (i.e = select and continue) and no edit the title. Add a [rename] button right of [Delete] Not sure what you have in mind for [export] ....Instead of a "enter new project  You now show the # of toolsets and worksets. also show the # of intermediate data and # of results.  Display each type of detail only when it is more than 0Replace the button that says [Toggle details] by a toggle with a check mark:  [ ] Show Details  Order the projects alphabetically by default. Later we may add alternative ordering/groupingsBUG: after playing around, creating a new project called Catherine then deleting it, then I could not select a project in the list anymore.  When I clicked continue it opened the new project I Catherine that I had just created .I could create 2 projects with the same name (i.e. CP) The new project doesn't always appear in the list (I needed to reload to see it)

In the slected project page e.g. test

I should be able to start a toolset without selecting a workset.

In search by example 

If i have gottne here by selecting a workset then serach-by-example, then why doi i still have to define the workset.? I should go into rating...  (the tabs let me go back to workset editing if needed)

The rating  screen is confusing... I am lost....

Andrew let's do this son the phone so i understand better what you have in mind.

Catherine's Feedback (3/11/2008)

- small FIX in projects page: I can type the name of a new project but when I click on new project nothing happens until I refresh (so of course I created 2!)

- samml Fix in projects page:  order the projects by time of creation or alphabetical (ideally there is a toogle to change that).  You list the number of workset and toolsets.  Instead list the numbers of worksets, intermediate files, results, and custom toolsets and possibly toolsets used...  The number of toolsets will be the same for every projects at the start so no point listing it.

- Small FIX:  When I start my new project I have no worksets yet so the title "Worksets", or "enter name of workset" doesn't make sense to me.  The buttons at the to (copy delete move etc.) should be grayed out is no action is possible. Also make the toolsets that are not Active gray out and not selectable.

- problem to discuss:  I click or double click on Search by Example and nothing happens...   So I tried to name a workset and then i could start the search.  This is REALLy not ok, way too complicated.  I should be able to start the search by example tool directly without picking a workset if there isn't any!  and it I create a new workset right from the top then you need to start a toolset that select the workset. 

 - small fix:  It is very important to change the cursor to something else (e.g. an hour glass) when the system is waiting for an answer, otherwise it looks/feels broken

 - Problem:  When I selected the all NCF it hanged, and finally came back to life after about 20 seconds with all the next 2 levels of the collection opened!  I didn't I ask for the hierarchy to be opened, I just wanted to select the whole collection.  Users won't mind (too much) a long wait if they are confident the system is not broken.  Same thing when I try to close the hierarchy... it seems to hang.  Actually I think I am really stuck this time.  Need to restart all.  So FIX:  give better feedback and don't open the hierarchy if the user didn't ask to do that.

 -  so I restarted, went back to the same project, try to create a new workset (i.e. really type its name) but I could never get the "create workset" to work.   So I restarted again, and now I get an error saying " error getting collection metadata"  (9:20 EST) I'll try again later.

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

Alejandro

• connecting to Google chart and Many Eyes API  

Matt

• Making the workbench look like Milena's designs (CSS-wise)
  • Stage 1: Front page (done) - will upload today
  • Stage 2: Second page (style projects, title, buttons, and border)
  • Stage 3: Window style (titles, border needs new images, dropshadow, controls)
• The CircleMagic widget
• Abstraction (Components)
  • Settle on what files a component must have (new inclusion: an xml config file that includes title, thumbnail image, description, and optionally some size info like default, desired, max/min) Comments welcome Component Creation Guide#newComponentGuide
  • Make some JIRA ticket for James (possibly Amit) Email request to Amit (Stan)
  • Make a JIRA ticket for Andrew Email request to Andrew (Stan)
• Abstraction (CSS)
  • Figure out why we have 10 css files.
  • Reduce that number
  • At the moment, it is convenient to keep my css changes separate from Andrew's, so we'll need at least two for the moment.
• Tool CSS
  • Style Advanced Chart Config tool

 
Andrew

• change the orientation of the tools in the toolset to be horizontal insteda of vertical
• remove the toolset bar at the bottom of the screen, and the animation of the toolsets going down the screen
• when returning to the toolset tab, the toolsets should appear

Mike P

• test insert of an OpenLaszlo (Flash) component into the workbench
  • FireFox = problems with overlap, Safari = works well
• test insert of Java Applet (Mandala Browser) into the workbench
  • FireFox = problems with overlap, Safari = problems with overlap
• Google Charts Servlet work
• Google Charts Component