Search (39 results, page 1 of 2)

0.045698274 = product of:
  0.09139655 = sum of:
    0.069153175 = weight(_text_:services in 5760) [ClassicSimilarity], result of:
      0.069153175 = score(doc=5760,freq=4.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.40155616 = fieldWeight in 5760, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5760)
    0.022243375 = product of:
      0.04448675 = sum of:
        0.04448675 = weight(_text_:22 in 5760) [ClassicSimilarity], result of:
          0.04448675 = score(doc=5760,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = 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.5 = coord(1/2)
  0.5 = coord(2/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.

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 50(2006) no.3, S.166-172

0.040652603 = product of:
  0.081305206 = sum of:
    0.05588421 = weight(_text_:services in 249) [ClassicSimilarity], result of:
      0.05588421 = score(doc=249,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.3245064 = fieldWeight in 249, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0625 = fieldNorm(doc=249)
    0.025421001 = product of:
      0.050842002 = sum of:
        0.050842002 = weight(_text_:22 in 249) [ClassicSimilarity], result of:
          0.050842002 = score(doc=249,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.30952093 = fieldWeight in 249, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=249)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 52(2008) no.3, S.148-163

0.039717898 = product of:
  0.079435796 = sum of:
    0.05588421 = weight(_text_:services in 227) [ClassicSimilarity], result of:
      0.05588421 = score(doc=227,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.3245064 = fieldWeight in 227, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0625 = fieldNorm(doc=227)
    0.023551589 = product of:
      0.047103178 = sum of:
        0.047103178 = weight(_text_:management in 227) [ClassicSimilarity], result of:
          0.047103178 = score(doc=227,freq=2.0), product of:
            0.15810528 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046906993 = queryNorm
            0.29792285 = fieldWeight in 227, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.0625 = fieldNorm(doc=227)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

This article examines the implementation of an authority control project in the Keystone Library Network, an eighteen-member1 library consortium in Pennsylvania. The project was made possible with monies procured through two Library Services and Technology Act grants. The first grant funded staff training opportunities; the second covered base file cleanup of bibliographic records. The grant process and the management of the authority control project are described in detail.

0.03557103 = product of:
  0.07114206 = sum of:
    0.048898686 = weight(_text_:services in 120) [ClassicSimilarity], result of:
      0.048898686 = score(doc=120,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 120, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=120)
    0.022243375 = product of:
      0.04448675 = sum of:
        0.04448675 = weight(_text_:22 in 120) [ClassicSimilarity], result of:
          0.04448675 = score(doc=120,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.2708308 = fieldWeight in 120, 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=120)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 50(2006) no.1, S.31-41

0.03557103 = product of:
  0.07114206 = sum of:
    0.048898686 = weight(_text_:services in 156) [ClassicSimilarity], result of:
      0.048898686 = score(doc=156,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 156, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=156)
    0.022243375 = product of:
      0.04448675 = sum of:
        0.04448675 = weight(_text_:22 in 156) [ClassicSimilarity], result of:
          0.04448675 = score(doc=156,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = 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.5 = coord(1/2)
  0.5 = coord(2/4)

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 46(2002) no.3, S.111-

0.03557103 = product of:
  0.07114206 = sum of:
    0.048898686 = weight(_text_:services in 167) [ClassicSimilarity], result of:
      0.048898686 = score(doc=167,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 167, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=167)
    0.022243375 = product of:
      0.04448675 = sum of:
        0.04448675 = weight(_text_:22 in 167) [ClassicSimilarity], result of:
          0.04448675 = score(doc=167,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.2708308 = fieldWeight in 167, 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=167)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 45(2001) no.2, S.73-79

0.03557103 = product of:
  0.07114206 = sum of:
    0.048898686 = weight(_text_:services in 180) [ClassicSimilarity], result of:
      0.048898686 = score(doc=180,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 180, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=180)
    0.022243375 = product of:
      0.04448675 = sum of:
        0.04448675 = weight(_text_:22 in 180) [ClassicSimilarity], result of:
          0.04448675 = score(doc=180,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = 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)

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 44(2000) no.1, S.33-43

0.032641627 = product of:
  0.065283254 = sum of:
    0.049395125 = weight(_text_:services in 1291) [ClassicSimilarity], result of:
      0.049395125 = score(doc=1291,freq=4.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28682584 = fieldWeight in 1291, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1291)
    0.015888125 = product of:
      0.03177625 = sum of:
        0.03177625 = weight(_text_:22 in 1291) [ClassicSimilarity], result of:
          0.03177625 = score(doc=1291,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.19345059 = fieldWeight in 1291, 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=1291)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

More and more users index everything on their own in the web 2.0. There are services for links, videos, pictures, books, encyclopaedic articles and scientific articles. All these services are library independent. But must that really be? Can't libraries help with their experience and tools to make user indexing better? On the experience of a project from German language Wikipedia together with the German person authority files (Personen Namen Datei - PND) located at German National Library (Deutsche Nationalbibliothek) I would like to show what is possible. How users can and will use the authority files, if we let them. We will take a look how the project worked and what we can learn for future projects. Conclusions - Authority files can have a role in the web 2.0 - there must be an open interface/ service for retrieval - everything that is indexed on the net with authority files can be easy integrated in a federated search - O'Reilly: You have to found ways that your data get more important that more it will be used

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.029788423 = product of:
  0.059576847 = sum of:
    0.041913155 = weight(_text_:services in 5803) [ClassicSimilarity], result of:
      0.041913155 = score(doc=5803,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2433798 = fieldWeight in 5803, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046875 = fieldNorm(doc=5803)
    0.017663691 = product of:
      0.035327382 = sum of:
        0.035327382 = weight(_text_:management in 5803) [ClassicSimilarity], result of:
          0.035327382 = score(doc=5803,freq=2.0), product of:
            0.15810528 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046906993 = queryNorm
            0.22344214 = fieldWeight in 5803, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046875 = fieldNorm(doc=5803)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

In 2018, the national, bilingual authority file maintained by Library and Archives Canada (LAC), called Canadiana Authorities, underwent major changes when the internally-developed Integrated Library System (ILS) AMICUS was decommissioned and OCLC's WorldShare Management Services (WMS) was adopted as a replacement. As a part of the transition, LAC split its single, bilingual authority file Canadiana Authorities into separate English and French language files and joined Name Authority Cooperative Program (NACO) in order to manage its English-language authority records. This has been a significant change that has challenged the organization to rethink everyday practices while maintaining its commitments to the Canadian and global library community. This paper discusses this national library's history of bilingual cataloging, the reason for the changes, and the attempt to ensure that the two files "talk" to each other.

0.025407877 = product of:
  0.050815754 = sum of:
    0.03492763 = weight(_text_:services in 190) [ClassicSimilarity], result of:
      0.03492763 = score(doc=190,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2028165 = fieldWeight in 190, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0390625 = fieldNorm(doc=190)
    0.015888125 = product of:
      0.03177625 = sum of:
        0.03177625 = weight(_text_:22 in 190) [ClassicSimilarity], result of:
          0.03177625 = score(doc=190,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = queryNorm
            0.19345059 = fieldWeight in 190, 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=190)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 44(2000) no.3, S.114-121

0.025407877 = product of:
  0.050815754 = sum of:
    0.03492763 = weight(_text_:services in 191) [ClassicSimilarity], result of:
      0.03492763 = score(doc=191,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2028165 = fieldWeight in 191, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0390625 = fieldNorm(doc=191)
    0.015888125 = product of:
      0.03177625 = sum of:
        0.03177625 = weight(_text_:22 in 191) [ClassicSimilarity], result of:
          0.03177625 = score(doc=191,freq=2.0), product of:
            0.1642603 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046906993 = 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)

Date

10. 9.2000 17:38:22

Source

Library resources and technical services. 44(2000) no.3, S.168-172

0.024823686 = product of:
  0.049647372 = sum of:
    0.03492763 = weight(_text_:services in 3083) [ClassicSimilarity], result of:
      0.03492763 = score(doc=3083,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2028165 = fieldWeight in 3083, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0390625 = fieldNorm(doc=3083)
    0.014719742 = product of:
      0.029439485 = sum of:
        0.029439485 = weight(_text_:management in 3083) [ClassicSimilarity], result of:
          0.029439485 = score(doc=3083,freq=2.0), product of:
            0.15810528 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046906993 = queryNorm
            0.18620178 = fieldWeight in 3083, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3083)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

Authority control is a quite recent term in the long history of cataloguing, although the underlying principle is among the very early principles of bibliographic control. Bibliographic control is a Field in transformation by the rapid expansion of the WWW, which has brought new problems to infonnation discovery and retrieval, creating new challenges and requirements in information management. In a comprehensive approach, authority control is presented as one of the most promising library activities in this respect. The evolution of work methods and standards for the sharing of authority files is reviewed, showing the imbalance in developments and practical achievements between name and subject authority, in an international perspective. The need to improve the network availability and usability of authority information assets in more effective and holistic ways is underlyned; and a new philosophy and scope is proposed for library authority work, based an the primacy of the linking function of authority data, and by expanding the finding, relating and informing functions of authority records. Some of these aspects are being addressed in several projects dealing with knowledge organization systems, notably to cope with multilingual needs and to enable semantic interoperability among different systems. Library practice itself should evolve in the same direction, thereby providing practical experience to inform new or improved principles and standards for authority work, while contributing to enhance local information services and to promote their involvement in the WWW environment.

0.014818538 = product of:
  0.059274152 = sum of:
    0.059274152 = weight(_text_:services in 402) [ClassicSimilarity], result of:
      0.059274152 = score(doc=402,freq=4.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.344191 = fieldWeight in 402, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046875 = fieldNorm(doc=402)
  0.25 = coord(1/4)

Abstract

The implementation of our online integrated catalog ACORN at Vanderbilt University Library has been a complex and time-consuming task. The authority control component represents an important portion of the effort. The authority file consists of approximately one-half million name, subject, series, and uniform title headings, the majority of which were supplied to us by a vendor, Blackwell North America (BNA). Authority work has been integrated into our cataloging routine successfully, new headings are being added to our database daily, and extant headings are being validated online. This paper will cover a description of how Vanderbilt selected the Northwestern Online Total Integrated System (NOTIS); the ongoing editing of the authority file following the BNA processing; the interrelationship of Vanderbilt University Library's three processing units, General Technical Services (GTS), Medical Library, and Law Library apropos of the authority function; and some of the policies and procedures drawn up by the Authority Control Coordinator with the assistance of the other librarians in Monograph and Serial Services.

0.012224671 = product of:
  0.048898686 = sum of:
    0.048898686 = weight(_text_:services in 5353) [ClassicSimilarity], result of:
      0.048898686 = score(doc=5353,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 5353, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5353)
  0.25 = coord(1/4)

Abstract

Argues that the efforts to achieve authority control in online catalogues are both misguided and counterproductive. Contrasts the characteristics of manual and online catalogues, demonstrating that although authority control may be beneficial in a traditional, manually produced catalogue, it is of little or no value in the online environment. Suggests that in future authority control may be dispensed with, thus releasing professional library staff from routine cataloguing tasks and leading to a greater integration of library services

0.012224671 = product of:
  0.048898686 = sum of:
    0.048898686 = weight(_text_:services in 5607) [ClassicSimilarity], result of:
      0.048898686 = score(doc=5607,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 5607, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5607)
  0.25 = coord(1/4)

Abstract

Many kinds of structure can be discerned in the headings and rules governing the Library of Congress Subject Headings. By addressing these structures at different levels, librarians can develop different approaches to the machine-assisted validation of subject headings, from the checking of individual words to the validation of complex forms of heading/subdivision compatibility. Using computer programs to assist with maintenance of subject headings is becoming increasingly necessary as technical services librarians strive to create consistent and useful patterns of subject collocation in library catalogs

0.012224671 = product of:
  0.048898686 = sum of:
    0.048898686 = weight(_text_:services in 2976) [ClassicSimilarity], result of:
      0.048898686 = score(doc=2976,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 2976, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2976)
  0.25 = coord(1/4)

Abstract

Neither the standards nor the software underlying institutional repositories anticipated performing name authority control on widely disparate metadata from highly unreliable sources. Without it, though, both machines and humans are stymied in their efforts to access and aggregate information by author. Many organizations are awakening to the problems and possibilities of name authority control, but without better coordination, their efforts will only confuse matters further. Local heuristics-based name-disambiguation software may help those repository managers who can implement it. For the time being, however, most repository managers can only control their own name lists as best they can after deposit while they advocate for better systems and services.

0.012224671 = product of:
  0.048898686 = sum of:
    0.048898686 = weight(_text_:services in 1076) [ClassicSimilarity], result of:
      0.048898686 = score(doc=1076,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.28394312 = fieldWeight in 1076, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.0546875 = fieldNorm(doc=1076)
  0.25 = coord(1/4)

Abstract

Authority data has always been at the core of library catalogues. Today, authority data is reference data on a wider scale. The former authorities of the "Sudoc" union catalogue mutated into "IdRef", a read/write platform of open data and services which seeks to become a national supplier of reliable identifiers for French universities. To support their dissemination and comply with high quality standards, Paprika and Qualinka have been added to our toolbox, to expedite the massive and secure linking of scientific publications to IdRef authorities.

0.010478289 = product of:
  0.041913155 = sum of:
    0.041913155 = weight(_text_:services in 5666) [ClassicSimilarity], result of:
      0.041913155 = score(doc=5666,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2433798 = fieldWeight in 5666, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046875 = fieldNorm(doc=5666)
  0.25 = coord(1/4)

Abstract

This paper discusses the concept of "metadata" in the scope of the "digital library," two terms recently used in a great diversity of perspectives. It is not the intent to promote privilege of any particular view, but rather to help provide a better understanding of these multiple perspectives. The paper starts with a discussion of the concept of digital library, followed by an analysis of the concept of metadata. It continues with a discussion about the relationship of this concept with technology, services, and scenarios of application. The concluding remarks stress the three main arguments assumed for the relevance of the concept of metadata: the growing number of heterogeneous genres of information resources, the new emerging scenarios for interoperability, and issues related to the cost and complexity of current technology.

0.010478289 = product of:
  0.041913155 = sum of:
    0.041913155 = weight(_text_:services in 5667) [ClassicSimilarity], result of:
      0.041913155 = score(doc=5667,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2433798 = fieldWeight in 5667, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046875 = fieldNorm(doc=5667)
  0.25 = coord(1/4)

Abstract

Forty years ago the ICCP in Paris laid the foundations of international co-operation in descriptive cataloging without explicitly speaking of authority control. Some of the factors in the evolution of authority control are the development of catalogs (from card catalog to local automation, to today's OPAC on the Web) and services provided by libraries (from individual service to local users to system networks, to the World Wide Web), as well as international agreements on cataloging (from Paris Principles to the UBC programme, to the report on Mandatory data elements for internationally shared resource authority records). This evolution progressed from the principle of uniform heading to the definition of authority entries and records, and from the responsibility of national bibliographic agencies for the form of the names of their own authors to be shared internationally to the concept of authorized equivalent heading. Some issues of the present state are the persisting differences among national rules and the aim of respecting both local culture and language and international readability.

0.010478289 = product of:
  0.041913155 = sum of:
    0.041913155 = weight(_text_:services in 2195) [ClassicSimilarity], result of:
      0.041913155 = score(doc=2195,freq=2.0), product of:
        0.17221296 = queryWeight, product of:
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046906993 = queryNorm
        0.2433798 = fieldWeight in 2195, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.6713707 = idf(docFreq=3057, maxDocs=44218)
          0.046875 = fieldNorm(doc=2195)
  0.25 = coord(1/4)

Abstract

«Current proposals for the future of the Web describe the use of ontologies for making the Web more intelligent for machine and automatic processing. The Virtual International Authority File (VIAF) could be one of the basic building blocks to a »semantic web« when combined with other controlled vocabularies and authority files from such sources as abstracting and indexing services, archives, museums, publishers, etc. Libraries now have an opportunity to make a great contribution to this future and should help make this vision a reality.« This article gives a status report on the VIAF, a cooperative project of the Library of Congress, the Bibliotheque nationale de France, OCLC and the German National Library.