Search (23 results, page 1 of 2)

0.12148523 = product of:
  0.24297047 = sum of:
    0.24297047 = sum of:
      0.15970877 = weight(_text_:headings in 3985) [ClassicSimilarity], result of:
        0.15970877 = score(doc=3985,freq=2.0), product of:
          0.24837378 = queryWeight, product of:
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.051211677 = queryNorm
          0.6430178 = fieldWeight in 3985, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.09375 = fieldNorm(doc=3985)
      0.0832617 = weight(_text_:22 in 3985) [ClassicSimilarity], result of:
        0.0832617 = score(doc=3985,freq=2.0), product of:
          0.17933457 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051211677 = queryNorm
          0.46428138 = fieldWeight in 3985, 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=3985)
  0.5 = coord(1/2)

Date

25.11.2005 18:37:22

0.077281 = product of:
  0.154562 = sum of:
    0.154562 = sum of:
      0.11293115 = weight(_text_:headings in 5920) [ClassicSimilarity], result of:
        0.11293115 = score(doc=5920,freq=4.0), product of:
          0.24837378 = queryWeight, product of:
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.051211677 = queryNorm
          0.45468226 = fieldWeight in 5920, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.046875 = fieldNorm(doc=5920)
      0.04163085 = weight(_text_:22 in 5920) [ClassicSimilarity], result of:
        0.04163085 = score(doc=5920,freq=2.0), product of:
          0.17933457 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051211677 = queryNorm
          0.23214069 = fieldWeight in 5920, 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=5920)
  0.5 = coord(1/2)

Abstract

Library of Congress Subject Headings (LCSH), a system originally designed as a tool for subject access to the Library's own collection in the late nineteenth century, has become, in the course of the last century, the main subject retrieval tool in library catalogs throughout the United States and in many other countries. It is one of the largest non-specialized controlled vocabularies in the world. As LCSH enters a new century, it faces an information environment that has undergone vast changes from what had prevailed when LCSH began, or, indeed, from its state in the early days of the online age. In order to continue its mission and to be useful in spheres outside library catalogs as well, LCSH must adapt to the multifarious environment. One possible approach is to adopt a series of scalable and flexible syntax and application rules to meet the needs of different user communities

Date

27. 5.2001 16:22:21

Source

The LCSH century: one hundred years with the Library of Congress Subject Headings system. Ed.: A.T.Stone

0.060742617 = product of:
  0.12148523 = sum of:
    0.12148523 = sum of:
      0.079854384 = weight(_text_:headings in 2205) [ClassicSimilarity], result of:
        0.079854384 = score(doc=2205,freq=2.0), product of:
          0.24837378 = queryWeight, product of:
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.051211677 = queryNorm
          0.3215089 = fieldWeight in 2205, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.849944 = idf(docFreq=940, maxDocs=44218)
            0.046875 = fieldNorm(doc=2205)
      0.04163085 = weight(_text_:22 in 2205) [ClassicSimilarity], result of:
        0.04163085 = score(doc=2205,freq=2.0), product of:
          0.17933457 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.051211677 = queryNorm
          0.23214069 = fieldWeight in 2205, 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=2205)
  0.5 = coord(1/2)

Abstract

Form subdivisions have always been an important part of the Library of Congress Subject Headings. However, when the MARC format was developed, no separate subfield code to identify form subdivisions was defined. Form and topical subdivisions were both included within a general subdivision category. In 1995, the USMARC Advisory Group approved a proposal defining subfield v for form subdivisions, and in 1999 the Library of Congress (LC) began identifying form subdivisions with the new code. However, there are millions of older bibliographic records lacking the explicit form subdivision coding. Identifying form subdivisions retrospectively is not a simple task. An algorithmic method was developed to identify form subdivisions coded as general subdivisions. The algorithm was used to identify 2,563 unique form subdivisions or combinations of form subdivisions in OCLC's WorldCat. The algorithm proved to be highly accurate with an error rate estimated to be less than 0.1%. The observed usage of the form subdivisions was highly skewed with the 100 most used form subdivisions or combinations of subdivisions accounting for 90% of the assignments.

Date

10. 9.2000 17:38:22

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

