Search (10 results, page 1 of 1)

0.03181964 = product of:
  0.04772946 = sum of:
    0.036470924 = weight(_text_:management in 1192) [ClassicSimilarity], result of:
      0.036470924 = score(doc=1192,freq=4.0), product of:
        0.17312427 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.051362853 = queryNorm
        0.21066327 = fieldWeight in 1192, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.03125 = fieldNorm(doc=1192)
    0.011258536 = product of:
      0.022517072 = sum of:
        0.022517072 = weight(_text_:system in 1192) [ClassicSimilarity], result of:
          0.022517072 = score(doc=1192,freq=2.0), product of:
            0.16177002 = queryWeight, product of:
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.051362853 = queryNorm
            0.13919188 = fieldWeight in 1192, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.03125 = fieldNorm(doc=1192)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

Abstract

In the June 2003 issue of D-Lib Magazine, Kenney et al. (2003) discuss a comparative study between Cornell's email reference staff and Google's Answers service. This interesting study provided insights on the potential impact of "computing and simple algorithms combined with human intelligence" for library reference services. As mentioned in the Kenney et al. article, Bill Arms (2000) had discussed the possibilities of automated digital libraries in an even earlier D-Lib article. Arms discusses not only automating reference services, but also another library function that seems to inspire lively debates about automation-metadata creation. While intended to illuminate, these debates sometimes generate more heat than light. In an effort to explore the potential for automating metadata generation, the Digital Knowledge Center (DKC) of the Sheridan Libraries at The Johns Hopkins University developed and tested an automated name authority control (ANAC) tool. ANAC represents a component of a digital workflow management system developed in connection with the digital Lester S. Levy Collection of Sheet Music. The evaluation of ANAC followed the spirit of the Kenney et al. study that was, as they stated, "more exploratory than scientific." These ANAC evaluation results are shared with the hope of fostering constructive dialogue and discussions about the potential for semi-automated techniques or frameworks for library functions and services such as metadata creation. The DKC's research agenda emphasizes the development of tools that combine automated processes and human intervention, with the overall goal of involving humans at higher levels of analysis and decision-making. Others have looked at issues regarding the automated generation of metadata. A session at the 2003 Joint Conference on Digital Libraries was devoted to automatic metadata creation, and a session at the 2004 conference addressed automated name disambiguation. Commercial vendors such as OCLC, Marcive, and LTI have long used automated techniques for matching names to Library of Congress authority records. We began developing ANAC as a component of a larger suite of open source tools to support workflow management for digital projects. This article describes the goals for the ANAC tool, provides an overview of the metadata records used for testing, describes the architecture for ANAC, and concludes with discussions of the methodology and evaluation of the experiment comparing human cataloging and ANAC-generated results.

0.018235464 = product of:
  0.05470639 = sum of:
    0.05470639 = weight(_text_:management in 1323) [ClassicSimilarity], result of:
      0.05470639 = score(doc=1323,freq=4.0), product of:
        0.17312427 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.051362853 = queryNorm
        0.31599492 = fieldWeight in 1323, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.046875 = fieldNorm(doc=1323)
  0.33333334 = coord(1/3)

Abstract

Maintaining a library of digital objects of necessaryy requires maintaining metadata about those objects. The metadata necessary for successful management and use of digital objeets is both more extensive than and different from the metadata used for managing collections of printed works and other physical materials. While a library may record descriptive metadata regarding a book in its collection, the book will not dissolve into a series of unconnected pages if the library fails to record structural metadata regarding the book's organization, nor will scholars be unable to evaluate the book's worth if the library fails to note that the book was produced using a Ryobi offset press. The Same cannot be said for a digital version of the saure book. Without structural metadata, the page image or text files comprising the digital work are of little use, and without technical metadata regarding the digitization process, scholars may be unsure of how accurate a reflection of the original the digital version provides. For internal management purposes, a library must have access to appropriate technical metadata in order to periodically refresh and migrate the data, ensuring the durability of valuable resources.

0.015436406 = product of:
  0.023154609 = sum of:
    0.016118024 = weight(_text_:management in 1216) [ClassicSimilarity], result of:
      0.016118024 = score(doc=1216,freq=2.0), product of:
        0.17312427 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.051362853 = queryNorm
        0.09310089 = fieldWeight in 1216, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.01953125 = fieldNorm(doc=1216)
    0.007036585 = product of:
      0.01407317 = sum of:
        0.01407317 = weight(_text_:system in 1216) [ClassicSimilarity], result of:
          0.01407317 = score(doc=1216,freq=2.0), product of:
            0.16177002 = queryWeight, product of:
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.051362853 = queryNorm
            0.08699492 = fieldWeight in 1216, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.01953125 = fieldNorm(doc=1216)
      0.5 = coord(1/2)
  0.6666667 = coord(2/3)

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.

0.013917915 = product of:
  0.041753743 = sum of:
    0.041753743 = product of:
      0.083507486 = sum of:
        0.083507486 = weight(_text_:22 in 6048) [ClassicSimilarity], result of:
          0.083507486 = score(doc=6048,freq=2.0), product of:
            0.17986396 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051362853 = 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.33333334 = coord(1/3)

Date

22. 9.2007 15:41:14

0.010745349 = product of:
  0.032236047 = sum of:
    0.032236047 = weight(_text_:management in 1187) [ClassicSimilarity], result of:
      0.032236047 = score(doc=1187,freq=2.0), product of:
        0.17312427 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.051362853 = queryNorm
        0.18620178 = fieldWeight in 1187, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1187)
  0.33333334 = coord(1/3)

