Search (9 results, page 1 of 1)

0.021780973 = product of:
  0.043561947 = sum of:
    0.043561947 = product of:
      0.08712389 = sum of:
        0.08712389 = weight(_text_:systems in 6326) [ClassicSimilarity], result of:
          0.08712389 = score(doc=6326,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.5432656 = fieldWeight in 6326, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.125 = fieldNorm(doc=6326)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

ACM transactions on information systems. 10(1992) no.3, S.194-315

0.019058352 = product of:
  0.038116705 = sum of:
    0.038116705 = product of:
      0.07623341 = sum of:
        0.07623341 = weight(_text_:systems in 3917) [ClassicSimilarity], result of:
          0.07623341 = score(doc=3917,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.47535738 = fieldWeight in 3917, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.109375 = fieldNorm(doc=3917)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

IEEE transactions on systems, man, and cybernetics. 19(1989) no.1, S.17-30

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

Abstract

Reviews the different types of hypertext systems and suggests that 3 types of hypertext exist: small, medium, and large volume hypertext

0.014140441 = product of:
  0.028280882 = sum of:
    0.028280882 = product of:
      0.056561764 = sum of:
        0.056561764 = weight(_text_:22 in 4915) [ClassicSimilarity], result of:
          0.056561764 = score(doc=4915,freq=2.0), product of:
            0.1827397 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.052184064 = queryNorm
            0.30952093 = fieldWeight in 4915, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=4915)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Source

International journal of information management. 11(1991) no.1, S.14-22

0.013476291 = product of:
  0.026952581 = sum of:
    0.026952581 = product of:
      0.053905163 = sum of:
        0.053905163 = weight(_text_:systems in 2223) [ClassicSimilarity], result of:
          0.053905163 = score(doc=2223,freq=4.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.33612844 = fieldWeight in 2223, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2223)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Maintaining a thesaurus is a time-consuming task which should go hand-in-hand with the indexing of information and should be supported by software. To connect different document databases their respective thesauri should be related. The most straightforward way to support to support this by computer is to map the terms of one thesaurus to those of another. Such a mapping creates one kind of metathesaurus. As citation systems are extended to include full-text online, a new thesaurus may be used to index individual paragraphs. To illustrate these principles several computer systems are described which help people maintain thesauri and metathesauri. Particular success has been had by the National Library of Medicine with its Medical Subject Headings and its Unified Medical Language System

0.010890487 = product of:
  0.021780973 = sum of:
    0.021780973 = product of:
      0.043561947 = sum of:
        0.043561947 = weight(_text_:systems in 5227) [ClassicSimilarity], result of:
          0.043561947 = score(doc=5227,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.2716328 = fieldWeight in 5227, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0625 = fieldNorm(doc=5227)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The disciplines of human-computer interaction, computer-supported collaborative work, information storage and retrieval, and artificial intelligence should complement one another in the new discipline of hypertext. This holistic view of hypertext focuses on links: links within a document (microtext), links among documents (macrotext), links among people (grouptext), and dynamic links (expertext). The principles and systems which are relevant to creating and accessing hypertext can be usefully presented under the heading of text, microtext, macrotext, grouptext and expertext. From text to expertext, people consistently use hierarchical structures, particularly hierarchical semantic nets, to organize information

0.010890487 = product of:
  0.021780973 = sum of:
    0.021780973 = product of:
      0.043561947 = sum of:
        0.043561947 = weight(_text_:systems in 7260) [ClassicSimilarity], result of:
          0.043561947 = score(doc=7260,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.2716328 = fieldWeight in 7260, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0625 = fieldNorm(doc=7260)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The concepts of hypertext, multimedia and hypermedia are often confused, but can defined thus: hypertext is text with links, multimedia is synchronized media, and hypermedia is multimedia with links. Presents descriptions of systems for hypertext, multimedia and hypermedia. The computer storage and processing requirements for multimedia are orders of magnitudes greater than those for hypertext. Nevertheless, the hypertext model can be extended to deal with hypermedia by including multimedia synchronization capabilities. Information technology and its associated terminology should help people effectively compare experiences and thus have more influence on future developments

0.009529176 = product of:
  0.019058352 = sum of:
    0.019058352 = product of:
      0.038116705 = sum of:
        0.038116705 = weight(_text_:systems in 823) [ClassicSimilarity], result of:
          0.038116705 = score(doc=823,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.23767869 = fieldWeight in 823, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.0546875 = fieldNorm(doc=823)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Connecting and evaluating thesauri is an important task for the systematic development of better information retrieval systems. Connecting thesauri includes not only determining when terms in different thesauri are the same but also determining what kinds of relationships can be transferred from one thesaurus to another. This paper first presents issues in connecting and evaluating thesauri. Various experiments in connecting a particular thesaurus, the Medical Subject Headings, with other medical thesauri are described. In these experiments, similar terms in two thesauri are recognized and then differences in two thesauri are exploited to create more powerful thesauri. Part of the evaluation requires the thesaurus to support automatic indexing and retrieving of documents

0.008167865 = product of:
  0.01633573 = sum of:
    0.01633573 = product of:
      0.03267146 = sum of:
        0.03267146 = weight(_text_:systems in 4540) [ClassicSimilarity], result of:
          0.03267146 = score(doc=4540,freq=2.0), product of:
            0.16037072 = queryWeight, product of:
              3.0731742 = idf(docFreq=5561, maxDocs=44218)
              0.052184064 = queryNorm
            0.2037246 = fieldWeight in 4540, 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=4540)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The Many Using and Creating Hypermedia (MUCH) systems is based on the Dexter model and treats the storage layer as a semantic net. The MUCH system provides a numer of recommended link types for representing application domain concepts, such as thesauri, documents and annotations. users of the system are expected to use those link types in the course of authoring meaningful hypermedia. based on the logs of usage of the MUCH system over 2 years by over 200 people, contrary to the designers' expectations, users did not exploit the ability to type semantic links. Typically authors used the default link type regardless of their semantic intentions. When a link type other than the default type was chosen, that choice was often inconsistent with the way another user would able a similar link. The system has proven to be useful for authoring conventional documents. Authors, however, were not practically able to produce hypertext documents. Based on these experiences a new system, RICH (Reusable Intelligent Collaborative Hypermedia), has been designed and built which emphasizes rules for typing links and maintaining the integrity of the semantic net