Search (5 results, page 1 of 1)

0.044200905 = product of:
  0.073668174 = sum of:
    0.031490285 = product of:
      0.12596114 = sum of:
        0.12596114 = weight(_text_:editors in 2749) [ClassicSimilarity], result of:
          0.12596114 = score(doc=2749,freq=4.0), product of:
            0.30020764 = queryWeight, product of:
              6.7132807 = idf(docFreq=145, maxDocs=44218)
              0.04471847 = queryNorm
            0.41958004 = fieldWeight in 2749, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              6.7132807 = idf(docFreq=145, maxDocs=44218)
              0.03125 = fieldNorm(doc=2749)
      0.25 = coord(1/4)
    0.021189814 = weight(_text_:u in 2749) [ClassicSimilarity], result of:
      0.021189814 = score(doc=2749,freq=2.0), product of:
        0.14642814 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.04471847 = queryNorm
        0.14471136 = fieldWeight in 2749, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.03125 = fieldNorm(doc=2749)
    0.020988077 = product of:
      0.041976154 = sum of:
        0.041976154 = weight(_text_:22 in 2749) [ClassicSimilarity], result of:
          0.041976154 = score(doc=2749,freq=6.0), product of:
            0.15659647 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04471847 = queryNorm
            0.268053 = fieldWeight in 2749, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=2749)
      0.5 = coord(1/2)
  0.6 = coord(3/5)

Classification

658.4/038 22

Date

22. 3.2009 18:43:51

DDC

658.4/038 22

Editor

Srikantaiah, T.K. u. M.D. Koenig

Footnote

Rez. in: JASIST 60(2006) no.3, S.642 (A.E. Prentice): "What is knowledge management (KM)? How do we define it? How do we use it and what are the benefits? KM is still an operational discipline that has yet to have an academic foundation. Its core has yet to solidify and concepts and practices remain fluid, making it difficult to discuss or even to identify the range of relevant elements. Being aware of this lack of a well-structured retrievable disciplinary literature, the editors made a practice of attending trade shows and conferences attended by KM professionals to look for presentations that would in some way expand knowledge of the field. They asked presenters to turn their paper into a book chapter, which is the major source of the material in this book. Although this is a somewhat chancy method of identifying authors and topics, several of the papers are excellent and a number add to an understanding of KM. Because of the fluidity of the area of study, the editors devised a three-dimensional topic expansion approach to the content so that the reader can follow themes in the papers that would not have been easy to do if one relied solely on the table of contents. The table of contents organizes the presentations into eight subject sections, each section with a foreword that introduces the topic and indicates briefly the contribution of each chapter to the overall section title. Following this, the Roadmap lists 18 topics or themes that appear in the book and relevant chapters where information on the theme can be found. Readers have the choice of following themes using the roadmap or of reading the book section by section. ..."

0.0063569443 = product of:
  0.03178472 = sum of:
    0.03178472 = weight(_text_:u in 3424) [ClassicSimilarity], result of:
      0.03178472 = score(doc=3424,freq=2.0), product of:
        0.14642814 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.04471847 = queryNorm
        0.21706703 = fieldWeight in 3424, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.046875 = fieldNorm(doc=3424)
  0.2 = coord(1/5)

Issue

4., überarb. u. erw.. Aufl.

0.0052974536 = product of:
  0.026487269 = sum of:
    0.026487269 = weight(_text_:u in 485) [ClassicSimilarity], result of:
      0.026487269 = score(doc=485,freq=2.0), product of:
        0.14642814 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.04471847 = queryNorm
        0.1808892 = fieldWeight in 485, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.0390625 = fieldNorm(doc=485)
  0.2 = coord(1/5)

Editor

Hompel, M ten u. H.J. Bullinger

0.0052974536 = product of:
  0.026487269 = sum of:
    0.026487269 = weight(_text_:u in 1554) [ClassicSimilarity], result of:
      0.026487269 = score(doc=1554,freq=2.0), product of:
        0.14642814 = queryWeight, product of:
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.04471847 = queryNorm
        0.1808892 = fieldWeight in 1554, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.2744443 = idf(docFreq=4547, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1554)
  0.2 = coord(1/5)

Editor

Stahl, F. u. W. Maass

0.0032483812 = product of:
  0.016241906 = sum of:
    0.016241906 = weight(_text_:r in 4522) [ClassicSimilarity], result of:
      0.016241906 = score(doc=4522,freq=2.0), product of:
        0.14802969 = queryWeight, product of:
          3.3102584 = idf(docFreq=4387, maxDocs=44218)
          0.04471847 = queryNorm
        0.1097206 = fieldWeight in 4522, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.3102584 = idf(docFreq=4387, maxDocs=44218)
          0.0234375 = fieldNorm(doc=4522)
  0.2 = coord(1/5)

Footnote

Rez. in: ZfBB 58(2011) H.2, S.108 (R. Schneider): "Kürzlich, während eines Vortrags zum Knowledge Management eines der weltweit grössten Wirtschaftsprüfer, überraschte eine Zuhörerin den Vortragenden mit einer simplen Frage: »Brauchen Sie nicht eigentlich Records Management?« Darauf der sichtlich überrumpelte Referent: »Was meinen Sie mit Records Management?« Soviel zum Stand der Dinge und zur Verankerung des Themas in der aktuellen Betriebslandschaft. Insofern trifft es sich gut, dass nach dem lange erwarteten Handbuch zum Records Management nun das Folgewerk mit demselben Haupttitel sowie dem Untertitel Gestaltung und Umsetzung von Peter Toebak erschienen ist. Der ungleich schlankere Band widmet sich - wie es der Untertitel andeutet - der konkreten Realisierung des betrieblichen Aktenmanagements und tut dies vor allen Dingen anhand eines Zehn-Schritte-Plans, der nach einer Einleitung und einer Rekapitulation der Kernproblematik des Records Management im dritten Kapitel vorgestellt und den folgenden vier Kapiteln ausführlich ausgearbeitet und in allen Details extemporiert wird. Die einzelnen Schritte dieses Plans reichen dabei von der Definition der Methodik (1) und der Identifikation des Umfelds (2) über die Identifikation der Prozesskategorien (3) und die Definition der Records-Serien (4) zu den eher applikationsorientierten Arbeitschritten. Diese umfassen nach der Identifikation der Anwendungen (5), die Integration der Systemlandschaft mit dem EDRMS (= Electronic Documentary Records Management System) (6), die Definition weiterer Attribute (7), die Auswahl und Installation des EDRMS (8) sowie die Umsetzung des EDRMS (9) und dessen Evaluation (10).