Search (53 results, page 3 of 3)

0.0021217826 = product of:
  0.029704956 = sum of:
    0.029704956 = weight(_text_:subject in 1624) [ClassicSimilarity], result of:
      0.029704956 = score(doc=1624,freq=2.0), product of:
        0.10738805 = queryWeight, product of:
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.03002521 = queryNorm
        0.27661324 = fieldWeight in 1624, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1624)
  0.071428575 = coord(1/14)

Abstract

Discusses a range of professional librarians' opinions on the urgent need either to adopt or replace the current cataloguing rules, a theme closely linked to the identity crisis facing libraries and librarians in the online electronic era. Topics examined include: Gorman and Oddy's views on restructuring AACR principles; the 13 metadata elements contained in the Dublin Core document (1995); catalogue search by known item; keyword search versus subject search; and the US Library of Congress's Program for cooperation cataloging

0.0021217826 = product of:
  0.029704956 = sum of:
    0.029704956 = weight(_text_:subject in 5180) [ClassicSimilarity], result of:
      0.029704956 = score(doc=5180,freq=2.0), product of:
        0.10738805 = queryWeight, product of:
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.03002521 = queryNorm
        0.27661324 = fieldWeight in 5180, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5180)
  0.071428575 = coord(1/14)

Abstract

The Science & Society Picture Library (SSPL) has been established to market the images of 3 of Britain's museums: the Science Museum in London, the National Railway Museum in York, and the National Museum of Photography, Film and Television in Bradford - collectively called the National Museum of Science and Industry). The images are drawn from many different collections within these museums and, as a result, SSPL represents one of the widest varieties of photographs, paintings, prints, posters and objects in the world. Discusses issues surrounding the SSPL's current task of developing an integrated cataloguing and indexing strategy by which metadata construction can proceed, and which will provide potential users with effective and standardized subject access to the many components of its holding

0.0020356115 = product of:
  0.02849856 = sum of:
    0.02849856 = product of:
      0.05699712 = sum of:
        0.05699712 = weight(_text_:schemes in 6921) [ClassicSimilarity], result of:
          0.05699712 = score(doc=6921,freq=2.0), product of:
            0.16067243 = queryWeight, product of:
              5.3512506 = idf(docFreq=569, maxDocs=44218)
              0.03002521 = queryNorm
            0.35474116 = fieldWeight in 6921, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.3512506 = idf(docFreq=569, maxDocs=44218)
              0.046875 = fieldNorm(doc=6921)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Abstract

Defines metadata, which for librarians means catalogue records for printed publications, and the need for them in document retrieval. The existence of many different sources of metadata had led to a need for simpler metadata schemes and a stadardised exchange format. The 1st Metadata Workshop, held in Dublin, Ohio, reached consensus on a simple resource description record, known as the Dublin core set, with 13 elements, which can serve to unify various models. Lists institutions intending to use it. The 2nd workshop resulted in a proposal for a container record architecture comprising more and different types of metadata than a Dublin core record. The Nordic Metadata project, outlined here, aims to improve the knowledge transfer to the Nordic countries and allow them to paricipate actively in international developments

0.0020356115 = product of:
  0.02849856 = sum of:
    0.02849856 = product of:
      0.05699712 = sum of:
        0.05699712 = weight(_text_:schemes in 4053) [ClassicSimilarity], result of:
          0.05699712 = score(doc=4053,freq=2.0), product of:
            0.16067243 = queryWeight, product of:
              5.3512506 = idf(docFreq=569, maxDocs=44218)
              0.03002521 = queryNorm
            0.35474116 = fieldWeight in 4053, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.3512506 = idf(docFreq=569, maxDocs=44218)
              0.046875 = fieldNorm(doc=4053)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Abstract

Within a digital library, collections may range from an ad hoc set of objects that serve a temporary purpose to established library collections intended to persist through time. The objects in these collections vary widely, from library and data center holdings to pointers to real-world objects, such as geographic places, and the various metadata schemes that describe them. The key to integrated use of such a variety of collections in a digital library is collection metadata that represents the inherent and contextual characteristics of a collection. The Alexandria Digital Library (ADL) Project has designed and implemented collection metadata for several purposes: in XML form, the collection metadatada 'registers' the collection with the user interface client; in HTML form, it is used for user documentation; eventually, it will be used to describe the collection to network search agents; and it is used for internal collection management, including mapping the object metadata attributes to the common search parameters of the system

