Search (373 results, page 19 of 19)

2.0495258E-4 = product of:
  0.0047139092 = sum of:
    0.0047139092 = product of:
      0.0094278185 = sum of:
        0.0094278185 = weight(_text_:1 in 5574) [ClassicSimilarity], result of:
          0.0094278185 = score(doc=5574,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.16284466 = fieldWeight in 5574, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=5574)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Library trends. 61(2012) no.1, S.248-258

2.0495258E-4 = product of:
  0.0047139092 = sum of:
    0.0047139092 = product of:
      0.0094278185 = sum of:
        0.0094278185 = weight(_text_:1 in 1152) [ClassicSimilarity], result of:
          0.0094278185 = score(doc=1152,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.16284466 = fieldWeight in 1152, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.046875 = fieldNorm(doc=1152)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Cataloging and classification quarterly. 61(2023) no.1, p.47-66

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 5598) [ClassicSimilarity], result of:
          0.007856515 = score(doc=5598,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 5598, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5598)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Date

1. 8.2006 11:48:59

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 172) [ClassicSimilarity], result of:
          0.007856515 = score(doc=172,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 172, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=172)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Knowledge organization. 33(2006) no.1, S.20-34

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 662) [ClassicSimilarity], result of:
          0.007856515 = score(doc=662,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 662, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=662)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Knowledge organization. 34(2007) no.1, S.41-57

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 1249) [ClassicSimilarity], result of:
          0.007856515 = score(doc=1249,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 1249, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1249)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

D-Lib magazine. 5(1999) no.1, xx S

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 865) [ClassicSimilarity], result of:
          0.007856515 = score(doc=865,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 865, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=865)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Library hi tech. 28(2010) no.1, S.81-93

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 1253) [ClassicSimilarity], result of:
          0.007856515 = score(doc=1253,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 1253, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1253)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Date

1. 5.2014 17:32:09

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 3897) [ClassicSimilarity], result of:
          0.007856515 = score(doc=3897,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 3897, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3897)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Abstract

The Early American Cookbooks digital project is a case study in analyzing collections as data using HathiTrust and the HathiTrust Research Center (HTRC) Portal. The purposes of the project are to create a freely available, searchable collection of full-text early American cookbooks within the HathiTrust Digital Library, to offer an overview of the scope and contents of the collection, and to analyze trends and patterns in the metadata and the full text of the collection. The digital project has two basic components: a collection of 1450 full-text cookbooks published in the United States between 1800 and 1920 and a website to present a guide to the collection and the results of the analysis. This article will focus on the workflow for analyzing the metadata and the full-text of the collection. The workflow will cover: 1) creating a searchable public collection of full-text titles within the HathiTrust Digital Library and uploading it to the HTRC Portal, 2) analyzing and visualizing legacy MARC data for the collection using MarcEdit, OpenRefine and Tableau, and 3) using the text analysis tools in the HTRC Portal to look for trends and patterns in the full text of the collection.

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 5398) [ClassicSimilarity], result of:
          0.007856515 = score(doc=5398,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 5398, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5398)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Date

1. 7.2019 18:49:14

1.707938E-4 = product of:
  0.0039282576 = sum of:
    0.0039282576 = product of:
      0.007856515 = sum of:
        0.007856515 = weight(_text_:1 in 63) [ClassicSimilarity], result of:
          0.007856515 = score(doc=63,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.13570388 = fieldWeight in 63, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.0390625 = fieldNorm(doc=63)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Source

Journal of the Association for Information Science and Technology. 72(2021) no.1, S.32-45

1.3663506E-4 = product of:
  0.0031426062 = sum of:
    0.0031426062 = product of:
      0.0062852125 = sum of:
        0.0062852125 = weight(_text_:1 in 1177) [ClassicSimilarity], result of:
          0.0062852125 = score(doc=1177,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.1085631 = fieldWeight in 1177, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.03125 = fieldNorm(doc=1177)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Abstract

This is the second part of an analysis of the methods that have been used to achieve or improve interoperability among metadata schemas and their applications in order to facilitate the conversion and exchange of metadata and to enable 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 (discussed in Part I of the article), record level (discussed in Part II of the article), and repository level (also discussed in Part II). The results of efforts to improve interoperability may be observed from different perspectives as well, including element-based and value-based approaches. As discussed in Part I of this study, the results of efforts to improve interoperability can be observed at different levels: 1. Schema level - Efforts are focused on the elements of the schemas, being independent of any applications. The results usually appear as derived element sets or encoded schemas, crosswalks, application profiles, and element registries. 2. Record level - Efforts are intended to integrate the metadata records through the mapping of the elements according to the semantic meanings of these elements. Common results include converted records and new records resulting from combining values of existing records. 3. Repository level - With harvested or integrated records from varying sources, efforts at this level focus on mapping value strings associated with particular elements (e.g., terms associated with subject or format elements). The results enable cross-collection searching. In the following sections, we will continue to analyze interoperability efforts and methodologies, focusing on the record level and the repository level. It should be noted that the models to be discussed in this article are not always mutually exclusive. Sometimes, within a particular project, more than one method may be used.

1.3663506E-4 = product of:
  0.0031426062 = sum of:
    0.0031426062 = product of:
      0.0062852125 = sum of:
        0.0062852125 = weight(_text_:1 in 1030) [ClassicSimilarity], result of:
          0.0062852125 = score(doc=1030,freq=2.0), product of:
            0.057894554 = queryWeight, product of:
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.023567878 = queryNorm
            0.1085631 = fieldWeight in 1030, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              2.4565027 = idf(docFreq=10304, maxDocs=44218)
              0.03125 = fieldNorm(doc=1030)
      0.5 = coord(1/2)
  0.04347826 = coord(1/23)

Abstract

In the last few years, the size of Linked Open Data (LOD) describing artworks, in general or domain-specific Knowledge Graphs (KGs), is gradually increasing. This provides (art-)historians and Cultural Heritage professionals with a wealth of information to explore. Specifically, structured data about iconographical and iconological (icon) aspects, i.e. information about the subjects, concepts and meanings of artworks, are extremely valuable for the state-of-the-art of computational tools, e.g. content recognition through computer vision. Nevertheless, a data quality evaluation for art domains, fundamental for data reuse, is still missing. The purpose of this study is filling this gap with an overview of art-historical data quality in current KGs with a focus on the icon aspects. Design/methodology/approach This study's analyses are based on established KG evaluation methodologies, adapted to the domain by addressing requirements from art historians' theories. The authors first select several KGs according to Semantic Web principles. Then, the authors evaluate (1) their structures' suitability to describe icon information through quantitative and qualitative assessment and (2) their content, qualitatively assessed in terms of correctness and completeness. Findings This study's results reveal several issues on the current expression of icon information in KGs. The content evaluation shows that these domain-specific statements are generally correct but often not complete. The incompleteness is confirmed by the structure evaluation, which highlights the unsuitability of the KG schemas to describe icon information with the required granularity. Originality/value The main contribution of this work is an overview of the actual landscape of the icon information expressed in LOD. Therefore, it is valuable to cultural institutions by providing them a first domain-specific data quality evaluation. Since this study's results suggest that the selected domain information is underrepresented in Semantic Web datasets, the authors highlight the need for the creation and fostering of such information to provide a more thorough art-historical dimension to LOD.