Search (25 results, page 1 of 2)

  • × year_i:[1990 TO 2000}
  • × theme_ss:"Volltextretrieval"
  1. Kristensen, J.; Järvelin, K.: ¬The effectiveness of a searching thesaurus in free-text searching in a full-text database (1990) 0.05
    0.05287661 = product of:
      0.10575322 = sum of:
        0.10575322 = product of:
          0.21150644 = sum of:
            0.21150644 = weight(_text_:searching in 2043) [ClassicSimilarity], result of:
              0.21150644 = score(doc=2043,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                1.0113229 = fieldWeight in 2043, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.125 = fieldNorm(doc=2043)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  2. Sclafani, F.: Controlled subject heading searching versus keyword searching (1999) 0.05
    0.05287661 = product of:
      0.10575322 = sum of:
        0.10575322 = product of:
          0.21150644 = sum of:
            0.21150644 = weight(_text_:searching in 3790) [ClassicSimilarity], result of:
              0.21150644 = score(doc=3790,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                1.0113229 = fieldWeight in 3790, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.125 = fieldNorm(doc=3790)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  3. Falk, H.: Document file searching (1998) 0.04
    0.040475223 = product of:
      0.08095045 = sum of:
        0.08095045 = product of:
          0.1619009 = sum of:
            0.1619009 = weight(_text_:searching in 2429) [ClassicSimilarity], result of:
              0.1619009 = score(doc=2429,freq=6.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.77413285 = fieldWeight in 2429, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.078125 = fieldNorm(doc=2429)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Considers the importance of generating indexes when creating large document files, to facilitate searching, and evaluates 4 commercial document file index creation and searching software packages: QuickFind; Sonar; ZyIndex; and FastFind
  4. DiMartino, D.; Zoe, L.R.: End-user full text searching : access or excess? (1996) 0.04
    0.03738941 = product of:
      0.07477882 = sum of:
        0.07477882 = product of:
          0.14955764 = sum of:
            0.14955764 = weight(_text_:searching in 7545) [ClassicSimilarity], result of:
              0.14955764 = score(doc=7545,freq=2.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.7151132 = fieldWeight in 7545, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.125 = fieldNorm(doc=7545)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  5. Poler, E.M.: Overcoming limitations in database searches (1992) 0.03
    0.03304788 = product of:
      0.06609576 = sum of:
        0.06609576 = product of:
          0.13219152 = sum of:
            0.13219152 = weight(_text_:searching in 2329) [ClassicSimilarity], result of:
              0.13219152 = score(doc=2329,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.6320768 = fieldWeight in 2329, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.078125 = fieldNorm(doc=2329)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Describes the advantages of full text databases and full text searching, particularly in the context of law databases, the drawbacks to such searching in terms of recall, precision and errors, and methods of overcoming some of these problems
  6. Sormunen, E.: Free-text searching in full-text databases : probing system limits (1993) 0.03
    0.03271573 = product of:
      0.06543146 = sum of:
        0.06543146 = product of:
          0.13086292 = sum of:
            0.13086292 = weight(_text_:searching in 7120) [ClassicSimilarity], result of:
              0.13086292 = score(doc=7120,freq=2.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.6257241 = fieldWeight in 7120, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.109375 = fieldNorm(doc=7120)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  7. Wildemuth, B.M.: Measures of success in searching a full-text fact base (1990) 0.03
    0.03271573 = product of:
      0.06543146 = sum of:
        0.06543146 = product of:
          0.13086292 = sum of:
            0.13086292 = weight(_text_:searching in 2050) [ClassicSimilarity], result of:
              0.13086292 = score(doc=2050,freq=8.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.6257241 = fieldWeight in 2050, product of:
                  2.828427 = tf(freq=8.0), with freq of:
                    8.0 = termFreq=8.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=2050)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The traditional measures of online searching proficiency (recall and precision) are less appropriate when applied to the searching of full text databases. The pilot study investigated and evaluated 5 measures of overall success in searching a full text data bank. Data was drawn from INQUIRER searches conducted by medical students at North Carolina Univ. at Chapel Hill. INQUIRER ia an online database of facts and concepts in microbiology. The 5 measures were: success/failure; precision; search term overlap; number of search cycles; and time per search. Concludes that the last 4 measures look promising for the evaluation of fact data bases such as ENQUIRER
  8. Hildreth, C.R.: ¬The use and understanding of keyword searching in a university online catalog (1997) 0.03
    0.03271573 = product of:
      0.06543146 = sum of:
        0.06543146 = product of:
          0.13086292 = sum of:
            0.13086292 = weight(_text_:searching in 7377) [ClassicSimilarity], result of:
              0.13086292 = score(doc=7377,freq=2.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.6257241 = fieldWeight in 7377, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.109375 = fieldNorm(doc=7377)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  9. Allen, E.E.: Searching, naturally (1998) 0.03
    0.028042056 = product of:
      0.05608411 = sum of:
        0.05608411 = product of:
          0.11216822 = sum of:
            0.11216822 = weight(_text_:searching in 2602) [ClassicSimilarity], result of:
              0.11216822 = score(doc=2602,freq=2.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.53633493 = fieldWeight in 2602, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.09375 = fieldNorm(doc=2602)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  10. Basch, R.: Searching full-text : tips and techniques (1992) 0.03
    0.026438305 = product of:
      0.05287661 = sum of:
        0.05287661 = product of:
          0.10575322 = sum of:
            0.10575322 = weight(_text_:searching in 5050) [ClassicSimilarity], result of:
              0.10575322 = score(doc=5050,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.5056614 = fieldWeight in 5050, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0625 = fieldNorm(doc=5050)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Gives tips for effective searching of full-text databases: think creatively about vocabulary and use of the OR connector to link synonyms; use truncation to pick up plurals and alternative work endings; anticipate international differences in spellimg, likie 'labor' and 'labour', and in vocabulary, like 'truck' and 'lorry'; avoid the AND operator, preferring proximity connectors like NEAR, WITHIN or PRE; use jargon instead of trying to anticipate all the abstract terminology that a writer might have used; and exploit any indexing available
  11. Kristensen, J.: Expanding end-users' query statements for free text searching with a search-aid thesaurus (1993) 0.03
    0.026438305 = product of:
      0.05287661 = sum of:
        0.05287661 = product of:
          0.10575322 = sum of:
            0.10575322 = weight(_text_:searching in 6621) [ClassicSimilarity], result of:
              0.10575322 = score(doc=6621,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.5056614 = fieldWeight in 6621, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0625 = fieldNorm(doc=6621)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Tests the effectiveness of a thesaurus as a search-aid in free text searching of a full text database. A set of queries was searched against a large full text database of newspaper articles. The thesaurus contained equivalence, hierarchical and associative relationships. Each query was searched in five modes: basic search, synonym search, narrower term search, related term search, and union of all previous searches. The searches were analyzed in terms of relative recall and precision
  12. Tenopir, C.: Full-text retrieval : systems and files (1994) 0.03
    0.026438305 = product of:
      0.05287661 = sum of:
        0.05287661 = product of:
          0.10575322 = sum of:
            0.10575322 = weight(_text_:searching in 2424) [ClassicSimilarity], result of:
              0.10575322 = score(doc=2424,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.5056614 = fieldWeight in 2424, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0625 = fieldNorm(doc=2424)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    State of the art review of the development of full text databases, encompassing: types of commercially available full text databases; online systems for full text databases; CD-ROM databases for full text databases; full text databases on magnetic discs or tapes; creation of full text databases; searching and display requirements for full text searching and software. Concludes that bibliographic information services without full text support solve only half of the retrieval problems
  13. Leppanen, E.: Homografiongelma tekstihaussa ja homografien disambiguoinnin vaikutukset (1996) 0.02
    0.024285134 = product of:
      0.048570268 = sum of:
        0.048570268 = product of:
          0.097140536 = sum of:
            0.097140536 = weight(_text_:searching in 27) [ClassicSimilarity], result of:
              0.097140536 = score(doc=27,freq=6.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.46447968 = fieldWeight in 27, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.046875 = fieldNorm(doc=27)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Homonymy is known to often cause false drops in free text searching in a full text database. The problem is quite common and difficult to avoid in Finnish, but nobody has examined it before. Reports on a study that examined the frequency of, and solutions to, the homonymy problem, based on searches made in a Finnish full text database containing about 55.000 newspaper articles. The results indicate that homonymy is not a very serious problem in full text searching, with only about 1 search result set out of 4 containing false drops caused by homonymy. Several other reasons for nonrelevance were much more common. However, in some set results there were a considerable number of homonymy errors, so the number seems to be very random. A study was also made into whether homonyms can be disambiguated by syntactic analysis. The result was that 75,2% of homonyms were disambiguated by this method. Verb homonyms were considerably easier to disambiguate than substantives. Although homonymy is not a very big problem it could perhaps easily be eliminated if there was a suitable syntactic analyzer in the IR system
    Footnote
    Übers. d. Titels: The homonymy problem in free text searching and the results of homonymy disambiguation
  14. Couvreur, T.R.; Benzel, R.N.; Miller, S.F.; Zeitler, D.N.; Lee, D.L.; Singhal, M.; Shivaratri, N.; Wong, W.Y.P.: ¬An analysis of performance and cost factors in searching large text databases using parallel search systems (1994) 0.02
    0.023133516 = product of:
      0.046267033 = sum of:
        0.046267033 = product of:
          0.092534065 = sum of:
            0.092534065 = weight(_text_:searching in 7657) [ClassicSimilarity], result of:
              0.092534065 = score(doc=7657,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.44245374 = fieldWeight in 7657, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=7657)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The results of modelling the performance of searching large text databases (>10 GBytes) via various parallel hardware architectures and search algorithms are discussed. The performance under load and the cost of each configuration are compared. Strengths, weaknesses, performance sensitivities, and search features supported for each configuration are also addressed. In addition, a common search workload used in the modelling is described. The search workload is derived from a set of searches run against the Chemical Abstracts file of bibliographic and abstract text available on STN International. This common workload is applied to all configurations modelled to provide a common basis of comparison
  15. Albus, W.; Smulders, H.: Doeltreffend zoeken in volledige teksten : 1. full-text retrieval bij de HavenInformatieBank (1998) 0.02
    0.023133516 = product of:
      0.046267033 = sum of:
        0.046267033 = product of:
          0.092534065 = sum of:
            0.092534065 = weight(_text_:searching in 1682) [ClassicSimilarity], result of:
              0.092534065 = score(doc=1682,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.44245374 = fieldWeight in 1682, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=1682)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    At Rotterdam Ports Authority in the Netherlands the Habour information database includes a press cuttings service and various online databases. To enable research staff to have direct access to information the POINT (Point Information Net) was begun in 1993. Using Verity software POINT provides simultaneously full text searching on a range of databases. The software uses current Web indexing technqiues to overcome the problems of excessive recall and low precision. A key element is the system's ability to recognise word combinations
    Footnote
    Übers. d. Titels: Effective searching on full texts: 1. full-text-retrieval on the Harbour information database
  16. Nahl, D.; Tenopir, C.: Affective and cognitive searching behavior of novice end-users of a full-text database (1996) 0.02
    0.020237612 = product of:
      0.040475223 = sum of:
        0.040475223 = product of:
          0.08095045 = sum of:
            0.08095045 = weight(_text_:searching in 4213) [ClassicSimilarity], result of:
              0.08095045 = score(doc=4213,freq=6.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.38706642 = fieldWeight in 4213, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=4213)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Footnote
    Novice end users were given 2 hours of training in searching a full-text magazine database (Magazine ASAP(TM)) on DIALOG. Subjects searched during 3 to 4 sessions in the presence of a trained monitor who prompted them to think aloud throughout the sessions. qualitative analysis of the transcripts and transaction logs yielded empirical information on user variables (purpose, motivation, satisfaction), uses of the database, move types, and every question users asked during the searches. The spontaneous, naturalistic questions were categorized according to affective, cognitive, and sensorimotor speech acts. Results show that most of the searches were performed for the self and were work related. The most common use of the database was to retrieve full-text articles online and to download and print them out rather than read them on screen. The majority of searches were judged satisfactory. Innovative uses included browsing for background information and obtaining contextualized sentences for language teaching. Searchers made twice as many moves to limit sets as moves to expand sets. Affective questions outnumbered cognitive and sensorimotor questions by two to one. This preponderance of affective micro-information needs during searching might be addressed by new system functions
  17. Miller, C.: Standardization of full-text files on Dialog : IAC goes first (1995) 0.02
    0.018694704 = product of:
      0.03738941 = sum of:
        0.03738941 = product of:
          0.07477882 = sum of:
            0.07477882 = weight(_text_:searching in 2776) [ClassicSimilarity], result of:
              0.07477882 = score(doc=2776,freq=2.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.3575566 = fieldWeight in 2776, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0625 = fieldNorm(doc=2776)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Knight Rider Information Inc./Dialog is creating standards for full text journal databases, directories and full text reports with the aim of making multiple file searching more efficient. The 1st reloaded file adhering to the new standard was loaded in Feb. 95. This was prompted by the merger of IAC Index and ASAP files. Explains how the reload was carried out and the implications for searchers
  18. Pirkola, A.; Jarvelin, K.: ¬The effect of anaphor and ellipsis resolution on proximity searching in a text database (1995) 0.02
    0.01652394 = product of:
      0.03304788 = sum of:
        0.03304788 = product of:
          0.06609576 = sum of:
            0.06609576 = weight(_text_:searching in 4088) [ClassicSimilarity], result of:
              0.06609576 = score(doc=4088,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.3160384 = fieldWeight in 4088, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=4088)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    So far, methods for ellipsis and anaphor resolution have been developed and the effects of anaphor resolution have been analyzed in the context of statistical information retrieval of scientific abstracts. No significant improvements has been observed. Analyzes the effects of ellipsis and anaphor resolution on proximity searching in a full text database. Anaphora and ellipsis are classified on the basis of the type of their correlates / antecedents rather than, as traditional, on the basis of their own linguistic type. The classification differentiates proper names and common nouns of basic words, compound words, and phrases. The study was carried out in a newspaper article database containing 55.000 full text articles. A set of 154 keyword pairs in different categories was created. Human resolution of keyword ellipsis and anaphora was performed to identify sentences and paragraphs which would match proximity searches after resolution. Findings indicate that ellipsis and anaphor resolution is most relevant for proper name phrases and only marginal in the other keyword categories. Therefore the recall effect of restricted resolution of proper name phrases only was analyzed for keyword pairs containing at least 1 proper name phrase. Findings indicate a recall increase of 38.2% in sentence searches, and 28.8% in paragraph searches when proper name ellipsis were resolved. The recall increase was 17.6% sentence searches, and 19.8% in paragraph searches when proper name anaphora were resolved. Some simple and computationally justifiable resolution method might be developed only for proper name phrases to support keyword based full text information retrieval. Discusses elements of such a method
  19. Voorbij, H.: Title keywords and subject descriptors : a comparison of subject search entries of books in the humanities and social sciences (1998) 0.02
    0.01652394 = product of:
      0.03304788 = sum of:
        0.03304788 = product of:
          0.06609576 = sum of:
            0.06609576 = weight(_text_:searching in 4721) [ClassicSimilarity], result of:
              0.06609576 = score(doc=4721,freq=4.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.3160384 = fieldWeight in 4721, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=4721)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    In order to compare the value of subject descriptors and title keywords as entries to subject searches, two studies were carried out. Both studies concentrated on monographs in the humanities and social sciences, held by the online public access catalogue of the National Library of the Netherlands. In the first study, a comparison was made by subject librarians between the subject descriptors and the title keywords of 475 records. They could express their opinion on a scale from 1 (descriptor is exactly or almost the same as word in title) to 7 (descriptor does not appear in title at all). It was concluded that 37 per cent of the records are considerably enhanced by a subject descriptor, and 49 per cent slightly or considerably enhanced. In the second study, subject librarians performed subject searches using title keywords and subject descriptors on the same topic. The relative recall amounted to 48 per cent and 86 per cent respectively. Failure analysis revealed the reasons why so many records that were found by subject descriptors were not found by title keywords. First, although completely meaningless titles hardly ever appear, the title of a publication does not always offer sufficient clues for title keyword searching. In those cases, descriptors may enhance the record of a publication. A second and even more important task of subject descriptors is controlling the vocabulary. Many relevant titles cannot be retrieved by title keyword searching because of the wide diversity of ways of expressing a topic. Descriptors take away the burden of vocabulary control from the user.
  20. Bernard, M.: Modelling the efficient access to full-text information (1996) 0.02
    0.016357865 = product of:
      0.03271573 = sum of:
        0.03271573 = product of:
          0.06543146 = sum of:
            0.06543146 = weight(_text_:searching in 5610) [ClassicSimilarity], result of:
              0.06543146 = score(doc=5610,freq=2.0), product of:
                0.2091384 = queryWeight, product of:
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.051699217 = queryNorm
                0.31286204 = fieldWeight in 5610, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  4.0452914 = idf(docFreq=2103, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=5610)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Describes a research goal set by many offices within the US Department of Energy. Reviews efficient full text searching techniques being developed to better understand and meet this goal. Classical computer human interaction (CHI) approaches provided by commercial information retrieval engines fail to contextualize information in ways that facilitates timely decision making. Discusses the uses of advanced CHI techniques in combination with deductive database technology to augment the weaknesses found in the presentation capabilities of information retrieval engines. Presents various techniques employed in a WWW based prototype system currently under development