Search (271 results, page 14 of 14)

0.0011038391 = product of:
  0.01324607 = sum of:
    0.01324607 = product of:
      0.02649214 = sum of:
        0.02649214 = weight(_text_:22 in 1709) [ClassicSimilarity], result of:
          0.02649214 = score(doc=1709,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.23214069 = fieldWeight in 1709, 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=1709)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

4. 2.2015 9:22:39

0.0011038391 = product of:
  0.01324607 = sum of:
    0.01324607 = product of:
      0.02649214 = sum of:
        0.02649214 = weight(_text_:22 in 2611) [ClassicSimilarity], result of:
          0.02649214 = score(doc=2611,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.23214069 = fieldWeight in 2611, 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=2611)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

10. 9.2000 17:38:22

0.0010460628 = product of:
  0.012552753 = sum of:
    0.012552753 = weight(_text_:internet in 577) [ClassicSimilarity], result of:
      0.012552753 = score(doc=577,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.1304718 = fieldWeight in 577, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.03125 = fieldNorm(doc=577)
  0.083333336 = coord(1/12)

Theme

Internet

0.0010460628 = product of:
  0.012552753 = sum of:
    0.012552753 = weight(_text_:internet in 3337) [ClassicSimilarity], result of:
      0.012552753 = score(doc=3337,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.1304718 = fieldWeight in 3337, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.03125 = fieldNorm(doc=3337)
  0.083333336 = coord(1/12)

Content

"Die Stadtbibliothek Reutlingen (www.stadtbibliothek-reutlingen.de) hat ihren gesamten Internetauftritt auf den Web-Opac Premium von BOND umgerüstet. Der WebOpac Premium ist weit mehr als ein gewöhnlicher Web-Opac. Vielmehr ist er ein Internet-Por-tal, in dessen Struktur alle Informationen und Angebote der Stadtbibliothek integriert sind. Mit dem Web-Opac Premium konnte die Bibliothek bei der Neugestaltung ihrer Internetseiten auf ein bestehendes und flexibel anpassbares Produkt zurückgreifen, um so Zeit und Arbeit zu sparen. Bestehende HTML-Seiten der alten Homepage wurden einfach in die neue Website übernommen. Zudem erhöhen viele Zusatzfunktionen des Web-Opac Premium die Attraktivität der Bibliothek. Neu ist auch die »Assoziative Suche« (Spider Search), mit der die Bibliotheksbenutzer bei der Mediensuche neue Sinnzusammenhänge erschließen und so ihre Suchergebnisse verbessern können. Für die übersichtliche Gliederung der Website sorgen die horizontale Navigationsleiste nach Abteilungen und Zweigstellen der Stadtbibliothek sowie ein blaues Navigationselement im linken Frame, das sich mit sprechenden Begriffen an alle Benutzer und bestimmte Zielgruppen der Bibliothek wendet. Unter dem Stichwort »Suche« können Leser sowohl nach Inhalten auf der Website als auch über drei Wege nach Medien suchen: über den Web-Opac der Stadtbibliothek, die Assoziative Mediensuche im Katalog der Bibliothek und in regionalen Katalogen, wie denen der Bibliothek der Fachhochschule Reutlingen, der UB oder der Stadtbücherei Tübingen. Der Bereich »Service« bietet viele Informationen zur Bibliothek und deren Benutzung. Unter »Meine Bibliothek« kann der Leser nach der Anmeldung sein Benutzerkonto einsehen, die Leihfrist der entliehenen Medien verlängern und sich sein persönliches Interessenprofil abspeichern. Das heißt der Leser legt gewünschte Stichwörter, Verfasser, Mediengruppen oder Interessenkreise fest und wird regelmäßig zu seinen Wunschthemen informiert. Der Bereich »Veranstaltungen« informiert über die aktuellen Veranstaltungen, untergliedert nach Kinderbibliothek, Hauptstelle und Zweigstellen. Das eingesetzte Veranstaltungsmodul des Web-Opacs Premium übernimmt die automatisierte Aktualisierung der angezeigten Veranstaltungen durch Angabe von Start- und Ablaufdatum."

9.19866E-4 = product of:
  0.011038392 = sum of:
    0.011038392 = product of:
      0.022076784 = sum of:
        0.022076784 = weight(_text_:22 in 1942) [ClassicSimilarity], result of:
          0.022076784 = score(doc=1942,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.19345059 = fieldWeight in 1942, 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=1942)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

22. 6.2008 17:14:24

7.8454707E-4 = product of:
  0.009414565 = sum of:
    0.009414565 = weight(_text_:internet in 1558) [ClassicSimilarity], result of:
      0.009414565 = score(doc=1558,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.09785385 = fieldWeight in 1558, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1558)
  0.083333336 = coord(1/12)

Content

"MOST INTEGRATED library systems, as they are currently configured and used, should be removed from public view. Before I say why, let me be clean that I think the integrated library system serves a very important, albeit limited, role. An integrated library system should serve as a key piece of the infrastructure of a library, handling such tasks as ma terials acquisition, cataloging (including holdings, of course), and circulation. The integrated library system should be a complete and accurate recording of a local library's holdings. It should not be presented to users as the primary system for locating information. It fails badly at that important job. - Lack of content- The central problem of almost any library catalog system is that it typically includes only information about the books and journals held by a parficular library. Most do not provide access to joumal article indexes, web search engines, or even selective web directories like the Librarians' Index to the Internet. If they do offen such access, it is only via links to these services. The library catalog is far from onestop shopping for information. Although we acknowledge that fact to each other, we still treat it as if it were the best place in the universe to begin a search. Most of us give the catalog a place of great prominente an our web pages. But Information for each book is limited to the author, title, and a few subject headings. Seldom can book reviews, jacket summaries, recommendations, or tables of contents be found-or anything at all to help users determine if they want the material. - Lack of coverage - Most catalogs do not allow patrons to discover even all the books that are available to them. If you're lucky, your catalog may cover the collections of those libraries with which you have close ties-such as a regional network. But that leaves out all those items that could be requested via interlibrary loan. As Steve Coffman pointed out in his "Building Earth's Largest Library" article, we must show our users the universe that is open to them, highlight the items most accessible, and provide an estimate of how long it would take to obtain other items. - Inability to increase coverage - Despite some well-meaning attempts to smash everything of interest into the library catalog, the fact remains that most integrated library systems expect MARC records and MARC records only. This means that whatever we want to put into the catalog must be described using MARC and AACR2 (see "Marc Must Die," LJ 10/15/02, p. 26ff.). This is a barrier to dramatically increasing the scope of a catalog system, even if we decided to do it. How would you, for example, use the Open Archives Initiative Harvesting Protocol to crawl the bibliographic records of remote repositories and make them searchable within your library catalog? It can't be dope, and it shouldn't. The library catalog should be a record of a given library's holdings. Period.

7.358928E-4 = product of:
  0.008830713 = sum of:
    0.008830713 = product of:
      0.017661426 = sum of:
        0.017661426 = weight(_text_:22 in 168) [ClassicSimilarity], result of:
          0.017661426 = score(doc=168,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.15476047 = fieldWeight in 168, 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=168)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

10. 9.2000 17:38:22

7.358928E-4 = product of:
  0.008830713 = sum of:
    0.008830713 = product of:
      0.017661426 = sum of:
        0.017661426 = weight(_text_:22 in 520) [ClassicSimilarity], result of:
          0.017661426 = score(doc=520,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.15476047 = fieldWeight in 520, 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=520)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

8. 1.2007 17:22:25

7.358928E-4 = product of:
  0.008830713 = sum of:
    0.008830713 = product of:
      0.017661426 = sum of:
        0.017661426 = weight(_text_:22 in 1936) [ClassicSimilarity], result of:
          0.017661426 = score(doc=1936,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = 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.083333336 = coord(1/12)

Date

22. 6.2008 13:29:15

6.439062E-4 = product of:
  0.007726874 = sum of:
    0.007726874 = product of:
      0.015453748 = sum of:
        0.015453748 = weight(_text_:22 in 2509) [ClassicSimilarity], result of:
          0.015453748 = score(doc=2509,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.1354154 = fieldWeight in 2509, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.02734375 = fieldNorm(doc=2509)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Source

Electronic library. 22(2004) no.2, S.112-120

6.439062E-4 = product of:
  0.007726874 = sum of:
    0.007726874 = product of:
      0.015453748 = sum of:
        0.015453748 = weight(_text_:22 in 3353) [ClassicSimilarity], result of:
          0.015453748 = score(doc=3353,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.1354154 = fieldWeight in 3353, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.02734375 = fieldNorm(doc=3353)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Source

Mitteilungen der Vereinigung Österreichischer Bibliothekarinnen und Bibliothekare. 58(2005) H.1, S.22-37