0.0017956087 = product of:
  0.02513852 = sum of:
    0.02513852 = weight(_text_:bibliographic in 1249) [ClassicSimilarity], result of:
      0.02513852 = score(doc=1249,freq=2.0), product of:
        0.11688946 = queryWeight, product of:
          3.893044 = idf(docFreq=2449, maxDocs=44218)
          0.03002521 = queryNorm
        0.21506234 = fieldWeight in 1249, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.893044 = idf(docFreq=2449, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1249)
  0.071428575 = coord(1/14)

Abstract

The Dublin Core metadata community and the INDECS/DOI community of authors, rights holders, and publishers are seeking common ground in the expression of metadata for information resources. Recent meetings at the 6th Dublin Core Workshop in Washington DC sketched out common models for semantics (informed by the requirements articulated in the IFLA Functional Requirements for the Bibliographic Record) and conventions for knowledge representation (based on the Resource Description Framework under development by the W3C). Further development of detailed requirements is planned by both communities in the coming months with the aim of fully representing the metadata needs of each. An open "Schema Harmonization" working group has been established to identify a common framework to support interoperability among these communities. The present document represents a starting point identifying historical developments and common requirements of these perspectives on metadata and charts a path for harmonizing their respective conceptual models. It is hoped that collaboration over the coming year will result in agreed semantic and syntactic conventions that will support a high degree of interoperability among these communities, ideally expressed in a single data model and using common, standard tools.

0.0017146593 = product of:
  0.024005229 = sum of:
    0.024005229 = weight(_text_:subject in 1256) [ClassicSimilarity], result of:
      0.024005229 = score(doc=1256,freq=4.0), product of:
        0.10738805 = queryWeight, product of:
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.03002521 = queryNorm
        0.22353725 = fieldWeight in 1256, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.03125 = fieldNorm(doc=1256)
  0.071428575 = coord(1/14)

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.

0.0014528577 = product of:
  0.020340007 = sum of:
    0.020340007 = product of:
      0.040680014 = sum of:
        0.040680014 = weight(_text_:22 in 1032) [ClassicSimilarity], result of:
          0.040680014 = score(doc=1032,freq=2.0), product of:
            0.10514317 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03002521 = queryNorm
            0.38690117 = fieldWeight in 1032, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=1032)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Date

22. 5.1998 18:45:36

0.0014528577 = product of:
  0.020340007 = sum of:
    0.020340007 = product of:
      0.040680014 = sum of:
        0.040680014 = weight(_text_:22 in 2275) [ClassicSimilarity], result of:
          0.040680014 = score(doc=2275,freq=2.0), product of:
            0.10514317 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03002521 = queryNorm
            0.38690117 = fieldWeight in 2275, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=2275)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Content

Bericht über den Workshop, der am 22. u. 23.6.98 in der SUB Göttingen stattfand

0.0011622861 = product of:
  0.016272005 = sum of:
    0.016272005 = product of:
      0.03254401 = sum of:
        0.03254401 = weight(_text_:22 in 903) [ClassicSimilarity], result of:
          0.03254401 = score(doc=903,freq=2.0), product of:
            0.10514317 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03002521 = queryNorm
            0.30952093 = fieldWeight in 903, 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=903)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Source

Cataloguing Australia. 23(1997) nos.1/2, S.17-22

0.0010608913 = product of:
  0.014852478 = sum of:
    0.014852478 = weight(_text_:subject in 1257) [ClassicSimilarity], result of:
      0.014852478 = score(doc=1257,freq=2.0), product of:
        0.10738805 = queryWeight, product of:
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.03002521 = queryNorm
        0.13830662 = fieldWeight in 1257, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.576596 = idf(docFreq=3361, maxDocs=44218)
          0.02734375 = fieldNorm(doc=1257)
  0.071428575 = coord(1/14)

