Search (3 results, page 1 of 1)

  • × theme_ss:"Normdateien"
  • × year_i:[1980 TO 1990}
  1. Taylor, A.G.: Authority files in online catalogs : an investigation of their value (1984) 0.01 
    0.009619858 = product of:
  0.057719145 = sum of:
    0.057719145 = product of:
      0.11543829 = sum of:
        0.11543829 = weight(_text_:programs in 326) [ClassicSimilarity], result of:
          0.11543829 = score(doc=326,freq=2.0), product of:
            0.25748047 = queryWeight, product of:
              5.79699 = idf(docFreq=364, maxDocs=44218)
              0.044416238 = queryNorm
            0.44833803 = fieldWeight in 326, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.79699 = idf(docFreq=364, maxDocs=44218)
              0.0546875 = fieldNorm(doc=326)
      0.5 = coord(1/2)
  0.16666667 = coord(1/6)
    Abstract
    Authority control is discussed from two viewpoints: The need for bibliographic records relating to a name to be brought together under one form of the name; and the need for cross references to direct a user to a heading from variant forms of the name. Data from two research projects that support the need for choosing one form of name are summarized. The author's study of user requests that resulted in no "hits" in an online catalog is described. Data are given to show that for only 6.4% of these requests would our current methods of cross referencing in authority records have been helpful, and that two system programs would have given much greater assistance.
  2. Gibbs, G.E.; Bisom, D.: Creating an interactive authority file for names in the UCLA ORION system : specifications and decisions (1989) 0.01 
    0.008738637 = product of:
  0.05243182 = sum of:
    0.05243182 = weight(_text_:computer in 440) [ClassicSimilarity], result of:
      0.05243182 = score(doc=440,freq=2.0), product of:
        0.16231956 = queryWeight, product of:
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.044416238 = queryNorm
        0.32301605 = fieldWeight in 440, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.0625 = fieldNorm(doc=440)
  0.16666667 = coord(1/6)
    Abstract
    The authors describe the creation of a linked authority system on the UCLA Library's ORION system. The computer specifications used to convert headings from the bibliographic file to authority records are given and the problems encountered in this process and the solutions decided upon are enumerated.
  3. Dickson, J.; Zadner, P.: Authority control and the authority file : a functional evaluation of LCNAF on RLIN (1989) 0.01 
    0.007646307 = product of:
  0.04587784 = sum of:
    0.04587784 = weight(_text_:computer in 425) [ClassicSimilarity], result of:
      0.04587784 = score(doc=425,freq=2.0), product of:
        0.16231956 = queryWeight, product of:
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.044416238 = queryNorm
        0.28263903 = fieldWeight in 425, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6545093 = idf(docFreq=3109, maxDocs=44218)
          0.0546875 = fieldNorm(doc=425)
  0.16666667 = coord(1/6)
    Abstract
    The costs of authority control are high and the information provided in authority files is often duplicated in separate bibliographic files. Librarians need to examine the compatibility of traditional methods of authority control with the advanced capabilities of current computer systems. This study investigates the actual use of the Library of Congress Name Authority File (LCNAF) by catalogers in an RLIN member library. Results show that some aspects of authority control could be expedited by changes in cataloging practice and search software.

Authors