Search (82 results, page 1 of 5)

0.06466791 = product of:
  0.12933582 = sum of:
    0.06924136 = weight(_text_:reference in 438) [ClassicSimilarity], result of:
      0.06924136 = score(doc=438,freq=2.0), product of:
        0.19255297 = queryWeight, product of:
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.047329273 = queryNorm
        0.35959643 = fieldWeight in 438, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.0625 = fieldNorm(doc=438)
    0.060094457 = product of:
      0.120188914 = sum of:
        0.120188914 = weight(_text_:file in 438) [ClassicSimilarity], result of:
          0.120188914 = score(doc=438,freq=2.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.47376698 = fieldWeight in 438, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0625 = fieldNorm(doc=438)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

Research and recent "theoretical" discussions of authority control are synthesized and organized into the following groups: general overviews; need for research; need for unique access points for names; need for authority control outside traditional library catalogs; reference structure for names and its relationship to users' needs; authority control for works; authority control for subjects; need for authority files; and, technological considerations. Conclusions are drawn about the need for research in the area of file design.

0.064308226 = product of:
  0.2572329 = sum of:
    0.2572329 = sum of:
      0.18028337 = weight(_text_:file in 1266) [ClassicSimilarity], result of:
        0.18028337 = score(doc=1266,freq=2.0), product of:
          0.25368783 = queryWeight, product of:
            5.3600616 = idf(docFreq=564, maxDocs=44218)
            0.047329273 = queryNorm
          0.71065044 = fieldWeight in 1266, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.3600616 = idf(docFreq=564, maxDocs=44218)
            0.09375 = fieldNorm(doc=1266)
      0.07694955 = weight(_text_:22 in 1266) [ClassicSimilarity], result of:
        0.07694955 = score(doc=1266,freq=2.0), product of:
          0.16573904 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.047329273 = queryNorm
          0.46428138 = fieldWeight in 1266, 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=1266)
  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.057835408 = product of:
  0.115670815 = sum of:
    0.051931016 = weight(_text_:reference in 5341) [ClassicSimilarity], result of:
      0.051931016 = score(doc=5341,freq=2.0), product of:
        0.19255297 = queryWeight, product of:
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.047329273 = queryNorm
        0.2696973 = fieldWeight in 5341, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.046875 = fieldNorm(doc=5341)
    0.0637398 = product of:
      0.1274796 = sum of:
        0.1274796 = weight(_text_:file in 5341) [ClassicSimilarity], result of:
          0.1274796 = score(doc=5341,freq=4.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.5025058 = fieldWeight in 5341, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.046875 = fieldNorm(doc=5341)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

In 1996, a study was undertaken at the University of Arkansas Libraries to evaluate the practice of front-end authority work for monographs copy cataloging. A sample of 283 name headings originating from Library of Congress, OCLC "Enhance" member, and general member copy was examined, and analysis revealed that 47.3 percent of headings correctly matched authority records already present in the library's local file. Another 41.3 percent exactly matched records in the OCLC authority file. These findings prompted the library to cease checking name headings at the point of cataloging. However, the level of inaccuracies present, combined with the value of authority records for cross-reference and note information, ensured that the Database Maintenance Unit would continue to review local headings reports and perform needed authority work.

0.056584418 = product of:
  0.113168836 = sum of:
    0.060586188 = weight(_text_:reference in 5608) [ClassicSimilarity], result of:
      0.060586188 = score(doc=5608,freq=2.0), product of:
        0.19255297 = queryWeight, product of:
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.047329273 = queryNorm
        0.31464687 = fieldWeight in 5608, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5608)
    0.05258265 = product of:
      0.1051653 = sum of:
        0.1051653 = weight(_text_:file in 5608) [ClassicSimilarity], result of:
          0.1051653 = score(doc=5608,freq=2.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.4145461 = fieldWeight in 5608, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5608)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