Abstract

Over the past three years, the Dublin Core Metadata Initiative has achieved a broad international consensus on the semantics of a simple element set for describing electronic resources. Since the first workshop in March 1995, which was reported in the very first issue of D-Lib Magazine, Dublin Core has been the topic of perhaps a dozen articles here. Originally intended to be simple and intuitive enough for authors to tag Web pages without special training, Dublin Core is being adapted now for more specialized uses, from government information and legal deposit to museum informatics and electronic commerce. To meet such specialized requirements, Dublin Core can be customized with additional elements or qualifiers. However, these refinements can compromise interoperability across applications. There are tradeoffs between using specific terms that precisely meet local needs versus general terms that are understood more widely. We can better understand this inevitable tension between simplicity and complexity if we recognize that metadata is a form of human language. With Dublin Core, as with a natural language, people are inclined to stretch definitions, make general terms more specific, specific terms more general, misunderstand intended meanings, and coin new terms. One goal of this paper, therefore, will be to examine the experience of some related ways to seek semantic interoperability through simplicity: planned languages, interlingua constructs, and pidgins. The problem of semantic interoperability is compounded when we consider Dublin Core in translation. All of the workshops, documents, mailing lists, user guides, and working group outputs of the Dublin Core Initiative have been in English. But in many countries and for many applications, people need a metadata standard in their own language. In principle, the broad elements of Dublin Core can be defined equally well in Bulgarian or Hindi. Since Dublin Core is a controlled standard, however, any parallel definitions need to be kept in sync as the standard evolves. Another goal of the paper, then, will be to define the conceptual and organizational problem of maintaining a metadata standard in multiple languages. In addition to a name and definition, which are meant for human consumption, each Dublin Core element has a label, or indexing token, meant for harvesting by search engines. For practical reasons, these machine-readable tokens are English-looking strings such as Creator and Subject (just as HTML tags are called HEAD, BODY, or TITLE). These tokens, which are shared by Dublin Cores in every language, ensure that metadata fields created in any particular language are indexed together across repositories. As symbols of underlying universal semantics, these tokens form the basis of semantic interoperability among the multiple Dublin Cores. As long as we limit ourselves to sharing these indexing tokens among exact translations of a simple set of fifteen broad elements, the definitions of which fit easily onto two pages, the problem of Dublin Core in multiple languages is straightforward. But nothing having to do with human language is ever so simple. Just as speakers of various languages must learn the language of Dublin Core in their own tongues, we must find the right words to talk about a metadata language that is expressable in many discipline-specific jargons and natural languages and that inevitably will evolve and change over time.

0.0010170004 = product of:
  0.014238005 = sum of:
    0.014238005 = product of:
      0.02847601 = sum of:
        0.02847601 = weight(_text_:22 in 2220) [ClassicSimilarity], result of:
          0.02847601 = score(doc=2220,freq=2.0), product of:
            0.10514317 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03002521 = queryNorm
            0.2708308 = fieldWeight in 2220, 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=2220)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Source

Nordinfo Nytt. 1997, nos.3/4, S.10-22

0.0010170004 = product of:
  0.014238005 = sum of:
    0.014238005 = product of:
      0.02847601 = sum of:
        0.02847601 = weight(_text_:22 in 2673) [ClassicSimilarity], result of:
          0.02847601 = score(doc=2673,freq=2.0), product of:
            0.10514317 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03002521 = queryNorm
            0.2708308 = fieldWeight in 2673, 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=2673)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Date

1. 8.1996 22:08:06

0.0010170004 = product of:
  0.014238005 = sum of:
    0.014238005 = product of:
      0.02847601 = sum of:
        0.02847601 = weight(_text_:22 in 3597) [ClassicSimilarity], result of:
          0.02847601 = score(doc=3597,freq=2.0), product of:
            0.10514317 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03002521 = queryNorm
            0.2708308 = fieldWeight in 3597, 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=3597)
      0.5 = coord(1/2)
  0.071428575 = coord(1/14)

Date

1. 8.1996 22:08:06