Creative Services for Web and Education

CSCW: Evaluation on Sakai Widget

Purpose of Testing

The primary purpose of the test is to observe how users interact with the low-fidelity Sakai widget prototype. The secondary purpose was to determine its feasibility.

Introduction to the System

For this prototype testing, it was proposed that the Sakai system would be improved through better communication features, more social networking and protected workspaces. These aspects will be available in one location, the Sakai Widget, placed on the desktop and updated throughout the day.

Interactivities of the System

Recent Discussion Board Items
Recent activities in the class show up in the top section of the widget. Users click a link to read it in Sakai.

Updates to Our Workspace
In the middle of the widget, the dedicated team workspace called Our Workspace shows recent updates for the team. Our Workspace is a worksite for groups within a class. This protected workspace will allow more freedom for groups to work where they are not visible to classmates but the instructor can still see their thinking process. Group members see the new items from their group as well as thumbnails of new image files in the widget. Users click a link to see the resource in the Sakai Our Workspace. This area enables students to stay in close contact with teammates so they can successfully get a team project done.

Chat
Classmates' availability for chat is visible in chat section. Chats can be initiated by mousing over the name and choosing the chat icon.

Social Networking
At the bottom of the widget, a social networking area is available for a quick visual cue on new content in chosen classmates' pages. This area supports self-expression and builds a stronger sense of community through social networking systems such as blogging, photo sites and video sharing.

Profiles of Users

Two users were chosen. One was a master's level student with a long history of using the Sakai learning environment (1.5 years) and one was an IT expert with experience in widgets and widget development.

Testing was conducted on the phone and in person. Background information was gathered. The users reviewed and used the widget. Then I asked a series of questions about the widget. There was also time for open discussion.

Debriefing

Debriefing was conducted in an informal, conversational style. Users were asked about their experience and whether they had anything further to add.

Summary of Appropriate and Problematic Aspects

A widget would be an appropriate method for keeping in close touch with necessary work. One user said that widgets are "more handy than applications" because they show only the most recent activity instead of everything simultaneously.

Specifically, the most useful aspects included the chat feature, discussion board updates, the addition of our workspace and our workspace updates.

One major problematic aspect of the widget was its feasibility. In its current form, Sakai is on a secure server. There would be a number of security issues to address before this widget could run on an open desktop including allowing the widget to log in automatically and preventing session time-outs.

Another problematic aspect requires more social networking research to determine 1) whether the social networking area is a worthwhile aspect of the widget, 2) if the addition of Facebook interactivity is possible. A user suggested that Facebook should be interconnected to the social networking area. This recommendation would need to be further examined as it is a third-party application.

It is also possible that the Social Networking Area should be removed. A user suggested that the social networking area is not valuable enough to justify the real estate on the widget.

Recommendations for Improvements

Add Shared Links Area.
A user suggested that a shared links area would improve the Sakai Widget. This section would represent the group's collection of relevant links and would also need to be developed in Sakai.

Add Design Details to Prototype for Future Testing.
Future testing on the prototype would include more interactivity on the Sakai widget so it could be better evaluated. Some aspects that were lacking included a button to minimize the widget, a text box and send button in the chat area and consistency of fonts since there was a mix of screenshots.

Focus on Chat.
A user suggested that chat was a most crucial part of working collaboratively, especially in a deadline situation, so development time would be well spent making the chat aspect robust.

Improve Clarity of Chat Availability.
Chat list of who is available will be more obvious on future prototype.

Enlarge Text.
Some text was difficult to read on the current design.