<html>
<head>
<title>
DL94: Putting Digital Libraries to Work: Issues from Experience with Community Memories
</title>
</head>

<body>

<!--#include virtual="/DL94/header.ihtml" -->

<h1>Putting Digital Libraries to Work: Issues from Experience with Community Memories</h1>

<p>
Catherine C. Marshall[1], Frank M. Shipman III[1], and Raymond J. McCall[2]<p>
<i>
[1] Xerox Palo Alto Research Center, 
3333 Coyote Hill Road, Palo Alto, CA 94304, 
(415) 812 - 4732, <br>
{marshall, shipman}@parc.xerox.com<p>

[2] College of Environmental Design &amp; Institute of Cognitive Science, University of Colorado, <br>
Boulder, CO 80309, (303) 492 - 7042, mccall@spot.colorado.edu<p>
</i>
<p>
<p>
<p>
<b><p>
Abstract</b><p>
Community memory can provide the crucial bridge between large-scale digital
libraries and the day-to-day activities of a community's members. Just as a
digital library is based on a general structure and conventional means of
access to diverse collections of materials, a community memory culls and shapes
the structure of this collection to meet more particular needs; it provides a
unique perspective on a larger, more general collection. Useful and usable
community memories require support for: (1) the acquisition and evolution of
content and structure; (2) the maintenance of mutually intelligible
organizations; and (3) the identification of relevant materials. In this paper,
we explore issues related to these three requirements based on our experiences
with the development and use of shared hypermedia information resources.<p>
<b><p>
Keywords</b>: Community memory, hypermedia, digital libraries, collaboration,
shared understanding.<b><p>
<p>
<p>
<p>
1. Introduction</b><p>
In principle, digital libraries will provide physically distributed communities
access to a broad spectrum of archival materials, including those that we
currently find in public, community, and work group repositories. But how will
these communities bring these ever-increasing electronic resources to bear on
their work? How will people use digital libraries in their day-to-day
activities? How will they apply these emerging collections to
information-intensive intellectual tasks -- research, design, education,
analysis -- work that requires information to be gathered, understood, and
communicated to others?<p>
Community memories will form the vital link between digital library collections
and the work in which they are used. Just as a digital library provides a
general structure and means of access to a collection of materials, a community
memory culls and shapes the structure of this collection to meet particular
needs; it provides a unique perspective on the collection.<p>
When people work together -- whether in designing a product, or creating
training materials from video-based documentation, or writing a coherent
analysis of a complex situation in the world -- they require, and put effort
into constructing and maintaining, shared understandings of what they are
doing: the task, the pertinent body of material, preliminary findings,
progress, and methods. We refer to the open-ended set of shared interpretations
and understandings developed and maintained by the group as community memory.<p>
<br>
<img src="figures/marshall.gif"><p>
Figure 1. Digital Libraries in use, forming community memory.<p>
<p>
Figure 1 illustrates our conceptualization of community memory. Materials are
drawn from many repositories, some archival, some transient (like news wires,
email, and other semi-ephemeral forms) and, through discourse and interaction,
combined with artifacts relating to the task at hand to form shared
understandings that are community memory. Shared understandings in turn become
the basis for communication and further work.<p>
We can already see community memory at work in on-line communities. Beyond
providing access to distributed computing resources and remote information, the
Internet is also an effective vehicle for human-human communication and the
means of forming communities and transient collections of materials around a
task or topic. These collaborations, and their associated community memory,
have the capacity to greatly extend the reach of the individual.<p>
For example, researchers at different sites have met on-line to organize a
conference; they have discussed individual papers, the program, and decisions
about conference content while referring to the body of submissions, and
implicitly, to the body of literature in the field. In effect, through their
conversations, they have formed a shared understanding about the current state
of the field. In other cases, a topic (rather than a task) helps maintain a
community: for example, high-energy physicists exchange preprints through the
World-Wide Web as a way of shortening the review and publication cycle. NSF
Collaboratory projects acknowledge the feasibility of distributed communities
in information-rich domains collaborating on line.<p>
Community memory is part of a continuum of progressively more specialized
resources. The Library of Congress holds a broader spectrum of materials than a
single university library. That library in turn is more general than a
departmental library. This progression can continue to the level of research
groups, or even to a single, well-stocked office bookshelf. As part of this
continuum, community memories help convey the <i>context</i> in which materials
have been gathered and used -- for example, search results become far more
pointed.<p>
Community memory is thus a linchpin to the effective performance of
intellectual work. But our past experiences building systems to support the
elicitation and reuse of community memory and experiences with network-wide
collaborations have shown us that there are significant barriers to realizing a
fully articulated, well organized, usable electronic community memory.<p>
Building useful and usable memories for distributed communities presents
fundamental challenges [26, 2]. Although it appears to be easy to amass the
kinds of materials that are part of a community memory -- for example,
electronic mail, culled, annotated library materials, "war stories" about how
prototypical problems were solved in past situations, software that embodies a
particular way of processing digital library information, or videotapes
documenting an activity -- it is still problematic how to put these materials
to productive use over time.<p>
Community memories need to be seeded, maintained, and generalized; they need to
reflect the evolution of shared understanding. Members of the community must be
mutually aware of each other's contributions, and the contributions must be
mutually intelligible. Effective community memories cannot exist in isolation
either from the tasks at hand or the information resources they refer to.
Finally, and most crucially, they have to be useful to the members of the
community: they must contribute directly to the work activities.<b><p>
<p>
2. Community Memory: Issues of Acquisition, Comprehension, and Location</b><p>
We are looking at community memory as a shared interpretive layer on top of
sifted subcollections that refer to materials taken from both within and
outside of digital libraries. To provide technological support for community
memory, we must examine the situations from which it arises, and the challenges
associated with our collective set of experiences designing systems to support
community memory.<p>
How do people use community memory as a resource for performing intellectual
work? First, they find the materials they need for their work (many times by
consulting colleagues, assistants, librarians, experts, and other human
resources); they read or otherwise apprehend portions of materials they've
gathered; finally, they modify these materials to suit the purposes at hand,
where modification may include synthesis of diverse sources, paraphrasing,
quoting outright, or using the gathered information as a taking-off point.
Thus, to perform information-intensive intellectual work, a member of a
community will act in many different roles: as searcher, as reader, as
contributor.<p>
We will take each of these roles as a separate vantage point, and examine the
issues and challenges raised by each.<b><p>
<p>
2.1. Acquiring Information: Contributor's Perspective</b><p>
Although it is easy to amass materials for community memory, it is difficult to
provide the incentive to add the requisite organization that will make the
shared resource useful to others [16, 3, 4]. In general, this difficulty is
intrinsic to certain types of groupware: contributors' efforts may far outweigh
the benefits they derive from the work [7]. Many existing efforts to provide
group memory or support long-term community-wide discussion have found that
without an individual's single-minded devotion to starting them and keeping
them going, the information space slowly dies and becomes irrelevant, even to
its originators. It is difficult to ensure real, continuing participation as
well as casual browsing.<p>
The difficulties of acquiring community memory are exacerbated by both
technological and social factors. First, contributors often don't derive
benefits commensurate with the amount of effort they expend: there is a large
gap between the collected materials they've used in their work (their files,
for example) and materials that have been organized so that others may
profitably use them. Not only does the structure of these materials arise over
time and in conjunction with particular tasks, but any additional structure
brings with it a considerable amount of overhead [19]. Second, as a changing,
evolving form, the community memory requires continuing thoughtful maintenance
to weed out growing inconsistencies and redundant contributions. Finally,
community memory arises out of tasks that take place in a distributed,
heterogeneous environment, one that involves paper as well as digital media
(see for example the description of analytic work in [9]), multiple authoring
tools, and many different collections of source material, retrieved from a
multiplicity of information services, each with its own formats, access
methods, and protocols; this blend of materials, media, and technology presents
significant obstacles to the construction of a side-product like community
memory.<p>
<b><p>
2.1.1. Emerging structure and incremental formalization.</b><p>
Through our work with tools like Aquanet, VIKI, and HOS, we have shown that the
groupware cost/benefit paradox [7] may be amenable to solutions like tools to
support the gradual emergence and evolution of structure and techniques to
support incremental formalization [14, 13, 23]. These tools and techniques
emphasize low-cost means of adding the kinds of structure that may organize
information from a digital library into a community memory.<p>
Aquanet [12] is a good example of a group tool that suffered from the
cost/benefit paradox. One of Aquanet's principle roles was to act as a
collaborative front-end for the exploratory manipulation and organization of
large collections of documents relevant to a particular task; in particular, we
had hoped people would work together to create large, tightly interlinked
structures of argumentation and evidence in the course of performing long-term
analyses. These structures would encourage people to develop multiple
interpretations of large collections of always-changing, possibly conflicting
materials and would form a shared interpretive layer over institutional
databases and commercial information services.<p>
Aquanet provided specific support for users to create and manipulate complex
graphical knowledge structures. In our original conception of the knowledge
structuring task, users would define graphical representations of the elements
in their problem domain and specify the ways in which these elements could be
interconnected. Users could then apply and change these structuring schemes
over the course of their tasks. Thus Aquanet provided a flexible way for people
to record the abstractions they use to interpret information, to reflect and
critique their analytic frameworks, and to explicitly negotiate about how
information is structured.<p>
But we did not anticipate the degree to which people found the definition of
such meta-schematic structures difficult. Not only were we requiring users to
categorize materials in their domain according to a schema when they brought
these materials into the tool; we were also requiring that they define the
structuring schema itself before they embarked on their tasks (although the
schemas could subsequently be modified).<p>
From observing Aquanet in use, we found that informal representations are
crucial to coaxing out partially formed, emerging interpretations. One of
Aquanet's unexpected strengths was the ability it gave people to express
interpretations -- interpretations that were less than fully formed -- in terms
of visual appearance or spatial positioning. Extra-linguistic means of
expression proved to be vital, allowing categories to be created without labels
and relationships between documents to be expressed visually. The kinesthetic
process of "trying things out" (as one might do wiggling molecular models in
space or moving a jigsaw puzzle piece into different orientations) was not
eliminated because a person was using a computer instead of manipulable paper
objects in the world.<p>
Out of our experiences with Aquanet, we designed VIKI, a tool to support
emergent, dynamic, exploratory interpretation [13]. VIKI supports the ad hoc
use of a visual symbol language so people can see and express structure as it
becomes apparent to them. In contrast with Aquanet, developing this language is
well-integrated with the task at hand. Because interpretation -- along with the
concommitant act of organizing materials -- is opportunistic, users are not
confined to a particular working style; they may work from gathered examples to
develop structure, they can work schematically (the mode Aquanet enforced), or
they may leave structure and meaning largely implicit.   Thus, in VIKI, we
complement the ability to develop abstraction and reflect on and critique
interpretive frameworks with the flexibility offered by ad hoc, visually
salient representations. We see support for emergent structure as a partial
solution to the cost/benefit paradox inherent in computer support for community
memory.<p>
Structure helps keep community memories intelligible to the members of the
community. Formal structure is also computationally tractable, raising the
possibility of computer support for the community's activities. With the
Hyper-Object Substrate (HOS), we have investigated the process of incremental
formalization to support the emergence of structure. To this end, HOS
integrates hypermedia and knowledge-based representations. Hypermedia
eliminates many of the cognitive costs of formalization that inhibit user
input. Integration with a formal knowledge representation reduces the burden of
formalization by allowing it to be distributed and making it demand-driven
[23].<p>
To further lower the cost of formalizing information, HOS actively supports
incremental formalization with mechanisms to recognize emergent structure
implicit in the community memory and suggest formalizations based on this
structure. Experience with the use of HOS indicates some success and a greater
potential for investigation of both methods for producing and interfaces to
suggesting possible formalizations.<b><p>
<p>
2.1.2. Maintenance of memory: seeding, evolutionary growth, and reseeding</b><p>
We have observed three major types of processes -- and stages -- in the life
cycle of community memories: seeding, evolutionary growth and reseeding.
Seeding is the creation of the initial body of information in community memory.
When this initial set of information reaches a certain size and level of
relevance to the community, it starts to grow and evolve spontaneously as the
result of additions made by its users. Seeding ends with the start of this
evolutionary growth. After this growth proceeds for some time, the memory
starts to become less and less useful; as a consequence, both use and growth
may diminish. This happens for a number of reasons, such as growing disorder in
the memory and the "needle in the haystack" problem -- i.e., the increasing
difficulty of finding useful information in the growing information collection.
At this point, the community memory must be revised -- i.e., reseeded. Its
information must be organized, winnowed, prioritized and generalized. The
methods for locating things in memory may themselves need to be altered. If
this reseeding is done successfully, the system can start another stage of
evolutionary growth, after which it will in turn need to be reseeded if it is
to continue to serve its users.<p>
We have repeatedly experienced this three-fold process in our attempts to build
community memories, for example, with large Issue-Based Information Systems
(IBIS) structures [16]. Very few IBISs for groups have gotten started without
the dedication of a single person or small core group of people who were
willing to create the seed: i.e., the initial set of issues, positions and
arguments. We have found that attempting to get the IBIS users themselves to
invent -- out of the blue -- relevant issues, answers and arguments is a
frustrating and generally unproductive experience for all concerned. Once there
is some argumentative discussion for users to react to, the situation changes
dramatically. It is easy to get people to react to what others have said, and
the difficulty changes from trying to elicit information to trying to keep up
with the information elicited. In our experience, this change makes it quite
clear when the evolutionary growth stage of an IBIS has begun.<p>
We found that as an issue base grew in size its maintenance became increasingly
difficult and error prone. The result was increasing disorder in the issue
base. We also found that it became increasingly difficult to locate relevant
information. There were also devastating synergies between these two problems.
For example, a given issue would often be raised and stored repeatedly,
typically with slightly different wording. These redundancies were very
difficult to detect, in part because of the difference in wording. The result
was that group discussion became fragmented into parallel discussions. As time
went on the fragmentations grew in number and even compounded themselves --
with branches of the fragmented discussions in turn becoming fragmented. As a
result, the IBIS increasingly ceased to function as a vehicle for group
communication. To restore it to functionality, it was necessary to reseed the
IBIS through a comprehensive edit of the issue base. <p>
We have also observed this three-fold process in the creation and development
of a number of large software systems, such as Symbolic's Genera, Unix and the
X-Windows system. In such systems, after the creation of the initial versions
of the systems (seeding), users developed ad hoc additions to system
functionality and often shared these as a community (evolutionary growth).
These additions were often winnowed, refined, combined and included in later
official versions of the software (reseeding), after which they entered another
stage of ad hoc additions to functionality (evolutionary growth) [5].<p>
<b><p>
2.1.3. Connecting community memories to external information. </b><p>
Monolithic attempts to create community memory are difficult and soon fail
because they are disconnected from the tools and materials people bring from
the task at hand as well as from outside reference materials, including the
outside information they obtain from other people [17, 11].<p>
The assumption implicit in the design of many tools is that communication is a
separate process from the user's main task. An analysis of computer network
designers showed how the logical map, a representation of the design which
shows network device interconnections, acted as the central artifact around
which most communication occurred [18]. In response, XNetwork provides
designers with an integrated view of the design and the discussions about the
design in conjunction with methods for importing electronic mail and bulletin
board discussions into the design space. The need to integrate discussion and
artifact signals a more general need to integrate <i>source</i> information and
<i>produced</i> information.<p>
Just as community memories must be connected with the means of communication
about their content, so must they be connected with the digital library
collections from which they arise. For example, prototypes of the Virtual
Notebook System (VNS) [20, 6] used generic hypermedia to overcome the
difficulty of integrating various sources of biomedical research information.
The VNS was intended as an electronic analog to a researcher's notebook that
could also act as a shared repository of information gathered from early
digital libraries and other on-line sources. Such external information
resources included the National Library of Medicine's Medline database
containing bibliographic and abstract information on articles from medical
journals. Users could connect to the Medline database through a graphical
interface and could easily "paste" interesting information into their hypertext
for later use.<p>
Experience with these early prototypes of the VNS shows the difficulty of
providing the needed connections to a variety of information sources and media.
Besides the connection to Medline, the VNS included interfaces to the
researchers' organizational information resources, i.e. hospital and
departmental information systems, as well as to their research information
resources, such as genome and experimental data databases. As these examples
show, the specific information resources used by a particular community can
differ greatly in scope. The experimental databases were used by only one
research group; the genome database was shared by a number of groups; and the
hospital and departmental information systems were used by most of the staff
within the institutions.<b><p>
<p>
2.2. Comprehension of Community Memory: Reader's Perspective</b><p>
If we examine shared resources from a reader's perspective, two main challenges
emerge. First we must be concerned with the community memory's intelligibility
-- are the materials organized and represented in such a way that they may be
understood not only by the person who contributed them, but also by other
members of the community? Can a community reach the high ground of shared
understanding?<p>
Second, we must be concerned with reusability -- will readers be able to apply
the collected materials to their tasks? Will they be able to reformulate and
generalize materials specific to one task such that the materials are once
again useful from a new perspective? Will members of the community be able to
re-apply schematic structures to organize new material that they've brought to
the task?<p>
<b><p>
2.2.1. Shared understanding</b><p>
Community memory critically rests on idea that any one community member's
contribution to such a shared resource is intelligible to other members of the
community. But how do we ensure intelligibility of material that results from a
task that's not necessarily accessible in time (community memory is usually an
asynchronous form of communication) or place (we assume that digital library
community memory is constructed by a distributed group of contributors)? Our
past efforts have focused on two different tactics to make shared spaces
mutually intelligible: meta-discussions within a space [8, 10] to discuss the
materials it contains and shared representations that structure and organize
the materials [15, 12, 21]. Yet the problem becomes much harder to solve as the
community memory grows in size; rationale for the content and structure of the
shared resource becomes opaque and inaccessible over time.<p>
Realistically, some portion of emerging structure (and structure is continually
emerging) will always be implicit. In systems to support collaborative
intellectual work like NoteCards and VIKI, the strategy to achieve mutual
intelligibility has been to encourage contributors to explicitly record
discussions <i>about</i> the work. <p>
NoteCards is a hypertext-based information-organizing tool originally intended
for individual use, but once a user community emerged, it became apparent that
many tasks people were performing using the tool -- writing papers, managing
projects, collecting and analyzing information -- were in fact group activities
[25]. As a result of this observation, NoteCards developers added facilities to
support collaborative work [8]. Three of the more important facilities were:
History Cards, tailored event-centered record keeping that could be annotated
by collaborators; Guided Tours, a technique that allowed a presentation
structure to be overlaid on a hypertext network; and TableTops, a means of
contextualizing work by allowing a number of cards to be grouped as a visual
composite [27, 10]. <p>
Each of these mechanisms involved a semi-automatic way of recording changes or
state (for example, TableTops recorded which cards were together on the screen,
including scrolling); these recordings were then supplemented by human
annotation to discuss the changes or state. Although VIKI provided no such
mechanisms, such discussions were invariably recorded, and a convention was
established over time about how collaborators communicated their changes to
each other; because state-saving is an intrinsic part of the tool's design,
most annotations covered changes.<p>
By contrast, systems like Aquanet rely on the meta-schematic description to
make contributions self-organizing and self-documenting, thereby rendering them
intelligible to readers. So, if one contributor creates, for example, a claim
as part of an argument, the contribution's type (along with the role it plays
in a community-defined structure) will allow readers to interpret it. This
strategy is based on two important assumptions: (1) people understand the
meaning of the meta-schematic description and use it in a uniform way and (2)
people fully use the schematic structures, and leave little implicit. In
practice, neither of these assumptions has been found to hold. Collaborators
still found themselves discussing the abstractions and how they ought to be
applied. They also left a great deal implicit (including why a particular
element should occupy a particular position in the shared space), thereby
introducing a great deal of ambiguity and inconsistency.<p>
In VIKI, implicit structure of this sort is identified by heuristic recognition
algorithms, making it available for discussion. Specific support for
conversations about recognizable implicit structures may help members of a
community keep their own contributions to the shared resource intelligible.<p>
<b><p>
2.2.2. Situatedness and task specificity</b><p>
From our discussion of acquisition, it is clear we are assuming that
contributions to community memory must be well-connected to the task at hand.
Thus we must call into question the applicability of the material,
representations, and structure that is constructed in service of one
intellectual activity to another. There are two sides to reuse of materials in
community memory: the ability to reuse the materials themselves (through
generalization and reapplication) and the ability to reuse the abstractions
that structure these materials. We look first at techniques for generalizing
the materials themselves.<p>
Generalization is a process in which details are removed and the resulting
information is, in part, abstracted from its original context so that it may be
applied to other situations. Generalizations are created with an expectation of
future use. Different generalizations will be appropriate for different future
situations.<p>
For example, in our experience with network design, the same design can be used
as an example in situations with similar budgetary considerations and in
situations using similar technology [5]. XNetwork, an environment for
supporting collaborative network design, allowed designers to continually add
and remove structure from the representation of the design and to make copies
of the design available as more general examples within the community memory.<p>
Since contributors cannot completely predict the situation of their audience,
it is difficult to know how much background to provide to make their
interpretations and knowledge useful at a later date [1]. As a result, not only
does the knowledge itself need to be generalized; it is also important to
record the context in which the materials constituting community memory were
created.<p>
We now turn our attention to the abstractions used to structure the materials
-- the meta-schematic descriptions of domains of interest. One of the original
motivations for providing this kind of abstraction is the ability to reapply it
to interpret related materials. We found this kind of reuse may be difficult to
support with tools that do not acknowledge the fluidity of abstraction, since
the structures people define are based on an idealization of the task and of
the materials and may not fit well with the contingencies of the actual
situation [24, 22].<p>
For example, in our experiences performing a long term analysis task that
involved assessing machine translation systems (see [14]), we found that the
abstract types that highlighted certain appropriate aspects of the systems
(like the approach they took to translation of natural language) were not
entirely appropriate for a seemingly similar task of identifying candidate
Spanish-English translation software for purchase. The new task required that
aspects like cost and hardware platform be made perspicuous. In general, fixed
representations of domain structure tend to cause material that doesn't quite
fit into the abstractions to get lost, to drop from sight. This problem with
the application of abstractions would surely be amplified as a community memory
grew and encompassed more materials and more related tasks.<p>
We addressed this problem in VIKI by assuming that representations are fluid,
lightweight, and locally-defined for the task. In the case of a community
memory, interpretive abstractions would need to part of a view of the
underlying materials rather than a property of the materials themselves.<b><p>
<p>
2.3. Locating Information in a Community Memory: Searcher's Perspective</b><p>
At first it might seem that the problem of locating information in community
memory is exactly analogous to locating material in a larger digital library --
a classic problem of information retrieval, and thus amenable to treatment by
well-understood information retrieval techniques. While this is certainly true
in part, there are a number of respects in which the retrieval issue is largely
and fundamentally different for electronic communities. One is the need for
active recovery of relevant information. The other has to do with the way in
which the community mediates retrieval, even the retrieval of information from
community memory.<p>
<b><p>
2.3.1. Active recovery of relevant material from community memory.</b><p>
One of the biggest problems with shared, collaboratively-constructed resources
like community memory is that members of the community are often unaware of
when there is some critical piece of information (either represented in
electronic form or in another community member's purview) that is critical to
their task. With many people contributing to a community memory, knowledge of
the overall contents is necessarily distributed. It is apparent from looking at
how community memories grow that a central obstacle to their success is "not
knowing what you don't know." This means that no matter how capable a retrieval
mechanism is, the user has to know to ask for information to receive it. To
facilitate the location of information relevant to the task at hand we have
developed a variety of active mechanisms to provide the user with information
without their explicitly asking for it.<p>
The JANUS system supporting design uses the relationships between
domain-oriented construction kits and a domain-oriented issue base to integrate
argumentative information into the task of constructing solution form [4].
JANUS employs knowledge-based critics that "look over the designer's shoulder"
and critique partially constructed solutions, pointing out potential
inadequacies and providing relevant rationale from a domain-oriented issue
base.<p>
XNetwork demonstrates how current collaborative practices by network designers
can be supported through a combination of passive and active mechanisms in
conjunction with an on-line community memory. XNetwork includes a
generalization of the critic mechanism of JANUS to support the recovery of
relevant information from a community memory. Similar to JANUS's critics,
XNetwork's agents volunteer information or take some action based on the user's
current actions. XNetwork agents can be created by users to act as proponents
of certain information and opinions. In this case, agents act as surrogates for
users, advertising the existence of information deemed important. In this way
the agents support communication among the members of a community.<p>
<b><p>
2.3.2. Querying for information.</b><p>
There are, of course, many instances where community members feel a need for
information and set out to retrieve it. Perhaps the central point about
retrieval in electronic communities is that informed people are the best
sources of information. Community memory can serve two crucial functions in
helping people to find information. First of all, it can serve as a cache for
that information, thus reducing the difficulty of search. Secondly, it can
serve as a means for identifying community members who either know the
information or can help in locating it.<p>
Community memory might consist in large part of explicit records of the
knowledge of the individuals in the community. This knowledge can be stored in
a number of ways, perhaps the most basic of which is frequently asked questions
(FAQs). In fact, an IBIS on recurring issues can be seen as nothing more than a
souped-up FAQ collection.<p>
As research on IBIS hypermedia has shown, the problem of retrieving issues is
by no means merely a conventional information retrieval problem. Above all, it
requires more than retrieval by content or bibliographic reference. Retrieval
of relevant information in complex question-based discussions is decisively
aided by associative indexing -- i.e., indexing by the relationships among
questions [17]. For one thing, answering a query (question/issue) might be
aided by the answers given to similar queries. The answer might also depend on
the answers given to other queries. Such similarity and dependency
relationships are also valuable information that can aid retrieval.<p>
Most of the knowledge of community members is not and cannot be stored in
community memory. Even so, a community memory can still be a decisive aid to
retrieval of such knowledge if it can guide the question-asker to the community
member who has the knowledge. There are at least two ways in which community
memory can be of help in this situation. One is by storing the questions that
its members want answered, so that other members can become aware of these
information needs. The other is by storing information about the types of
knowledge possessed by its various members--i.e., who knows what types of
things. Community members may themselves be the best guide for finding other
knowledgeable community members.<b><p>
<p>
3. Conclusions</b><p>
Community memory is the set of shared materials, understandings, and
conventions that emerge within a community; it culls and brings context and
perspective to digital library materials. It is a critical element in the
evolving picture of what it means to bring digital libraries into a work
setting.<p>
In this paper, we have discussed issues from three different perspectives:<p>
<p>
 *	How community memory is acquired from contributors<p>
<p>
 *	How community memory is understood by its diverse members<p>
<p>
 *	How people locate the information they need in a community memory<p>
<p>
We use our experiences to illustrate how community memories are begun, grow,
and are re-used, and the issues and problems intrinsic in developing technology
to support them.<b><p>
<p>
<p>
References</b><p>
[1]	Ackerman, M.S. Definitional and Contextual Issues in Organizational and
Group Memories. In <i>Proceedings of the Twenty-seventh Hawaii International
Conference on System Sciences (HICSS'94)</i> 1994.<p>
<p>
[2]	Berlin, L., Jeffries, R., O'Day, V.L., Paepcke, A., Wharton, C. "Where Did
You Put It? Issues in the Design and Use of a Group Memory," <i>Proceedings of
InterCHI '93</i>, (Amsterdam, The Netherlands, Apr. 24-29). 1993, pp. 23-30.<p>
<p>
[3]	Conklin, E.J., and Yakemovic, K.C. A Process-Oriented Approach to Design
Rationale. <i>Human Computer Interaction</i> 6, 3-4 (1991), pp. 357-391.<p>
<p>
[4]	Fischer, G., Lemke, A., McCall, R., and Morch, A. Making Argumentation
Serve Design. <i>Human Computer Interaction</i>  6, 3-4 (1991), pp. 393-419. <p>
<p>
[5]	Fischer, G., McCall, R., Ostwald J., Reeves, B., and Shipman, F. "Seeding,
Evolutionary Growth, and Reseeding: Supporting the Incremental Development of
Design Environments", <i>Proceedings of CHI '94</i>,  (Boston, Mass.) 1994, pp.
292-298.<p>
<p>
[6]	Gorry, G.A., Burger, A., Chaney, J., Long, K., and Tausk, C. Computer
Support for Biomedical Research Groups. In <i>Proceedings of the Conference on
Computer-Supported Cooperative Work (CSCW'88)</i> (Portland, Oregon, Sept.
26-28). ACM, New York, 1988, pp. 39-51.<p>
<p>
[7]	Grudin, J. Why CSCW Applications Fail: Problems in the Design and
Evaluation of Organizational Interfaces. In <i>Proceedings of the Conference on
Computer-Supported Cooperative Work (CSCW'88)</i> (Portland, Oregon, Sept.
26-28). ACM, New York, 1988, pp. 85-93.<p>
<p>
[8]	Irish, P.M., Trigg, R.H. "Supporting Collaboration in Hypermedia: Issues
and Experiences," <i>Journal of the American Society for Information
Science</i>, March, 1989.<p>
<p>
[9]	Levy, D. and Marshall C.C., "What Color was George Washington's White
Horse? A Look at the Assumptions Underlying Digital Libraries," <i>Proceedings
of Digital Libaries '94</i>, (College Station, Texas, June 19-21). 1994.<p>
<p>
[10]	Marshall C.C. and Irish P., "Guided Tours and On-Line Presentations: How
Authors Make Existing Hypertext Intelligible for Readers," <i>Hypertext '89
Proceedings,</i> (Pittsburgh, Penn., Nov. 5-8). 1989.<p>
<p>
[11]	Marshall, C.C. Work Practice Study: Analysts and Notetaking. Xerox Palo
Alto Research Center, 3333 Coyote Hill Road, Palo Alto, CA 94304.<p>
<p>
[12]	Marshall, C.C., Halasz, F., Rogers, R., and Janssen, W. Aquanet: a
hypertext tool to hold your knowledge in place. In <i>Proceedings of Hypertext
'91</i> (San Antonio, Texas, Dec. 15-18). ACM, New York, 1991, pp. 261-275.<p>
<p>
[13]	Marshall, C.C., Shipman, F.M., Coombs, J.H., VIKI: Spatial Hypertext
Supporting Emergent Structure. Submitted to 1994 European Conference on
Hypermedia Technologies (Edinburgh, Scottland, Sept. 18-23). 1994.<p>
<p>
[14]	Marshall, C.C., and Rogers, R.A. Two Years before the Mist: Experiences
with Aquanet. In <i>Proceedings of European Conference on Hypertext (ECHT
'92)</i> (Milano, Italy, Dec. 1992). pp. 53-62.<p>
<p>
[15]	McCall, R.  "On the structure and use of issue systems in design,"
Doctoral Dissertation (1978) University of California, Berkeley, University
Microfilms(1979).<p>
<p>
[16]	McCall, R., Schaab, B., and Schuler, W. An Information Station for the
Problem Solver: System Concepts. In <i>Applications of Mini- and Microcomputers
in Information, Documentation and Libraries</i>, C. Keren, L. Perlmutter, Eds.
New York: Elsevier, 1983.<p>
<p>
[17]	McCall, R., Bennett, P., d'Oronzio, P., Ostwald, J., Shipman, F., and
Wallace, N. PHIDIAS: Integrating CAD Graphics into Dynamic Hypertext. In
<i>Proceedings of the European Conference on Hypertext (ECHT'90)</i> (Paris,
France, Nov.). 1990, pp. 152-165.<p>
<p>
[18]	Reeves, B.N., and Shipman, F.M. Supporting Communication between Designers
with Artifact-Centered Evolving Information Spaces. In <i>Proceedings of the
Conference on Computer Supported Cooperative Work (CSCW '92)</i> (Toronto,
Canada, Oct. 31-Nov. 4). ACM, New York, 1992, pp. 394-401.<p>
<p>
[19]	Russell, D.M., Stefik, M.J., Pirollli, P., and Card, S.K. The Cost
Structure of Sensemaking. <i>Proceedings of InterCHI '93</i> (Amsterdam,
Netherlands). 1993, pp. 269-276.<p>
<p>
[20]	Shipman, F.M., Chaney, R.J., and Gorry, G.A. Distributed Hypertext for
Collaborative Research: The Virtual Notebook System. In <i>Proceedings of
Hypertext '89</i> (Pittsburgh, Penn., Nov. 5-8). ACM, New York, 1989, pp.
129-135.<p>
<p>
[21]	Shipman, F.M. Supporting Knowledge-Base Evolution with Incremental
Formalization. Technical Report CU-CS-658-93, Department of Computer Science,
University of Colorado, Boulder, 1993.<p>
<p>
[22]	Shipman, F.M., and Marshall, C.C. Formality Considered Harmful:
Experiences, Emerging Themes, and Directions. Technical Report CU-CS-648-93,
Department of Computer Science, University of Colorado, Boulder, 1993.<p>
<p>
[23]	Shipman, F.M., and McCall, R. Supporting Knowledge-Base Evolution with
Incremental Formalization. In <i>Proceedings of CHI'94</i> (Boston, Mass., Apr.
24-28). 1994, pp. 285-291.<p>
<p>
[24]	Suchman, L.A. <i>Plans and Situated Actions: The problem of human-machine
communication</i>. Cambridge University Press, Cambridge, UK, 1987.<p>
<p>
[25]	Suchman, L., R. Trigg, and F. Halasz.  Supporting Collaboration in
NoteCards.  In D. Marca and G. Bock (Eds.) <i>Groupware: Software for
Computer-Supported Cooperative Work</i>, Los Alamitos, CA: IEEE Computer
Society Press, 1992; pp. 394-403.  (First published in Proceedings of the First
Conference on Computer-Supported Cooperative Work, Dec. 1986, pp. 153-162.)<p>
<p>
[26]	Terveen, L., Selfridge, P.G., Long, M. D. "From 'Folklore' to 'Living
Design Memory'" <i>Proceedings of InterCHI '93</i>, Amsterdam, The Netherlands,
(24-29 April 1993), pp. 15-22.<p>
<p>
[27]	Trigg, R. "Guided Tours and Tabletops: Tools for Communicating in a
Hypertext Environment." <i>CSCW '88 Proceedings</i>, Portland, Oregon,
(September 26-28, 1988), pp. 216-226.<p>
<p>
<!--#include virtual="/DL94/footer.ihtml" -->
</body></html>