Platform-wide Issues

From [[http://cpsquare.org CPsquare]], the community of practice on communities of practice.

Jump to: navigation, search
... part of the technology for communities project,
started off by the authors of [Digital Habitats], Etienne Wenger, Nancy White, and John D. Smith.

Contents

Definition

(system-wide?) Peer-to-peer versus centralized platforms.

Uses in communities of practice

Whether decided by the community in a collective fashion, these features affect the life.

Polarities

  • Together/apart, Synch/Asynch:
  • Interaction/publication:
  • Individual/group:

Key features

  • Automatic translation Text is automatically translated into another language.
    • Helps multi-lingual communities have access to a larger proportion of the potential conversation.
  • Web based easy creation. Wizard so non technical person can set up and manage a list.
    • Although email lists are seen as simple by participants and have low bandwidth requirements, most email list programs are sophisticated and complex. An inexperienced user is likely to have some difficulty translating from technical choices to the desired affordances for participation. Tools that make those decisions easy to understand, easy to make and easy to change are very helpful.
  • Ability to upload/download subscriber data (import/export) Bulk subscribe features, save copies of member database, integrate with other systems. Typically through standard file formats.
    • A list owner needs to be sure that some portability is available, should the list software or the list host change policies such that the list needs to move.
  • Spell Checker (1)
    • Normally, spelling errors and so on are not eliminated from the recording at the time of the meeting - using flip charts for example. By adding spell checking, the meeting content can immediately be made production ready and posted immediately to a web site or sent by email to support high quality outreach.
  • Easy to set-up, anyone can use Tool is accessible technically and functionally
    • Distributed control is important and helps promote a sense of egalitarian involvement and contribution.
  • Archiving on website Allows reading of and searching through past announcements, newsletters, or outdated discussions.
    • Important when content has longer "shelf life" or when there are frequent new members joining the community. The archives can provide a history/background for new members.
  • Common Look (3, 5) A look that is used across all pages is used first on the main page.
    • Although variety can be meaningful and enjoyable, there is a cost when users have to re-orient to a different "look".
  • Pure HTML versus heavy client

Related material

Personal tools