The Use of 'Community': Knowing Users in the Face of Changing Constituencies

On April 15th, 2008, here at the UMich iSchool, I presented my work on how participants within Cyberinfrastructure projects come to know (and thus constitute) their intended communities.

Click here for a draft of this article to appear in CSCW2008.

Below is the abstact for the talk.

Abstract:

'Community' is one of the most important, yet most variably deployed, terms within contemporary information infrastructure design. I seek to clarify its usage by turning attention to the ways in which it serves as an organizing principle. To do so, I ethnographically traced the activities in the Water and Environmental Research Systems Network (WATERS). WATERS is a large observatory and cyberinfrastructure development project intending to serve heterogeneous scientific disciplines studying the water environment. In 2005 WATERS was forced to reorganize as a new group of hydrological scientists was added to the project. This event initiated a series of discussions about who the infrastructure was intended to serve, and how it would do so.

In WATERS the definition of their communities became a stand-in for debates over design decisions, the allocation of resources, and a future trajectory of scientific research. The use of 'community' by participants in IT development projects is substantially divorced from its traditional meanings which emphasize collective moral orientations or shared affective ties; instead, community is closer in practice to 'constituency,' and is used as a short-hand for issues of (political) representation, inclusion and mandate.