This site has been moved to Home
One of the things that Sakai lacks is a simple way to present content to a student in a manner consistent with an approach to pedagogy defined by a teacher. Sakai tools are heavily focused on collaboration (chat, discussion, wiki, etc.). There are some tools, such as Melete, Samigo, and the Resource Tool, that present content, but they are large applications aimed at accomplishing specific tasks.
The Sousa project is aimed at creating simple, sequenced content for delivery to a student. It is based on the idea that content should be managed by the Content Hosting Service, thus giving users complete access to it via the Resource tool. Sequences are saved in XML files, and eventually will have an export mechanism that will zip up a sequence with its content items. It can be thought of as a learning construction kit that's easy to extend and flexible in its use.
You might be interested in Sousa History and how this came to be.
See also Resource View project.
Download the 2.4.x-2 code.
This project has gone through several name changes. Originally it was just the Sequencer project, but that didn't distinguish it from other sequencer applications in Sakai like Melete and SCORM. The "Page Object Content Sequencer" was more descriptive, but people were a bit put off by the similarity of POCS to Pox when pronounced. Feedback at the Eighth Sakai Conference suggested that a better name was needed. After some discussion and thought, the name "Sousa: the Page Object Sequencer" was selected. Sousa is a reference to John Phillips Sousa, the American composer of marches and band music. The wish is for an application that would "line them up and make them march".
The Sequencer project also owes a debt to the UC Berkeley Gallery Tool, since that served as the conceptual basis for Sousa. Some of the inspiration for this work came from Learning Structures