Discusses the function of MARC field 670 in providing AACR authority control in OPACs through the AAAF: where field 670 is used to justify the form of content of established headings and their cross references. Reports results of a study of field 670 entries from national name authority records pertaining to the subject area of the Catholic Church in terms of: the number of field 670 entries per record; types of work cited; and information on the work themselves. Results indicate that considerable differences exist among the categories of authority records, with some (modern personal names and uniform titles) being more amenable to computerized generation. It was found possible to identify tentatively a core reference for authority work in a subject area

0.04840336 = product of:
  0.19361344 = sum of:
    0.19361344 = sum of:
      0.1487262 = weight(_text_:file in 156) [ClassicSimilarity], result of:
        0.1487262 = score(doc=156,freq=4.0), product of:
          0.25368783 = queryWeight, product of:
            5.3600616 = idf(docFreq=564, maxDocs=44218)
            0.047329273 = queryNorm
          0.58625674 = fieldWeight in 156, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            5.3600616 = idf(docFreq=564, maxDocs=44218)
            0.0546875 = fieldNorm(doc=156)
      0.04488724 = weight(_text_:22 in 156) [ClassicSimilarity], result of:
        0.04488724 = score(doc=156,freq=2.0), product of:
          0.16573904 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.047329273 = queryNorm
          0.2708308 = fieldWeight in 156, 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=156)
  0.25 = coord(1/4)

Abstract

Subject access in the OPAC, as discussed in this article, is predicated on two different kinds of searching: subject (authority, alphabetic, or controlled vocabulary searching) or keyword (uncontrolled, free text, natural language vocabulary). The literature has focused on demonstrating that both approaches are needed, but very few authors address the need to integrate keyword into authority searching. The article discusses this difference and compares, with a query on the term garbage, search results in two online catalogs, one that performs keyword searches through the authority file and one where only bibliographic records are included in keyword searches.

Date

10. 9.2000 17:38:22

0.041514903 = product of:
  0.08302981 = sum of:
    0.060586188 = weight(_text_:reference in 180) [ClassicSimilarity], result of:
      0.060586188 = score(doc=180,freq=2.0), product of:
        0.19255297 = queryWeight, product of:
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.047329273 = queryNorm
        0.31464687 = fieldWeight in 180, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.0546875 = fieldNorm(doc=180)
    0.02244362 = product of:
      0.04488724 = sum of:
        0.04488724 = weight(_text_:22 in 180) [ClassicSimilarity], result of:
          0.04488724 = score(doc=180,freq=2.0), product of:
            0.16573904 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.047329273 = queryNorm
            0.2708308 = fieldWeight in 180, 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=180)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

A variety of information communities have developed metadata schemes to meet the needs of their own users. The ability of libraries to incorporate and use multiple metadata schemes in current library systems will depend on the compatibility of imported data with existing catalog data. Authority control will play an important role in metadata interoperability. In this article, I discuss factors for successful authority control in current library catalogs, which include operation in a well-defined and bounded universe, application of principles and standard practices to access point creation, reference to authoritative lists, and bibliographic record creation by highly trained individuals. Metadata characteristics and environmental models are examined and the likelihood of successful authority control is explored for a variety of metadata environments.

Date

10. 9.2000 17:38:22

0.037513137 = product of:
  0.15005255 = sum of:
    0.15005255 = sum of:
      0.1051653 = weight(_text_:file in 5760) [ClassicSimilarity], result of:
        0.1051653 = score(doc=5760,freq=2.0), product of:
          0.25368783 = queryWeight, product of:
            5.3600616 = idf(docFreq=564, maxDocs=44218)
            0.047329273 = queryNorm
          0.4145461 = fieldWeight in 5760, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            5.3600616 = idf(docFreq=564, maxDocs=44218)
            0.0546875 = fieldNorm(doc=5760)
      0.04488724 = weight(_text_:22 in 5760) [ClassicSimilarity], result of:
        0.04488724 = score(doc=5760,freq=2.0), product of:
          0.16573904 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.047329273 = queryNorm
          0.2708308 = fieldWeight in 5760, 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=5760)
  0.25 = coord(1/4)

