Capturing and Presenting Relevant Information in the EDC Eric Minick, Jackson Fox Design, Learning, and Collaboration Spring 2002

Overview Rationale Rationale Approach Approach Behavior Behavior Implementation Implementation Future Work Future Work

Rationale EDC problems do no exist without precedent EDC problems do no exist without precedent EDC does not play well with others EDC does not play well with others Adding the ability to add viewpoints to a discussion will improve the ability of the EDC to aid problem-solving Adding the ability to add viewpoints to a discussion will improve the ability of the EDC to aid problem-solving

Approach Identify basic workflow Identify basic workflow Identify sources of information Identify sources of information Harvest resources Harvest resources Store resources Store resources Provide resources to EDC users Provide resources to EDC users Develop a sample implementation Develop a sample implementation

Behavior Links are gathered in the Organizer and assigned relevant tags EDC session is developed and topics identified Organizer provides relevant links to EDC EDC session: users can provide notes on resources Agents are sent out to gather links

Implementation We’ve implemented some pieces We’ve implemented some pieces A RTD schedule agent and CLI agent. A RTD schedule agent and CLI agent. The backend database. The backend database. Database interaction classes in Java Database interaction classes in Java A simple test web page for front to back test A simple test web page for front to back test Some of an organizer. Some of an organizer.

Future Work Integration with the EDC Integration with the EDC Complete UI Complete UI Complete and intelligent Organizer Complete and intelligent Organizer More Agents / More intelligent Agents More Agents / More intelligent Agents Examination of whether a keyword model makes sense Examination of whether a keyword model makes sense

Questions?