A Taxonomy of Collaborative Work/Learning

Here is a list of features that have been supported in various CSCL/CSCW applications. The references (listed in the bibliography) are to papers in which these features have been implemented or discussed.

Communication tools

• Email, etalk or other windows for communication itself [ONeill94, Jehng94, Monteferrante92]
• Colors to indicate people on the system [Muhlhauser94]
• Tools or labels catagorizing the type of communication [Oneill94, Jehng94]
• Tools for coordinating communication like buttons or cursors to communicate who currently got the floor [Wolf92, Stefik87, Keys90]
• Tools for resolving conflict, recognizing one's work is the way to go
• Tools to communicate with the system [Wolf92]
• Tools to communicate the goals of the activity
• Databases for storing ideas [Campione92, Scardamalia92, Oneill94]

Hardware Support

• Multiple mice [Bier91, Bricker95]
• Networks [Gisi94, Muhlhauser92, Muhlhauser94]
• Meeting room systems (no video) [Wolf92, Stefik87, Keys90, JiPing90]
• Meeting room video teleconferencing
• Computer-based teleconferencing [Gaver92]
• "Face to face" computer teleconferencing [Ishii92, Takemura92]
• Controlled input vs. uncontrolled input (anarchy mode) [Muhlhauser92]

Voting systems

• Systems for voting and acceptance

Interface tools

• View of objects, either customizable (private) or WYSIWIS [Smith92, Gisi94, Wolf92, Stefik87, Keys90]
• Shared pointer vs individualize pointer [Gisi94]
• Entering/leaving sessions [Gisi94]
• Easy transition between private and public work [Gisi94, Keys90]
• Hidden spaces/private spaces [Wolf92]
• Minimal training [Keys90]
• Virtual worlds or MUD type interface

Object management

• Owernership attributes/primitives
• Access attributes/primitives
• Object version control
• Ability to manipulate object [Wolf92]
• Primitives for cloning objects
• Undo/"what if" (support for trial and error, hypothesis testing)

Evaluation tools

• log files
• testing methods

CoImage

The computer supported collaboration system we are designing is currently named CoImage. CoImage will support synchronous communication in either co-present or networked (distance) situation. In the co-present case, CoImage will support the use of multiple mice or other multiple input devices. Our focus will be a group size of 2-4 users, although nothing will preclude more from access in the networked situation.

CoImage is being designed as a collaboration aware set of image classes and authoring environment. The CoImage system will support the implemenation of applications such as the multiuser editors described in many of the papers listed in the bibliography). The CoImage classes will also support these features:

Communication tools

• For the system communicate the goals of the activity
• For logging work sessions to files for later analysis

Support for individuals

• View of objects, either allowing customizable views or enforcing WYSIWIS
• Having public view and private views with an easy way to transition between public and private work
• Allowing users to enter/leave a session at any time
• Having individualize pointers, color coded to the users preference
• Using colors to indicate different users of the system

Object management

• Object owernership attributes and primitives
• Object access attributes and primitives
• Ability to manipulate objects
• Primitves for cloning and deleting objects
• Both loosely couple and tightly coupled object manipulation
• An undo or "what if" feature that will support trial and error, hypothesis testing. This will be implemented as a sort of fine grained version control