Search (5 results, page 1 of 1)

0.021210661 = product of:
  0.042421322 = sum of:
    0.042421322 = product of:
      0.084842645 = sum of:
        0.084842645 = weight(_text_:22 in 1808) [ClassicSimilarity], result of:
          0.084842645 = score(doc=1808,freq=2.0), product of:
            0.1827397 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052184064 = queryNorm
            0.46428138 = fieldWeight in 1808, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=1808)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

17. 9.2018 18:19:22

0.018862877 = product of:
  0.037725754 = sum of:
    0.037725754 = product of:
      0.07545151 = sum of:
        0.07545151 = weight(_text_:systems in 5988) [ClassicSimilarity], result of:
          0.07545151 = score(doc=5988,freq=6.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.4704818 = fieldWeight in 5988, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0625 = fieldNorm(doc=5988)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The library technology industry, broadly speaking, shows more affinity toward utility than innovation. Library automation systems are not necessarily exciting technologies, but they are workhorse applications that must support the complex tasks of acquiring, describing, and providing access to materials and services. They represent substantial investments, and their effectiveness is tested daily in the library. But more than efficiency is at stake: These products must be aligned with the priorities of the library relative to collection management, service provision, and other functions.

Source

https://americanlibrariesmagazine.org/2019/05/01/library-systems-report-2019/

0.010605331 = product of:
  0.021210661 = sum of:
    0.021210661 = product of:
      0.042421322 = sum of:
        0.042421322 = weight(_text_:22 in 5583) [ClassicSimilarity], result of:
          0.042421322 = score(doc=5583,freq=2.0), product of:
            0.1827397 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052184064 = queryNorm
            0.23214069 = fieldWeight in 5583, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=5583)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

11.12.2019 17:47:22

0.008167865 = product of:
  0.01633573 = sum of:
    0.01633573 = product of:
      0.03267146 = sum of:
        0.03267146 = weight(_text_:systems in 653) [ClassicSimilarity], result of:
          0.03267146 = score(doc=653,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.2037246 = fieldWeight in 653, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.046875 = fieldNorm(doc=653)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Will man sich auf dem weiten Feld der Datenverarbeitung die Entwicklungsstadien der letzten drei Jahrzehnte vergegenwärtigen, ist es hilfreich, mindestens vier Aspekte in den Blick zu nehmen: - Hardware: Industrie, Systeme - Software: Programmierung, Sprachen, Entwicklungssysteme - Software: Konkrete Anwendungsfelder, z.B. Bibliothekswesen - Bestimmte Anwendungssysteme, z.B. allegro-C Am Beispiel des an der UB Braunschweig entstandenen Systems allegro-C, dessen Entwicklung 1980 begann und bis heute andauert, lassen sich die Trends, die Evo- und Revolutionen der 30 Jahre nachverfolgen, und dies wird hier versucht. Die Stationen und Etappen der allegro-Geschichte sind knapp aufgelistet in einer Chronik, die ihrerseits im Kern eine spezialisierte allegro-Datenbank ist. Für die Anfangszeit bis Ende 1994 existiert eine ausführliche Darstellung der Entwicklung von Torsten Ahlers.

0.007700737 = product of:
  0.015401474 = sum of:
    0.015401474 = product of:
      0.030802948 = sum of:
        0.030802948 = weight(_text_:systems in 3971) [ClassicSimilarity], result of:
          0.030802948 = score(doc=3971,freq=4.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.19207339 = fieldWeight in 3971, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.03125 = fieldNorm(doc=3971)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Why we organize our personal digital data the way we do and how design of new PIM systems can help us manage our information more efficiently. Each of us has an ever-growing collection of personal digital data: documents, photographs, PowerPoint presentations, videos, music, emails and texts sent and received. To access any of this, we have to find it. The ease (or difficulty) of finding something depends on how we organize our digital stuff. In this book, personal information management (PIM) experts Ofer Bergman and Steve Whittaker explain why we organize our personal digital data the way we do and how the design of new PIM systems can help us manage our collections more efficiently.