Search (161 results, page 1 of 9)

0.11521824 = product of:
  0.17282735 = sum of:
    0.13507548 = weight(_text_:title in 3601) [ClassicSimilarity], result of:
      0.13507548 = score(doc=3601,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.49232465 = fieldWeight in 3601, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.0625 = fieldNorm(doc=3601)
    0.037751865 = product of:
      0.07550373 = sum of:
        0.07550373 = weight(_text_:22 in 3601) [ClassicSimilarity], result of:
          0.07550373 = score(doc=3601,freq=4.0), product of:
            0.17248978 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049257044 = queryNorm
            0.4377287 = fieldWeight in 3601, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=3601)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

Explains how 5 Internet search engines (AltaVista, HotBot, InfoSeek, Lycos, and Yahoo) handle field searching. Includes a chart which identifies where on a search engine's page a particular field is searched and the prefix syntax used, and gives examples. Details the individual fields that can be searched: data, title, URL, images, audiovideo and other page content, links and page depth

Source

Online. 22(1998) no.3, S.18-22

0.080885045 = product of:
  0.121327564 = sum of:
    0.10130662 = weight(_text_:title in 4190) [ClassicSimilarity], result of:
      0.10130662 = score(doc=4190,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.3692435 = fieldWeight in 4190, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.046875 = fieldNorm(doc=4190)
    0.020020949 = product of:
      0.040041897 = sum of:
        0.040041897 = weight(_text_:22 in 4190) [ClassicSimilarity], result of:
          0.040041897 = score(doc=4190,freq=2.0), product of:
            0.17248978 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049257044 = queryNorm
            0.23214069 = fieldWeight in 4190, 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=4190)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

Creates an open, metadata aware system for distributed, collaborative WWW indexing. The system has 3 main components: a harvester (for collecting information), a database (for making the collection searchable), and a user interface (for making the information available). all components can be distributed across networked computers, thus supporting scalability. The system is metadata aware and thus allows searches on several fields including title, document author and URL. Nordic Web Index (NWI) is an application using this system to create a regional Nordic Web-indexing service. NWI is built using 5 collaborating service points within the Nordic countries. The NWI databases can be used to build additional services

Date

1. 8.1996 22:08:06

