Search (7 results, page 1 of 1)

0.03486972 = product of:
  0.06973944 = sum of:
    0.057480477 = weight(_text_:policy in 2659) [ClassicSimilarity], result of:
      0.057480477 = score(doc=2659,freq=2.0), product of:
        0.24257277 = queryWeight, product of:
          5.361833 = idf(docFreq=563, maxDocs=44218)
          0.04524064 = queryNorm
        0.23696178 = fieldWeight in 2659, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.361833 = idf(docFreq=563, maxDocs=44218)
          0.03125 = fieldNorm(doc=2659)
    0.012258965 = product of:
      0.02451793 = sum of:
        0.02451793 = weight(_text_:22 in 2659) [ClassicSimilarity], result of:
          0.02451793 = score(doc=2659,freq=2.0), product of:
            0.15842502 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04524064 = queryNorm
            0.15476047 = fieldWeight in 2659, 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=2659)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

The Library of Congress Subject Headings (LCSH) has been developed over the course of more than a century, predating the semantic web by some time. Until the 1986, the only concept-toconcept relationship available was an undifferentiated "See Also" reference, which was used for both associative (RT) and hierarchical (BT/NT) connections. In that year, in preparation for the first release of the headings in machine readable MARC Authorities form, an attempt was made to automatically convert these "See Also" links into the standardized thesaural relations. Unfortunately, the rule used to determine the type of reference to generate relied on the presence of symmetric links to detect associatively related terms; "See Also" references that were only present in one of the related terms were assumed to be hierarchical. This left the process vulnerable to inconsistent use of references in the pre-conversion data, with a marked bias towards promoting relationships to hierarchical status. The Library of Congress was aware that the results of the conversion contained many inconsistencies, and intended to validate and correct the results over the course of time. Unfortunately, twenty years later, less than 40% of the converted records have been evaluated. The converted records, being the earliest encountered during the Library's cataloging activities, represent the most basic concepts within LCSH; errors in the syndetic structure for these records affect far more subordinate concepts than those nearer the periphery. Worse, a policy of patterning new headings after pre-existing ones leads to structural errors arising from the conversion process being replicated in these newer headings, perpetuating and exacerbating the errors. As the LCSH prepares for its second great conversion, from MARC to SKOS, it is critical to address these structural problems. As part of the work on converting the headings into SKOS, I have experimented with different visualizations of the tangled web of broader terms embedded in LCSH. This poster illustrates several of these renderings, shows how they can help users to judge which relationships might not be correct, and shows just exactly how Doorbells and Mammals are related.

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.01796265 = product of:
  0.0718506 = sum of:
    0.0718506 = weight(_text_:policy in 82) [ClassicSimilarity], result of:
      0.0718506 = score(doc=82,freq=2.0), product of:
        0.24257277 = queryWeight, product of:
          5.361833 = idf(docFreq=563, maxDocs=44218)
          0.04524064 = queryNorm
        0.29620224 = fieldWeight in 82, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          5.361833 = idf(docFreq=563, maxDocs=44218)
          0.0390625 = fieldNorm(doc=82)
  0.25 = coord(1/4)

Abstract

Aggregated journal-journal citation networks based on the Journal Citation Reports 2004 of the Science Citation Index (5,968 journals) and the Social Science Citation Index (1,712 journals) are made accessible from the perspective of any of these journals. A vector-space model Is used for normalization, and the results are brought online at http://www.leydesdorff.net/jcr04 as input files for the visualization program Pajek. The user is thus able to analyze the citation environment in terms of links and graphs. Furthermore, the local impact of a journal is defined as its share of the total citations in the specific journal's citation environments; the vertical size of the nodes is varied proportionally to this citation impact. The horizontal size of each node can be used to provide the same information after correction for within-journal (self-)citations. In the "citing" environment, the equivalents of this measure can be considered as a citation activity index which maps how the relevant journal environment is perceived by the collective of authors of a given journal. As a policy application, the mechanism of Interdisciplinary developments among the sciences is elaborated for the case of nanotechnology journals.

0.0094307605 = product of:
  0.037723042 = sum of:
    0.037723042 = product of:
      0.075446084 = sum of:
        0.075446084 = weight(_text_:bibliography in 2515) [ClassicSimilarity], result of:
          0.075446084 = score(doc=2515,freq=2.0), product of:
            0.248568 = queryWeight, product of:
              5.494352 = idf(docFreq=493, maxDocs=44218)
              0.04524064 = queryNorm
            0.3035229 = fieldWeight in 2515, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.494352 = idf(docFreq=493, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2515)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

The internal organization of large software projects requires an extraordinary effort in the development and maintenance of repositories made up of software artifacts (business components, data models, functional and technical documentation, etc.). During the software development process, different artifacts are created to help users in the transfer of knowledge and enable communication between workers and teams. The storage, maintenance and publication of these artifacts in knowledge bases - usually referred to as "software repositories" are a useful tool for future software development projects, as they contain the collective, learned experience of the teams and provide the basis to estimate and reuse the work completed in the past. Different techniques similar to those used by the library community have been used in the past to organize these software repositories and help users in the difficult task or identifying and retrieving artifacts (software and documentation). These techniques include software classification - with a special emphasis on faceted classifications, keyword-based retrieval and formal method techniques. The paper discusses the different knowledge organization techniques applied in these repositories to identify and retrieve software artifacts and ensure the reusability of software components and documentation at the different phases of the development process across different projects. An enumeration of the main approaches documented in specialized bibliography is provided.

0.0045971116 = product of:
  0.018388446 = sum of:
    0.018388446 = product of:
      0.036776893 = sum of:
        0.036776893 = weight(_text_:22 in 1289) [ClassicSimilarity], result of:
          0.036776893 = score(doc=1289,freq=2.0), product of:
            0.15842502 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04524064 = queryNorm
            0.23214069 = fieldWeight in 1289, 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=1289)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Content

Vortrag anlässlich des Workshops: "Extending the multilingual capacity of The European Library in the EDL project Stockholm, Swedish National Library, 22-23 November 2007".

0.0038309265 = product of:
  0.015323706 = sum of:
    0.015323706 = product of:
      0.030647412 = sum of:
        0.030647412 = weight(_text_:22 in 1397) [ClassicSimilarity], result of:
          0.030647412 = score(doc=1397,freq=2.0), product of:
            0.15842502 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04524064 = queryNorm
            0.19345059 = fieldWeight in 1397, 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=1397)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

22. 3.2008 14:29:25

0.0038309265 = product of:
  0.015323706 = sum of:
    0.015323706 = product of:
      0.030647412 = sum of:
        0.030647412 = weight(_text_:22 in 5272) [ClassicSimilarity], result of:
          0.030647412 = score(doc=5272,freq=2.0), product of:
            0.15842502 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04524064 = queryNorm
            0.19345059 = fieldWeight in 5272, 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=5272)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

22. 7.2006 16:11:05

0.0015323706 = product of:
  0.0061294823 = sum of:
    0.0061294823 = product of:
      0.012258965 = sum of:
        0.012258965 = weight(_text_:22 in 1789) [ClassicSimilarity], result of:
          0.012258965 = score(doc=1789,freq=2.0), product of:
            0.15842502 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04524064 = queryNorm
            0.07738023 = fieldWeight in 1789, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.015625 = fieldNorm(doc=1789)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

23. 3.2008 19:10:22