0.05207995 = product of:
  0.1041599 = sum of:
    0.1041599 = product of:
      0.2083198 = sum of:
        0.2083198 = weight(_text_:headings in 492) [ClassicSimilarity], result of:
          0.2083198 = score(doc=492,freq=10.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.8387351 = fieldWeight in 492, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0546875 = fieldNorm(doc=492)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

An analysis of a sample of 9.442 headings assigned by the LoC to bibliographic records disclosed 2 types of invalid headings: those that were erroneous and those that were obsolete. Each type revealed recurring patterns. Errors and obsolete elements occuring in assigned heading involve MARC coding, terminology in main headings and subdivisions, application of subdivisions, and in mechanical elements such as punctuation and capitalization. Different headings (e.g. personal name, corporate name, topical, etc.) display different patterns as well as predominance of errors and obsoleteness. Although the overall error rate is low, an awareness and understanding of patterns of errors and obsolescnce in subject heading strings should contribute to improvement in subject heading assignment and subject authority control

0.049908984 = product of:
  0.09981797 = sum of:
    0.09981797 = product of:
      0.19963594 = sum of:
        0.19963594 = weight(_text_:headings in 1781) [ClassicSimilarity], result of:
          0.19963594 = score(doc=1781,freq=18.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.8037722 = fieldWeight in 1781, product of:
              4.2426405 = tf(freq=18.0), with freq of:
                18.0 = termFreq=18.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1781)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Recognition, by libraries, of the need for improved efficiency and reliability in subject authority control in catalogues led to a study of the feasibility of automatically creating a subject heading validation file by scanning the OLUC. The premises were: that although the file would not be axhaustive, it would contain the majority of frequently used headings; and that the predicted level of accurary in the file would be high. A sample file of Library of Congress assigned subject headings, from the OCLC Subject Headings Corrections database was analyzed. Results showed that: the frequency of use varies inversely with the number of headings at a given rrate of use; a small number of headings with high frequencies of use accounts for the majority of total use, while a large proportion shows very low frequency of use; topical headings account for 2/3 of assigned headings; and error and obsolescence rates are both low and are in inverse relationship to the frequency of heading use. Concludes that an automatically generated subject heading validation file is feasible and could serve various purposes, including: verification of subject heading strings constructed by cataloguers; updating of subject headings in catalogue maintenance; and validation of subject headings during retrospective catalogue conversion

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

Abstract

The only comprehensive treatise an the Library of Congress Subject Headings system, now fully updated to address LCSH in the electronic environment.

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

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

0.039927192 = product of:
  0.079854384 = sum of:
    0.079854384 = product of:
      0.15970877 = sum of:
        0.15970877 = weight(_text_:headings in 8039) [ClassicSimilarity], result of:
          0.15970877 = score(doc=8039,freq=2.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.6430178 = fieldWeight in 8039, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.09375 = fieldNorm(doc=8039)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.039927192 = product of:
  0.079854384 = sum of:
    0.079854384 = product of:
      0.15970877 = sum of:
        0.15970877 = weight(_text_:headings in 6816) [ClassicSimilarity], result of:
          0.15970877 = score(doc=6816,freq=2.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.6430178 = fieldWeight in 6816, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.09375 = fieldNorm(doc=6816)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

0.037643716 = product of:
  0.07528743 = sum of:
    0.07528743 = product of:
      0.15057486 = sum of:
        0.15057486 = weight(_text_:headings in 2268) [ClassicSimilarity], result of:
          0.15057486 = score(doc=2268,freq=4.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.606243 = fieldWeight in 2268, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0625 = fieldNorm(doc=2268)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Beginning with Cutter, theorists of subject headings have conceded that certain elements of systematic arrangement in the dictionary catalog are inevitable; yet the fact that no specific guidelines have ever been developed for the determination of the extent to which subject collocation at the expense of specific and direct entry should be allowed has resulted in the many irregularities and inconsistencies now existing in the LCSH

0.037199963 = product of:
  0.074399926 = sum of:
    0.074399926 = product of:
      0.14879985 = sum of:
        0.14879985 = weight(_text_:headings in 3816) [ClassicSimilarity], result of:
          0.14879985 = score(doc=3816,freq=10.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.5990965 = fieldWeight in 3816, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3816)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The Library of Congress Subject Headings schema (LCSH) is by far the most commonly used and widely accepted subject vocabulary for general application. It is the de facto universal controlled vocabulary and has been a model for developing subject heading systems by many countries. However, LCSH's complex syntax and rules for constructing headings restrict its application by requiring highly skilled personnel and limit the effectiveness of automated authority control. Recent trends, driven to a large extent by the rapid growth of the Web, are forcing changes in bibliographic control systems to make them easier to use, understand, and apply, and subject headings are no exception. The purpose of adapting the LCSH with a simplified syntax to create FAST is to retain the very rich vocabulary of LCSH while making the schema easier to understand, control, apply, and use. The schema maintains upward compatibility with LCSH, and any valid set of LC subject headings can be converted to FAST headings.

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

Abstract

Recent trends, driven to a large extent by the rapid proliferation of digital resources, are forcing changes in bibliographic control to make it easier to use, understand, and apply subject data. Subject headings are no exception. The enormous volume and rapid growth of digital libraries and repositories and the emergence of numerous metadata schemes have spurred a reexamination of the way subject data are to be provided for such resources efficiently and effectively. To address this need, OCLC in cooperation with the Library of Congress, has taken a new approach, called FAST (Faceted Application of Subject Terminology). FAST headings are based on the existing vocabulary in Library of Congress Subject Headings (LCSH), but are applied with a simpler syntax than required by Library of Congress application policies. Adapting the LCSH vocabulary in a simplified faceted syntax retains the rich vocabulary of LCSH while making it easier to understand, control, apply, and use.

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.03293825 = product of:
  0.0658765 = sum of:
    0.0658765 = product of:
      0.131753 = sum of:
        0.131753 = weight(_text_:headings in 6109) [ClassicSimilarity], result of:
          0.131753 = score(doc=6109,freq=4.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.5304626 = fieldWeight in 6109, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.0546875 = fieldNorm(doc=6109)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This article describes FAST, the Faceted Application of Subject Terminology, a project at OCLC to make Library of Congress Subject Headings easier to use in Dublin Core metadata by breaking out facets of space, time, and form. Work on FAST can be watched at its web site, http://www.miskatonic.org/library/, which has recent presentations and reports. It is interesting to see facets and Dublin Core combined, though both LCSH and FAST subject headings are beyond what most people making a small faceted classification would want or need.

0.028232787 = product of:
  0.056465574 = sum of:
    0.056465574 = product of:
      0.11293115 = sum of:
        0.11293115 = weight(_text_:headings in 3431) [ClassicSimilarity], result of:
          0.11293115 = score(doc=3431,freq=4.0), product of:
            0.24837378 = queryWeight, product of:
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.051211677 = queryNorm
            0.45468226 = fieldWeight in 3431, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.849944 = idf(docFreq=940, maxDocs=44218)
              0.046875 = fieldNorm(doc=3431)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

With the current information environment characterized by the proliferation of digital resources, including collaboratively created and shared resources, Library of Congress Subject Headings (LCSH) is facing the challenges of effective and efficient subject-based organization and retrieval of digital resources. To explore the feasibility of utilizing LCSH in a digital environment, we might need to revisit its basic characteristics. The objectives of our study were to analyze LCSH in both syntactic and relational structures, to discover the structural characteristics of LCSH, and to identify problems and issues for the feasibility of LCSH as an effective subject access tool. This study reports and discusses issues raised by the syntactic and hierarchical structures of LCSH that present challenges to its use in a networked environment. Given the results of this study, we recommend a number of provisional future directions for the development of LCSH towards further becoming a viable system for digital and networked resources.

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

Abstract

In addition to using title keywords and subject headings for searching in the online catalog, the searcher may also use class numbers as access points. Library of Congress class or call numbers are particular effective in certain kinds of specific-item subject searching and serve as supplements to keywords and descriptors, improving precision and recall. Class number searching in the database can produce unique results because these numbers collect citations in ways that differ from those of keywords and descriptors

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

Abstract

Contribution to a thematic issue devoted to a subject control in on-line catalogues. Examines whether a subject cataloguing code is, at this point in time, necessary or economically feasible, as well as questioning who will develop such a code and if experiences with AACR2 should make librarians fearful or hopeful about similar work with subject headings.

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

Abstract

The principle of uniform heading underlies the rules for headings in descriptive cataloging in the American tradition. The rationale and the evolution of the principle are examined and its implications discussed in terms of the history of cataloging codes. The ideal embodied in the principle of uniform heading has been undergoing gradual modification in recent codes and considerably compromised in cataloging practice today.