Search (3 results, page 1 of 1)

0.062177487 = product of:
  0.12435497 = sum of:
    0.040692065 = weight(_text_:social in 5797) [ClassicSimilarity], result of:
      0.040692065 = score(doc=5797,freq=2.0), product of:
        0.1847249 = queryWeight, product of:
          3.9875789 = idf(docFreq=2228, maxDocs=44218)
          0.046325076 = queryNorm
        0.22028469 = fieldWeight in 5797, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.9875789 = idf(docFreq=2228, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5797)
    0.083662905 = sum of:
      0.052280862 = weight(_text_:aspects in 5797) [ClassicSimilarity], result of:
        0.052280862 = score(doc=5797,freq=2.0), product of:
          0.20938325 = queryWeight, product of:
            4.5198684 = idf(docFreq=1308, maxDocs=44218)
            0.046325076 = queryNorm
          0.2496898 = fieldWeight in 5797, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.5198684 = idf(docFreq=1308, maxDocs=44218)
            0.0390625 = fieldNorm(doc=5797)
      0.031382043 = weight(_text_:22 in 5797) [ClassicSimilarity], result of:
        0.031382043 = score(doc=5797,freq=2.0), product of:
          0.16222252 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.046325076 = queryNorm
          0.19345059 = fieldWeight in 5797, 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=5797)
  0.5 = coord(2/4)

Abstract

The article discusses various aspects of the Dewey Decimal Classification (DDC) system of classifying library books in 2013. Background is presented on some librarians' desire to stop using DDC and adopt a genre-based system of classification. It says librarians can use the DDC to deal with problems and issues related to library book classification. It highlights the benefits of using captions and relative index terms and semantic relationships in DDC.

Content

"As knowledge brokers, we are living in interesting times for libraries and librarians. We wonder sometimes if our traditional tools like the Dewey Decimal Classification (DDC) system can cope with the onslaught of information. The categories provided don't always seem adequate for the knowledge-discovery habits of today's patrons. They have grown accustomed to new ways for their information needs to be met, from the fire-and-forget style of a hard-to-control classic Google search to the pervasive, always-on style of Google Now, anticipating users' information needs without their having even asked a verbal question. Contrariwise, I believe that we, as librarians, could be making better use of our tools. Many (like the DDC) are a reflection of the same social and epistemological forces that brought about modernity at the turn of the last century. We as librarians are in the unique position of providing services that are as ground-breaking as these tools. As we see the need to provide unique and cutting-edge knowledge discovery to our users, I argue in this article that the DDC can play a key role in fulfilling this purpose."

Source

Knowledge quest. 42(2013) no.2, S.22-29

0.04510647 = product of:
  0.09021294 = sum of:
    0.06510731 = weight(_text_:social in 2629) [ClassicSimilarity], result of:
      0.06510731 = score(doc=2629,freq=2.0), product of:
        0.1847249 = queryWeight, product of:
          3.9875789 = idf(docFreq=2228, maxDocs=44218)
          0.046325076 = queryNorm
        0.3524555 = fieldWeight in 2629, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.9875789 = idf(docFreq=2228, maxDocs=44218)
          0.0625 = fieldNorm(doc=2629)
    0.025105633 = product of:
      0.050211266 = sum of:
        0.050211266 = weight(_text_:22 in 2629) [ClassicSimilarity], result of:
          0.050211266 = score(doc=2629,freq=2.0), product of:
            0.16222252 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046325076 = queryNorm
            0.30952093 = fieldWeight in 2629, 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=2629)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Source

Metadata for semantic and social applications : proceedings of the International Conference on Dublin Core and Metadata Applications, Berlin, 22 - 26 September 2008, DC 2008: Berlin, Germany / ed. by Jane Greenberg and Wolfgang Klas

0.0052629285 = product of:
  0.021051714 = sum of:
    0.021051714 = product of:
      0.04210343 = sum of:
        0.04210343 = weight(_text_:22 in 1752) [ClassicSimilarity], result of:
          0.04210343 = score(doc=1752,freq=10.0), product of:
            0.16222252 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046325076 = queryNorm
            0.2595412 = fieldWeight in 1752, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1752)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Content

Some examples of identifiers for concepts follow: <http://dewey.info/concept/338.4/en/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the English-language version of Edition 22. <http://dewey.info/concept/338.4/de/edn/22/> This identifier is used to retrieve or identify the 338.4 concept in the German-language version of Edition 22. <http://dewey.info/concept/333.7-333.9/> This identifier is used to retrieve or identify the 333.7-333.9 concept across all editions and language versions. <http://dewey.info/concept/333.7-333.9/about.skos> This identifier is used to retrieve a SKOS representation of the 333.7-333.9 concept (using the "resource" element). There are several open issues at this preliminary stage of development: Use cases: URIs need to represent the range of statements or questions that could be submitted to a Dewey web service. Therefore, it seems that some general questions have to be answered first: What information does an agent have when coming to a Dewey web service? What kind of questions will such an agent ask? Placement of the {locale} component: It is still an open question if the {locale} component should be placed after the {version} component instead (<http://dewey.info/concept/338.4/edn/22/en>) to emphasize that the most important instantiation of a Dewey class is its edition, not its language version. From a services point of view, however, it could make more sense to keep the current arrangement, because users are more likely to come to the service with a present understanding of the language version they are seeking without knowing the specifics of a certain edition in which they are trying to find topics. Identification of other Dewey entities: The goal is to create a locator that does not answer all, but a lot of questions that could be asked about the DDC. Which entities are missing but should be surfaced for services or user agents? How will those services or agents interact with them? Should some entities be rendered in a different way as presented? For example, (how) should the DDC Summaries be retrievable? Would it be necessary to make the DDC Manual accessible through this identifier structure?"