Search (95 results, page 1 of 5)

0.14800835 = product of:
  0.74004173 = sum of:
    0.74004173 = weight(_text_:pmh in 4166) [ClassicSimilarity], result of:
      0.74004173 = score(doc=4166,freq=4.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        1.8297744 = fieldWeight in 4166, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.109375 = fieldNorm(doc=4166)
  0.2 = coord(1/5)

Object

OAI-PMH

0.123000376 = product of:
  0.30750093 = sum of:
    0.26164427 = weight(_text_:pmh in 4772) [ClassicSimilarity], result of:
      0.26164427 = score(doc=4772,freq=2.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.64692295 = fieldWeight in 4772, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4772)
    0.045856647 = weight(_text_:22 in 4772) [ClassicSimilarity], result of:
      0.045856647 = score(doc=4772,freq=2.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.2708308 = fieldWeight in 4772, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4772)
  0.4 = coord(2/5)

Abstract

The Open Archives Initiative (OAI) was created as a practical way to promote interoperability between e-print repositories. Although the scope of the OAI has been broadened, e-print repositories still represent a significant fraction of OAI data providers. This article presents a brief survey of OAI e-print repositories, and of services using metadata harvested from e-print repositories using the OAI protocol for metadata harvesting (OAI-PMH). It then discusses several situations where metadata harvesting may be used to further improve the utility of e-print archives as a component of the scholarly communication infrastructure.

Date

18.12.2005 13:18:22

0.118670695 = product of:
  0.59335345 = sum of:
    0.59335345 = weight(_text_:pmh in 3340) [ClassicSimilarity], result of:
      0.59335345 = score(doc=3340,freq=14.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        1.4670835 = fieldWeight in 3340, product of:
          3.7416575 = tf(freq=14.0), with freq of:
            14.0 = termFreq=14.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.046875 = fieldNorm(doc=3340)
  0.2 = coord(1/5)

Abstract

The Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) is an evolving protocol and philosophy regarding interoperability for digital libraries (DLs). Previously, "distributed searching" models were popular for DL interoperability. However, experience has shown distributed searching systems across large numbers of DLs to be difficult to maintain in an Internet environment. The OAI-PMH is a move away from distributed searching, focusing on the arguably simpler model of "metadata harvesting". We detail NASA's involvement in defining and testing the OAI-PMH and experience to date with adapting existing NASA distributed searching DLs (such as the NASA Technical Report Server) to use the OAI-PMH and metadata harvesting. We discuss some of the entirely new DL projects that the OAI-PMH has made possible, such as the Technical Report Interchange Project. We explain the strategic importance of the OAI-PMH to the mission of NASA's Scientific and Technical Information Program.

Object

OAI-PMH

0.07768821 = product of:
  0.38844103 = sum of:
    0.38844103 = weight(_text_:pmh in 4776) [ClassicSimilarity], result of:
      0.38844103 = score(doc=4776,freq=6.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.9604316 = fieldWeight in 4776, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.046875 = fieldNorm(doc=4776)
  0.2 = coord(1/5)

Abstract

OAIster, at the University of Michigan, University Libraries, Digital Library Production Service (DLPS), is an Andrew W. Mellon Foundation grant-funded project designed to test the feasibility of using the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH) to harvest digital object metadata from multiple and varied digital object repositories and develop a service to allow end-users to access that metadata. This article describes in-depth the development of our system to harvest, store, transform the metadata into Digital Library eXtension Service (DLXS) Bibliographic Class format, build indexes and make the metadata searchable through an interface using the XPAT search engine. Results of the testing of our service and statistics on usage are reported, as well as the issues that we have encountered during our harvesting and transformation operations. The article closes by discussing the future improvements and potential of OAIster and the OAI-PMH protocol.

Object

OAI-PMH

0.06343215 = product of:
  0.31716076 = sum of:
    0.31716076 = weight(_text_:pmh in 4771) [ClassicSimilarity], result of:
      0.31716076 = score(doc=4771,freq=4.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.78418905 = fieldWeight in 4771, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.046875 = fieldNorm(doc=4771)
  0.2 = coord(1/5)

Abstract

The authors, who jointly serve as the Open Archives Initiative (OAI) executive, reflect an the three-year history of the OAI. Three years of technical work recently culminated in the release of a stabie production version 2 of the OAI Protocol for Metadata Harvesting (OAI-PMH). This technical product, the work that led up to it, and the process that made it possible have attracted some favor from the digital library and information community. The paper explores a number of factors in the history of the OAI that the authors believe have contributed to this positive response. The factors include focus an a defined problem Statement, an operational model in which strong leadership is balanced with solicited participation, a healthy dose of community building and Support, and sensible technical decisions.

Object

OAI-PMH

0.06343215 = product of:
  0.31716076 = sum of:
    0.31716076 = weight(_text_:pmh in 4777) [ClassicSimilarity], result of:
      0.31716076 = score(doc=4777,freq=4.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.78418905 = fieldWeight in 4777, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.046875 = fieldNorm(doc=4777)
  0.2 = coord(1/5)

Abstract

The MetaScholar Initiative is a collaborative endeavor to explore the feasibility and utility of scholarly portal services developed in conjunction with Open Archives Initiative (OAI) metadata harvesting technologies. The MetaScholar Initiative comprises two projects, the MetaArchive and AmericanSouth projects, both funded by grants from the Andrew W. Mellon Foundation totaling $600,000. These two projects have created two metadata aggregation networks connecting some 24 libraries, archives, museums, and electronic text centers. Each network has an associated portal being created under the guidance of teams composed of scholars, librarians, archivists, and technologists. The MetaScholar Initiative is studying issues such as metadata normalization, alternative forms of scholarly communication through portals, and the process of facilitating smaller archival institutions in providing better access to their collections through the OAI Protocol for Metadata Harvesting (OAI-PMH). The MetaScholar Initiative is based at Emory University in Atlanta, Georgia.

Object

OAI-PMH

0.0448533 = product of:
  0.2242665 = sum of:
    0.2242665 = weight(_text_:pmh in 4773) [ClassicSimilarity], result of:
      0.2242665 = score(doc=4773,freq=2.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.55450535 = fieldWeight in 4773, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.046875 = fieldNorm(doc=4773)
  0.2 = coord(1/5)

Object

OAI-PMH

0.0448533 = product of:
  0.2242665 = sum of:
    0.2242665 = weight(_text_:pmh in 4775) [ClassicSimilarity], result of:
      0.2242665 = score(doc=4775,freq=2.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.55450535 = fieldWeight in 4775, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.046875 = fieldNorm(doc=4775)
  0.2 = coord(1/5)

Object

OAI-PMH

0.0448533 = product of:
  0.2242665 = sum of:
    0.2242665 = weight(_text_:pmh in 4778) [ClassicSimilarity], result of:
      0.2242665 = score(doc=4778,freq=2.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.55450535 = fieldWeight in 4778, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.046875 = fieldNorm(doc=4778)
  0.2 = coord(1/5)

Object

OAI-PMH

0.037377752 = product of:
  0.18688875 = sum of:
    0.18688875 = weight(_text_:pmh in 2986) [ClassicSimilarity], result of:
      0.18688875 = score(doc=2986,freq=2.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.4620878 = fieldWeight in 2986, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2986)
  0.2 = coord(1/5)

Abstract

Current institutional repository software provides few tools to help metadata librarians understand and analyse their collections. In this paper, we compare and contrast metadata analysis tools that were developed simultaneously, but independently, at two New Zealand institutions during a period of national investment in research repositories: the Metadata Analysis Tool (MAT) at The University of Waikato, and the Kiwi Research Information Service (KRIS) at the National Library of New Zealand. The tools have many similarities: they are convenient, online, on-demand services that harvest metadata using OAI-PMH, they were developed in response to feedback from repository administrators, and they both help pinpoint specific metadata errors as well as generating summary statistics. They also have significant differences: one is a dedicated tool while the other is part of a wider access tool; one gives a holistic view of the metadata while the other looks for specific problems; one seeks patterns in the data values while the other checks that those values conform to metadata standards. Both tools work in a complementary manner to existing web-based administration tools. We have observed that discovery and correction of metadata errors can be quickly achieved by switching web browser views from the analysis tool to the repository interface, and back. We summarise the findings from both tools' deployment into a checklist of requirements for metadata analysis tools.

0.026430065 = product of:
  0.13215032 = sum of:
    0.13215032 = weight(_text_:pmh in 3173) [ClassicSimilarity], result of:
      0.13215032 = score(doc=3173,freq=4.0), product of:
        0.40444425 = queryWeight, product of:
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.048351415 = queryNorm
        0.32674545 = fieldWeight in 3173, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          8.364683 = idf(docFreq=27, maxDocs=44218)
          0.01953125 = fieldNorm(doc=3173)
  0.2 = coord(1/5)

Abstract

The integration of metadata from distinct, heterogeneous data sources requires metadata interoperability, which is a qualitative property of metadata information objects that is not given by default. The technique of metadata mapping allows domain experts to establish metadata interoperability in a certain integration scenario. Mapping solutions, as a technical manifestation of this technique, are already available for the intensively studied domain of database system interoperability, but they rarely exist for the Web. If we consider the amount of steadily increasing structured metadata and corresponding metadata schemes on theWeb, we can observe a clear need for a mapping solution that can operate in aWeb-based environment. To achieve that, we first need to build its technical core, which is a mapping model that provides the language primitives to define mapping relationships. Existing SemanticWeb languages such as RDFS and OWL define some basic mapping elements (e.g., owl:equivalentProperty, owl:sameAs), but do not address the full spectrum of semantic and structural heterogeneities that can occur among distinct, incompatible metadata information objects. Furthermore, it is still unclear how to process defined mapping relationships during run-time in order to deliver metadata to the client in a uniform way. As the main contribution of this thesis, we present an abstract mapping model, which reflects the mapping problem on a generic level and provides the means for reconciling incompatible metadata. Instance transformation functions and URIs take a central role in that model. The former cover a broad spectrum of possible structural and semantic heterogeneities, while the latter bind the complete mapping model to the architecture of the Word Wide Web. On the concrete, language-specific level we present a binding of the abstract mapping model for the RDF Vocabulary Description Language (RDFS), which allows us to create mapping specifications among incompatible metadata schemes expressed in RDFS. The mapping model is embedded in a cyclic process that categorises the requirements a mapping solution should fulfil into four subsequent phases: mapping discovery, mapping representation, mapping execution, and mapping maintenance. In this thesis, we mainly focus on mapping representation and on the transformation of mapping specifications into executable SPARQL queries. For mapping discovery support, the model provides an interface for plugging-in schema and ontology matching algorithms. For mapping maintenance we introduce the concept of a simple, but effective mapping registry. Based on the mapping model, we propose aWeb-based mediator wrapper-architecture that allows domain experts to set up mediation endpoints that provide a uniform SPARQL query interface to a set of distributed metadata sources. The involved data sources are encapsulated by wrapper components that expose the contained metadata and the schema definitions on the Web and provide a SPARQL query interface to these metadata. In this thesis, we present the OAI2LOD Server, a wrapper component for integrating metadata that are accessible via the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH). In a case study, we demonstrate how mappings can be created in aWeb environment and how our mediator wrapper architecture can easily be configured in order to integrate metadata from various heterogeneous data sources without the need to install any mapping solution or metadata integration solution in a local system environment.

Content

Die Integration von Metadaten aus unterschiedlichen, heterogenen Datenquellen erfordert Metadaten-Interoperabilität, eine Eigenschaft die nicht standardmäßig gegeben ist. Metadaten Mapping Verfahren ermöglichen es Domänenexperten Metadaten-Interoperabilität in einem bestimmten Integrationskontext herzustellen. Mapping Lösungen sollen dabei die notwendige Unterstützung bieten. Während diese für den etablierten Bereich interoperabler Datenbanken bereits existieren, ist dies für Web-Umgebungen nicht der Fall. Betrachtet man das Ausmaß ständig wachsender strukturierter Metadaten und Metadatenschemata im Web, so zeichnet sich ein Bedarf nach Web-basierten Mapping Lösungen ab. Den Kern einer solchen Lösung bildet ein Mappingmodell, das die zur Spezifikation von Mappings notwendigen Sprachkonstrukte definiert. Existierende Semantic Web Sprachen wie beispielsweise RDFS oder OWL bieten zwar grundlegende Mappingelemente (z.B.: owl:equivalentProperty, owl:sameAs), adressieren jedoch nicht das gesamte Sprektrum möglicher semantischer und struktureller Heterogenitäten, die zwischen unterschiedlichen, inkompatiblen Metadatenobjekten auftreten können. Außerdem fehlen technische Lösungsansätze zur Überführung zuvor definierter Mappings in ausfu¨hrbare Abfragen. Als zentraler wissenschaftlicher Beitrag dieser Dissertation, wird ein abstraktes Mappingmodell pr¨asentiert, welches das Mappingproblem auf generischer Ebene reflektiert und Lösungsansätze zum Abgleich inkompatibler Schemata bietet. Instanztransformationsfunktionen und URIs nehmen in diesem Modell eine zentrale Rolle ein. Erstere überbrücken ein breites Spektrum möglicher semantischer und struktureller Heterogenitäten, während letztere das Mappingmodell in die Architektur des World Wide Webs einbinden. Auf einer konkreten, sprachspezifischen Ebene wird die Anbindung des abstrakten Modells an die RDF Vocabulary Description Language (RDFS) präsentiert, wodurch ein Mapping zwischen unterschiedlichen, in RDFS ausgedrückten Metadatenschemata ermöglicht wird. Das Mappingmodell ist in einen zyklischen Mappingprozess eingebunden, der die Anforderungen an Mappinglösungen in vier aufeinanderfolgende Phasen kategorisiert: mapping discovery, mapping representation, mapping execution und mapping maintenance. Im Rahmen dieser Dissertation beschäftigen wir uns hauptsächlich mit der Representation-Phase sowie mit der Transformation von Mappingspezifikationen in ausführbare SPARQL-Abfragen. Zur Unterstützung der Discovery-Phase bietet das Mappingmodell eine Schnittstelle zur Einbindung von Schema- oder Ontologymatching-Algorithmen. Für die Maintenance-Phase präsentieren wir ein einfaches, aber seinen Zweck erfüllendes Mapping-Registry Konzept. Auf Basis des Mappingmodells stellen wir eine Web-basierte Mediator-Wrapper Architektur vor, die Domänenexperten die Möglichkeit bietet, SPARQL-Mediationsschnittstellen zu definieren. Die zu integrierenden Datenquellen müssen dafür durch Wrapper-Komponenen gekapselt werden, welche die enthaltenen Metadaten im Web exponieren und SPARQL-Zugriff ermöglichen. Als beipielhafte Wrapper Komponente präsentieren wir den OAI2LOD Server, mit dessen Hilfe Datenquellen eingebunden werden können, die ihre Metadaten über das Open Archives Initative Protocol for Metadata Harvesting (OAI-PMH) exponieren. Im Rahmen einer Fallstudie zeigen wir, wie Mappings in Web-Umgebungen erstellt werden können und wie unsere Mediator-Wrapper Architektur nach wenigen, einfachen Konfigurationsschritten Metadaten aus unterschiedlichen, heterogenen Datenquellen integrieren kann, ohne dass dadurch die Notwendigkeit entsteht, eine Mapping Lösung in einer lokalen Systemumgebung zu installieren.

0.022234662 = product of:
  0.1111733 = sum of:
    0.1111733 = weight(_text_:22 in 5743) [ClassicSimilarity], result of:
      0.1111733 = score(doc=5743,freq=4.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.6565931 = fieldWeight in 5743, 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=5743)
  0.2 = coord(1/5)

Date

30. 3.2002 19:45:22

Source

Revista Española de Documentaçion Cientifica. 22(1999) no.2, S.198-219

0.02096304 = product of:
  0.10481519 = sum of:
    0.10481519 = weight(_text_:22 in 4899) [ClassicSimilarity], result of:
      0.10481519 = score(doc=4899,freq=2.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.61904186 = fieldWeight in 4899, 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=4899)
  0.2 = coord(1/5)

Date

16. 7.2000 20:58:22

0.02096304 = product of:
  0.10481519 = sum of:
    0.10481519 = weight(_text_:22 in 2840) [ClassicSimilarity], result of:
      0.10481519 = score(doc=2840,freq=2.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.61904186 = fieldWeight in 2840, 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=2840)
  0.2 = coord(1/5)

Source

Library hi tech. 22(2004) no.1

0.018342659 = product of:
  0.091713294 = sum of:
    0.091713294 = weight(_text_:22 in 4407) [ClassicSimilarity], result of:
      0.091713294 = score(doc=4407,freq=2.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.5416616 = fieldWeight in 4407, 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=4407)
  0.2 = coord(1/5)

Date

28. 3.2002 9:22:34

0.018342659 = product of:
  0.091713294 = sum of:
    0.091713294 = weight(_text_:22 in 7196) [ClassicSimilarity], result of:
      0.091713294 = score(doc=7196,freq=2.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.5416616 = fieldWeight in 7196, 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=7196)
  0.2 = coord(1/5)

Source

Library hi tech. 22(2004) no.1

0.018342659 = product of:
  0.091713294 = sum of:
    0.091713294 = weight(_text_:22 in 2841) [ClassicSimilarity], result of:
      0.091713294 = score(doc=2841,freq=2.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.5416616 = fieldWeight in 2841, 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=2841)
  0.2 = coord(1/5)

Source

Library hi tech. 22(2004) no.2

0.015722279 = product of:
  0.07861139 = sum of:
    0.07861139 = weight(_text_:22 in 6048) [ClassicSimilarity], result of:
      0.07861139 = score(doc=6048,freq=2.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.46428138 = fieldWeight in 6048, 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=6048)
  0.2 = coord(1/5)

Date

22. 9.2007 15:41:14

0.014823108 = product of:
  0.07411554 = sum of:
    0.07411554 = weight(_text_:22 in 2408) [ClassicSimilarity], result of:
      0.07411554 = score(doc=2408,freq=4.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.4377287 = fieldWeight in 2408, 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=2408)
  0.2 = coord(1/5)

Date

13. 1.2007 18:31:22

Source

Cataloging and classification quarterly. 22(1996) nos.3/4, S.43-58

0.014823108 = product of:
  0.07411554 = sum of:
    0.07411554 = weight(_text_:22 in 2845) [ClassicSimilarity], result of:
      0.07411554 = score(doc=2845,freq=4.0), product of:
        0.16931842 = queryWeight, product of:
          3.5018296 = idf(docFreq=3622, maxDocs=44218)
          0.048351415 = queryNorm
        0.4377287 = fieldWeight in 2845, 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=2845)
  0.2 = coord(1/5)

Date

9.12.2005 19:22:38

Source

Library hi tech. 22(2004) no.2, S.175-181