Search (23 results, page 1 of 2)

0.07907778 = product of:
  0.15815556 = sum of:
    0.15815556 = sum of:
      0.13040166 = weight(_text_:headings in 2659) [ClassicSimilarity], result of:
        0.13040166 = score(doc=2659,freq=12.0), product of:
          0.24837378 = queryWeight, product of:
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.051211677 = queryNorm
          0.52502185 = fieldWeight in 2659, product of:
            3.4641016 = tf(freq=12.0), with freq of:
              12.0 = termFreq=12.0
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.03125 = fieldNorm(doc=2659)
      0.0277539 = weight(_text_:22 in 2659) [ClassicSimilarity], result of:
        0.0277539 = score(doc=2659,freq=2.0), product of:
          0.17933457 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051211677 = 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)

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.034577962 = product of:
  0.069155924 = sum of:
    0.069155924 = product of:
      0.13831185 = sum of:
        0.13831185 = weight(_text_:headings in 2503) [ClassicSimilarity], result of:
          0.13831185 = score(doc=2503,freq=6.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.55686975 = fieldWeight in 2503, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.046875 = fieldNorm(doc=2503)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Content

The aim of this study is to develop a software tool, VisuaLCSH, for effective searching, browsing, and maintenance of LCSH. This tool enables visualizing subject headings and hierarchical structures implied and embedded in LCSH. A conceptual framework for converting the hierarchical structure of headings in LCSH to an explicit tree structure is proposed, described, and implemented. The highlights of VisuaLCSH are summarized below: 1) revealing multiple aspects of a heading; 2) normalizing the hierarchical relationships in LCSH; 3) showing multi-level hierarchies in LCSH sub-trees; 4) improving the navigational function of LCSH in retrieval; and 5) enabling the implementation of generic search, i.e., the 'exploding' feature, in searching LCSH.

0.02881497 = product of:
  0.05762994 = sum of:
    0.05762994 = product of:
      0.11525988 = sum of:
        0.11525988 = weight(_text_:headings in 3870) [ClassicSimilarity], result of:
          0.11525988 = score(doc=3870,freq=6.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.46405816 = fieldWeight in 3870, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3870)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Data from multiple knowledge organization systems are combined to provide a global overview of the content holdings of a small personal library. Subject headings and classification data are used to effectively map the combined book and topic space of the library. While harvested and manipulated by hand, the work reveals issues and potential solutions when using automated techniques to produce topic maps of much larger libraries. The small library visualized consists of the thirty-nine, digital, English language books found in the Osama Bin Laden (OBL) compound in Abbottabad, Pakistan upon his death. As this list of books has garnered considerable media attention, it is worth providing a visual overview of the subject content of these books - some of which is not readily apparent from the titles. Metadata from subject headings and classification numbers was combined to create book-subject maps. Tree maps of the classification data were also produced. The books contain 328 subject headings. In order to enhance the base map with meaningful thematic overlay, library holding count data was also harvested (and aggregated from duplicates). This additional data revealed the relative scarcity or popularity of individual books.

0.023527324 = product of:
  0.04705465 = sum of:
    0.04705465 = product of:
      0.0941093 = sum of:
        0.0941093 = weight(_text_:headings in 1102) [ClassicSimilarity], result of:
          0.0941093 = score(doc=1102,freq=4.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.3789019 = fieldWeight in 1102, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1102)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Many large digital collections are currently organized by subject; although useful, these information organization structures are large and complex and thus difficult to browse. Current online tools and visualization prototypes show small, localized subsets and do not provide the ability to explore the predominant patterns of the overall subject structure. This study describes subject tree modifications that facilitate browsing for documents by capitalizing on the highly uneven distribution of real-world collections. The approach is demonstrated on two large collections organized by the Library of Congress Subject Headings (LCSH) and Medical Subject Headings (MeSH). Results show that the LCSH subject tree can be reduced to 49% of its initial complexity while maintaining access to 83% of the collection, and the MeSH tree can be reduced to 45% of its initial complexity while maintaining access to 97% of the collection. A simple solution to negate the loss of access is discussed. The visual impact is demonstrated by using traditional outline views and a slider control allowing searchers to change the subject structure dynamically according to their needs. This study has implications for the development of information organization theory and human-information interaction techniques for subject trees.

