July 30, 2003

1. Meeting flow - Meghna created xml file which includes statement, statement key, character key and state key to address branching structure and animations. It was suggested to use punctuation within statement as the trigger for animation states, but this idea was rejected. Animation states will be hand coded.
2. Animations - 3 characters are currently designed (blonde woman, black youth, elderly man). Committee has requested to replace blonde woman with asian male for the Perez case. (Keep blonde woman for future case.) All characters will have the following states (labeled thus):
   • blink (randomized neutral state)
   • sleep (triggered by mouse inactivity - needs to be coded properly in Flash file)
   • exclaim
   • question
   • sleepy
   • happy
   • content
   • angry
   • worried
   • also, first frame of each character is labeled passive, and is an inactive gray version of the character, used when nothing else is going on, and the character is a listener, not speaker.
3. Library - xml file created to indicate variables of all resources that will be needed. It was unclear whether GaTech resources would be represented multiple times in the tool - for each specific issue cited (class A, with multiple entries for the multiple issues), and again as the entire text for browsing (class B, one entry, full text version or link to full text version). This would affect the unique value needed for the title, and should be decided before developing the xml file of the library. (The unique value might be a combination of the title of the resource plus the section, paragraph or page from which the citation comes.) Suggested fields (or variables) to be included:
   • author
   • title (unique value)
   • topic (one only, from defined list)
   • keywords (multiple, from defined list)
   • statement key (same as from Meeting xml)
   • date of bibliography
   • resource type (candidate's file, bibliography, GaTech resource)
4. Conclusion - the concluding statement (outcome of the meeting) should be a cumulative effect of the three decision points that the user selected. It was suggested that this be programmed so that DP1x + DP2x + DP3x = ConclusionY where DP1x is First Decision Point with value from 0-2 indicating the appropriateness of response, and Conclusion is a value within a certain range that yields a particular outcome. This idea was tabled, and outcomes are to be hard coded.

Future Revisions

Lists to be updated:

• Topic List (undergoing revision)
• Sample Bibliography
• Georgia Tech Resources
• Credits

Link to this Page

• Minutes

Project Organization

Related Links