Date

10. 9.2000 17:38:22

0.029653504 = product of:
  0.05930701 = sum of:
    0.04327585 = weight(_text_:reference in 191) [ClassicSimilarity], result of:
      0.04327585 = score(doc=191,freq=2.0), product of:
        0.19255297 = queryWeight, product of:
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.047329273 = queryNorm
        0.22474778 = fieldWeight in 191, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.0683694 = idf(docFreq=2055, maxDocs=44218)
          0.0390625 = fieldNorm(doc=191)
    0.016031157 = product of:
      0.032062314 = sum of:
        0.032062314 = weight(_text_:22 in 191) [ClassicSimilarity], result of:
          0.032062314 = score(doc=191,freq=2.0), product of:
            0.16573904 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.047329273 = queryNorm
            0.19345059 = fieldWeight in 191, 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=191)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

International efforts to provide authority control include the work of IFLA, the AUTHOR Project funded by the European Commission, and related work conducted under the auspices of the ICA/CDS. IFLA developed the guidelines Form and Structure of Corporate Headings, documented the formulation of names along the lines of national origin in its publication Names of Persons, and published Guidelines for Authority and Reference Entries. Attention has shifted from a single authority record for each entity that would be shared internationally through the exchange of records to linking parallel authority records for the same entity. The access control of the future will account for difference in cataloging rules, transliteration standards, and cultural differences within the same language as well as for the need for different languages and scripts and will enable users to display the script and form of a heading that they expect. Project AUTHOR is a shared set of resource national authority files that used selections from the authority files of France, the United Kingdom, Spain, Portugal, and Belgium. The prototype tested an adaptation of Z39.50 server software for authority records and displays for user interface. An international standard for authority control records has been developed for corporate bodies, persons, and families. Through joint meetings efforts have been synchronized to develop authority control at the international level.

Date

10. 9.2000 17:38:22

