Search (103 results, page 1 of 6)

0.084412016 = product of:
  0.21103004 = sum of:
    0.1924681 = weight(_text_:conversion in 2425) [ClassicSimilarity], result of:
      0.1924681 = score(doc=2425,freq=6.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.81157964 = fieldWeight in 2425, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=2425)
    0.018561937 = product of:
      0.037123874 = sum of:
        0.037123874 = weight(_text_:22 in 2425) [ClassicSimilarity], result of:
          0.037123874 = score(doc=2425,freq=2.0), product of:
            0.13707404 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.039143547 = 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.4 = coord(2/5)

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.051940776 = product of:
  0.12985194 = sum of:
    0.11112151 = weight(_text_:conversion in 3338) [ClassicSimilarity], result of:
      0.11112151 = score(doc=3338,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.46856573 = fieldWeight in 3338, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=3338)
    0.018730428 = product of:
      0.037460856 = sum of:
        0.037460856 = weight(_text_:29 in 3338) [ClassicSimilarity], result of:
          0.037460856 = score(doc=3338,freq=2.0), product of:
            0.13769476 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.039143547 = queryNorm
            0.27205724 = fieldWeight in 3338, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.0546875 = fieldNorm(doc=3338)
      0.5 = coord(1/2)
  0.4 = coord(2/5)

Abstract

Reports on work carried out as part of a feasibility study for UseMARCON (User Controlled Generic MARC Converter); a European Community funded project to develop a toolbox capable of converting bibliographic records from any MARC format into any other MARC format through a central conversion format. Reviews the use of MARC formats as internal or cataloguing formats or an exchange formats available in tape magnetic tape services. Special attention is paid to the actual us and use trends of UNIMARC, with particular reference to the role of UNIMARC as a new stage in the evolution of MARC formats, devised to improve and facilitate the exchange of bibliographic information between different systems

Source

Program. 29(1995) no.4, S.445-459

