<?xml version="1.0" encoding="UTF-8"?><xml><records><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>6</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Mark S. Ackerman</style></author><author><style face="normal" font="default" size="100%">Christine A Halverson</style></author><author><style face="normal" font="default" size="100%">Erickson, Thomas</style></author><author><style face="normal" font="default" size="100%">Kellogg, Wendy A</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Resources, co-evolution and artifacts: Theory in CSCW</style></title></titles><keywords><keyword><style  face="normal" font="default" size="100%">co-evolution</style></keyword><keyword><style  face="normal" font="default" size="100%">CSCW theory</style></keyword><keyword><style  face="normal" font="default" size="100%">resource</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2007</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">NoFile</style></url></web-urls></urls><publisher><style face="normal" font="default" size="100%">Springer</style></publisher><pub-location><style face="normal" font="default" size="100%">New York</style></pub-location><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;How do software and other technical systems come to be adopted and used?&lt;/p&gt;&lt;p&gt;People use software and other technical systems in many ways, and a considerable amount of time and energy may be spent integrating the functionality of the system with the everyday activities it is intended to support. Understanding how this comes about, and understanding how to design systems so that it happens more easily, is a topic of great interest to the CSCW, IT and IS communities.&lt;/p&gt;&lt;p&gt;Resources, Co-Evolution and Artifacts: Theory in CSCW approaches this problem by looking at resources - artifacts that have come to be used in a particular manner in a given situation - and examining how they get created, adopted, modified, and abandoned. The theoretical and empirical studies in this volume examine issues such as:&lt;/p&gt;&lt;p&gt;- how resources are tailored or otherwise changed as situations change;&lt;/p&gt;&lt;p&gt;- how a resource is maintained and reused within an organization;&lt;/p&gt;&lt;p&gt;- the ways in which the value of a resource comes to be understood;&lt;/p&gt;&lt;p&gt;- the ways in which an artifact is transformed to function more effectively;&lt;/p&gt;&lt;p&gt;- how one might approach the problem of designing a resource de novo.&lt;/p&gt;</style></abstract></record><record><source-app name="Biblio" version="7.x">Drupal-Biblio</source-app><ref-type>47</ref-type><contributors><authors><author><style face="normal" font="default" size="100%">Christine A Halverson</style></author><author><style face="normal" font="default" size="100%">Erickson, Thomas</style></author><author><style face="normal" font="default" size="100%">Mark S. Ackerman</style></author></authors></contributors><titles><title><style face="normal" font="default" size="100%">Behind the Help Desk: Evolution of a Knowledge Management System in a Large Organization</style></title><secondary-title><style face="normal" font="default" size="100%">Proceedings of the 2004 ACM Conference on Computer Supported Cooperative Work (CSCW&#039;04)</style></secondary-title></titles><keywords><keyword><style  face="normal" font="default" size="100%">design approaches</style></keyword><keyword><style  face="normal" font="default" size="100%">distributed cognition</style></keyword><keyword><style  face="normal" font="default" size="100%">ethnography</style></keyword><keyword><style  face="normal" font="default" size="100%">FAQ</style></keyword><keyword><style  face="normal" font="default" size="100%">frequently asked questions</style></keyword><keyword><style  face="normal" font="default" size="100%">help desk</style></keyword></keywords><dates><year><style  face="normal" font="default" size="100%">2004</style></year></dates><urls><web-urls><url><style face="normal" font="default" size="100%">Complete</style></url></web-urls></urls><pages><style face="normal" font="default" size="100%">304–313</style></pages><language><style face="normal" font="default" size="100%">eng</style></language><abstract><style face="normal" font="default" size="100%">&lt;p&gt;This paper examines the way in which a knowledge management system (KMS)-by which we mean the people, processes and software-came into being and evolved in response to a variety of shifting social, technical and organizational pressures. We draw upon data from a two year ethnographic study of a sophisticated help desk to trace the KMS from its initial conception as a &quot;Common Problems&quot; database for help desk personnel, to its current instantiation as a set of Frequently Asked Questions published on an intranet for help desk clients. We note how shifts in management, organizational structure, incentives, software technologies, and other factors affected the development of the system. This study sheds light on some of the difficulties that accompany the implementation of CSCW systems, and provides an analysis of how such systems are often designed by bricolage.&lt;br&gt;&amp;nbsp;&lt;/p&gt;</style></abstract></record></records></xml>