Academia.eduAcademia.edu

Figure from:Knowledge management: problems, promises, realities, and challenges

See full PDFdownloadDownload figure
Figure 6. DynaSites provides several means to integrate the information repository. Term links bidirectionally connect the use of a term and its definition in DynaGloss. Keyword links connect records in sources with definitions in DynaGloss. Author links connect each contribution to the author's persona in the community space. Users create cross links, which connect arbitrary entries or connect an entry to any page on the Web. Integration in DynaSites. We use several strategies to link the information spaces in DynaSites (see Figure 6). Perhaps the most important are the term links, which enable DynaGloss to automatically integrate infor- mation across the entire DynaSites reposi- tory. For example, suppose the term “knowl- edge management” is defined in DynaGloss and appears in entries (shown cross-hatched in Figure 6) of both Forum A and Forum B. A user reading the entry in Forum A would see “knowledge management” represented as alink. Selecting the link would take her to the “knowledge management” entry in Dyna- Gloss, which contains a definition and a list of all uses of the term throughout DynaSites. This list includes a link to the entry in Forum B containing “knowledge management.” By following this link, the user would be likely to find a discussion relevant to Forum A, but possibly expressing a different perspective. The community space holds persona pages for each DynaSites user. Users design per-

Figure 6 DynaSites provides several means to integrate the information repository. Term links bidirectionally connect the use of a term and its definition in DynaGloss. Keyword links connect records in sources with definitions in DynaGloss. Author links connect each contribution to the author's persona in the community space. Users create cross links, which connect arbitrary entries or connect an entry to any page on the Web. Integration in DynaSites. We use several strategies to link the information spaces in DynaSites (see Figure 6). Perhaps the most important are the term links, which enable DynaGloss to automatically integrate infor- mation across the entire DynaSites reposi- tory. For example, suppose the term “knowl- edge management” is defined in DynaGloss and appears in entries (shown cross-hatched in Figure 6) of both Forum A and Forum B. A user reading the entry in Forum A would see “knowledge management” represented as alink. Selecting the link would take her to the “knowledge management” entry in Dyna- Gloss, which contains a definition and a list of all uses of the term throughout DynaSites. This list includes a link to the entry in Forum B containing “knowledge management.” By following this link, the user would be likely to find a discussion relevant to Forum A, but possibly expressing a different perspective. The community space holds persona pages for each DynaSites user. Users design per-

Related Figures (9)

Table 2. Two perspectives on knowledge management.
Table 2. Two perspectives on knowledge management.
In the design perspective, an organizational memory plays two roles. First, it is a source of information to help workers understand the problems they face. Second, itis a receptacle for new information and products created dur- ing work. In traditional KM approaches, knowledge engineers carefully craft a knowl- edge base that will periodically be updated. In a design-based approach, organizational memory is a continuously evolving informa- tion space that is fed directly by the knowl- edge created during work. So, information repositories and organizational memories are Figure 1. Knowledge management as a cyclic process.
In the design perspective, an organizational memory plays two roles. First, it is a source of information to help workers understand the problems they face. Second, itis a receptacle for new information and products created dur- ing work. In traditional KM approaches, knowledge engineers carefully craft a knowl- edge base that will periodically be updated. In a design-based approach, organizational memory is a continuously evolving informa- tion space that is fed directly by the knowl- edge created during work. So, information repositories and organizational memories are Figure 1. Knowledge management as a cyclic process.
Figure 2. Two help desk scenarios: (a) broadcasting decontextualized information can cause information overload; (b) access to contextualized information supports learning on demand.
Figure 2. Two help desk scenarios: (a) broadcasting decontextualized information can cause information overload; (b) access to contextualized information supports learning on demand.
Table 4. Comparison of information access and delivery approaches.
Table 4. Comparison of information access and delivery approaches.
Table 5. Our conceptual contributions and prototype systems.
Table 5. Our conceptual contributions and prototype systems.
Figure 3. A Domain-Oriented Design Environment for designing local area network: (a-b) the construction worksheet; (c) the specification component; (d) the group memory; (e) the catalog.
Figure 3. A Domain-Oriented Design Environment for designing local area network: (a-b) the construction worksheet; (c) the specification component; (d) the group memory; (e) the catalog.
Figure 4. The Envisionment and Discovery Collaboratory. In the action space (foreground), stakeholders use physical objects to interact with an underlying computational simulation environment. In the reflection space (background), stakeholders access information, fill out surveys, and add new information.
Figure 4. The Envisionment and Discovery Collaboratory. In the action space (foreground), stakeholders use physical objects to interact with an underlying computational simulation environment. In the reflection space (background), stakeholders access information, fill out surveys, and add new information.