0.050798405 = product of:
  0.25399202 = sum of:
    0.25399202 = weight(_text_:conversion in 2) [ClassicSimilarity], result of:
      0.25399202 = score(doc=2,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        1.0710074 = fieldWeight in 2, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.125 = fieldNorm(doc=2)
  0.2 = coord(1/5)

0.04399271 = product of:
  0.21996355 = sum of:
    0.21996355 = weight(_text_:conversion in 2894) [ClassicSimilarity], result of:
      0.21996355 = score(doc=2894,freq=6.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.9275196 = fieldWeight in 2894, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0625 = fieldNorm(doc=2894)
  0.2 = coord(1/5)

Abstract

To solve the problem of information loss caused by format changes requires 1 more conversion to be made, i.e. to SGML or XML. Describes the 2 formats and discusses the conversion issues involved. The sooner conversion to SGML or XML is commenced the better for the organization and if necessary, outside facilities can be called upon to provide the expertise

0.038493622 = product of:
  0.1924681 = sum of:
    0.1924681 = weight(_text_:conversion in 119) [ClassicSimilarity], result of:
      0.1924681 = score(doc=119,freq=6.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.81157964 = fieldWeight in 119, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=119)
  0.2 = coord(1/5)

Abstract

The Program for Cooperative Cataloging (PCC) has formal relationships with the Library of Congress (LC), Share-VDE, and Linked Data for Production Phase 2 (LD4P2) for work on Bibliographic Framework (BIBFRAME), and PCC institutions have been very active in the exploration of MARC to BIBFRAME conversion processes. This article will review the involvement of PCC in the development of BIBFRAME and examine the work of LC, Share-VDE, and LD4P2 on MARC to BIBFRAME conversion. It will conclude with a discussion of areas for further exploration by the PCC leading up to the creation of PCC conversion specifications and PCC BIBFRAME data.

0.037052415 = product of:
  0.092631035 = sum of:
    0.07937251 = weight(_text_:conversion in 2422) [ClassicSimilarity], result of:
      0.07937251 = score(doc=2422,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.3346898 = fieldWeight in 2422, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0390625 = fieldNorm(doc=2422)
    0.013258526 = product of:
      0.026517052 = sum of:
        0.026517052 = weight(_text_:22 in 2422) [ClassicSimilarity], result of:
          0.026517052 = score(doc=2422,freq=2.0), product of:
            0.13707404 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.039143547 = 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.4 = coord(2/5)

Source

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

0.0359199 = product of:
  0.1795995 = sum of:
    0.1795995 = weight(_text_:conversion in 4893) [ClassicSimilarity], result of:
      0.1795995 = score(doc=4893,freq=4.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.7573166 = fieldWeight in 4893, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0625 = fieldNorm(doc=4893)
  0.2 = coord(1/5)

Abstract

The constant change of technology produces a shorter life cycle for electronic formats than for conventional formats. In libraries and archives, information may have a longer life cycle than elsewhere. The technical problems of electronic format conversion may become overwhelming. Discusses aesthetics and quality assurance issues

0.032994535 = product of:
  0.16497268 = sum of:
    0.16497268 = weight(_text_:conversion in 2515) [ClassicSimilarity], result of:
      0.16497268 = score(doc=2515,freq=6.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.6956397 = fieldWeight in 2515, product of:
          2.4494898 = tf(freq=6.0), with freq of:
            6.0 = termFreq=6.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.046875 = fieldNorm(doc=2515)
  0.2 = coord(1/5)

Abstract

One of the primary goals of Unesco's Common Communication Format (CCF) has been to maintain compatibility between two major information communities: libraries; and abstracting and indexing organisations. While abstracting and indexing organisations do not follow any single standard for description or the structure and encoding of machine records, libraries have clearly defined standards and practices. Among CCF-using organisations are some that wish to incorporate records produced by national bibliographic agencies, especially national libraries, into their own data bases. They need the ability to convert UNIMARC records to CCF. To accomplish this they require a source of records, a computer to process them, a computer programm designed for record conversion and a table or instructions laying out the specific way in which each UNIMARC data element is to be processed in the course of conversion to CCF. Examines the factors to be considered in planning a table that would be sufficiently detailed to accomplish record conversion, and outlines problems that might be encountered.

0.031429913 = product of:
  0.15714955 = sum of:
    0.15714955 = weight(_text_:conversion in 5174) [ClassicSimilarity], result of:
      0.15714955 = score(doc=5174,freq=4.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.662652 = fieldWeight in 5174, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5174)
  0.2 = coord(1/5)

Abstract

With 50 different MARC formats in use globally and 10 employed in European Union national libraries problems are created in the international supply of cataloguing data and the quality of records. UseMARCON is a cooperative project of Dutch, Portuguese, UK and German national libraries using software from Jouve Systems d'Information in France to produce a generic conversion program capable of translating bibliographic records in any ISO2709 format into any other ISO2709 format using UNIMARC as a switching format. Outlines what is required in the process of conversion; describes the functionality of the software; and lists the MARC formats with which UseMARCON can operate. The project was finished in 1997

0.026939923 = product of:
  0.13469961 = sum of:
    0.13469961 = weight(_text_:conversion in 2396) [ClassicSimilarity], result of:
      0.13469961 = score(doc=2396,freq=4.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.56798744 = fieldWeight in 2396, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.046875 = fieldNorm(doc=2396)
  0.2 = coord(1/5)

Abstract

The topic was the implementation of format integration which will enalbe materials which have some aspect of seriality but could also be defined as another format, to be catalogues as both. An update of OCLC's format integration was given. The 1st phase, encompassing the changes to fields 010-8XX, will be complete by the end of 1994. The 2nd phase, which will contain changes to the 007 and 008 fields and the introduction of the 006 field, is scheduled for completion by the end 0f 1995. Local system vendors were supportive of format integration and changes to relevant programs were underway in preparation for implementation. In a discussion of conversion of pre-format integration records to format integration MARC it was felt that adequate staff and funding would not be available for massive conversion projects and that only selected records would be converted

0.025399202 = product of:
  0.12699601 = sum of:
    0.12699601 = weight(_text_:conversion in 4020) [ClassicSimilarity], result of:
      0.12699601 = score(doc=4020,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.5355037 = fieldWeight in 4020, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0625 = fieldNorm(doc=4020)
  0.2 = coord(1/5)

Abstract

Traces the history of the MARC formats, for computerized bibliographic records and computerized cataloguing, from the initial work of the Library of Congress in the early 60s through to the various stages of development of the MARC Pilot Project (1966 to 1968); MARC2 (1968 to 1974); Distribution Service (1968); Retrospective Conversion (1968 to 1970); the Committee on Representation in Machine-Readable Form of Bibliographic Information (MARBI) and the USMARC Advisory Group; and the expansion, linkage and integration stages (1980 to the present)

0.025399202 = product of:
  0.12699601 = sum of:
    0.12699601 = weight(_text_:conversion in 870) [ClassicSimilarity], result of:
      0.12699601 = score(doc=870,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.5355037 = fieldWeight in 870, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0625 = fieldNorm(doc=870)
  0.2 = coord(1/5)

Abstract

Presents a brief survey of the emergence of MARC formats, their components, standardization efforts, and the UseMARCON conversion program by means of which any MARC format can be converted to any other. HUNMARC was issued in 1994 in accordance with Hungarian standards of librarianship. Some important questions arising in connection with the implementation of HUNMARC can be answered by comparing the HUNMARC and USMARC formats

0.025399202 = product of:
  0.12699601 = sum of:
    0.12699601 = weight(_text_:conversion in 96) [ClassicSimilarity], result of:
      0.12699601 = score(doc=96,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.5355037 = fieldWeight in 96, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0625 = fieldNorm(doc=96)
  0.2 = coord(1/5)

Footnote

Übers. des Titels: Conversion of bibliographic data

0.025399202 = product of:
  0.12699601 = sum of:
    0.12699601 = weight(_text_:conversion in 890) [ClassicSimilarity], result of:
      0.12699601 = score(doc=890,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.5355037 = fieldWeight in 890, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0625 = fieldNorm(doc=890)
  0.2 = coord(1/5)

Abstract

The original purpose of the MARC format was to specify the formatting of data to be exchanged electronically. Compares the SAMARC format with USMARC and UNIMARC, both well established and widely used in the International community, in terms of scope, updating mechanisms, completeness and the current status of the formats. Recommends conversion to USMARC given the fact that SAMARC is hampered by an inadequate infrastructure which makes it unresponsive to immediate needs and the UNIMARC is still being developed. Discusses the benefits and the negative aspects of converting to USMARC

0.022449937 = product of:
  0.11224968 = sum of:
    0.11224968 = weight(_text_:conversion in 5172) [ClassicSimilarity], result of:
      0.11224968 = score(doc=5172,freq=4.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.47332287 = fieldWeight in 5172, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0390625 = fieldNorm(doc=5172)
  0.2 = coord(1/5)

Abstract

One of the big challenges facing academic libraries today is to increase the relevance of the libraries to their user communities. If the libraries can increase the visibility of their resources on the open web, it will increase the chances of the libraries to reach to their user communities via the user's first search experience. BIBFRAME and library Linked Data will enable libraries to publish their resources in a way that the Web understands, consume Linked Data to enrich their resources relevant to the libraries' user communities, and visualize networks across collections. However, one of the important steps for transitioning to BIBFRAME and library Linked Data involves crosswalks, mapping MARC fields and subfields across data models and performing necessary data reformatting to be in compliance with the specifications of the new model, which is currently BIBFRAME 2.0. This article looks into how the Library of Congress has mapped library bibliographic data from the MARC format to the BIBFRAME 2.0 model and vocabulary published and updated since April 2016, available from http://www.loc.gov/bibframe/docs/index.html based on the recently released conversion specifications and converter, developed by the Library of Congress with input from many community members. The BIBFRAME 2.0 standard and conversion tools will enable libraries to transform bibliographic data from MARC into BIBFRAME 2.0, which introduces a Linked Data model as the improved method of bibliographic control for the future, and make bibliographic information more useful within and beyond library communities.

0.022224303 = product of:
  0.11112151 = sum of:
    0.11112151 = weight(_text_:conversion in 8864) [ClassicSimilarity], result of:
      0.11112151 = score(doc=8864,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.46856573 = fieldWeight in 8864, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=8864)
  0.2 = coord(1/5)

Abstract

The paper reviews the development of the USMARC Format for Classification Data, a standard for communication of classification data in machine-readable form. It considers the uses for online classification schedules, both for technical services and reference functions and gives an overview of the format specification details of data elements used and of the structure of the records. The paper describes an experiment conducted at the Library of Congress to test the format as well as the development of the classification database encompassing the LCC schedules. Features of the classification system are given. The LoC will complete its conversion of the LCC in mid-1995

0.022224303 = product of:
  0.11112151 = sum of:
    0.11112151 = weight(_text_:conversion in 4335) [ClassicSimilarity], result of:
      0.11112151 = score(doc=4335,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.46856573 = fieldWeight in 4335, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4335)
  0.2 = coord(1/5)

Abstract

The paper discusses the role of XML and its perspectives in library information systems, particularly with regards to basic functions of bibliographic formats - storage and transportation of the data. Slim XML Schema for UNIMARC representation is presented, its main features being lossless conversion from MARC to XML, roundtripability from XML back to MARC, support for embedded fields and extended range of indicator values, independence from any specific dialect of MARC format, stability to any changes of the format.

0.022224303 = product of:
  0.11112151 = sum of:
    0.11112151 = weight(_text_:conversion in 5423) [ClassicSimilarity], result of:
      0.11112151 = score(doc=5423,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.46856573 = fieldWeight in 5423, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5423)
  0.2 = coord(1/5)

Abstract

This article explores recent discussions about appropriate mark-up conventions for library information intended for use on the World Wide Web. In particular, the question of whether the MARC 21 format will continue to be useful and whether the time is right for a full-fledged conversion effort to XML is explored. The author concludes that the MARC format will be relevant well into the future, and its use will not hamper access to bibliographic information via the web. Early XML exploratory efforts carried out at the Stanford University's Lane Medical Library are reported on. Although these efforts are a promising start, much more consultation and investigation is needed to arrive at broadly acceptable standards for XML library information encoding and retrieval.

0.022224303 = product of:
  0.11112151 = sum of:
    0.11112151 = weight(_text_:conversion in 5578) [ClassicSimilarity], result of:
      0.11112151 = score(doc=5578,freq=2.0), product of:
        0.23715246 = queryWeight, product of:
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.039143547 = queryNorm
        0.46856573 = fieldWeight in 5578, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          6.0585327 = idf(docFreq=280, maxDocs=44218)
          0.0546875 = fieldNorm(doc=5578)
  0.2 = coord(1/5)

Abstract

Potential uses for classification data in machine readable form and reasons for the development of a standard, the USMARC Format for Classification Data, which allows for classification data to interact with other USMARC bibliographic and authority data are discussed. The development, structure, content, and use of the standard is reviewed with implementation decisions for the Library of Congress Classification scheme noted. The author examines the implementation of USMARC classification at LC, the conversion of the schedules, and the functionality of the software being used. Problems in the effort are explored, and enhancements desired for the online classification system are considered.

0.021309925 = product of:
  0.05327481 = sum of:
    0.026757756 = product of:
      0.053515512 = sum of:
        0.053515512 = weight(_text_:29 in 5228) [ClassicSimilarity], result of:
          0.053515512 = score(doc=5228,freq=2.0), product of:
            0.13769476 = queryWeight, product of:
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.039143547 = queryNorm
            0.38865322 = fieldWeight in 5228, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5176873 = idf(docFreq=3565, maxDocs=44218)
              0.078125 = fieldNorm(doc=5228)
      0.5 = coord(1/2)
    0.026517052 = product of:
      0.053034104 = sum of:
        0.053034104 = weight(_text_:22 in 5228) [ClassicSimilarity], result of:
          0.053034104 = score(doc=5228,freq=2.0), product of:
            0.13707404 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.039143547 = queryNorm
            0.38690117 = fieldWeight in 5228, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.078125 = fieldNorm(doc=5228)
      0.5 = coord(1/2)
  0.4 = coord(2/5)

Date

29. 9.1996 18:58:22