Abstract

In June of this year, I performed my final official duties as part of the Dublin Core Metadata Initiative management team. It is a happy irony to affix a seal on that service in this journal, as both D-Lib Magazine and the Dublin Core celebrate their tenth anniversaries. This essay is a personal reflection on some of the achievements and lessons of that decade. The OCLC-NCSA Metadata Workshop took place in March of 1995, and as we tried to understand what it meant and who would care, D-Lib magazine came into being and offered a natural venue for sharing our work. I recall a certain skepticism when Bill Arms said "We want D-Lib to be the first place people look for the latest developments in digital library research." These were the early days in the evolution of electronic publishing, and the goal was ambitious. By any measure, a decade of high-quality electronic publishing is an auspicious accomplishment, and D-Lib (and its host, CNRI) deserve congratulations for having achieved their goal. I am grateful to have been a contributor. That first DC workshop led to further workshops, a community, a variety of standards in several countries, an ISO standard, a conference series, and an international consortium. Looking back on this evolution is both satisfying and wistful. While I am pleased that the achievements are substantial, the unmet challenges also provide a rich till in which to cultivate insights on the development of digital infrastructure.

0.00927861 = product of:
  0.02783583 = sum of:
    0.02783583 = product of:
      0.05567166 = sum of:
        0.05567166 = weight(_text_:22 in 2686) [ClassicSimilarity], result of:
          0.05567166 = score(doc=2686,freq=2.0), product of:
            0.17986396 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051362853 = 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.33333334 = coord(1/3)

Date

10. 9.2004 10:22:40

0.0075217444 = product of:
  0.022565233 = sum of:
    0.022565233 = weight(_text_:management in 1210) [ClassicSimilarity], result of:
      0.022565233 = score(doc=1210,freq=2.0), product of:
        0.17312427 = queryWeight, product of:
          3.3706124 = idf(docFreq=4130, maxDocs=44218)
          0.051362853 = queryNorm
        0.13034125 = fieldWeight in 1210, 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=1210)
  0.33333334 = coord(1/3)

Abstract

The Semantic Web activity is a W3C project whose goal is to enable a 'cooperative' Web where machines and humans can exchange electronic content that has clear-cut, unambiguous meaning. This vision is based on the automated sharing of metadata terms across Web applications. The declaration of schemas in metadata registries advance this vision by providing a common approach for the discovery, understanding, and exchange of semantics. However, many of the issues regarding registries are not clear, and ideas vary regarding their scope and purpose. Additionally, registry issues are often difficult to describe and comprehend without a working example. This article will explore the role of metadata registries and will describe three prototypes, written by the Dublin Core Metadata Initiative. The article will outline how the prototypes are being used to demonstrate and evaluate application scope, functional requirements, and technology solutions for metadata registries. Metadata schema registries are, in effect, databases of schemas that can trace an historical line back to shared data dictionaries and the registration process encouraged by the ISO/IEC 11179 community. New impetus for the development of registries has come with the development activities surrounding creation of the Semantic Web. The motivation for establishing registries arises from domain and standardization communities, and from the knowledge management community. Examples of current registry activity include:

0.0075056907 = product of:
  0.022517072 = sum of:
    0.022517072 = product of:
      0.045034144 = sum of:
        0.045034144 = weight(_text_:system in 4840) [ClassicSimilarity], result of:
          0.045034144 = score(doc=4840,freq=2.0), product of:
            0.16177002 = queryWeight, product of:
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.051362853 = queryNorm
            0.27838376 = fieldWeight in 4840, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.0625 = fieldNorm(doc=4840)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

In this talk we present a retrieval model based on social ontologies. More specifically, we utilize the Wikipedia category system in order to perform semantic searches. That is, textual input is used to build queries by means of which documents are retrieved which do not necessarily contain any query term but are semantically related to the input text by virtue of their content. We present a desktop which utilizes this search facility in a web-based environment - the so called eHumanities Desktop.

0.0065674796 = product of:
  0.019702438 = sum of:
    0.019702438 = product of:
      0.039404877 = sum of:
        0.039404877 = weight(_text_:system in 1228) [ClassicSimilarity], result of:
          0.039404877 = score(doc=1228,freq=2.0), product of:
            0.16177002 = queryWeight, product of:
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.051362853 = queryNorm
            0.2435858 = fieldWeight in 1228, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.1495528 = idf(docFreq=5152, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1228)
      0.5 = coord(1/2)
  0.33333334 = coord(1/3)

Abstract

Interoperability between digital libraries depends on effective sharing of metadata. Successful sharing of metadata requires common standards for metadata exchange. Previous efforts have focused on either defining a single metadata standard, such as Dublin Core, or building digital library middleware, such as Z39.50 or Stanford's Digital Library Interoperability Protocol. In this article, we propose a distributed architecture for managing metadata and metadata schema. Instead of normalizing all metadata and schema to a single format, we have focused on building a middleware framework that tolerates heterogeneity. By providing facilities for typing and dynamic conversion of metadata, our system permits continual introduction of new forms of metadata with minimal impact on compatibility.

0.004639305 = product of:
  0.013917915 = sum of:
    0.013917915 = product of:
      0.02783583 = sum of:
        0.02783583 = weight(_text_:22 in 1236) [ClassicSimilarity], result of:
          0.02783583 = score(doc=1236,freq=2.0), product of:
            0.17986396 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051362853 = 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.33333334 = coord(1/3)

Date

26.12.2011 14:01:22