0.063675195 = product of:
  0.19102558 = sum of:
    0.19102558 = weight(_text_:title in 1032) [ClassicSimilarity], result of:
      0.19102558 = score(doc=1032,freq=4.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.6962522 = fieldWeight in 1032, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.0625 = fieldNorm(doc=1032)
  0.33333334 = coord(1/3)

Abstract

Content characteristics of a webpage include factors such as keyword position in a webpage, keyword duplication, layout, and their combination. These factors may impact webpage visibility in a search engine. Four hypotheses are presented relating to the impact of selected content characteristics on webpage visibility in search engine results lists. Webpage visibility can be improved by increasing the frequency of keywords in the title, in the full-text and in both the title and full-text.

0.056281447 = product of:
  0.16884434 = sum of:
    0.16884434 = weight(_text_:title in 3279) [ClassicSimilarity], result of:
      0.16884434 = score(doc=3279,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.6154058 = fieldWeight in 3279, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.078125 = fieldNorm(doc=3279)
  0.33333334 = coord(1/3)

Abstract

Sets out the basic approach of search engines. They all rely on relevance ranking. Some offer Booelan searching, the option to insist that a keyword is present, proximity searching, and title searching. Refining searches using these techniques can help make search results more relevant

0.056281447 = product of:
  0.16884434 = sum of:
    0.16884434 = weight(_text_:title in 2106) [ClassicSimilarity], result of:
      0.16884434 = score(doc=2106,freq=8.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.6154058 = fieldWeight in 2106, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2106)
  0.33333334 = coord(1/3)

Abstract

This paper presents a new approach to query expansion in search engines through the use of general non-topical terms (NTTs) and domain-specific semi-topical terms (STTs). NTTs and STTs can be used in conjunction with topical terms (TTs) to improve precision in retrieval results. In Phase I, 20 topical queries in two domains (Health and the Social Sciences) were carried out in Google and from the results of the queries, 800 pages were textually analysed. Of 1442 NTTs and STTs identified, 15% were shared between the two domains; 62% were NTTs and 38% were STTs; and approximately 64% occurred before while 36% occurred after their respective topical terms (TTs). Findings of Phase II showed that query expansion through NTTs (or STTs) particularly in the 'exact title' and URL search options resulted in more precise and manageable results. Statistically significant differences were found between Health and the Social Sciences vis-à-vis keyword and 'exact phrase' search results; however there were no significant differences in exact title and URL search results. The ratio of exact phrase, exact title, and URL search result frequencies to keyword search result frequencies also showed statistically significant differences between the two domains. Our findings suggest that web searching could be greatly enhanced combining NTTs (and STTs) with TTs in an initial query. Additionally, search results would improve if queries are restricted to the exact title or URL search options. Finally, we suggest the development and implementation of knowledge-based lists of NTTs (and STTs) by both general and specialized search engines to aid query expansion.

0.055715796 = product of:
  0.16714738 = sum of:
    0.16714738 = weight(_text_:title in 1027) [ClassicSimilarity], result of:
      0.16714738 = score(doc=1027,freq=4.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.6092207 = fieldWeight in 1027, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1027)
  0.33333334 = coord(1/3)

Abstract

This paper discusses the impact of metadata implementation in a webpage on its visibility performance in a search engine results list. Influential internal and external factors of metadata implementation were identified. How these factors affect webpage visibility in a search engine results list was examined in an experimental study. Findings suggest that metadata is a good mechanism to improve webpage visibility, the metadata subject field plays a more important role than any other metadata field and keywords extracted from the webpage itself, particularly title or full-text, are most effective. To maximize the effects, these keywords should come from both title and full-text.

0.055715796 = product of:
  0.16714738 = sum of:
    0.16714738 = weight(_text_:title in 1033) [ClassicSimilarity], result of:
      0.16714738 = score(doc=1033,freq=4.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.6092207 = fieldWeight in 1033, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1033)
  0.33333334 = coord(1/3)

Abstract

This paper discusses the impact of metadata implementation in a webpage on its visibility performance in a search engine results list. Influential internal and external factors of metadata implementation were identified. How these factors affect webpage visibility in a search engine results list was examined in an experimental study. Findings suggest that metadata is a good mechanism to improve webpage visibility, the metadata subject field plays a more important role than any other metadata field and keywords extracted from the webpage itself, particularly title or full-text, are most effective. To maximize the effects, these keywords should come from both title and full-text.

0.033768874 = product of:
  0.10130662 = sum of:
    0.10130662 = weight(_text_:title in 160) [ClassicSimilarity], result of:
      0.10130662 = score(doc=160,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.3692435 = fieldWeight in 160, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.046875 = fieldNorm(doc=160)
  0.33333334 = coord(1/3)

Abstract

Aims to discover whether known item searches are possible with some of the most popular search engines on the WWW and if the results retrieved using such a search would be satisfactory to users. 4 major search engines (InfoSeek, Excite, AltaVista and Lycos) were tested and compared, using the most sophisticated search techniques available. 39 Web sites were selected and searched by title, and ranked according to the relevance and order of the displayed results. Concludes that these search engines were clearly not designed with known item searches in mind and most users searching the Web are unschooled in the intricacies of database searching and do not know how to construct complex search queries or used advanced searching techniques to the fullest potential. Infoseek Guide was rated the best with Excite and AltaVista also achieving satisfactory results. Lycos A2Z was not ot rated as being well equipped for this type of searching

0.033768874 = product of:
  0.10130662 = sum of:
    0.10130662 = weight(_text_:title in 2411) [ClassicSimilarity], result of:
      0.10130662 = score(doc=2411,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.3692435 = fieldWeight in 2411, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.046875 = fieldNorm(doc=2411)
  0.33333334 = coord(1/3)

Abstract

The scope and characteristics of what may be considered the first three generations of automated Internet indexing systems are identified and described as to their methods of compiling their datasets, their search interfaces and the associated etymological metaphors and mythologies. These three are suggested to be: firstly, the Archie system for single keyword and regular expression searches of the file lists of anonymous ftp sites: secondly, the Veronica system for Boolean keyword in title searches of the world's gopher servers; thirdly, a range of software techniques jnown as robots and search engines, which compile searchable databases of information accessible via the WWW, such as the currently popular Lycos project at Carnegie Mellon University. The present dominance of WWW client software as the preferred interface to Internet information has led to provision of methods of also using the first two systems by this single interface, and these are also noted

0.033768874 = product of:
  0.10130662 = sum of:
    0.10130662 = weight(_text_:title in 3185) [ClassicSimilarity], result of:
      0.10130662 = score(doc=3185,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.3692435 = fieldWeight in 3185, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.046875 = fieldNorm(doc=3185)
  0.33333334 = coord(1/3)

Abstract

With this title, readers learn to push the search engine to its limits and extract the best content from Google, without having to learn complicated code. "Google Power" takes Google users under the hood, and teaches them a wide range of advanced web search techniques, through practical examples. Its content is organised by topic, so reader learns how to conduct in-depth searches on the most popular search topics, from health to government listings to people.

0.033768874 = product of:
  0.10130662 = sum of:
    0.10130662 = weight(_text_:title in 1060) [ClassicSimilarity], result of:
      0.10130662 = score(doc=1060,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.3692435 = fieldWeight in 1060, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.046875 = fieldNorm(doc=1060)
  0.33333334 = coord(1/3)

Abstract

This paper talks about several schemes for improving retrieval effectiveness that can be used in the named page finding tasks of web information retrieval (Overview of the TREC-2002 web track. In: Proceedings of the Eleventh Text Retrieval Conference TREC-2002, NIST Special Publication #500-251, 2003). These methods were applied on top of the basic information retrieval model as additional mechanisms to upgrade the system. Use of the title of web pages was found to be effective. It was confirmed that anchor texts of incoming links was beneficial as suggested in other works. Sentence-query similarity is a new type of information proposed by us and was identified to be the best information to take advantage of. Stratifying and re-ranking the retrieval list based on the maximum count of index terms in common between a sentence and a query resulted in significant improvement of performance. To demonstrate these facts a large-scale web information retrieval system was developed and used for experimentation.

0.026077747 = product of:
  0.07823324 = sum of:
    0.07823324 = product of:
      0.23469973 = sum of:
        0.23469973 = weight(_text_:3a in 2514) [ClassicSimilarity], result of:
          0.23469973 = score(doc=2514,freq=2.0), product of:
            0.41760176 = queryWeight, product of:
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.049257044 = queryNorm
            0.56201804 = fieldWeight in 2514, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              8.478011 = idf(docFreq=24, maxDocs=44218)
              0.046875 = fieldNorm(doc=2514)
      0.33333334 = coord(1/3)
  0.33333334 = coord(1/3)

Content

Vgl.: http%3A%2F%2Fdelab.csd.auth.gr%2F~dimitris%2Fcourses%2Fir_spring06%2Fpage_rank_computing%2Fp527-li.pdf. Vgl. auch: http://www2002.org/CDROM/refereed/643/.

0.023878198 = product of:
  0.07163459 = sum of:
    0.07163459 = weight(_text_:title in 3073) [ClassicSimilarity], result of:
      0.07163459 = score(doc=3073,freq=4.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.26109457 = fieldWeight in 3073, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.0234375 = fieldNorm(doc=3073)
  0.33333334 = coord(1/3)

Content

If Babel symbolized our incommensurate ambition, the Library of Alexandria showed how this Ambition might be achieved. Set up by Ptolemy I in the third century B.C., it was meant to hold every book an every imaginable subject. To ensure that no title escaped its vast catalog. a royal decree ordered that any book brought into the City was to be confiscated and copied; only then would the original (sometimes the copy) be returned. A curious document from the second century B.C., the perhaps apocryphal "Letter of Aristeas," recounts the library's origins. To assemble a universal library (says the letter), King Ptolemy wrote "to all the sovereigns and governors an earth" begging them to send to him every kind of book by every kind of author, "poets and prose writers, rhetoricians and sophists, doctors and soothsayers, historians and all others, too." The king's librarians calculated that they required 500.000 scrolls if they were to collect in Alexandria "all the books of all the peoples of the world." But even this (by our standards) modest stock of a half-million books was too much for any reader. The librarians of Alexandria devised a system of annotated catalogs for which they chose works, they deemed especially important, and appended a brief description to each title - one of the earliest "recommended reading" lists. In Alexandria, it became clear that the greater your ambition, the narrower your scope. But our ambition persists recently, the most popular Internet search service. Google, announced that it had concluded agreements with several leading research libraries to make some of their books available online to researchers.

0.018875934 = product of:
  0.0566278 = sum of:
    0.0566278 = product of:
      0.1132556 = sum of:
        0.1132556 = weight(_text_:22 in 3227) [ClassicSimilarity], result of:
          0.1132556 = score(doc=3227,freq=4.0), product of:
            0.17248978 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049257044 = queryNorm
            0.6565931 = fieldWeight in 3227, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=3227)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

7. 2.1996 22:38:41

Pages

22 S

0.018875934 = product of:
  0.0566278 = sum of:
    0.0566278 = product of:
      0.1132556 = sum of:
        0.1132556 = weight(_text_:22 in 4007) [ClassicSimilarity], result of:
          0.1132556 = score(doc=4007,freq=4.0), product of:
            0.17248978 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049257044 = queryNorm
            0.6565931 = fieldWeight in 4007, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=4007)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

22. 8.1999 20:22:06

0.018875934 = product of:
  0.0566278 = sum of:
    0.0566278 = product of:
      0.1132556 = sum of:
        0.1132556 = weight(_text_:22 in 4009) [ClassicSimilarity], result of:
          0.1132556 = score(doc=4009,freq=4.0), product of:
            0.17248978 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049257044 = queryNorm
            0.6565931 = fieldWeight in 4009, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=4009)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

22. 8.1999 21:22:59

0.0177964 = product of:
  0.053389195 = sum of:
    0.053389195 = product of:
      0.10677839 = sum of:
        0.10677839 = weight(_text_:22 in 4686) [ClassicSimilarity], result of:
          0.10677839 = score(doc=4686,freq=2.0), product of:
            0.17248978 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.049257044 = queryNorm
            0.61904186 = fieldWeight in 4686, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.125 = fieldNorm(doc=4686)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

27.11.2005 18:04:22

0.01694965 = product of:
  0.05084895 = sum of:
    0.05084895 = product of:
      0.1016979 = sum of:
        0.1016979 = weight(_text_:catalogue in 2604) [ClassicSimilarity], result of:
          0.1016979 = score(doc=2604,freq=2.0), product of:
            0.23806341 = queryWeight, product of:
              4.8330836 = idf(docFreq=956, maxDocs=44218)
              0.049257044 = queryNorm
            0.42718828 = fieldWeight in 2604, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8330836 = idf(docFreq=956, maxDocs=44218)
              0.0625 = fieldNorm(doc=2604)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

Resource discovery is the problem of locating, and keeping track of, documents and other resources available on the Internet. Investigates some of the techniques that are currently being employed to help solve this problem. These include manually created catalogue records, centralized robot indexes, distributed indexing technology and author supplied metadata

0.01694965 = product of:
  0.05084895 = sum of:
    0.05084895 = product of:
      0.1016979 = sum of:
        0.1016979 = weight(_text_:catalogue in 4876) [ClassicSimilarity], result of:
          0.1016979 = score(doc=4876,freq=2.0), product of:
            0.23806341 = queryWeight, product of:
              4.8330836 = idf(docFreq=956, maxDocs=44218)
              0.049257044 = queryNorm
            0.42718828 = fieldWeight in 4876, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.8330836 = idf(docFreq=956, maxDocs=44218)
              0.0625 = fieldNorm(doc=4876)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

EEVL consists of several distinct resources, which exist as separate databases. This article describes the approach taken to tackle a particular problem that was identified through evaluation studies, namely, that searches of the EEVL catalogue too frequently matched nor records. The solution described in this paper is a cross-search facility for 3 of the EEVL databases

0.016884437 = product of:
  0.05065331 = sum of:
    0.05065331 = weight(_text_:title in 3071) [ClassicSimilarity], result of:
      0.05065331 = score(doc=3071,freq=2.0), product of:
        0.27436262 = queryWeight, product of:
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.049257044 = queryNorm
        0.18462175 = fieldWeight in 3071, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.570018 = idf(docFreq=457, maxDocs=44218)
          0.0234375 = fieldNorm(doc=3071)
  0.33333334 = coord(1/3)

Content

"One of the things I enjoyed the most when I was a reference librarian was the wide range of questions my clients sent my way. What was the original title of the first Godzilla movie? (Gojira, released in 1954) Who said 'I'm as pure as the driven slush'? (Tallulah Bankhead) What percentage of adults have gone to a jazz performance in the last year? (11%) I have found that librarians, speech writers and journalists have one thing in common - we all need to find information on all kinds of topics, and we usually need the answers right now. The following are a few of my favorite sites for finding answers to those there-must-be-an-answer-out-there questions. - For the electronic equivalent to the "ready reference" shelf of resources that most librarians keep hidden behind their desks, check out RefDesk . It is particularly good for answering factual questions - Where do I get the new Windows XP Service Pack? Where is the 386 area code? How do I contact my member of Congress? - Another resource for lots of those quick-fact questions is InfoPlease, the publishers of the Information Please almanac .- Right now, it's full of Olympics data, but it also has links to facts and factoids that you would look up in an almanac, atlas, or encyclopedia. - If you want numbers, start with the Statistical Abstract of the US. This source, produced by the U.S. Census Bureau, gives you everything from the divorce rate by state to airline cost indexes going back to 1980. It is many librarians' secret weapon for pulling numbers together quickly. - My favorite question is "how does that work?" Haven't you ever wondered how they get that Olympic torch to continue to burn while it is being carried by runners from one city to the next? Or how solar sails manage to propel a spacecraft? For answers, check out the appropriately-named How Stuff Works. - For questions about movies, my first resource is the Internet Movie Database. It is easy to search, is such a popular site that mistakes are corrected quickly, and is a fun place to catch trailers of both upcoming movies and those dating back to the 30s. - When I need to figure out who said what, I still tend to rely on the print sources such as Bartlett's Familiar Quotations . No, the current edition is not available on the web, but - and this is the librarian in me - I really appreciate the fact that I not only get the attribution but I also see the source of the quote. There are far too many quotes being attributed to a celebrity, but with no indication of the publication in which the quote appeared. Take, for example, the much-cited quote of Margaret Meade, "Never doubt that a small group of thoughtful committed people can change the world; indeed, it's the only thing that ever has!" Then see the page on the Institute for Intercultural Studies site, founded by Meade, and read its statement that it has never been able to verify this alleged quote from Meade. While there are lots of web-based sources of quotes (see QuotationsPage.com and Bartleby, for example), unless the site provides the original source for the quotation, I wouldn't rely on the citation. Of course, if you have a hunch as to the source of a quote, and it was published prior to 1923, head over to Project Gutenberg , which includes the full text of over 12,000 books that are in the public domain. When I needed to confirm a quotation of the Red Queen in "Through the Looking Glass", this is where I started. - And if you are stumped as to where to go to find information, instead of Googling it, try the Librarians' Index to the Internet. While it is somewhat US-centric, it is a great directory of web resources."