23.12.2012 Views

Preface for the Third Edition - Read

Preface for the Third Edition - Read

Preface for the Third Edition - Read

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

7. Systems 321<br />

needed to manage meta-data about <strong>the</strong> knowledge workers that work with <strong>the</strong><br />

KMS, e.g., in directory services. Finally, synchronization services export a portion<br />

of <strong>the</strong> knowledge workspace <strong>for</strong> work offline and (re-)integrate <strong>the</strong> work on knowledge<br />

elements that has been done offline.<br />

Infrastructure services. The personalization, knowledge and integration services<br />

layers toge<strong>the</strong>r can be viewed as a KMS in a narrow sense 517 . These layers are<br />

based on an Intranet infrastructure which provides basic functionality <strong>for</strong> synchronous<br />

and asynchronous communication, <strong>the</strong> sharing of data and documents as well<br />

as <strong>the</strong> management of electronic assets in general and of Web content in particular.<br />

In analogy to data warehousing, extract, trans<strong>for</strong>mation and loading tools provide<br />

access to <strong>the</strong> data and knowledge sources 518 . Fur<strong>the</strong>rmore, inspection services<br />

(viewer) are required <strong>for</strong> heterogeneous data and document <strong>for</strong>mats. Inspection services<br />

support viewing of documents without <strong>the</strong> corresponding application, e.g., a<br />

text document without <strong>the</strong> text processing software that created <strong>the</strong> document.<br />

Data and knowledge sources. The data and knowledge source layer gives some<br />

examples of <strong>the</strong> wide variety of electronic sources <strong>for</strong> data and knowledge which<br />

have to be integrated into <strong>the</strong> KMS or at least accessed through <strong>the</strong> KMS. In addition<br />

to organization-internal sources, such as <strong>the</strong> organization’s transaction processing<br />

systems, data base systems, data warehouses, document management systems,<br />

content management systems, messaging systems and personal (or group)<br />

in<strong>for</strong>mation management systems, many organizations need to include organization-external<br />

sources into <strong>the</strong>ir KMS. There is a huge and growing market <strong>for</strong><br />

external (on-line) data bases. They can be classified e.g., into fact data bases that<br />

contain large collections of data and reference data bases which collect literature<br />

and/or references to literature. Examples <strong>for</strong> some well-known data supply companies<br />

that operate hundreds of data bases are (Mertens/Griese 2002, 20ff): DIALOG<br />

In<strong>for</strong>mation Services, Lockheed In<strong>for</strong>mation System, Predicasts, Reuters, or <strong>the</strong><br />

Statistisches Bundesamt in Germany. Last but not least, <strong>the</strong> Internet, especially <strong>the</strong><br />

WWW and newsgroups, provide abundant material that has to be considered in a<br />

KMS architecture.<br />

In <strong>the</strong> following, <strong>the</strong> functions of a KMS that are required to per<strong>for</strong>m <strong>the</strong>se services<br />

are discussed according to <strong>the</strong> layers shown in Figure B-59. The layers comprising<br />

KMS in a narrow sense - personalization, knowledge services and integration,<br />

are discussed in detail. Due to <strong>the</strong>ir importance as key components of KMS,<br />

<strong>the</strong> four bundles discovery, publication, collaboration and learning that toge<strong>the</strong>r<br />

provide <strong>the</strong> knowledge services are discussed separately.<br />

516. For a description of <strong>the</strong>se dimensions see section 7.5.3 - “Example: Infotop” on<br />

page 349.<br />

517. See section 4.3.2 - “Definition” on page 86.<br />

518. The input part of a data warehouse architecture has been called data acquisition layer,<br />

Gray/Watson 1998, 17 or input layer, Muksch/Behme 1998a, 45.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!