Search (18 results, page 1 of 1)

0.04233017 = product of:
  0.253981 = sum of:
    0.21004635 = weight(_text_:verteilte in 5748) [ClassicSimilarity], result of:
      0.21004635 = score(doc=5748,freq=2.0), product of:
        0.21036641 = queryWeight, product of:
          6.45514 = idf(docFreq=188, maxDocs=44218)
          0.032588977 = queryNorm
        0.99847853 = fieldWeight in 5748, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.45514 = idf(docFreq=188, maxDocs=44218)
          0.109375 = fieldNorm(doc=5748)
    0.043934636 = weight(_text_:internet in 5748) [ClassicSimilarity], result of:
      0.043934636 = score(doc=5748,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.45665127 = fieldWeight in 5748, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.109375 = fieldNorm(doc=5748)
  0.16666667 = coord(2/12)

Theme

Internet
Verteilte bibliographische Datenbanken

0.015919631 = product of:
  0.095517784 = sum of:
    0.060013242 = weight(_text_:verteilte in 1256) [ClassicSimilarity], result of:
      0.060013242 = score(doc=1256,freq=2.0), product of:
        0.21036641 = queryWeight, product of:
          6.45514 = idf(docFreq=188, maxDocs=44218)
          0.032588977 = queryNorm
        0.28527957 = fieldWeight in 1256, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.45514 = idf(docFreq=188, maxDocs=44218)
          0.03125 = fieldNorm(doc=1256)
    0.035504546 = weight(_text_:internet in 1256) [ClassicSimilarity], result of:
      0.035504546 = score(doc=1256,freq=16.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.36902997 = fieldWeight in 1256, product of:
          4.0 = tf(freq=16.0), with freq of:
            16.0 = termFreq=16.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.03125 = fieldNorm(doc=1256)
  0.16666667 = coord(2/12)

Abstract

This article describes an approach for linking geographically distributed collections of metadata so that they are searchable as a single collection. We describe the infrastructure, which uses standard Internet protocols such as the Lightweight Directory Access Protocol (LDAP) and the Common Indexing Protocol (CIP), to distribute queries, return results, and exchange index information. We discuss the advantages of using linked collections of authoritative metadata as an alternative to using a keyword indexing search-engine for resource discovery. We examine other architectures that use metadata for resource discovery, such as Dienst/NCSTRL, the AHDS HTTP/Z39.50 Gateway, and the ROADS initiative. Finally, we discuss research issues and future directions of the project. The Internet Scout Project, which is funded by the National Science Foundation and is located in the Computer Sciences Department at the University of Wisconsin-Madison, is charged with assisting the higher education community in resource discovery on the Internet. To that end, the Scout Report and subsequent subject-specific Scout Reports were developed to guide the U.S. higher education community to research-quality resources. The Scout Report Signpost utilizes the content from the Scout Reports as the basis of a metadata collection. Signpost consists of more than 2000 cataloged Internet sites using established standards such as Library of Congress subject headings and abbreviated call letters, and emerging standards such as the Dublin Core (DC). This searchable and browseable collection is free and freely accessible, as are all of the Internet Scout Project's services.
As well developed as both the Scout Reports and Signpost are, they cannot capture the wealth of high-quality content that is available on the Internet. An obvious next step toward increasing the usefulness of our own collection and its value to our customer base is to partner with other high-quality content providers who have developed similar collections and to develop a single, virtual collection. Project Isaac (working title) is the Internet Scout Project's latest resource discovery effort. Project Isaac involves the development of a research testbed that allows experimentation with protocols and algorithms for creating, maintaining, indexing and searching distributed collections of metadata. Project Isaac's infrastructure uses standard Internet protocols, such as the Lightweight Directory Access Protocol (LDAP) and the Common Indexing Protocol (CIP) to distribute queries, return results, and exchange index or centroid information. The overall goal is to support a single-search interface to geographically distributed and independently maintained metadata collections.

Theme

Verteilte bibliographische Datenbanken

0.0081712045 = product of:
  0.098054454 = sum of:
    0.098054454 = product of:
      0.19610891 = sum of:
        0.19610891 = weight(_text_:vernetzung in 4462) [ClassicSimilarity], result of:
          0.19610891 = score(doc=4462,freq=2.0), product of:
            0.20326729 = queryWeight, product of:
              6.237302 = idf(docFreq=234, maxDocs=44218)
              0.032588977 = queryNorm
            0.96478343 = fieldWeight in 4462, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.237302 = idf(docFreq=234, maxDocs=44218)
              0.109375 = fieldNorm(doc=4462)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

0.004184251 = product of:
  0.050211012 = sum of:
    0.050211012 = weight(_text_:internet in 5971) [ClassicSimilarity], result of:
      0.050211012 = score(doc=5971,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.5218872 = fieldWeight in 5971, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.125 = fieldNorm(doc=5971)
  0.083333336 = coord(1/12)

Theme

Internet

0.004184251 = product of:
  0.050211012 = sum of:
    0.050211012 = weight(_text_:internet in 5973) [ClassicSimilarity], result of:
      0.050211012 = score(doc=5973,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.5218872 = fieldWeight in 5973, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.125 = fieldNorm(doc=5973)
  0.083333336 = coord(1/12)

Theme

Internet

0.004184251 = product of:
  0.050211012 = sum of:
    0.050211012 = weight(_text_:internet in 5974) [ClassicSimilarity], result of:
      0.050211012 = score(doc=5974,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.5218872 = fieldWeight in 5974, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.125 = fieldNorm(doc=5974)
  0.083333336 = coord(1/12)

Theme

Internet

0.0040856022 = product of:
  0.049027227 = sum of:
    0.049027227 = product of:
      0.098054454 = sum of:
        0.098054454 = weight(_text_:vernetzung in 498) [ClassicSimilarity], result of:
          0.098054454 = score(doc=498,freq=2.0), product of:
            0.20326729 = queryWeight, product of:
              6.237302 = idf(docFreq=234, maxDocs=44218)
              0.032588977 = queryNorm
            0.48239172 = fieldWeight in 498, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              6.237302 = idf(docFreq=234, maxDocs=44218)
              0.0546875 = fieldNorm(doc=498)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Abstract

"Veränderungen sind nur das Salz des Vergnügens"- dieses Zitat aus Friedrich Schillers "Kabale und Liebe" bildete die Klammer der 38. Tagung der Arbeitsgemeinschaft der Spezialbibliotheken (ASpB), die im 75. Jahr ihres Bestehens stattfand. Im Folgenden wird ein Überblick über die Vorträge und Diskussionen des zweiten Panels gegeben, das ebenso wie die anderen Panels nach literarischen Werken benannt wurde: Wilhelm Genazinos Drama "Im Dickicht der Einzelheiten" steht als Überschrift für die künftige Erschließung in Spezialbibliotheken zwischen Vernetzung und Automatisierung. Moderiert wurde das Panel von Karin Schmidgall vom Deutschen Literaturarchiv Marbach.

0.0036612197 = product of:
  0.043934636 = sum of:
    0.043934636 = weight(_text_:internet in 5972) [ClassicSimilarity], result of:
      0.043934636 = score(doc=5972,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.45665127 = fieldWeight in 5972, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.109375 = fieldNorm(doc=5972)
  0.083333336 = coord(1/12)

Theme

Internet

0.0035639112 = product of:
  0.021383466 = sum of:
    0.012552753 = weight(_text_:internet in 1236) [ClassicSimilarity], result of:
      0.012552753 = score(doc=1236,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.1304718 = fieldWeight in 1236, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.03125 = fieldNorm(doc=1236)
    0.008830713 = product of:
      0.017661426 = sum of:
        0.017661426 = weight(_text_:22 in 1236) [ClassicSimilarity], result of:
          0.017661426 = score(doc=1236,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.15476047 = fieldWeight in 1236, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03125 = fieldNorm(doc=1236)
      0.5 = coord(1/2)
  0.16666667 = coord(2/12)

Abstract

Dublin Core is often presented as a modern form of catalog card -- a set of elements (and now qualifiers) that describe resources in a complete package. Sometimes it is proposed as an exchange format for sharing records among multiple collections. The founding principle that "every element is optional and repeatable" reinforces the notion that a Dublin Core description is to be taken as a whole. This paper, in contrast, is based on a much different premise: Dublin Core is a language. More precisely, it is a small language for making a particular class of statements about resources. Like natural languages, it has a vocabulary of word-like terms, the two classes of which -- elements and qualifiers -- function within statements like nouns and adjectives; and it has a syntax for arranging elements and qualifiers into statements according to a simple pattern. Whenever tourists order a meal or ask directions in an unfamiliar language, considerate native speakers will spontaneously limit themselves to basic words and simple sentence patterns along the lines of "I am so-and-so" or "This is such-and-such". Linguists call this pidginization. In such situations, a small phrase book or translated menu can be most helpful. By analogy, today's Web has been called an Internet Commons where users and information providers from a wide range of scientific, commercial, and social domains present their information in a variety of incompatible data models and description languages. In this context, Dublin Core presents itself as a metadata pidgin for digital tourists who must find their way in this linguistically diverse landscape. Its vocabulary is small enough to learn quickly, and its basic pattern is easily grasped. It is well-suited to serve as an auxiliary language for digital libraries. This grammar starts by defining terms. It then follows a 200-year-old tradition of English grammar teaching by focusing on the structure of single statements. It concludes by looking at the growing dictionary of Dublin Core vocabulary terms -- its registry, and at how statements can be used to build the metadata equivalent of paragraphs and compositions -- the application profile.

Date

26.12.2011 14:01:22

0.0031381883 = product of:
  0.03765826 = sum of:
    0.03765826 = weight(_text_:internet in 6798) [ClassicSimilarity], result of:
      0.03765826 = score(doc=6798,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.3914154 = fieldWeight in 6798, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.09375 = fieldNorm(doc=6798)
  0.083333336 = coord(1/12)

Theme

Internet

0.0031381883 = product of:
  0.03765826 = sum of:
    0.03765826 = weight(_text_:internet in 1747) [ClassicSimilarity], result of:
      0.03765826 = score(doc=1747,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.3914154 = fieldWeight in 1747, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.09375 = fieldNorm(doc=1747)
  0.083333336 = coord(1/12)

Theme

Internet

0.0022076783 = product of:
  0.02649214 = sum of:
    0.02649214 = product of:
      0.05298428 = sum of:
        0.05298428 = weight(_text_:22 in 6048) [ClassicSimilarity], result of:
          0.05298428 = score(doc=6048,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = 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.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

22. 9.2007 15:41:14

0.0018306099 = product of:
  0.021967318 = sum of:
    0.021967318 = weight(_text_:internet in 2795) [ClassicSimilarity], result of:
      0.021967318 = score(doc=2795,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.22832564 = fieldWeight in 2795, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2795)
  0.083333336 = coord(1/12)

Abstract

The Dublin Core Metadata Initiative continues to grow in participation and recognition as the predominant resource discovery metadata standard on the Internet. With its approval as ISO 15836, DC is firmly established as a foundation block of modular, interoperable metadata for distributed resources. This report summarizes developments in DCMI over the past year, including the annual conference, progress of working groups, new developments in encoding methods, and advances in documentation and dissemination. New developments in broadening the community to commercial users of metadata are discussed, and plans for an international network of national affiliates are described.

0.0014717856 = product of:
  0.017661426 = sum of:
    0.017661426 = product of:
      0.035322852 = sum of:
        0.035322852 = weight(_text_:22 in 2686) [ClassicSimilarity], result of:
          0.035322852 = score(doc=2686,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.30952093 = fieldWeight in 2686, 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=2686)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

10. 9.2004 10:22:40

0.0013075785 = product of:
  0.015690941 = sum of:
    0.015690941 = weight(_text_:internet in 1176) [ClassicSimilarity], result of:
      0.015690941 = score(doc=1176,freq=2.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.16308975 = fieldWeight in 1176, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1176)
  0.083333336 = coord(1/12)

Abstract

The rapid growth of Internet resources and digital collections has been accompanied by a proliferation of metadata schemas, each of which has been designed based on the requirements of particular user communities, intended users, types of materials, subject domains, project needs, etc. Problems arise when building large digital libraries or repositories with metadata records that were prepared according to diverse schemas. This article (published in two parts) contains an analysis of the methods that have been used to achieve or improve interoperability among metadata schemas and applications, for the purposes of facilitating conversion and exchange of metadata and enabling cross-domain metadata harvesting and federated searches. From a methodological point of view, implementing interoperability may be considered at different levels of operation: schema level, record level, and repository level. Part I of the article intends to explain possible situations in which metadata schemas may be created or implemented, whether in individual projects or in integrated repositories. It also discusses approaches used at the schema level. Part II of the article will discuss metadata interoperability efforts at the record and repository levels.

0.0011038391 = product of:
  0.01324607 = sum of:
    0.01324607 = product of:
      0.02649214 = sum of:
        0.02649214 = weight(_text_:22 in 266) [ClassicSimilarity], result of:
          0.02649214 = score(doc=266,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.23214069 = fieldWeight in 266, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=266)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

22. 5.2021 12:43:05

9.245976E-4 = product of:
  0.011095171 = sum of:
    0.011095171 = weight(_text_:internet in 1216) [ClassicSimilarity], result of:
      0.011095171 = score(doc=1216,freq=4.0), product of:
        0.09621047 = queryWeight, product of:
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.032588977 = queryNorm
        0.11532187 = fieldWeight in 1216, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          2.9522398 = idf(docFreq=6276, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1216)
  0.083333336 = coord(1/12)

Abstract

Reality is messy. Individuals perceive or define objects differently. Objects may change over time, morphing into new versions of their former selves or into things altogether different. A book can give rise to a translation, derivation, or edition, and these resulting objects are related in complex ways to each other and to the people and contexts in which they were created or transformed. Providing a normalized view of such a messy reality is a precondition for managing information. From the first library catalogs, through Melvil Dewey's Decimal Classification system in the nineteenth century, to today's MARC encoding of AACR2 cataloging rules, libraries have epitomized the process of what David Levy calls "order making", whereby catalogers impose a veneer of regularity on the natural disorder of the artifacts they encounter. The pre-digital library within which the Catalog and its standards evolved was relatively self-contained and controlled. Creating and maintaining catalog records was, and still is, the task of professionals. Today's Web, in contrast, has brought together a diversity of information management communities, with a variety of order-making standards, into what Stuart Weibel has called the Internet Commons. The sheer scale of this context has motivated a search for new ways to describe and index information. Second-generation search engines such as Google can yield astonishingly good search results, while tools such as ResearchIndex for automatic citation indexing and techniques for inferring "Web communities" from constellations of hyperlinks promise even better methods for focusing queries on information from authoritative sources. Such "automated digital libraries," according to Bill Arms, promise to radically reduce the cost of managing information. Alongside the development of such automated methods, there is increasing interest in metadata as a means of imposing pre-defined order on Web content. While the size and changeability of the Web makes professional cataloging impractical, a minimal amount of information ordering, such as that represented by the Dublin Core (DC), may vastly improve the quality of an automatic index at low cost; indeed, recent work suggests that some types of simple description may be generated with little or no human intervention.
At the time of writing, the Dublin Core Metadata Initiative (DCMI) has clarified its commitment to the simple approach. The qualification principles announced in early 2000 support the use of DC elements as the basis for simple statements about resources, rather than as the foundation for more descriptive clauses. This paper takes a critical look at some of the issues that led up to this renewed commitment to simplicity. We argue that: * There remains a compelling need for simple, "pidgin" metadata. From a technical and economic perspective, document-centric metadata, where simple string values are associated with a finite set of properties, is most appropriate for generic, cross-domain discovery queries in the Internet Commons. Such metadata is not necessarily fixed in physical records, but may be projected algorithmically from more complex metadata or from content itself. * The Dublin Core, while far from perfect from an engineering perspective, is an acceptable standard for such simple metadata. Agreements in the global information space are as much social as technical, and the process by which the Dublin Core has been developed, involving a broad cross-section of international participants, is a model for such "socially developed" standards. * Efforts to introduce complexity into Dublin Core are misguided. Complex descriptions may be necessary for some Web resources and for some purposes, such as administration, preservation, and reference linking. However, complex descriptions require more expressive data models that differentiate between agents, documents, contexts, events, and the like. An attempt to intermix simplicity and complexity, and the data models most appropriate for them, defeats the equally noble goals of cross-domain description and extensive resource description. * The principle of modularity suggests that metadata formats tailored for simplicity be used alongside others tailored for complexity.

9.19866E-4 = product of:
  0.011038392 = sum of:
    0.011038392 = product of:
      0.022076784 = sum of:
        0.022076784 = weight(_text_:22 in 4550) [ClassicSimilarity], result of:
          0.022076784 = score(doc=4550,freq=2.0), product of:
            0.11412105 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.032588977 = queryNorm
            0.19345059 = fieldWeight in 4550, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0390625 = fieldNorm(doc=4550)
      0.5 = coord(1/2)
  0.083333336 = coord(1/12)

Date

10.11.2018 16:27:22