0.023290861 = product of:
  0.046581723 = sum of:
    0.046581723 = product of:
      0.093163446 = sum of:
        0.093163446 = weight(_text_:headings in 232) [ClassicSimilarity], result of:
          0.093163446 = score(doc=232,freq=2.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.37509373 = fieldWeight in 232, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0546875 = fieldNorm(doc=232)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This paper examines some traditional information searching methods and their role in Hungarian OPACs. What challenges are there in the digital and online environment? How do users work with them and do they give users satisfactory results? What kinds of techniques are users employing? In this paper I examine the user interfaces of UDC, thesauri, subject headings etc. in the Hungarian library. The key question of the paper is whether a universal system or local solutions is the best approach for searching in the digital environment.

0.017346188 = product of:
  0.034692377 = sum of:
    0.034692377 = product of:
      0.06938475 = sum of:
        0.06938475 = weight(_text_:22 in 3406) [ClassicSimilarity], result of:
          0.06938475 = score(doc=3406,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.38690117 = fieldWeight in 3406, 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=3406)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

30. 5.2010 16:22:35

0.017346188 = product of:
  0.034692377 = sum of:
    0.034692377 = product of:
      0.06938475 = sum of:
        0.06938475 = weight(_text_:22 in 2755) [ClassicSimilarity], result of:
          0.06938475 = score(doc=2755,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.38690117 = fieldWeight in 2755, 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=2755)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

1. 2.2016 18:25:22

0.01663633 = product of:
  0.03327266 = sum of:
    0.03327266 = product of:
      0.06654532 = sum of:
        0.06654532 = weight(_text_:headings in 617) [ClassicSimilarity], result of:
          0.06654532 = score(doc=617,freq=2.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.2679241 = fieldWeight in 617, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0390625 = fieldNorm(doc=617)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The study adopts a naturalistic approach to investigate users' interaction with a browsable MeSH (medical subject headings) display designed to facilitate query construction for the PubMed bibliographic database. The purpose of the study is twofold: first, to test the usefulness of a browsable interface utilizing the principle of faceted classification; and second, to investigate users' preferred query submission methods in different problematic situations. An interface that incorporated multiple query submission methods - the conventional single-line query box as well as methods associated the faceted classification display was constructed. Participants' interactions with the interface were monitored remotely over a period of 10 weeks; information about their problematic situations and information retrieval behaviors were also collected during this time. The traditional controlled experiment was not adequate in answering the author's research questions; hence, the author provides his rationale for a naturalistic approach. The study's findings show that there is indeed a selective compatibility between query submission methods provided by the MeSH display and users' problematic situations. The query submission methods associated with the display were found to be the preferred search tools when users' information needs were vague and the search topics unfamiliar. The findings support the theoretical proposition that users engaging in an information retrieval process with a variety of problematic situations need different approaches. The author argues that rather than treat the information retrieval system as a general purpose tool, more attention should be given to the interaction between the functionality of the tool and the characteristics of users' problematic situations.

0.014718729 = product of:
  0.029437458 = sum of:
    0.029437458 = product of:
      0.058874916 = sum of:
        0.058874916 = weight(_text_:22 in 3355) [ClassicSimilarity], result of:
          0.058874916 = score(doc=3355,freq=4.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.32829654 = fieldWeight in 3355, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=3355)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 1.2017 16:54:03
22. 1.2017 17:10:56

0.013309063 = product of:
  0.026618127 = sum of:
    0.026618127 = product of:
      0.053236254 = sum of:
        0.053236254 = weight(_text_:headings in 3646) [ClassicSimilarity], result of:
          0.053236254 = score(doc=3646,freq=2.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.21433927 = fieldWeight in 3646, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.03125 = fieldNorm(doc=3646)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The use of diagrams to express relationships in classification is not new. Many classificationists have used this approach, but usually in a minor display to make a point or for part of a difficult relational situation. Ranganathan, for example, used diagrams for some of his more elusive concepts. The thesaurus in particular and subject headings in general, with direct and indirect crossreferences or equivalents, need many more diagrams than normally are included to make relationships and even semantics clear. A picture very often is worth a thousand words. Rolling has used directed graphs (arrowgraphs) to join terms as a practical method for rendering relationships between indexing terms lucid. He has succeeded very weIl in this endeavor. Four diagrams in this selection are all that one needs to explain how to employ the system; from initial listing to completed arrowgraph. The samples of his work include illustration of off-page connectors between arrowgraphs. The great advantage to using diagrams like this is that they present relations between individual terms in a format that is easy to comprehend. But of even greater value is the fact that one can use his arrowgraphs as schematics for making three-dimensional wire-and-ball models, in which the relationships may be seen even more clearly. In fact, errors or gaps in relations are much easier to find with this methodology. One also can get across the notion of the threedimensionality of classification systems with such models. Pettee's "hand reaching up and over" (q.v.) is not a figment of the imagination. While the actual hand is a wire or stick, the concept visualized is helpful in illuminating the three-dimensional figure that is latent in all systems that have cross-references or "broader," "narrower," or, especially, "related" terms. Classification schedules, being hemmed in by the dimensions of the printed page, also benefit from such physical illustrations. Rolling, an engineer by conviction, was the developer of information systems for the Cobalt Institute, the European Atomic Energy Community, and European Coal and Steel Community. He also developed and promoted computer-aided translation at the Commission of the European Communities in Luxembourg. One of his objectives has always been to increase the efficiency of mono- and multilingual thesauri for use in multinational information systems.

0.012142331 = product of:
  0.024284663 = sum of:
    0.024284663 = product of:
      0.048569325 = sum of:
        0.048569325 = weight(_text_:22 in 2500) [ClassicSimilarity], result of:
          0.048569325 = score(doc=2500,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.2708308 = fieldWeight in 2500, 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=2500)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

30. 1.2007 18:22:41

0.010407712 = product of:
  0.020815425 = sum of:
    0.020815425 = product of:
      0.04163085 = sum of:
        0.04163085 = weight(_text_:22 in 1289) [ClassicSimilarity], result of:
          0.04163085 = score(doc=1289,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = 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.5 = coord(1/2)

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.010407712 = product of:
  0.020815425 = sum of:
    0.020815425 = product of:
      0.04163085 = sum of:
        0.04163085 = weight(_text_:22 in 1781) [ClassicSimilarity], result of:
          0.04163085 = score(doc=1781,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.23214069 = fieldWeight in 1781, 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=1781)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 3.2008 14:35:21

0.010407712 = product of:
  0.020815425 = sum of:
    0.020815425 = product of:
      0.04163085 = sum of:
        0.04163085 = weight(_text_:22 in 3693) [ClassicSimilarity], result of:
          0.04163085 = score(doc=3693,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.23214069 = fieldWeight in 3693, 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=3693)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

22. 7.2010 19:36:46

0.010407712 = product of:
  0.020815425 = sum of:
    0.020815425 = product of:
      0.04163085 = sum of:
        0.04163085 = weight(_text_:22 in 1709) [ClassicSimilarity], result of:
          0.04163085 = score(doc=1709,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.23214069 = fieldWeight in 1709, 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=1709)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

4. 2.2015 9:22:39

0.008673094 = product of:
  0.017346188 = sum of:
    0.017346188 = product of:
      0.034692377 = sum of:
        0.034692377 = weight(_text_:22 in 1397) [ClassicSimilarity], result of:
          0.034692377 = score(doc=1397,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = 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.5 = coord(1/2)

Date

22. 3.2008 14:29:25

0.008673094 = product of:
  0.017346188 = sum of:
    0.017346188 = product of:
      0.034692377 = sum of:
        0.034692377 = weight(_text_:22 in 5272) [ClassicSimilarity], result of:
          0.034692377 = score(doc=5272,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = 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.5 = coord(1/2)

Date

22. 7.2006 16:11:05

0.008673094 = product of:
  0.017346188 = sum of:
    0.017346188 = product of:
      0.034692377 = sum of:
        0.034692377 = weight(_text_:22 in 3070) [ClassicSimilarity], result of:
          0.034692377 = score(doc=3070,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.19345059 = fieldWeight in 3070, 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=3070)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

20. 1.2015 18:30:22

0.008673094 = product of:
  0.017346188 = sum of:
    0.017346188 = product of:
      0.034692377 = sum of:
        0.034692377 = weight(_text_:22 in 4573) [ClassicSimilarity], result of:
          0.034692377 = score(doc=4573,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.19345059 = fieldWeight in 4573, 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=4573)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

9.12.2018 16:22:25

0.008673094 = product of:
  0.017346188 = sum of:
    0.017346188 = product of:
      0.034692377 = sum of:
        0.034692377 = weight(_text_:22 in 4641) [ClassicSimilarity], result of:
          0.034692377 = score(doc=4641,freq=2.0), product of:
            0.17933457 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.051211677 = queryNorm
            0.19345059 = fieldWeight in 4641, 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=4641)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

21.12.2018 17:22:13