Search (160 results, page 2 of 8)

  • × theme_ss:"Datenformate"
  1. MARC and metadata : METS, MODS, and MARCXML: current and future implications part 2 (2004) 0.02
    0.024727121 = product of:
      0.049454242 = sum of:
        0.049454242 = product of:
          0.098908484 = sum of:
            0.098908484 = weight(_text_:22 in 2841) [ClassicSimilarity], result of:
              0.098908484 = score(doc=2841,freq=2.0), product of:
                0.18260197 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.052144732 = 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.5 = coord(1/2)
    
    Source
    Library hi tech. 22(2004) no.2
  2. Guenther, R.S.: Automating the Library of Congress Classification Scheme : implementation of the USMARC format for classification data (1996) 0.02
    0.024692593 = product of:
      0.049385186 = sum of:
        0.049385186 = product of:
          0.09877037 = sum of:
            0.09877037 = weight(_text_:data in 5578) [ClassicSimilarity], result of:
              0.09877037 = score(doc=5578,freq=12.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.59902847 = fieldWeight in 5578, product of:
                  3.4641016 = tf(freq=12.0), with freq of:
                    12.0 = termFreq=12.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=5578)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    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.
    Object
    USMARC for classification data
  3. Woods, E.W.; IFLA Section on classification and Indexing and Indexing and Information Technology; Joint Working Group on a Classification Format: Requirements for a format of classification data : Final report, July 1996 (1996) 0.02
    0.024439331 = product of:
      0.048878662 = sum of:
        0.048878662 = product of:
          0.097757325 = sum of:
            0.097757325 = weight(_text_:data in 3008) [ClassicSimilarity], result of:
              0.097757325 = score(doc=3008,freq=4.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.5928845 = fieldWeight in 3008, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.09375 = fieldNorm(doc=3008)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Object
    USMARC for classification data
  4. Zapounidou, S.; Sfakakis, M.; Papatheodorou, C.: Library data integration : towards BIBFRAME mapping to EDM (2014) 0.02
    0.024439331 = product of:
      0.048878662 = sum of:
        0.048878662 = product of:
          0.097757325 = sum of:
            0.097757325 = weight(_text_:data in 1589) [ClassicSimilarity], result of:
              0.097757325 = score(doc=1589,freq=16.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.5928845 = fieldWeight in 1589, product of:
                  4.0 = tf(freq=16.0), with freq of:
                    16.0 = termFreq=16.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.046875 = fieldNorm(doc=1589)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Integration of library data into the Linked Data environment is a key issue in libraries and is approached on the basis of interoperability between library data conceptual models. Achieving interoperability for different representations of the same or related entities between the library and cultural heritage domains shall enhance rich bibliographic data reusability and support the development of new data-driven information services. This paper aims to contribute to the desired interoperability by attempting to map core semantic paths between the BIBFRAME and EDM conceptual models. BIBFRAME is developed by the Library of Congress to support transformation of legacy library data in MARC format into linked data. EDM is the model developed for and used in the Europeana Cultural Heritage aggregation portal.
  5. Concise UNIMARC Classification Format : Draft 5 (20000125) (2000) 0.02
    0.02304162 = product of:
      0.04608324 = sum of:
        0.04608324 = product of:
          0.09216648 = sum of:
            0.09216648 = weight(_text_:data in 4421) [ClassicSimilarity], result of:
              0.09216648 = score(doc=4421,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.5589768 = fieldWeight in 4421, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.125 = fieldNorm(doc=4421)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Object
    UNIMARC for classification data
  6. Shieh, J.: PCC's work on URIs in MARC (2020) 0.02
    0.02304162 = product of:
      0.04608324 = sum of:
        0.04608324 = product of:
          0.09216648 = sum of:
            0.09216648 = weight(_text_:data in 122) [ClassicSimilarity], result of:
              0.09216648 = score(doc=122,freq=8.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.5589768 = fieldWeight in 122, product of:
                  2.828427 = tf(freq=8.0), with freq of:
                    8.0 = termFreq=8.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.0625 = fieldNorm(doc=122)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    In 2015, the PCC Task Group on URIs in MARC was tasked to identify and address linked data identifiers deployment in the current MARC format. By way of a pilot test, a survey, MARC Discussion papers, Proposals, etc., the Task Group initiated and introduced changes to MARC encoding. The Task Group succeeded in laying the ground work for preparing library data transition from MARC data to a linked data, RDF environment.
  7. Byrne, D.J.: MARC manual : understanding and using MARC records (1998) 0.02
    0.021194674 = product of:
      0.04238935 = sum of:
        0.04238935 = product of:
          0.0847787 = sum of:
            0.0847787 = weight(_text_:22 in 6077) [ClassicSimilarity], result of:
              0.0847787 = score(doc=6077,freq=2.0), product of:
                0.18260197 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.052144732 = 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.5 = coord(1/2)
    
    Date
    2. 8.2001 16:22:33
  8. Leeves, J.: Harmonising standards for bibliographic data interchange (1993) 0.02
    0.020366108 = product of:
      0.040732216 = sum of:
        0.040732216 = product of:
          0.08146443 = sum of:
            0.08146443 = weight(_text_:data in 6031) [ClassicSimilarity], result of:
              0.08146443 = score(doc=6031,freq=4.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.49407038 = fieldWeight in 6031, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.078125 = fieldNorm(doc=6031)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Reviews the provision for bibliographic data within EDIFACT, compares those provisions with the BIC draft standards for bibliographic databases and examines the implications for MARC based standards. Outlines the role of the major players involved. Describes stanbdards dealing with EDIFACT in greatest detail. Describes the library systems using the records
  9. ISO 8459: Bibliographic data element directory : Pt.1: Interloan applications (ISO 8459-1:1988). - Pt.2: Acquisition applications (ISO 8459-2:1992). - Pt.3: Information retrieval applications (ISO 8459-3:1994). - Pt.4: Circulation applications (ISO/CD 8459-4:1996) - Pt.5: Data elements for the exchange of cataloguing and metadata (ISO/DIS 8459-5:2000) (1988-) 0.02
    0.020366108 = product of:
      0.040732216 = sum of:
        0.040732216 = product of:
          0.08146443 = sum of:
            0.08146443 = weight(_text_:data in 4439) [ClassicSimilarity], result of:
              0.08146443 = score(doc=4439,freq=4.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.49407038 = fieldWeight in 4439, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.078125 = fieldNorm(doc=4439)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  10. Xu, A.; Hess, K.; Akerman, L.: From MARC to BIBFRAME 2.0 : Crosswalks (2018) 0.02
    0.020366108 = product of:
      0.040732216 = sum of:
        0.040732216 = product of:
          0.08146443 = sum of:
            0.08146443 = weight(_text_:data in 5172) [ClassicSimilarity], result of:
              0.08146443 = score(doc=5172,freq=16.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.49407038 = fieldWeight in 5172, product of:
                  4.0 = tf(freq=16.0), with freq of:
                    16.0 = termFreq=16.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=5172)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    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.
  11. Hegna, K.; Murtomaa, E.: Data mining MARC to find : FRBR? (2003) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 69) [ClassicSimilarity], result of:
              0.08064567 = score(doc=69,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 69, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.109375 = fieldNorm(doc=69)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  12. Leazer, G.H.: ¬An examination of data elements for bibliographic description : toward a conceptual schema for the USMARC formats (1992) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 4822) [ClassicSimilarity], result of:
              0.08064567 = score(doc=4822,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 4822, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.109375 = fieldNorm(doc=4822)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  13. Cantrall, D.: From MARC to Mosaic : progressing toward data interchangeability at the Oregon State Archives (1994) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 8470) [ClassicSimilarity], result of:
              0.08064567 = score(doc=8470,freq=8.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 8470, product of:
                  2.828427 = tf(freq=8.0), with freq of:
                    8.0 = termFreq=8.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=8470)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Explains the technology used by the Oregon State Archives to relaize the goal of data interchangeability given the prescribed nature of the MARC format. Describes an emergent model of learning and information delivery focusing on the example of World Wide Web, accessed most often by the software client Mosaic, which is the fastest growing segment of the Internet information highway. Also describes The Data Magician, a flexible program which allows for many combinations of input and output formats, and will read unconventional formats such as MARC communications format. Oregon State Archives, using Mosaic and The Data Magician, are consequently able to present valuable electronic information to a variety of users
  14. Guenther, R.S.: ¬The Library of Congress Classification in the USMARC format (1994) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 8864) [ClassicSimilarity], result of:
              0.08064567 = score(doc=8864,freq=8.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 8864, product of:
                  2.828427 = tf(freq=8.0), with freq of:
                    8.0 = termFreq=8.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=8864)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    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
    Object
    USMARC for classification data
  15. Soergel, D.: Framework for data element standardization (1995) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 4574) [ClassicSimilarity], result of:
              0.08064567 = score(doc=4574,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 4574, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.109375 = fieldNorm(doc=4574)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  16. Dextre Clarke, S.G.; Will, L.D.; Cochard, N.: ¬The BS8723 thesaurus data model and exchange format, and its relationship to SKOS (2008) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 6051) [ClassicSimilarity], result of:
              0.08064567 = score(doc=6051,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 6051, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.109375 = fieldNorm(doc=6051)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  17. Schmitz, K.-D.: MARTIF: a new ISO standard for the interchange of terminological data (1995) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 6852) [ClassicSimilarity], result of:
              0.08064567 = score(doc=6852,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 6852, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.109375 = fieldNorm(doc=6852)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  18. Duclos-Faure, D.: Format d'echange des donnees locales : ou en sommes-nous? (1997) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 888) [ClassicSimilarity], result of:
              0.08064567 = score(doc=888,freq=8.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 888, product of:
                  2.828427 = tf(freq=8.0), with freq of:
                    8.0 = termFreq=8.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=888)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Since Sep 1996 a group with representatives from the French National Library (BNF), French Joint Catalogue (CCF), Directorate of Scientific and Technical Information (DISTNB), Directorate of Reading (DL) and the Higher Education Bibliography Agency (ABES) has been working on establishing a format for exchanging local data which will accomodtae the needs of all users; conform to international standards and take account of new technological tools (Z39.50-1995). Using pre-existing formats with UNIMARC as the basis, the new format will allow selection of documents by different location criteria, establish conditions of communication and manage interlibrary loan. To date fields have been defined for data on location and management of copies, and for descriptive data on copies
    Footnote
    Übers. des Titels: Formats of exchanging local data: where are we now?
  19. Matoria, R.K.; Upadhyay, P.K.: Migration of data from one library management system to another : a case study in India (2004) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 4200) [ClassicSimilarity], result of:
              0.08064567 = score(doc=4200,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 4200, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.109375 = fieldNorm(doc=4200)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
  20. Garden, A.: ¬L'avenir des formats de données (2001) 0.02
    0.020161418 = product of:
      0.040322836 = sum of:
        0.040322836 = product of:
          0.08064567 = sum of:
            0.08064567 = weight(_text_:data in 4202) [ClassicSimilarity], result of:
              0.08064567 = score(doc=4202,freq=2.0), product of:
                0.16488427 = queryWeight, product of:
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.052144732 = queryNorm
                0.48910472 = fieldWeight in 4202, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.1620505 = idf(docFreq=5088, maxDocs=44218)
                  0.109375 = fieldNorm(doc=4202)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Footnote
    Übers. des Titels: The future of data formats

Authors

Years

Languages

  • e 131
  • d 15
  • f 6
  • nl 2
  • sp 2
  • pl 1
  • More… Less…

Types

  • a 131
  • el 14
  • m 6
  • s 6
  • l 3
  • n 3
  • ? 2
  • b 2
  • r 2
  • x 1
  • More… Less…

Classifications