From EduTechWiki - Reading time: 6 min
Here is a table of typical C3MS components along with a list of functions useful to activity-based pedagogical designs. This is not a canonical list, it only demonstrates the spirit.
|
Function |
C3MS modules (tools of the portal) |
|---|---|
|
Content management |
News engine (including a organization by topics and an annotation mechanism) |
|
Knowledge exchange |
News syndication (headlines from other portals) |
|
Exchange of arguments |
Forums and/or new engine |
|
Project support |
Project management modules, |
|
Knowledge management |
FAQ manager |
|
Community management |
Presence, profile and identification of members |
Some of these tools are awareness tools : elements that answer "who, what, where, when, and how".
The abstract of Schneider et al. (2003) argues that C3MS can fill in needs as "scenario and "community" engine.
See the C3MS project-based learning model for more details.
Pedagogical story-boarding with a C3MS follows a simple principle. The teacher creates a pedagogical scenario (activity) by defining different phases of the work process. Each phase contains at least an elementary activity which in turn should be supported by a tool (portal brick). Larger projects can contain several smaller scenarios. The scenario building bricks, i.e. elementary activities are something like "search on the Internet", "insert a link", "make a comment", "coedit a text", "vote for something", "enter an item to a glossary". It is needless to say that portals can not provide all the tools than can be imagined, e.g. on-line drawing programs are hard to find. Anyhow, it should be planned that at least the products of some activity should be posted to the portal, in order to discuss, annotate and reuse them. In the TECFA SEED Catalog (based on the original TECFA SEED teacher's catalog) we classify the scenarios according to the following categories:
While as we showed before, C3MS portal provide rich functionalities for pedagogical "story-boarding" they have been designed first of all as community portals and therefore are ideally suited to boost collective learning, creativity and optimal experience.
First, the portal should be a rich information space for " domain support " and it should encourage students add their own contribution. Such a space also encourages exploration . Typical tools are links managers, wikis, news engines and RSS feed that keep users up-to-date about articles posted to other interesting portals or individual weblogs.
Intellectual support is provided via forums, annotations and articles. Student productions are always accessible to all (including visitors) and therefore provide for recognition . One could manage activities by using various standard tools like articles, forums and the calendar, but it may be more appropriate to use special tools, e.g. simple project management tools or special purpose ones. In our experience, it has been shown that students are more like to contribute to an environment if they own an online identity. In the student's partly automatically generated home page on the portal one can see their contributions, read public parts of their personal blog and conversely each production in the portal is signed with a clickable link to the author. A successful teaching by projects pedagogy needs to provide strong emotional support and it is therefore important to encourage spontaneous, playful interaction and corner's for humour that will augment quality of on-line life and contribute to class spirit. Tools like the shoutbox or a little quotation box can do wonders.
See also creativity, community and motivation.
Finding an appropriate portal is very difficult. In the absence of standards for active pedagogics and given the dominance of so called "e-learning platforms", we suggest to adopt one of the following solutions:
Currently, we repeat, there is no "off the shelf" platform for the kind of pedagogics we advocate and covers all your needs. E.g. so far, we do not know yet the full potential of C3MS like PostNuke or Drupal. One major limitation of using C3MS portals seems to be the lack of provision for integration (and in particular data-flow) between applications which are required for more complex Computer Supported Collaborative Learning (CSLS) scenarios. Another limitation concerns management of contents, activities and people over time: How can we efficiently enough "reset" or move some of it so that fresh activities of the same kind can start with an empty slate while keeping past student production available to new students.? Some of these issues can be dealt with by careful planning of module use and naming, as well as differentiated write access permissions. In other words, handling these issues require the same sort of planning that a traditional user-driven educational site does. But certainly, things could be improved and automatized to some degree. We are also aware that C3MS portals are not the answer for more complex CSCL workflow scenarios. However, we think that there is an important need to actively support educational scenarios requiring less complex technology and that can be used for other interesting purposes such as community building.
Portalware as candidates to support educational scenarios can be categorized in 5 main classes