Search (43 results, page 1 of 3)

0.11132976 = product of:
  0.16699463 = sum of:
    0.06022381 = weight(_text_:resources in 4261) [ClassicSimilarity], result of:
      0.06022381 = score(doc=4261,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.32264733 = fieldWeight in 4261, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.0625 = fieldNorm(doc=4261)
    0.10677081 = sum of:
      0.05134755 = weight(_text_:management in 4261) [ClassicSimilarity], result of:
        0.05134755 = score(doc=4261,freq=2.0), product of:
          0.17235184 = queryWeight, product of:
            3.3706124 = idf(docFreq=4130, maxDocs=44218)
            0.051133685 = queryNorm
          0.29792285 = fieldWeight in 4261, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            3.3706124 = idf(docFreq=4130, maxDocs=44218)
            0.0625 = fieldNorm(doc=4261)
      0.055423267 = weight(_text_:22 in 4261) [ClassicSimilarity], result of:
        0.055423267 = score(doc=4261,freq=2.0), product of:
          0.17906146 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051133685 = queryNorm
          0.30952093 = fieldWeight in 4261, 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=4261)
  0.6666667 = coord(2/3)

Date

17. 7.2002 19:22:06

Theme

Information Resources Management

0.05726506 = product of:
  0.08589759 = sum of:
    0.06022381 = weight(_text_:resources in 944) [ClassicSimilarity], result of:
      0.06022381 = score(doc=944,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.32264733 = fieldWeight in 944, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.0625 = fieldNorm(doc=944)
    0.025673775 = product of:
      0.05134755 = sum of:
        0.05134755 = weight(_text_:management in 944) [ClassicSimilarity], result of:
          0.05134755 = score(doc=944,freq=2.0), product of:
            0.17235184 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.051133685 = queryNorm
            0.29792285 = fieldWeight in 944, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.0625 = fieldNorm(doc=944)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

Many libraries manage Web sites intended to provide their users with online resources suitable for answering reference questions. Most of these sites can be analyzed in terms of their depth, and their organizing and searching features. Composing a typology based on these factors sheds light on the critical design decisions that influence whether users of these sites succees or fail to find information easily, rapidly and accurately. The same analysis highlights some larger design issues, both for Web sites and for information management at large

0.042618744 = product of:
  0.06392811 = sum of:
    0.052695833 = weight(_text_:resources in 1264) [ClassicSimilarity], result of:
      0.052695833 = score(doc=1264,freq=8.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.28231642 = fieldWeight in 1264, product of:
          2.828427 = tf(freq=8.0), with freq of:
            8.0 = termFreq=8.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.02734375 = fieldNorm(doc=1264)
    0.011232276 = product of:
      0.022464553 = sum of:
        0.022464553 = weight(_text_:management in 1264) [ClassicSimilarity], result of:
          0.022464553 = score(doc=1264,freq=2.0), product of:
            0.17235184 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.051133685 = queryNorm
            0.13034125 = fieldWeight in 1264, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.02734375 = fieldNorm(doc=1264)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

Defining metadata as "data about data" provokes more questions than it answers. What are the forms of the data and metadata? Can we be more specific about the manner in which the metadata is "about" the data? Are data and metadata distinguished only in the context of their relationship? Is the nature of the relationship between the datasets declarative or procedural? Can the metadata itself be described by other data? Over the past several years, we have been engaged in a number of efforts examining the role, format, composition, and architecture of metadata for networked resources. During this time, we have noticed the tendency to be led astray by comfortable, but somewhat inappropriate, models in the non-digital information environment. Rather than pursuing familiar models, there is the need for a new model that fully exploits the unique combination of computation and connectivity that characterizes the digital library. In this paper, we describe an extension of the Warwick Framework that we call Distributed Active Relationships (DARs). DARs provide a powerful model for representing data and metadata in digital library objects. They explicitly express the relationships between networked resources, and even allow those relationships to be dynamically downloadable and executable. The DAR model is based on the following principles, which our examination of the "data about data" definition has led us to regard as axiomatic: * There is no essential distinction between data and metadata. We can only make such a distinction in terms of a particular "about" relationship. As a result, what is metadata in the context of one "about" relationship may be data in another. * There is no single "about" relationship. There are many different and important relationships between data resources. * Resources can be related without regard for their location. The connectivity in networked information architectures makes it possible to have data in one repository describe data in another repository. * The computational power of the networked information environment makes it possible to consider active or dynamic relationships between data sets. This adds considerable power to the "data about data" definition. First, data about another data set may not physically exist, but may be automatically derived. Second, the "about" relationship may be an executable object -- in a sense interpretable metadata. As will be shown, this provides useful mechanisms for handling complex metadata problems such as rights management of digital objects. The remainder of this paper describes the development and consequences of the DAR model. Section 2 reviews the Warwick Framework, which is the basis for the model described in this paper. Section 3 examines the concept of the Warwick Framework Catalog, which provides a mechanism for expressing the relationships between the packages in a Warwick Framework container. With that background established, section 4 generalizes the Warwick Framework by removing the restriction that it only contains "metadata". This allows us to consider digital library objects that are aggregations of (possibly distributed) data sets, with the relationships between the data sets expressed using a Warwick Framework Catalog. Section 5 further extends the model by describing Distributed Active Relationships (DARs). DARs are the explicit relationships that have the potential to be executable, as alluded to earlier. Finally, section 6 describes two possible implementations of these concepts.

0.04014921 = product of:
  0.12044762 = sum of:
    0.12044762 = weight(_text_:resources in 5903) [ClassicSimilarity], result of:
      0.12044762 = score(doc=5903,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.64529467 = fieldWeight in 5903, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.125 = fieldNorm(doc=5903)
  0.33333334 = coord(1/3)

0.035130557 = product of:
  0.10539167 = sum of:
    0.10539167 = weight(_text_:resources in 3231) [ClassicSimilarity], result of:
      0.10539167 = score(doc=3231,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.56463283 = fieldWeight in 3231, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.109375 = fieldNorm(doc=3231)
  0.33333334 = coord(1/3)

0.035130557 = product of:
  0.10539167 = sum of:
    0.10539167 = weight(_text_:resources in 477) [ClassicSimilarity], result of:
      0.10539167 = score(doc=477,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.56463283 = fieldWeight in 477, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.109375 = fieldNorm(doc=477)
  0.33333334 = coord(1/3)

Footnote

Rez. in: Library resources and technical services 41(1998) no.1, S.347-349 (J.K. Duke)

0.034770235 = product of:
  0.1043107 = sum of:
    0.1043107 = weight(_text_:resources in 4183) [ClassicSimilarity], result of:
      0.1043107 = score(doc=4183,freq=6.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.5588416 = fieldWeight in 4183, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.0625 = fieldNorm(doc=4183)
  0.33333334 = coord(1/3)

Abstract

A status of cataloging in Thailand shows a movement toward the use of information technology. The international standards for cataloging are being used and modified to effectively organize the information resources. An expanded scope of resources needed cataloging now covers cataloging the Web resources. The paper mentions Thailand's participation in the international working group on the use of metadata for libraries

0.025093256 = product of:
  0.075279765 = sum of:
    0.075279765 = weight(_text_:resources in 1103) [ClassicSimilarity], result of:
      0.075279765 = score(doc=1103,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.40330917 = fieldWeight in 1103, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.078125 = fieldNorm(doc=1103)
  0.33333334 = coord(1/3)

Abstract

This article presents our exploration of computer science clustering algorithms as they relate to the Scorpion system. Scorpion is a research project at OCLC that explores the indexing and cataloging of electronic resources. For a more complete description of the Scorpion, please visit the Scorpion Web site at <http://purl.oclc.org/scorpion>

0.021512985 = product of:
  0.064538956 = sum of:
    0.064538956 = weight(_text_:resources in 5903) [ClassicSimilarity], result of:
      0.064538956 = score(doc=5903,freq=12.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.3457656 = fieldWeight in 5903, product of:
          3.4641016 = tf(freq=12.0), with freq of:
            12.0 = termFreq=12.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.02734375 = fieldNorm(doc=5903)
  0.33333334 = coord(1/3)

Abstract

RDF - the Resource Description Framework - is a foundation for processing metadata; it provides interoperability between applications that exchange machine-understandable information on the Web. RDF emphasizes facilities to enable automated processing of Web resources. RDF metadata can be used in a variety of application areas; for example: in resource discovery to provide better search engine capabilities; in cataloging for describing the content and content relationships available at a particular Web site, page, or digital library; by intelligent software agents to facilitate knowledge sharing and exchange; in content rating; in describing collections of pages that represent a single logical "document"; for describing intellectual property rights of Web pages, and in many others. RDF with digital signatures will be key to building the "Web of Trust" for electronic commerce, collaboration, and other applications. Metadata is "data about data" or specifically in the context of RDF "data describing web resources." The distinction between "data" and "metadata" is not an absolute one; it is a distinction created primarily by a particular application. Many times the same resource will be interpreted in both ways simultaneously. RDF encourages this view by using XML as the encoding syntax for the metadata. The resources being described by RDF are, in general, anything that can be named via a URI. The broad goal of RDF is to define a mechanism for describing resources that makes no assumptions about a particular application domain, nor defines the semantics of any application domain. The definition of the mechanism should be domain neutral, yet the mechanism should be suitable for describing information about any domain. This document introduces a model for representing RDF metadata and one syntax for expressing and transporting this metadata in a manner that maximizes the interoperability of independently developed web servers and clients. The syntax described in this document is best considered as a "serialization syntax" for the underlying RDF representation model. The serialization syntax is XML, XML being the W3C's work-in-progress to define a richer Web syntax for a variety of applications. RDF and XML are complementary; there will be alternate ways to represent the same RDF data model, some more suitable for direct human authoring. Future work may lead to including such alternatives in this document.

Content

RDF Data Model At the core of RDF is a model for representing named properties and their values. These properties serve both to represent attributes of resources (and in this sense correspond to usual attribute-value-pairs) and to represent relationships between resources. The RDF data model is a syntax-independent way of representing RDF statements. RDF statements that are syntactically very different could mean the same thing. This concept of equivalence in meaning is very important when performing queries, aggregation and a number of other tasks at which RDF is aimed. The equivalence is defined in a clean machine understandable way. Two pieces of RDF are equivalent if and only if their corresponding data model representations are the same. Table of contents 1. Introduction 2. RDF Data Model 3. RDF Grammar 4. Signed RDF 5. Examples 6. Appendix A: Brief Explanation of XML Namespaces

0.018474422 = product of:
  0.055423267 = sum of:
    0.055423267 = product of:
      0.110846534 = sum of:
        0.110846534 = weight(_text_:22 in 5449) [ClassicSimilarity], result of:
          0.110846534 = score(doc=5449,freq=2.0), product of:
            0.17906146 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133685 = queryNorm
            0.61904186 = fieldWeight in 5449, 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=5449)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

22. 2.1997 19:26:34

0.018474422 = product of:
  0.055423267 = sum of:
    0.055423267 = product of:
      0.110846534 = sum of:
        0.110846534 = weight(_text_:22 in 5837) [ClassicSimilarity], result of:
          0.110846534 = score(doc=5837,freq=2.0), product of:
            0.17906146 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133685 = queryNorm
            0.61904186 = fieldWeight in 5837, 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=5837)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

30.11.1996 13:22:37

0.018474422 = product of:
  0.055423267 = sum of:
    0.055423267 = product of:
      0.110846534 = sum of:
        0.110846534 = weight(_text_:22 in 4085) [ClassicSimilarity], result of:
          0.110846534 = score(doc=4085,freq=2.0), product of:
            0.17906146 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133685 = queryNorm
            0.61904186 = fieldWeight in 4085, 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=4085)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

7.11.1999 18:22:39

0.017743612 = product of:
  0.053230833 = sum of:
    0.053230833 = weight(_text_:resources in 1252) [ClassicSimilarity], result of:
      0.053230833 = score(doc=1252,freq=4.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.28518265 = fieldWeight in 1252, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1252)
  0.33333334 = coord(1/3)

Abstract

A subject gateway, in the context of network-based resource access, can be defined as some facility that allows easier access to network-based resources in a defined subject area. The simplest types of subject gateways are sets of Web pages containing lists of links to resources. Some gateways index their lists of links and provide a simple search facility. More advanced gateways offer a much enhanced service via a system consisting of a resource database and various indexes, which can be searched and/or browsed through a Web-based interface. Each entry in the database contains information about a network-based resource, such as a Web page, Web site, mailing list or document. Entries are usually created by a cataloguer manually identifying a suitable resource, describing the resource using a template, and submitting the template to the database for indexing. Subject gateways are also known as subject-based information gateways (SBIGs), subject-based gateways, subject index gateways, virtual libraries, clearing houses, subject trees, pathfinders and other variations thereof. This paper describes the characteristics of some of the subject gateways currently accessible through the Web, and compares them to automatic "vacuum cleaner" type search engines, such as AltaVista. The application of WHOIS++, centroids, query routing, and forward knowledge to searching several of these subject gateways simultaneously is outlined. The paper concludes with looking at some of the issues facing subject gateway development in the near future. The paper touches on many of the issues mentioned in a previous paper in D-Lib Magazine, especially regarding resource-discovery related initiatives and services.

0.01616512 = product of:
  0.04849536 = sum of:
    0.04849536 = product of:
      0.09699072 = sum of:
        0.09699072 = weight(_text_:22 in 4084) [ClassicSimilarity], result of:
          0.09699072 = score(doc=4084,freq=2.0), product of:
            0.17906146 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133685 = queryNorm
            0.5416616 = fieldWeight in 4084, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=4084)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

7.11.1999 18:22:54

0.01616512 = product of:
  0.04849536 = sum of:
    0.04849536 = product of:
      0.09699072 = sum of:
        0.09699072 = weight(_text_:22 in 6021) [ClassicSimilarity], result of:
          0.09699072 = score(doc=6021,freq=2.0), product of:
            0.17906146 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133685 = queryNorm
            0.5416616 = fieldWeight in 6021, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=6021)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Source

Ariadne. 1999, no.22

0.015055953 = product of:
  0.045167856 = sum of:
    0.045167856 = weight(_text_:resources in 1668) [ClassicSimilarity], result of:
      0.045167856 = score(doc=1668,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.2419855 = fieldWeight in 1668, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.046875 = fieldNorm(doc=1668)
  0.33333334 = coord(1/3)

Abstract

This working paper describes the creation of a test database to carry out the automatic classification tasks of the DESIRE II work package D3.6a on. It is an improved version of NetLab's existing "All" Engineering database created after a comparative study of the outcome of two different approaches to collecting the documents. These two methods were selected from seven different general methodologies to build robot-generated subject indices, presented in this paper. We found a surprisingly low overlap between the Engineering link collections we used as seed pages for the robot and subsequently an even more surprisingly low overlap between the resources collected by the two different approaches. That inspite of using basically the same services to start the harvesting process from. A intellectual evaluation of the contents of both databases showed almost exactly the same percentage of relevant documents (77%), indicating that the main difference between those aproaches was the coverage of the resulting database.

0.015055953 = product of:
  0.045167856 = sum of:
    0.045167856 = weight(_text_:resources in 1254) [ClassicSimilarity], result of:
      0.045167856 = score(doc=1254,freq=2.0), product of:
        0.18665522 = queryWeight, product of:
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.051133685 = queryNorm
        0.2419855 = fieldWeight in 1254, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.650338 = idf(docFreq=3122, maxDocs=44218)
          0.046875 = fieldNorm(doc=1254)
  0.33333334 = coord(1/3)

Abstract

The purpose of this essay is to identify and explore the dynamics of the literature associated with the Dublin Core Workshop Series. The essay opens by identifying the problems that the Dublin Core Workshop Series is addressing, the status of the Internet at the time of the first workshop, and the contributions each workshop has made to the ongoing discussion. The body of the essay describes the characteristics of the literature, highlights key documents, and identifies the major researchers. The essay closes with evaluation of the literary trends and considerations of future research directions. The essay concludes that a shift from a descriptive emphasis to a more empirical form of literature is about to take place. Future research questions are identified in the areas of satisfying searcher needs, the impact of surrogate descriptions on search engine performance, and the effectiveness of surrogate descriptions in authenticating Internet resources.

0.014822762 = product of:
  0.044468287 = sum of:
    0.044468287 = product of:
      0.088936575 = sum of:
        0.088936575 = weight(_text_:management in 1125) [ClassicSimilarity], result of:
          0.088936575 = score(doc=1125,freq=6.0), product of:
            0.17235184 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.051133685 = queryNorm
            0.51601756 = fieldWeight in 1125, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.0625 = fieldNorm(doc=1125)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

Der Thesaurus Technik und Management ist die umfangreichste strukturierte Sammlung des aktuellen Fachwortschatzes zur Technik und dem produktionsorientierten Management. Für 48.000 deutsche und 32.000 englische Fachwörter werden die synonymen, hierarchischen und verwandten Beziehungen aufgezeigt und in 34.000 Begriffsfamilien zusammengefaßt. Alle Begriffssätze sind alphabetisch aufgelistet. Die zum Begriffssatz gehörenden Vorzugsbenennungen, Synonyme, Unter-, Ober- und verwandte Relationen und Rückverweise sind gekennzeichnet

0.013855817 = product of:
  0.04156745 = sum of:
    0.04156745 = product of:
      0.0831349 = sum of:
        0.0831349 = weight(_text_:22 in 8959) [ClassicSimilarity], result of:
          0.0831349 = score(doc=8959,freq=2.0), product of:
            0.17906146 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133685 = queryNorm
            0.46428138 = fieldWeight in 8959, 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=8959)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

16. 7.2002 20:22:55

0.013855817 = product of:
  0.04156745 = sum of:
    0.04156745 = product of:
      0.0831349 = sum of:
        0.0831349 = weight(_text_:22 in 5664) [ClassicSimilarity], result of:
          0.0831349 = score(doc=5664,freq=2.0), product of:
            0.17906146 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051133685 = queryNorm
            0.46428138 = fieldWeight in 5664, 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=5664)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Date

10.11.1996 16:36:22