Search (8 results, page 1 of 1)

0.017229345 = product of:
  0.05168803 = sum of:
    0.05168803 = weight(_text_:development in 863) [ClassicSimilarity], result of:
      0.05168803 = score(doc=863,freq=2.0), product of:
        0.16011542 = queryWeight, product of:
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.04384008 = queryNorm
        0.32281733 = fieldWeight in 863, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.0625 = fieldNorm(doc=863)
  0.33333334 = coord(1/3)

Imprint

London : British Library / Research and Development Department

0.0152287325 = product of:
  0.045686197 = sum of:
    0.045686197 = weight(_text_:development in 5540) [ClassicSimilarity], result of:
      0.045686197 = score(doc=5540,freq=4.0), product of:
        0.16011542 = queryWeight, product of:
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.04384008 = queryNorm
        0.2853329 = fieldWeight in 5540, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5540)
  0.33333334 = coord(1/3)

Abstract

Reviews the 20 years' evolution and development of the USBC, as a means of overcoming the weaknesses inherent in the ISBN, from its first proposal in 1974. Briefly describes the various phases of USBC's development, including: fisrt extensive testing (1977-1979); first research project (1980-82); work performed on USBC as part of proposals for the setting up of the United Kingdom Library Database System (UKLDS) (1982-84), in which USBC was to be used to create a merged retrospective database of MARC and non MARC cataloguing records; the DOCMATCH Projects, using the USBC with periodical articles (1987-89); refining of USBC by means of expert systems (1986-87); use of USBC to clean up the BLCMP database (1989-91); and the QUALCAT Project, to set up a large bibliographic database integrating records from different databases and using USBC for merging, cleaning and control and to develop an expert system to select the best record from a number of duplicates (1989-91). Reports briefly on the project, undertaken by Bradford University, Dept. of Computing, UK, to explore the application of USBC technology to the British Library Document Supply Centre's computerized interloans system. Concludes that, although the USBC has never achieved the status of an accepted standard, it has more than made for this by demonstrating its adaptibility and power in a range of situation requiring an ability to detect duplicate records and to merge and combine files

0.015075676 = product of:
  0.04522703 = sum of:
    0.04522703 = weight(_text_:development in 6294) [ClassicSimilarity], result of:
      0.04522703 = score(doc=6294,freq=2.0), product of:
        0.16011542 = queryWeight, product of:
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.04384008 = queryNorm
        0.28246516 = fieldWeight in 6294, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.0546875 = fieldNorm(doc=6294)
  0.33333334 = coord(1/3)

Imprint

London : British Library / Research and Development Department

0.015075676 = product of:
  0.04522703 = sum of:
    0.04522703 = weight(_text_:development in 1787) [ClassicSimilarity], result of:
      0.04522703 = score(doc=1787,freq=2.0), product of:
        0.16011542 = queryWeight, product of:
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.04384008 = queryNorm
        0.28246516 = fieldWeight in 1787, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1787)
  0.33333334 = coord(1/3)

Abstract

Describes work of the BOPAC2 project, funded by the British Library Research and Inoovation Centre, from Sep 1996 to Jan 1997, to investigate the issues involved in managing large and complex retrievals involving Z39.50 searches, including searches of multiple databases. The system is a WWW front end that allows simultaneously access to a number of library OPACs via Z39.50. The system is designed to make access to large and complex retrieval simpler, similar records are clustered together and retrievals may be sorted in a number of ways and by different criteria. Describes the design, development and evaluation of the system with suggestions for future work

0.015075676 = product of:
  0.04522703 = sum of:
    0.04522703 = weight(_text_:development in 5348) [ClassicSimilarity], result of:
      0.04522703 = score(doc=5348,freq=2.0), product of:
        0.16011542 = queryWeight, product of:
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.04384008 = queryNorm
        0.28246516 = fieldWeight in 5348, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5348)
  0.33333334 = coord(1/3)

Abstract

This paper describes a Research Project, funded by the British Library Research and Innovation Centre, from September 1996 to January 1998.1 The Project developed and extensively tested and evaluated a World Wide Web front end called BOPAC2 that allows access to a number of library catalogues via Z39.50 either simultaneously or individually. BOPAC2 is designed to make access to large and complex retrievals simpler. Similar records are clustered together and retrievals may be sorted in a number of ways and by different criteria. The design, development and evaluation of the system are described along with suggestions for future work

0.012922008 = product of:
  0.038766023 = sum of:
    0.038766023 = weight(_text_:development in 257) [ClassicSimilarity], result of:
      0.038766023 = score(doc=257,freq=2.0), product of:
        0.16011542 = queryWeight, product of:
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.04384008 = queryNorm
        0.242113 = fieldWeight in 257, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.046875 = fieldNorm(doc=257)
  0.33333334 = coord(1/3)

Abstract

This article describes cooperation between Bradford University Library and the Department of Computing that has resulted in nine research projects over a twenty five year period on various aspects of bibliographic control. It recounts the origins of the Universal Standard Bibliographic Code (USBC) and its development for the identification of both books and non book material. It then describes various aspects of the projects including simulating the merging necessary to set up a national database, the cleaning of a database, its use in inter library lending, and its application together with expert systems for the quality control of databases. The final project is BOPAC that has used modern technology to create faster and better access to a number of library catalogues worldwide and has demonstrated that authority control in its present form is not effective.

0.010768341 = product of:
  0.03230502 = sum of:
    0.03230502 = weight(_text_:development in 5553) [ClassicSimilarity], result of:
      0.03230502 = score(doc=5553,freq=2.0), product of:
        0.16011542 = queryWeight, product of:
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.04384008 = queryNorm
        0.20176083 = fieldWeight in 5553, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.652261 = idf(docFreq=3116, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5553)
  0.33333334 = coord(1/3)

Abstract

At the beginning of the eighties the Library Establishment was engaged in a battle with the heretics over the implementation of AACR2. Those who were in favour of the new code wanted immediate implementation of AACR2. The critics, however, wanted delay, arguing that the disruption of implementation would damage library services and be very expensive. They also argued that delay would mean that progress in automation would make implementation easier in a few years time. No one would claim that the early implementation was a complete disaster. Few, however, could pretend that it made a dramatic impact in improving the quality of our catalogues while some would argue that it had made them worse. Since there are no figures for the cost of the implementation the critics are justified in arguing that the Library of Congress and the British Library paid a heavy price in order to ensure that implementation took place. Today we face a new challenge. Bibliographic control is at a stage of development which could lead to a dramatic improvement in its scope and effectiveness. This will not be done by producing another edition of AACR. Nor will it be done by maintaining that the main entry is essential. Horizons need to be widened. Principles need to be reexamined. New methods need to be considered and the whole exercise must be linked to automation and not the traditional methods of the past. This paper is an attempt to look at some of the possibilities.

0.004619787 = product of:
  0.0138593605 = sum of:
    0.0138593605 = product of:
      0.04157808 = sum of:
        0.04157808 = weight(_text_:22 in 5162) [ClassicSimilarity], result of:
          0.04157808 = score(doc=5162,freq=2.0), product of:
            0.1535205 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04384008 = queryNorm
            0.2708308 = fieldWeight in 5162, 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=5162)
      0.33333334 = coord(1/3)
  0.33333334 = coord(1/3)

Source

Cataloging and classification quarterly. 22(1996) no.1, S.3-28