Search (95 results, page 1 of 5)

0.031173116 = product of:
  0.06234623 = sum of:
    0.005885557 = product of:
      0.023542227 = sum of:
        0.023542227 = weight(_text_:based in 1769) [ClassicSimilarity], result of:
          0.023542227 = score(doc=1769,freq=2.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.16644597 = fieldWeight in 1769, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.0390625 = fieldNorm(doc=1769)
      0.25 = coord(1/4)
    0.056460675 = weight(_text_:term in 1769) [ClassicSimilarity], result of:
      0.056460675 = score(doc=1769,freq=2.0), product of:
        0.21904005 = queryWeight, product of:
          4.66603 = idf(docFreq=1130, maxDocs=44218)
          0.04694356 = queryNorm
        0.25776416 = fieldWeight in 1769, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.66603 = idf(docFreq=1130, maxDocs=44218)
          0.0390625 = fieldNorm(doc=1769)
  0.5 = coord(2/4)

Abstract

Purpose - Bibliographic records should now be used in innovative end-user applications that enable users to learn about, discover and exploit available content, and this information should be interpreted and reused also beyond the library domain. New conceptual models such as FRBR offer the foundation for such developments. The main motivation for this research is to contribute to the adoption of the FRBR model in future bibliographic standards and systems, by analysing limitations in existing bibliographic information and looking for short- and long-term solutions that can improve the data quality in terms of expressing the FRBR model. Design/methodology/approach - MARC records in three collections (BIBSYS catalogue, Slovenian National Bibliography and BTJ catalogue) were first analysed by looking at statistics of field and subfield usage to determine common patterns that express FRBR. Based on this, different rules for interpreting the information were developed. Finally typical problems/errors found in MARC records were analysed. Findings - Different types of FRBR entity-relationship structures that typically can be found in bibliographic records are identified. Problems related to interpreting these from bibliographic records are analyzed. Frbrisation of consistent and complete MARC records is relatively successful, particularly if all entities are systematically described and relationships among them are clearly indicated. Research limitations/implications - Advanced matching was not used for clustering of identical entities. Practical implications - Cataloguing guidelines are proposed to enable better frbrisation of MARC records in the interim period, before new formats are developed and implemented. Originality/value - This is the first in depth analysis of manifestations embodying several expressions and of works and agents as subjects.

0.019761236 = product of:
  0.079044946 = sum of:
    0.079044946 = weight(_text_:term in 8166) [ClassicSimilarity], result of:
      0.079044946 = score(doc=8166,freq=2.0), product of:
        0.21904005 = queryWeight, product of:
          4.66603 = idf(docFreq=1130, maxDocs=44218)
          0.04694356 = queryNorm
        0.36086982 = fieldWeight in 8166, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.66603 = idf(docFreq=1130, maxDocs=44218)
          0.0546875 = fieldNorm(doc=8166)
  0.25 = coord(1/4)

Abstract

Discusses the origins of the concept of main entry and of confusion about what is meant by the term: a card in the catalogue, or a line above the the description serving as an access point. Examines the drawbacks of dual meaning: the full bibliographic record headed by the name of the author; and the author heading itself. Calls for change in the transfer to the electronic catalogue of terminology that was only descriptive and meaningful in the card catalogue. Proposes, in answer to the question of how the role of the entry can be transformed into uniform, collocative author-name access in the MARC record, that the 100/110 main entry MARC field be transformed into the primary field for the creator's authorized personal or corporate name

0.018703869 = product of:
  0.037407737 = sum of:
    0.0035313342 = product of:
      0.014125337 = sum of:
        0.014125337 = weight(_text_:based in 1169) [ClassicSimilarity], result of:
          0.014125337 = score(doc=1169,freq=2.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.09986758 = fieldWeight in 1169, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.0234375 = fieldNorm(doc=1169)
      0.25 = coord(1/4)
    0.033876404 = weight(_text_:term in 1169) [ClassicSimilarity], result of:
      0.033876404 = score(doc=1169,freq=2.0), product of:
        0.21904005 = queryWeight, product of:
          4.66603 = idf(docFreq=1130, maxDocs=44218)
          0.04694356 = queryNorm
        0.1546585 = fieldWeight in 1169, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          4.66603 = idf(docFreq=1130, maxDocs=44218)
          0.0234375 = fieldNorm(doc=1169)
  0.5 = coord(2/4)

Abstract

T.1: Today's thesauri are mostly electronic tools, having moved on from the paper-based era when thesaurus standards were first developed. They are built and maintained with the support of software and need to integrate with other software, such as search engines and content management systems. Whereas in the past thesauri were designed for information professionals trained in indexing and searching, today there is a demand for vocabularies that untrained users will find to be intuitive. ISO 25964 makes the transition needed for the world of electronic information management. However, part 1 retains the assumption that human intellect is usually involved in the selection of indexing terms and in the selection of search terms. If both the indexer and the searcher are guided to choose the same term for the same concept, then relevant documents will be retrieved. This is the main principle underlying thesaurus design, even though a thesaurus built for human users may also be applied in situations where computers make the choices. Efficient exchange of data is a vital component of thesaurus management and exploitation. Hence the inclusion in this standard of recommendations for exchange formats and protocols. Adoption of these will facilitate interoperability between thesaurus management systems and the other computer applications, such as indexing and retrieval systems, that will utilize the data. Thesauri are typically used in post-coordinate retrieval systems, but may also be applied to hierarchical directories, pre-coordinate indexes and classification systems. Increasingly, thesaurus applications need to mesh with others, such as automatic categorization schemes, free-text search systems, etc. Part 2 of ISO 25964 describes additional types of structured vocabulary and gives recommendations to enable interoperation of the vocabularies at all stages of the information storage and retrieval process.

0.017428853 = product of:
  0.034857705 = sum of:
    0.009416891 = product of:
      0.037667565 = sum of:
        0.037667565 = weight(_text_:based in 562) [ClassicSimilarity], result of:
          0.037667565 = score(doc=562,freq=2.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.26631355 = fieldWeight in 562, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.0625 = fieldNorm(doc=562)
      0.25 = coord(1/4)
    0.025440816 = product of:
      0.05088163 = sum of:
        0.05088163 = weight(_text_:22 in 562) [ClassicSimilarity], result of:
          0.05088163 = score(doc=562,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.30952093 = fieldWeight in 562, 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=562)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

The paper performs a thought experiment on the concept of a record based on the Functional Requirements for Bibliographic Records and library system functions, and concludes that if we want to develop a functional bibliographic record we need to do it within the context of a flexible, functional library systems record structure. The article suggests a new way to look at the library systems record that would allow libraries to move forward in terms of technology but also in terms of serving library users.

Source

Library hi tech. 22(2004) no.2, S.166-174

0.016956761 = product of:
  0.033913523 = sum of:
    0.011652809 = product of:
      0.046611235 = sum of:
        0.046611235 = weight(_text_:based in 2425) [ClassicSimilarity], result of:
          0.046611235 = score(doc=2425,freq=4.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.3295462 = fieldWeight in 2425, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2425)
      0.25 = coord(1/4)
    0.022260714 = product of:
      0.04452143 = sum of:
        0.04452143 = weight(_text_:22 in 2425) [ClassicSimilarity], result of:
          0.04452143 = score(doc=2425,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.2708308 = fieldWeight in 2425, 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=2425)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

The FRBR model is by many considered to be an important contribution to the next generation of bibliographic catalogues, but a major challenge for the library community is how to use this model on already existing MARC-based bibliographic catalogues. This problem requires a solution for the interpretation and conversion of MARC records, and a tool for this kind of conversion is developed as a part of the Norwegian BIBSYS FRBR project. The tool is based on a systematic approach to the interpretation and conversion process and is designed to be adaptable to the rules applied in different catalogues.

Source

Research and advanced technology for digital libraries : 10th European conference, proceedings / ECDL 2006, Alicante, Spain, September 17 - 22, 2006

0.015809556 = product of:
  0.063238226 = sum of:
    0.063238226 = product of:
      0.12647645 = sum of:
        0.12647645 = weight(_text_:assessment in 4792) [ClassicSimilarity], result of:
          0.12647645 = score(doc=4792,freq=2.0), product of:
            0.25917634 = queryWeight, product of:
              5.52102 = idf(docFreq=480, maxDocs=44218)
              0.04694356 = queryNorm
            0.4879938 = fieldWeight in 4792, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.52102 = idf(docFreq=480, maxDocs=44218)
              0.0625 = fieldNorm(doc=4792)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

The paper aims to review major developments in the MARC format, including a brief description of metadata schemes and cross-walks. It also offers an assessment of how well MARC works for Arabic script materials, a description of the degree to which MARC is used in Saudi Arabia, and the prospects for the use of XML versions of MARC in the Arab world.

0.014534365 = product of:
  0.02906873 = sum of:
    0.009988121 = product of:
      0.039952483 = sum of:
        0.039952483 = weight(_text_:based in 4752) [ClassicSimilarity], result of:
          0.039952483 = score(doc=4752,freq=4.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.28246817 = fieldWeight in 4752, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.046875 = fieldNorm(doc=4752)
      0.25 = coord(1/4)
    0.019080611 = product of:
      0.038161222 = sum of:
        0.038161222 = weight(_text_:22 in 4752) [ClassicSimilarity], result of:
          0.038161222 = score(doc=4752,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.23214069 = fieldWeight in 4752, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=4752)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

As educational technology becomes pervasive, demand will grow for library content to be incorporated into courseware. Among the barriers impeding interoperability between libraries and educational tools is the difference in specifications commonly used for the exchange of digital objects and metadata. Among libraries, Metadata Encoding and Transmission Standard (METS) is a new but increasingly popular standard; the IMS content-package (IMS-CP) plays a parallel role in educational technology. This article describes how METS-encoded library content can be converted into digital objects for IMS-compliant systems through an XSLT-based crosswalk. The conceptual models behind METS and IMS-CP are compared, the design and limitations of an XSLT-based translation are described, and the crosswalks are related to other techniques to enhance interoperability.

Source

Library hi tech. 22(2004) no.1, S.69-81

0.013833362 = product of:
  0.055333447 = sum of:
    0.055333447 = product of:
      0.11066689 = sum of:
        0.11066689 = weight(_text_:assessment in 1183) [ClassicSimilarity], result of:
          0.11066689 = score(doc=1183,freq=2.0), product of:
            0.25917634 = queryWeight, product of:
              5.52102 = idf(docFreq=480, maxDocs=44218)
              0.04694356 = queryNorm
            0.4269946 = fieldWeight in 1183, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              5.52102 = idf(docFreq=480, maxDocs=44218)
              0.0546875 = fieldNorm(doc=1183)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

This paper brings light to the existing practice of cataloging in the college libraries of Assam in terms of utilizing the MARC 21 standard and its structure, i.e., the tags, subfield codes, and indicators. Catalog records from six college libraries are collected and a survey is conducted to understand the local users' information requirements for the catalog. Places, where libraries have scope to improve and which divisions of tags could be more helpful for them in information retrieval, are identified and suggested. This study fulfilled the need for local-level assessment of the catalogs.

0.013492031 = product of:
  0.053968124 = sum of:
    0.053968124 = product of:
      0.10793625 = sum of:
        0.10793625 = weight(_text_:22 in 5743) [ClassicSimilarity], result of:
          0.10793625 = score(doc=5743,freq=4.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.6565931 = fieldWeight in 5743, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.09375 = fieldNorm(doc=5743)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

30. 3.2002 19:45:22

Source

Revista Española de Documentaçion Cientifica. 22(1999) no.2, S.198-219

0.013071639 = product of:
  0.026143279 = sum of:
    0.0070626684 = product of:
      0.028250674 = sum of:
        0.028250674 = weight(_text_:based in 4751) [ClassicSimilarity], result of:
          0.028250674 = score(doc=4751,freq=2.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.19973516 = fieldWeight in 4751, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.046875 = fieldNorm(doc=4751)
      0.25 = coord(1/4)
    0.019080611 = product of:
      0.038161222 = sum of:
        0.038161222 = weight(_text_:22 in 4751) [ClassicSimilarity], result of:
          0.038161222 = score(doc=4751,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.23214069 = fieldWeight in 4751, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=4751)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

The article discusses the future of the MARC formats and outlines how future cataloguing practice and bibliographic records might look. Background and basic functionality of the MARC formats are outlined, and it is pointed out that MARC is manifest in several different formats. This is illustrated through a comparison between the MARC21 format and the Danish MARC format "danMARC2". It is argued that present cataloguing codes and MARC formats are based primarily on the Paris principles and that "functional requirements for bibliographic records" (FRBR) would serve as a more solid and user-oriented platform for future development of cataloguing codes and formats. Furthermore, it is argued that MARC is a library-specific format, which results in neither exchange with library external sectors nor inclusion of other texts being facilitated. XML could serve as the technical platform for a model for future registrations, consisting of some core data and different supplements of data necessary for different sectors and purposes.

Source

Library hi tech. 22(2004) no.1, S.40-51

0.013071639 = product of:
  0.026143279 = sum of:
    0.0070626684 = product of:
      0.028250674 = sum of:
        0.028250674 = weight(_text_:based in 3841) [ClassicSimilarity], result of:
          0.028250674 = score(doc=3841,freq=2.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.19973516 = fieldWeight in 3841, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.046875 = fieldNorm(doc=3841)
      0.25 = coord(1/4)
    0.019080611 = product of:
      0.038161222 = sum of:
        0.038161222 = weight(_text_:22 in 3841) [ClassicSimilarity], result of:
          0.038161222 = score(doc=3841,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.23214069 = fieldWeight in 3841, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.046875 = fieldNorm(doc=3841)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

This entry describes the development of the MARC Communications format. After a brief overview of the initial 10 years it describes the succeeding phases of development up to the present. This takes the reader through the expansion of the format for all types of bibliographic data and for a multiple character scripts. At the same time a large business community was developing that offered products based on the format to the library community. The introduction of the Internet in the 1990s and the Web technology brought new opportunities and challenges and the format was adapted to this new environment. There has been a great deal of international adoption of the format that has continued into the 2000s. More recently new syntaxes for MARC 21 and models are being explored.

Date

27. 8.2011 14:22:38

0.012720408 = product of:
  0.05088163 = sum of:
    0.05088163 = product of:
      0.10176326 = sum of:
        0.10176326 = weight(_text_:22 in 2840) [ClassicSimilarity], result of:
          0.10176326 = score(doc=2840,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.61904186 = fieldWeight in 2840, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.125 = fieldNorm(doc=2840)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Source

Library hi tech. 22(2004) no.1

0.011130357 = product of:
  0.04452143 = sum of:
    0.04452143 = product of:
      0.08904286 = sum of:
        0.08904286 = weight(_text_:22 in 7196) [ClassicSimilarity], result of:
          0.08904286 = score(doc=7196,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.5416616 = fieldWeight in 7196, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=7196)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Source

Library hi tech. 22(2004) no.1

0.011130357 = product of:
  0.04452143 = sum of:
    0.04452143 = product of:
      0.08904286 = sum of:
        0.08904286 = weight(_text_:22 in 4973) [ClassicSimilarity], result of:
          0.08904286 = score(doc=4973,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.5416616 = fieldWeight in 4973, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=4973)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

26. 8.2000 19:22:35

0.011130357 = product of:
  0.04452143 = sum of:
    0.04452143 = product of:
      0.08904286 = sum of:
        0.08904286 = weight(_text_:22 in 6838) [ClassicSimilarity], result of:
          0.08904286 = score(doc=6838,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.5416616 = fieldWeight in 6838, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=6838)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Source

Dialog mit Bibliotheken. 13(2001) H.3, S.20-22

0.011130357 = product of:
  0.04452143 = sum of:
    0.04452143 = product of:
      0.08904286 = sum of:
        0.08904286 = weight(_text_:22 in 2841) [ClassicSimilarity], result of:
          0.08904286 = score(doc=2841,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.5416616 = fieldWeight in 2841, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.109375 = fieldNorm(doc=2841)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Source

Library hi tech. 22(2004) no.2

0.010893034 = product of:
  0.021786068 = sum of:
    0.005885557 = product of:
      0.023542227 = sum of:
        0.023542227 = weight(_text_:based in 2422) [ClassicSimilarity], result of:
          0.023542227 = score(doc=2422,freq=2.0), product of:
            0.14144066 = queryWeight, product of:
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.04694356 = queryNorm
            0.16644597 = fieldWeight in 2422, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.0129938 = idf(docFreq=5906, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2422)
      0.25 = coord(1/4)
    0.015900511 = product of:
      0.031801023 = sum of:
        0.031801023 = weight(_text_:22 in 2422) [ClassicSimilarity], result of:
          0.031801023 = score(doc=2422,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.19345059 = fieldWeight in 2422, 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=2422)
      0.5 = coord(1/2)
  0.5 = coord(2/4)

Abstract

Catalogs have for centuries been the main tool that enabled users to search for items in a library by author, title, or subject. A catalog can be interpreted as a set of bibliographic records, where each record acts as a surrogate for a publication. Every record describes a specific publication and contains the data that is used to create the indexes of search systems and the information that is presented to the user. Bibliographic records are often captured and exchanged by the use of the MARC format. Although there are numerous rdquodialectsrdquo of the MARC format in use, they are usually crafted on the same basis and are interoperable with each other -to a certain extent. The data model of a MARC-based catalog, however, is rdquo[...] extremely non-normalized with excessive replication of datardquo [1]. For instance, a literary work that exists in numerous editions and translations is likely to yield a large result set because each edition or translation is represented by an individual record, that is unrelated to other records that describe the same work.

Source

Research and advanced technology for digital libraries : 7th European Conference, proceedings / ECDL 2003, Trondheim, Norway, August 17-22, 2003

0.0095403055 = product of:
  0.038161222 = sum of:
    0.038161222 = product of:
      0.076322444 = sum of:
        0.076322444 = weight(_text_:22 in 6077) [ClassicSimilarity], result of:
          0.076322444 = score(doc=6077,freq=2.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.46428138 = fieldWeight in 6077, 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=6077)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

2. 8.2001 16:22:33

0.008994687 = product of:
  0.03597875 = sum of:
    0.03597875 = product of:
      0.0719575 = sum of:
        0.0719575 = weight(_text_:22 in 2408) [ClassicSimilarity], result of:
          0.0719575 = score(doc=2408,freq=4.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.4377287 = fieldWeight in 2408, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2408)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

13. 1.2007 18:31:22

Source

Cataloging and classification quarterly. 22(1996) nos.3/4, S.43-58

0.008994687 = product of:
  0.03597875 = sum of:
    0.03597875 = product of:
      0.0719575 = sum of:
        0.0719575 = weight(_text_:22 in 2845) [ClassicSimilarity], result of:
          0.0719575 = score(doc=2845,freq=4.0), product of:
            0.16438834 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04694356 = queryNorm
            0.4377287 = fieldWeight in 2845, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0625 = fieldNorm(doc=2845)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Date

9.12.2005 19:22:38

Source

Library hi tech. 22(2004) no.2, S.175-181