Search (21 results, page 1 of 2)

0.045621287 = product of:
  0.091242574 = sum of:
    0.091242574 = sum of:
      0.05638113 = weight(_text_:network in 190) [ClassicSimilarity], result of:
        0.05638113 = score(doc=190,freq=2.0), product of:
          0.22917621 = queryWeight, product of:
            4.4533744 = idf(docFreq=1398, maxDocs=44218)
            0.05146125 = queryNorm
          0.2460165 = fieldWeight in 190, product of:
            1.4142135 = tf(freq=2.0), with freq of:
              2.0 = termFreq=2.0
            4.4533744 = idf(docFreq=1398, maxDocs=44218)
            0.0390625 = fieldNorm(doc=190)
      0.034861445 = weight(_text_:22 in 190) [ClassicSimilarity], result of:
        0.034861445 = score(doc=190,freq=2.0), product of:
          0.18020853 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.05146125 = 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)

Date

10. 9.2000 17:38:22

0.031893983 = product of:
  0.06378797 = sum of:
    0.06378797 = product of:
      0.12757593 = sum of:
        0.12757593 = weight(_text_:network in 5557) [ClassicSimilarity], result of:
          0.12757593 = score(doc=5557,freq=4.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.5566718 = fieldWeight in 5557, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.0625 = fieldNorm(doc=5557)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.031893983 = product of:
  0.06378797 = sum of:
    0.06378797 = product of:
      0.12757593 = sum of:
        0.12757593 = weight(_text_:network in 227) [ClassicSimilarity], result of:
          0.12757593 = score(doc=227,freq=4.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.5566718 = fieldWeight in 227, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.0625 = fieldNorm(doc=227)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.020916866 = product of:
  0.041833732 = sum of:
    0.041833732 = product of:
      0.083667465 = sum of:
        0.083667465 = weight(_text_:22 in 131) [ClassicSimilarity], result of:
          0.083667465 = score(doc=131,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = queryNorm
            0.46428138 = fieldWeight in 131, 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=131)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.020916866 = product of:
  0.041833732 = sum of:
    0.041833732 = product of:
      0.083667465 = sum of:
        0.083667465 = weight(_text_:22 in 1266) [ClassicSimilarity], result of:
          0.083667465 = score(doc=1266,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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.5 = coord(1/2)
  0.5 = coord(1/2)

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.020916866 = product of:
  0.041833732 = sum of:
    0.041833732 = product of:
      0.083667465 = sum of:
        0.083667465 = weight(_text_:22 in 1290) [ClassicSimilarity], result of:
          0.083667465 = score(doc=1290,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = queryNorm
            0.46428138 = fieldWeight in 1290, 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=1290)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.01993374 = product of:
  0.03986748 = sum of:
    0.03986748 = product of:
      0.07973496 = sum of:
        0.07973496 = weight(_text_:network in 3083) [ClassicSimilarity], result of:
          0.07973496 = score(doc=3083,freq=4.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.34791988 = fieldWeight in 3083, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3083)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.01993374 = product of:
  0.03986748 = sum of:
    0.03986748 = product of:
      0.07973496 = sum of:
        0.07973496 = weight(_text_:network in 5687) [ClassicSimilarity], result of:
          0.07973496 = score(doc=5687,freq=4.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.34791988 = fieldWeight in 5687, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5687)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

InterParty is a project that aims to develop a mechanism that will enable the interoperation of identifiers for "parties" or persons (authors, publishers, etc. - persons and corporate bodies in library authority files) across multiple domains. Partners represent the book industry, rights management, libraries, and identifier and technology communities, united by their perception of a common benefit from interoperation in terms of access to "common metadata" held by other members to improve the quality of their own data. The InterParty solution proposes a distributed network of members who provide access to "common metadata," defined as information in the public domain, sufficient to identify and distinguish the "public identity" of a person. At a minimum the InterParty network would provide access to multiple domains of data about persons, including multiple library authority files, author licensing data files, etc. It will also add value by providing a facility for linking records between different data files by means of a "link record." Link records will assert that an identity recorded in one database is the same as another identity recorded in another database. Linked data will be mutually enriching and therefore more reliable and supportive of accurate disambiguation of persons within and between databases. InterParty has potential to develop a common system that supports both the emerging needs of e-commerce and the traditional requirements of library authority control.

0.016914338 = product of:
  0.033828676 = sum of:
    0.033828676 = product of:
      0.06765735 = sum of:
        0.06765735 = weight(_text_:network in 4345) [ClassicSimilarity], result of:
          0.06765735 = score(doc=4345,freq=2.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.29521978 = fieldWeight in 4345, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.046875 = fieldNorm(doc=4345)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

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.014095282 = product of:
  0.028190564 = sum of:
    0.028190564 = product of:
      0.05638113 = sum of:
        0.05638113 = weight(_text_:network in 5678) [ClassicSimilarity], result of:
          0.05638113 = score(doc=5678,freq=2.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.2460165 = fieldWeight in 5678, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.0390625 = fieldNorm(doc=5678)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Explicit authority control of works is essentially non-existent. Our catalogs are built on a principle of controlling headings, and primarily headings for names of authors. Our syndetic structure creates a spider's web of networked relationships among forms of headings, but it ends there, despite the potential richness of depth among bibliographic entities. Effective authority control of works could yield richness in the catalog that would enhance retrieval capabilities. Works are considered to constitute the intellectual content of informative artifacts that may be collected and ordered for retrieval. In a 1992 study the author examined a random sample of works drawn from the catalog of the Georgetown University Library. For each progenitor work, an instantiation network (also referred to as a bibliographic family) was constituted. A detailed analysis of the linkages that would be required for authority control of these networks is reviewed here. A new study is also presented, in which Library of Congress authority records for the works in this sample are sought and analyzed. Results demonstrate a near total lack of control, with only 5.6% of works for which authority records were found. From a sample of 410 works, of which nearly half have instantiation networks, only 23 works could be said to have implicit authority control. However, many instantiation networks are made up of successive derivations that can be implicitly linked through collocation. The difficult work of explicitly linking instantiations comes with title changes, translations, and containing relations. The empirical evidence in the present study suggests that explicit control of expressions will provide the best control over instantiation networks because it is instantiations such as translations, abridgments, and adaptations that require explicit linking.

0.014095282 = product of:
  0.028190564 = sum of:
    0.028190564 = product of:
      0.05638113 = sum of:
        0.05638113 = weight(_text_:network in 2295) [ClassicSimilarity], result of:
          0.05638113 = score(doc=2295,freq=2.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.2460165 = fieldWeight in 2295, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2295)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

The paper provides an illustration of the benefits of subject authority control improving multilingual subject access in NEBIS - Netzwerk von Bibliotheken und Informationsstellen in der Schweiz. This example of good practice focuses on some important aspects of classification and indexing. NEBIS subject authorities comprise a classification scheme and multilingual subject descriptor system. A bibliographic system supported by subject authority control empowers libraries as it enables them to expand and adjust vocabulary and link subjects to suit their specific audience. Most importantly it allows the management of different subject vocabularies in numerous languages. In addition, such an enriched subject index creates re-usable and shareable source of subject statements that has value in the wider context of information exchange. The illustrations and supporting arguments are based on indexing practice, subject authority control and use of classification in ETH-Bibliothek, which is the largest library within the NEBIS network.

0.013944578 = product of:
  0.027889157 = sum of:
    0.027889157 = product of:
      0.055778313 = sum of:
        0.055778313 = weight(_text_:22 in 249) [ClassicSimilarity], result of:
          0.055778313 = score(doc=249,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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(1/2)

Date

10. 9.2000 17:38:22

0.012201506 = product of:
  0.024403011 = sum of:
    0.024403011 = product of:
      0.048806023 = sum of:
        0.048806023 = weight(_text_:22 in 5760) [ClassicSimilarity], result of:
          0.048806023 = score(doc=5760,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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(1/2)

Date

10. 9.2000 17:38:22

0.012201506 = product of:
  0.024403011 = sum of:
    0.024403011 = product of:
      0.048806023 = sum of:
        0.048806023 = weight(_text_:22 in 120) [ClassicSimilarity], result of:
          0.048806023 = score(doc=120,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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(1/2)

Date

10. 9.2000 17:38:22

0.012201506 = product of:
  0.024403011 = sum of:
    0.024403011 = product of:
      0.048806023 = sum of:
        0.048806023 = weight(_text_:22 in 156) [ClassicSimilarity], result of:
          0.048806023 = score(doc=156,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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(1/2)

Date

10. 9.2000 17:38:22

0.012201506 = product of:
  0.024403011 = sum of:
    0.024403011 = product of:
      0.048806023 = sum of:
        0.048806023 = weight(_text_:22 in 167) [ClassicSimilarity], result of:
          0.048806023 = score(doc=167,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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(1/2)

Date

10. 9.2000 17:38:22

0.012201506 = product of:
  0.024403011 = sum of:
    0.024403011 = product of:
      0.048806023 = sum of:
        0.048806023 = weight(_text_:22 in 180) [ClassicSimilarity], result of:
          0.048806023 = score(doc=180,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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(1/2)

Date

10. 9.2000 17:38:22

0.00996687 = product of:
  0.01993374 = sum of:
    0.01993374 = product of:
      0.03986748 = sum of:
        0.03986748 = weight(_text_:network in 1166) [ClassicSimilarity], result of:
          0.03986748 = score(doc=1166,freq=4.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.17395994 = fieldWeight in 1166, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.01953125 = fieldNorm(doc=1166)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

This article presents an overview of the LEAF project (Linking and Exploring Authority Files)1, which has set out to provide a framework for international, collaborative work in the sector of authority data with respect to authority control. Elaborating the virtues of authority control in today's Web environment is an almost futile exercise, since so much has been said and written about it in the last few years.2 The World Wide Web is generally understood to be poorly structured-both with regard to content and to locating required information. Highly structured databases might be viewed as small islands of precision within this chaotic environment. Though the Web in general or any particular structured database would greatly benefit from increased authority control, it should be noted that our following considerations only refer to authority control with regard to databases of "memory institutions" (i.e., libraries, archives, and museums). Moreover, when talking about authority records, we exclusively refer to personal name authority records that describe a specific person. Although different types of authority records could indeed be used in similar ways to the ones presented in this article, discussing those different types is outside the scope of both the LEAF project and this article. Personal name authority records-as are all other "authorities"-are maintained as separate records and linked to various kinds of descriptive records. Name authority records are usually either kept in independent databases or in separate tables in the database containing the descriptive records. This practice points at a crucial benefit: by linking any number of descriptive records to an authorized name record, the records related to this entity are collocated in the database. Variant forms of the authorized name are referenced in the authority records and thus ensure the consistency of the database while enabling search and retrieval operations that produce accurate results. On one hand, authority control may be viewed as a positive prerequisite of a consistent catalogue; on the other, the creation of new authority records is a very time consuming and expensive undertaking. As a consequence, various models of providing access to existing authority records have emerged: the Library of Congress and the French National Library (Bibliothèque nationale de France), for example, make their authority records available to all via a web-based search service.3 In Germany, the Personal Name Authority File (PND, Personennamendatei4) maintained by the German National Library (Die Deutsche Bibliothek, Frankfurt/Main) offers a different approach to shared access: within a closed network, participating institutions have online access to their pooled data. The number of recent projects and initiatives that have addressed the issue of authority control in one way or another is considerable.5 Two important current initiatives should be mentioned here: The Name Authority Cooperative (NACO) and Virtual International Authority File (VIAF).
NACO was established in 1976 and is hosted by the Library of Congress. At the beginning of 2003, nearly 400 institutions were involved in this undertaking, including 43 institutions from outside the United States.6 Despite the enormous success of NACO and the impressive annual growth of the initiative, there are requirements for participation that form an obstacle for many institutions: they have to follow the Anglo-American Cataloguing Rules (AACR2) and employ the MARC217 data format. Participating institutions also have to belong to either OCLC (Online Computer Library Center) or RLG (Research Libraries Group) in order to be able to contribute records, and they have to provide a specified minimum number of authority records per year. A recent proof of concept project of the Library of Congress, OCLC and the German National Library-Virtual International Authority File (VIAF)8-will, in its first phase, test automatic linking of the records of the Library of Congress Name Authority File (LCNAF) and the German Personal Name Authority File by using matching algorithms and software developed by OCLC. The results are expected to form the basis of a "Virtual International Authority File". The project will then test the maintenance of the virtual authority file by employing the Open Archives Initiative Protocol for Metadata Harvesting (OAI-PMH)9 to harvest the metadata for new, updated, and deleted records. When using the "Virtual International Authority File" a cataloguer will be able to check the system to see whether the authority record he wants to establish already exists. The final phase of the project will test possibilities for displaying records in the preferred language and script of the end user. Currently, there are still some clear limitations associated with the ways in which authority records are used by memory institutions. One of the main problems has to do with limited access: generally only large institutions or those that are part of a library network have unlimited online access to permanently updated authority records. Smaller institutions outside these networks usually have to fall back on less efficient ways of obtaining authority data, or have no access at all. Cross-domain sharing of authority data between libraries, archives, museums and other memory institutions simply does not happen at present. Public users are, by and large, not even aware that such things as name authority records exist and are excluded from access to these information resources.

0.009866697 = product of:
  0.019733394 = sum of:
    0.019733394 = product of:
      0.039466787 = sum of:
        0.039466787 = weight(_text_:network in 5042) [ClassicSimilarity], result of:
          0.039466787 = score(doc=5042,freq=2.0), product of:
            0.22917621 = queryWeight, product of:
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.05146125 = queryNorm
            0.17221154 = fieldWeight in 5042, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.4533744 = idf(docFreq=1398, maxDocs=44218)
              0.02734375 = fieldNorm(doc=5042)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Testing on the syntactic component of the language is in progress, carried out by a team working on the basis of some terms of the Thesaurus which have been identified for possessing some special features. This will maybe lead to some changes and simplifications in the original structures coming from the GRIS model <http://wwwaib.it/aib/commiss/gris/ guida.htm> and the Feasibility Study. Within June 2006, two basic documents will be published: - a paper volume containing the Rules, concerning both terminology and syntax, explanations of the Thesaurus, criteria, choices made about the categories and the width of the semantic network, etc.; - a CD containing the Thesaurus. One side of great interest will be the c-learning process of the indexing language of the new Soggettario. This has to be undertaken only after the prototype stage is done. At that time, once the text of the Rules will have been published, it will be possible for the system to spread, to be learned, and to be tested by various indexers and partners.

0.008715361 = product of:
  0.017430723 = sum of:
    0.017430723 = product of:
      0.034861445 = sum of:
        0.034861445 = weight(_text_:22 in 191) [ClassicSimilarity], result of:
          0.034861445 = score(doc=191,freq=2.0), product of:
            0.18020853 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05146125 = 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(1/2)

Date

10. 9.2000 17:38:22