Search (5 results, page 1 of 1)

0.10175028 = product of:
  0.4070011 = sum of:
    0.4070011 = weight(_text_:heading in 2621) [ClassicSimilarity], result of:
      0.4070011 = score(doc=2621,freq=2.0), product of:
        0.38061732 = queryWeight, product of:
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.06292258 = queryNorm
        1.0693184 = fieldWeight in 2621, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.125 = fieldNorm(doc=2621)
  0.25 = coord(1/4)

0.07194831 = product of:
  0.28779325 = sum of:
    0.28779325 = weight(_text_:heading in 6594) [ClassicSimilarity], result of:
      0.28779325 = score(doc=6594,freq=4.0), product of:
        0.38061732 = queryWeight, product of:
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.06292258 = queryNorm
        0.7561223 = fieldWeight in 6594, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.0625 = fieldNorm(doc=6594)
  0.25 = coord(1/4)

Abstract

A system based authority control system was essential to support OCLC's large database and the number and diversity of its users. The authority control system had to be able to (1) identify nonidentical heading entries in bibliographic records of the same name, geographic place, or subject, and (2) maintain a link from the erroneous form of the heading to the valid form (i.e. cross reference). Over 3.6 million headings have been corrected as part of these efforts

0.044515748 = product of:
  0.17806299 = sum of:
    0.17806299 = weight(_text_:heading in 760) [ClassicSimilarity], result of:
      0.17806299 = score(doc=760,freq=2.0), product of:
        0.38061732 = queryWeight, product of:
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.06292258 = queryNorm
        0.4678268 = fieldWeight in 760, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.0546875 = fieldNorm(doc=760)
  0.25 = coord(1/4)

Abstract

Normalization rules are essential for interoperability between bibliographic systems. In the process of working with Name Authority Cooperative Program (NACO) authority files to match records with Functional Requirements for Bibliographic Records (FRBR) and developing the Faceted Application of Subject Terminology (FAST) subject heading schema, the authors found inconsistencies in independently created NACO normalization implementations. Investigating these, the authors found ambiguities in the NACO standard that need resolution, and came to conclusions on how the procedure could be simplified with little impact on matching headings. To encourage others to test their software for compliance with the current rules, the authors have established a Web site that has test files and interactive services showing their current implementation.

0.031796962 = product of:
  0.12718785 = sum of:
    0.12718785 = weight(_text_:heading in 4816) [ClassicSimilarity], result of:
      0.12718785 = score(doc=4816,freq=2.0), product of:
        0.38061732 = queryWeight, product of:
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.06292258 = queryNorm
        0.334162 = fieldWeight in 4816, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0489783 = idf(docFreq=284, maxDocs=44421)
          0.0390625 = fieldNorm(doc=4816)
  0.25 = coord(1/4)

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.011846382 = product of:
  0.04738553 = sum of:
    0.04738553 = weight(_text_:und in 3459) [ClassicSimilarity], result of:
      0.04738553 = score(doc=3459,freq=6.0), product of:
        0.13955593 = queryWeight, product of:
          2.217899 = idf(docFreq=13141, maxDocs=44421)
          0.06292258 = queryNorm
        0.33954507 = fieldWeight in 3459, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          2.217899 = idf(docFreq=13141, maxDocs=44421)
          0.0625 = fieldNorm(doc=3459)
  0.25 = coord(1/4)

Content

Beitrag anlässlich des FRBR-Workshops für Expertengruppenmitglieder am 8. und 9. Juli 2004 in Der Deutschen Bibliothek mit der Zielsetzung: Die Functional Requirements for Bibliographic Records (FRBR) haben seit ihrer Veröffentlichung 1998 durch die IFLA die bibliothekarische Diskussion befruchtet. Was verbirgt sich hinter den FRBR? Welche Auswirkungen hat dieses Modell, das Beziehungen zwischen Entitäten darstellt, auf Regelwerke, Normdateien, Formate, Online-Kataloge und andere Bereiche? Welche Erfahrungen sind international bereits mit den FRBR gesammelt worden? Können wir die FRBR in Deutschland und Österreich nutzbringend in die Standardisierungsarbeit einbringen?