Search (4 results, page 1 of 1)

0.0108685335 = product of:
  0.021737067 = sum of:
    0.021737067 = product of:
      0.043474134 = sum of:
        0.043474134 = weight(_text_:libraries in 2540) [ClassicSimilarity], result of:
          0.043474134 = score(doc=2540,freq=2.0), product of:
            0.1711139 = queryWeight, product of:
              3.2850544 = idf(docFreq=4499, maxDocs=44218)
              0.052088603 = queryNorm
            0.25406548 = fieldWeight in 2540, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.2850544 = idf(docFreq=4499, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2540)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Purpose - This editorial seeks to examine the definition of a "digital library" to see whether one can be constructed that usefully distinguishes a digital library from other types of electronic resources. Design/methodology/approach - The primary methodology compares definitions from multiple settings, including formal institutional settings, working definitions from articles, and a synthesis created in a seminar at Humboldt University in Berlin. Findings - At this point, digital libraries are evolving too fast for any lasting definition. Definitions that users readily understand are too broad and imprecise, and definitions with more technical precision quickly grow too obscure for common use. Originality/value - A functional definition of a digital library would add clarity to a burgeoning field, especially when trying to evaluate a resource. The student perspective provides a fresh look at the problem.

0.0088216085 = product of:
  0.017643217 = sum of:
    0.017643217 = product of:
      0.035286434 = sum of:
        0.035286434 = weight(_text_:22 in 1935) [ClassicSimilarity], result of:
          0.035286434 = score(doc=1935,freq=2.0), product of:
            0.18240541 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052088603 = queryNorm
            0.19345059 = fieldWeight in 1935, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1935)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 6.2008 13:03:30

0.0088216085 = product of:
  0.017643217 = sum of:
    0.017643217 = product of:
      0.035286434 = sum of:
        0.035286434 = weight(_text_:22 in 3340) [ClassicSimilarity], result of:
          0.035286434 = score(doc=3340,freq=2.0), product of:
            0.18240541 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052088603 = queryNorm
            0.19345059 = fieldWeight in 3340, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3340)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

Journal of the Association for Information Science and Technology. 68(2017) no.1, S.22-35

0.007057287 = product of:
  0.014114574 = sum of:
    0.014114574 = product of:
      0.028229147 = sum of:
        0.028229147 = weight(_text_:22 in 1936) [ClassicSimilarity], result of:
          0.028229147 = score(doc=1936,freq=2.0), product of:
            0.18240541 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052088603 = queryNorm
            0.15476047 = fieldWeight in 1936, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=1936)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 6.2008 13:29:15