0.026021665 = product of:
  0.10408666 = sum of:
    0.10408666 = product of:
      0.20817332 = sum of:
        0.20817332 = weight(_text_:file in 4191) [ClassicSimilarity], result of:
          0.20817332 = score(doc=4191,freq=6.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.8205885 = fieldWeight in 4191, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0625 = fieldNorm(doc=4191)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

The report deals with the necessity for developing a National Subject Authority File in russia. Basic approaches creating such a file creation are introduced. The history and main features of the National Library of Russia Subject authority File are described. The report includes information on number of projects being undertaken both in NLR and in Russia

0.025195366 = product of:
  0.10078146 = sum of:
    0.10078146 = product of:
      0.20156293 = sum of:
        0.20156293 = weight(_text_:file in 5179) [ClassicSimilarity], result of:
          0.20156293 = score(doc=5179,freq=10.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.79453135 = fieldWeight in 5179, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.046875 = fieldNorm(doc=5179)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Outlines the benefits sought by the Anglo American Authority File (AAF) project in replacing with a common authority file the Library of Congress US Name Authority File (USNAF) and the British Library Name Authority List (BLNAL). Describes the progress and techniques in the implementation of the project to create the AAF in the British Library (BL) and explains how it is used by cataloguers. Phase 1 was completed in 1996 with the loading of USNAF. Records were in USMARC format but searchable and reusable in conjunction with BLNAL. Phase 2 to eliminate duplicates was completed in 1997 for personal names and corporate names will be dealt with in 1999 when the BL Corporate Bibliographic System is also due to go live. This will prepare the ground for Phase 3, retrospective conversion to integrate BLNAL with USNAF into a single unified file

0.025195366 = product of:
  0.10078146 = sum of:
    0.10078146 = product of:
      0.20156293 = sum of:
        0.20156293 = weight(_text_:file in 310) [ClassicSimilarity], result of:
          0.20156293 = score(doc=310,freq=10.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.79453135 = fieldWeight in 310, product of:
              3.1622777 = tf(freq=10.0), with freq of:
                10.0 = termFreq=10.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.046875 = fieldNorm(doc=310)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Authority files have played an important role in improving the quality of indexing and subject cataloging. Although authorities can significantly improve search by increasing the number of access points, they are rarely an integral part of the information retrieval process, particularly end-users searches. A retrieval prototype, searchFAST, was developed to test the feasibility of using an authority file as an index to bibliographic records. searchFAST uses FAST (Faceted Application of Subject Terminology) as an index to OCLC's WorldCat.org bibliographic database. The searchFAST methodology complements, rather than replaces, existing WorldCat.org access. The bibliographic file is searched indirectly; first the authority file is searched to identify appropriate subject headings, then the headings are used to retrieve the matching bibliographic records. The prototype demonstrates the effectiveness and practicality of using an authority file as an index. Searching the authority file leverages authority control work by increasing the number of access points while supporting a simple interface designed for end-users.

0.022768958 = product of:
  0.09107583 = sum of:
    0.09107583 = product of:
      0.18215166 = sum of:
        0.18215166 = weight(_text_:file in 5495) [ClassicSimilarity], result of:
          0.18215166 = score(doc=5495,freq=6.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.71801496 = fieldWeight in 5495, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5495)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

This paper compares one hundred corporate names listed in the National Authority File (LC NAF) on OCLC with the corporate names listed on official corporate web pages collected between October 1st and November 30th, 2001 in order to understand and evaluate their differences. Twenty five percent of corporate names found in the National Authority File are different from the form of corporate names found on official corporate web pages in this study. This creates a concern that users may not be finding everything issued by corporate bodies in library catalogs. Which form of corporate names should catalogers use as the authorized headings?

0.022768958 = product of:
  0.09107583 = sum of:
    0.09107583 = product of:
      0.18215166 = sum of:
        0.18215166 = weight(_text_:file in 1939) [ClassicSimilarity], result of:
          0.18215166 = score(doc=1939,freq=6.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.71801496 = fieldWeight in 1939, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1939)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

This article describes the project to build the initial International Standard Name Identifier (ISNI) database by deploying the techniques used to develop the Virtual International Authority File (VIAF). It focuses particularly on the work of the OCLC team in transforming the VIAF "resource file" model of matched data into a robust, operational, and authoritative file of uniquely assigned ISNIs as a base for an ongoing ISNI assignment system, and on the quality assurance validation of the database provided by the British Library and the Bibliothèque nationale de France. The need for future interaction between ongoing ISNI assignment and name authority control in libraries is also explored.

0.022768958 = product of:
  0.09107583 = sum of:
    0.09107583 = product of:
      0.18215166 = sum of:
        0.18215166 = weight(_text_:file in 5796) [ClassicSimilarity], result of:
          0.18215166 = score(doc=5796,freq=6.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.71801496 = fieldWeight in 5796, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5796)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Local and regional authority files exist to cover gaps in national and international authority files. These types of authority files should not exist alone if they are going to be fully utilized by other institutions that may have resources about the same individuals or topics. This article discusses how the Western Name Authority File, a regional controlled vocabulary of personal names and corporate bodies, can link to larger authority files such as the Library of Congress Name Authority File and Wikidata. Workflows and issues encountered with linking this local authority file to larger authority files are discussed.

0.022535421 = product of:
  0.090141684 = sum of:
    0.090141684 = product of:
      0.18028337 = sum of:
        0.18028337 = weight(_text_:file in 4345) [ClassicSimilarity], result of:
          0.18028337 = score(doc=4345,freq=8.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.71065044 = fieldWeight in 4345, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.046875 = fieldNorm(doc=4345)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

The development of the National Authority File of Geographic Names has been carried out by the Russian State Library (RSL) since 2003 in the framework of the Federal program called "Russian culture (2001-2005)". The file will be a part of the complex of the authority files for the network of Russian libraries (LIBNET). Its aim is to provide usage of standardized Russian geographic names in the library practice (cataloguing of the documents and information retrieval), established officially on the federal level. The Russian National Authority File for Geographical Names is identified by the code "rugeo" in the MARC 21 format for use in subfield $2 for subject/index term sources.

0.022535421 = product of:
  0.090141684 = sum of:
    0.090141684 = product of:
      0.18028337 = sum of:
        0.18028337 = weight(_text_:file in 2978) [ClassicSimilarity], result of:
          0.18028337 = score(doc=2978,freq=8.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.71065044 = fieldWeight in 2978, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.046875 = fieldNorm(doc=2978)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

To date, the library literature has overflowed with articles on the theory and application of the FRBR conceptual model, but little has been written about its counterpart for authorities: the Functional Requirements for Authority Data conceptual model (FRAD). A few discussions of the theory of FRAD have been written by Glenn Patton and members of the FRANAR Working Group, but nothing has been documented yet about its application real authority files. The following article addresses this gap in the literature by analyzing the FRAD conceptual model, examining its applicability to an authority file for manuscripts, and proposing a way to implement and display this entity-relationship model in a local authority file. The usefulness of this FRAD-based authority file in cataloging manuscripts is evaluated and presented.

0.0212466 = product of:
  0.0849864 = sum of:
    0.0849864 = product of:
      0.1699728 = sum of:
        0.1699728 = weight(_text_:file in 5556) [ClassicSimilarity], result of:
          0.1699728 = score(doc=5556,freq=4.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.6700077 = fieldWeight in 5556, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0625 = fieldNorm(doc=5556)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Italy's ICCU (Istituto Centrale per il Catalogo Unico) is coordinating a national effort to build a shared online authority file through the National Library Service (SBN). The status of that project and the implications of maintaining such a resource are described.

0.0212466 = product of:
  0.0849864 = sum of:
    0.0849864 = product of:
      0.1699728 = sum of:
        0.1699728 = weight(_text_:file in 2499) [ClassicSimilarity], result of:
          0.1699728 = score(doc=2499,freq=4.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.6700077 = fieldWeight in 2499, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0625 = fieldNorm(doc=2499)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

The requirement for and development of the Anglo-American Authority File (AAAF) is described. The mechanics of its production and updating are indicated and its role within British Library cataloguing practice examined. Further developments of the file are discussed and developments through IFLA towards international exchange of authority data are described, indicating both opportunities and difficulties. The EC-funded project AUTHOR is outlined and, finally, the British Library's work with the Library of Congress and American Library Association on extending LCSH to works of fiction is described.

0.0212466 = product of:
  0.0849864 = sum of:
    0.0849864 = product of:
      0.1699728 = sum of:
        0.1699728 = weight(_text_:file in 5557) [ClassicSimilarity], result of:
          0.1699728 = score(doc=5557,freq=4.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.6700077 = fieldWeight in 5557, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0625 = fieldNorm(doc=5557)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

This paper gives a short overview of the library situation in the Bavarian Library Network and the authority files used in German libraries. It deals with the implementation of the authority file for personal names into the Bavarian Union Catalogue and the experiences in using it. Finally, it looks into costs and benefits of the use of authority files in the Bavarian Network Catalogue.

0.0212466 = product of:
  0.0849864 = sum of:
    0.0849864 = product of:
      0.1699728 = sum of:
        0.1699728 = weight(_text_:file in 440) [ClassicSimilarity], result of:
          0.1699728 = score(doc=440,freq=4.0), product of:
            0.25368783 = queryWeight, product of:
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.047329273 = queryNorm
            0.6700077 = fieldWeight in 440, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              5.3600616 = idf(docFreq=564, maxDocs=44218)
              0.0625 = fieldNorm(doc=440)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

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.