Search (174 results, page 1 of 9)

  • × theme_ss:"Datenformate"
  1. Hagler, R.: ¬The bibliographic record and information technology (1997) 0.03
    0.032984905 = product of:
      0.06596981 = sum of:
        0.016118534 = weight(_text_:information in 6175) [ClassicSimilarity], result of:
          0.016118534 = score(doc=6175,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.19395474 = fieldWeight in 6175, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.078125 = fieldNorm(doc=6175)
        0.049851276 = product of:
          0.09970255 = sum of:
            0.09970255 = weight(_text_:services in 6175) [ClassicSimilarity], result of:
              0.09970255 = score(doc=6175,freq=4.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.5736517 = fieldWeight in 6175, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.078125 = fieldNorm(doc=6175)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Footnote
    Rez.: Library resources and technical services 42(1998) no.1, S.71-73 (D. CannCasciato); Reference and user services quarterly 37(1997) no.2, S.235-236 (E. McGrath)
  2. Format integration and its effect on cataloging, training, and systems (1993) 0.03
    0.030821227 = product of:
      0.061642453 = sum of:
        0.019342242 = weight(_text_:information in 67) [ClassicSimilarity], result of:
          0.019342242 = score(doc=67,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.23274569 = fieldWeight in 67, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.09375 = fieldNorm(doc=67)
        0.042300213 = product of:
          0.084600426 = sum of:
            0.084600426 = weight(_text_:services in 67) [ClassicSimilarity], result of:
              0.084600426 = score(doc=67,freq=2.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.4867596 = fieldWeight in 67, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.09375 = fieldNorm(doc=67)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Footnote
    Rez. in: Information technology and libraries 13(1994) no.1, S.78-79 (K.L. Walter)
    Series
    ALCTS papers on library technical services and collections; no.4
  3. Gopinath, M.A.: Standardization for resource sharing databases (1995) 0.03
    0.028620753 = product of:
      0.057241507 = sum of:
        0.03158575 = weight(_text_:information in 4414) [ClassicSimilarity], result of:
          0.03158575 = score(doc=4414,freq=12.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.38007212 = fieldWeight in 4414, product of:
              3.4641016 = tf(freq=12.0), with freq of:
                12.0 = termFreq=12.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=4414)
        0.025655756 = product of:
          0.05131151 = sum of:
            0.05131151 = weight(_text_:22 in 4414) [ClassicSimilarity], result of:
              0.05131151 = score(doc=4414,freq=2.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.30952093 = fieldWeight in 4414, 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=4414)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    It is helpful and essential to adopt standards for bibliographic information, project description and institutional information which are shareable for access to information resources within a country. Describes a strategy for adopting international standards of bibliographic information exchange for developing a resource sharing facilitation database in India. A list of 22 ISO standards for information processing is included
    Source
    Library science with a slant to documentation and information studies. 32(1995) no.3, S.i-iv
  4. USMARC format for community information : including guidelines for content designation (1993) 0.03
    0.026994899 = product of:
      0.053989798 = sum of:
        0.025789656 = weight(_text_:information in 8044) [ClassicSimilarity], result of:
          0.025789656 = score(doc=8044,freq=8.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.3103276 = fieldWeight in 8044, product of:
              2.828427 = tf(freq=8.0), with freq of:
                8.0 = termFreq=8.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=8044)
        0.028200142 = product of:
          0.056400284 = sum of:
            0.056400284 = weight(_text_:services in 8044) [ClassicSimilarity], result of:
              0.056400284 = score(doc=8044,freq=2.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.3245064 = fieldWeight in 8044, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.0625 = fieldNorm(doc=8044)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    The latest format. Features specifications for inputting and communicating community information - i.e., information about non-bibliographic resources (programs, services, organizations, individuals, one-time and ongoing events) that fulfill a community's information needs. Defines the codes and conventions (tags, indicators, subfield codes and codes values) that identify the data elements in the records. Includes full record examples showing how records are coded
  5. Yee, M.M.: New perspectives on the shared cataloging environment and a MARC 21 shopping list (2004) 0.03
    0.026927948 = product of:
      0.10771179 = sum of:
        0.10771179 = sum of:
          0.056400284 = weight(_text_:services in 132) [ClassicSimilarity], result of:
            0.056400284 = score(doc=132,freq=2.0), product of:
              0.1738033 = queryWeight, product of:
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.047340166 = queryNorm
              0.3245064 = fieldWeight in 132, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.0625 = fieldNorm(doc=132)
          0.05131151 = weight(_text_:22 in 132) [ClassicSimilarity], result of:
            0.05131151 = score(doc=132,freq=2.0), product of:
              0.16577719 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.047340166 = queryNorm
              0.30952093 = fieldWeight in 132, 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=132)
      0.25 = coord(1/4)
    
    Date
    10. 9.2000 17:38:22
    Source
    Library resources and technical services. 48(2004) no.3, S.165-178
  6. El-Sherbini, M.A.: Cataloging and classification : review of the literature 2005-06 (2008) 0.03
    0.026927948 = product of:
      0.10771179 = sum of:
        0.10771179 = sum of:
          0.056400284 = weight(_text_:services in 249) [ClassicSimilarity], result of:
            0.056400284 = score(doc=249,freq=2.0), product of:
              0.1738033 = queryWeight, product of:
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.047340166 = queryNorm
              0.3245064 = fieldWeight in 249, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.0625 = fieldNorm(doc=249)
          0.05131151 = weight(_text_:22 in 249) [ClassicSimilarity], result of:
            0.05131151 = score(doc=249,freq=2.0), product of:
              0.16577719 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.047340166 = 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.25 = coord(1/4)
    
    Date
    10. 9.2000 17:38:22
    Source
    Library resources and technical services. 52(2008) no.3, S.148-163
  7. Shaw, D.: Automating access to bibliographic information (1996) 0.03
    0.026387924 = product of:
      0.05277585 = sum of:
        0.012894828 = weight(_text_:information in 4351) [ClassicSimilarity], result of:
          0.012894828 = score(doc=4351,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.1551638 = fieldWeight in 4351, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=4351)
        0.03988102 = product of:
          0.07976204 = sum of:
            0.07976204 = weight(_text_:services in 4351) [ClassicSimilarity], result of:
              0.07976204 = score(doc=4351,freq=4.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.45892134 = fieldWeight in 4351, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.0625 = fieldNorm(doc=4351)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    Contrasts early in house automation efforts, such as the development of the MARC format and bibliographic utilities, with the creation of databases by abstracting and indexing services. Concludes that today's attempts to provide unified bibliographic access to the library's entire collection must find ways to integrate this plethora of independently developed access tools
    Source
    Technical services management: 1965-1990. A quarter of a century of change and a look into the future. Festschrift for Kathryn Luther Henderson. Ed.: L.C. Smith et al
  8. Ranta, J.A.: Queens Borough Public Library's Guidelines for cataloging community information (1996) 0.03
    0.026150364 = product of:
      0.05230073 = sum of:
        0.029851943 = weight(_text_:information in 6523) [ClassicSimilarity], result of:
          0.029851943 = score(doc=6523,freq=14.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.3592092 = fieldWeight in 6523, product of:
              3.7416575 = tf(freq=14.0), with freq of:
                14.0 = termFreq=14.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0546875 = fieldNorm(doc=6523)
        0.022448786 = product of:
          0.04489757 = sum of:
            0.04489757 = weight(_text_:22 in 6523) [ClassicSimilarity], result of:
              0.04489757 = score(doc=6523,freq=2.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.2708308 = fieldWeight in 6523, 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=6523)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    Currently, few resources exist to guide libraries in the cataloguing of community information using the new USMARC Format for Cammunity Information (1993). In developing a community information database, Queens Borough Public Library, New York City, formulated their own cataloguing procedures for applying AACR2, LoC File Interpretations, and USMARC Format for Community Information to community information. Their practices include entering corporate names directly whenever possible and assigning LC subject headings for classes of persons and topics, adding neighbourhood level geographic subdivisions. The guidelines were specially designed to aid non cataloguers in cataloguing community information and have enabled library to maintain consistency in handling corporate names and in assigning subject headings, while creating database that is highly accessible to library staff and users
    Source
    Cataloging and classification quarterly. 22(1996) no.2, S.51-69
  9. Mishra, K.S.: Bibliographic databases and exchange formats (1997) 0.02
    0.021945897 = product of:
      0.043891795 = sum of:
        0.01823604 = weight(_text_:information in 1757) [ClassicSimilarity], result of:
          0.01823604 = score(doc=1757,freq=4.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.21943474 = fieldWeight in 1757, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=1757)
        0.025655756 = product of:
          0.05131151 = sum of:
            0.05131151 = weight(_text_:22 in 1757) [ClassicSimilarity], result of:
              0.05131151 = score(doc=1757,freq=2.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.30952093 = fieldWeight in 1757, 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=1757)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    Computers play an important role in the development of bibliographic databases. Exchange formats are needed for the generation and exchange of bibliographic data at different levels: international, national, regional and local. Discusses the formats available at national and international level such as the International Standard Exchange Format (ISO 2709); the various MARC formats and the Common Communication Format (CCF). Work on Indian standards involving the Bureau of Indian Standards, the National Information System for Science and Technology (NISSAT) and other institutions proceeds only slowly
    Source
    DESIDOC bulletin of information technology. 17(1997) no.5, S.17-22
  10. Murphy, C.: Curriculum-enhanced MARC (CEMARC) : a new cataloging format for school librarians (1995) 0.02
    0.021515176 = product of:
      0.04303035 = sum of:
        0.011282975 = weight(_text_:information in 5100) [ClassicSimilarity], result of:
          0.011282975 = score(doc=5100,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.13576832 = fieldWeight in 5100, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0546875 = fieldNorm(doc=5100)
        0.03174738 = product of:
          0.06349476 = sum of:
            0.06349476 = weight(_text_:22 in 5100) [ClassicSimilarity], result of:
              0.06349476 = score(doc=5100,freq=4.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.38301262 = fieldWeight in 5100, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=5100)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Date
    11. 9.1996 19:22:20
    Source
    Literacy: traditional, cultural, technological. Proceedings of the 23rd Annual Conference of the International Association of School Librarianship (selected papers), Pittsburgh, Pennsylvania, Pittsburgh University, School of Library and Information Science, 17-22 Jul 94
  11. Crook, M.: Barbara Tillett discusses cataloging rules and conceptual models (1996) 0.02
    0.020995736 = product of:
      0.041991472 = sum of:
        0.019542687 = weight(_text_:information in 7683) [ClassicSimilarity], result of:
          0.019542687 = score(doc=7683,freq=6.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.23515764 = fieldWeight in 7683, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0546875 = fieldNorm(doc=7683)
        0.022448786 = product of:
          0.04489757 = sum of:
            0.04489757 = weight(_text_:22 in 7683) [ClassicSimilarity], result of:
              0.04489757 = score(doc=7683,freq=2.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.2708308 = fieldWeight in 7683, 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=7683)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    The chief of cataloguing policy and support office at the LoC presents her views on the usefulness of conceptual modelling in determining future directions for cataloguing and the MARC format. After describing the evolution of bibliographic processes, suggests usign the entity-relationship conceptual model to step back from how we record information today and start thinking about what information really means and why we provide it. Argues that now is the time to reexamine the basic principles which underpin Anglo-American cataloguing codes and that MARC formats should be looked at to see how they can evolve towards a future, improved structure for communicating bibliographic and authority information
    Source
    OCLC newsletter. 1996, no.220, S.20-22
  12. Eden, B.L.: Metadata and librarianship : will MARC survive? (2004) 0.02
    0.020995736 = product of:
      0.041991472 = sum of:
        0.019542687 = weight(_text_:information in 4750) [ClassicSimilarity], result of:
          0.019542687 = score(doc=4750,freq=6.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.23515764 = fieldWeight in 4750, product of:
              2.4494898 = tf(freq=6.0), with freq of:
                6.0 = termFreq=6.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0546875 = fieldNorm(doc=4750)
        0.022448786 = product of:
          0.04489757 = sum of:
            0.04489757 = weight(_text_:22 in 4750) [ClassicSimilarity], result of:
              0.04489757 = score(doc=4750,freq=2.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.2708308 = fieldWeight in 4750, 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=4750)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    Metadata schema and standards are now a part of the information landscape. Librarianship has slowly realized that MARC is only one of a proliferation of metadata standards, and that MARC has many pros and cons related to its age, original conception, and biases. Should librarianship continue to promote the MARC standard? Are there better metadata standards out there that are more robust, user-friendly, and dynamic in the organization and presentation of information? This special issue examines current initiatives that are actively incorporating MARC standards and concepts into new metadata schemata, while also predicting a future where MARC may not be the metadata schema of choice for the organization and description of information.
    Source
    Library hi tech. 22(2004) no.1, S.6-7
  13. Mueller, C.J.; Whittaker, M.A.: What is this thing called MARC(S)? (1990) 0.02
    0.020547485 = product of:
      0.04109497 = sum of:
        0.012894828 = weight(_text_:information in 3588) [ClassicSimilarity], result of:
          0.012894828 = score(doc=3588,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.1551638 = fieldWeight in 3588, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=3588)
        0.028200142 = product of:
          0.056400284 = sum of:
            0.056400284 = weight(_text_:services in 3588) [ClassicSimilarity], result of:
              0.056400284 = score(doc=3588,freq=2.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.3245064 = fieldWeight in 3588, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.0625 = fieldNorm(doc=3588)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    Contribution to an issue devoted to serials and reference services. Familiarity with the basic elements of the MARC format and their effect on the display and retrieval of bibliographic data is an essential element of public service in those libraries with MARC-based on-line catalogues. Describes the components of a MARC record. To successfully retrieve the information sought from an on-line catalogue, the catalogue user must know whether it is in an indexed field and, if so, must be familiar with the search strategies required by the system.
  14. Kokabi, M.: Is the future of MARC assured? (1996) 0.02
    0.020547485 = product of:
      0.04109497 = sum of:
        0.012894828 = weight(_text_:information in 6724) [ClassicSimilarity], result of:
          0.012894828 = score(doc=6724,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.1551638 = fieldWeight in 6724, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=6724)
        0.028200142 = product of:
          0.056400284 = sum of:
            0.056400284 = weight(_text_:services in 6724) [ClassicSimilarity], result of:
              0.056400284 = score(doc=6724,freq=2.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.3245064 = fieldWeight in 6724, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.0625 = fieldNorm(doc=6724)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    The MARC machine readable catalogue is now more than 20 years old. It has been, and still is, criticized from different points of view. Reviews some positive and negative opinions on MARC as expressed by different sectors of the profession, and considers its future in relation to technological innovations. MARC remains a valuable means of communicating bibliographical information
    Source
    OCLC systems and services. 12(1996) no.2, S.33-36
  15. German, L.: Bibliographic utilities (2009) 0.02
    0.020547485 = product of:
      0.04109497 = sum of:
        0.012894828 = weight(_text_:information in 3858) [ClassicSimilarity], result of:
          0.012894828 = score(doc=3858,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.1551638 = fieldWeight in 3858, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=3858)
        0.028200142 = product of:
          0.056400284 = sum of:
            0.056400284 = weight(_text_:services in 3858) [ClassicSimilarity], result of:
              0.056400284 = score(doc=3858,freq=2.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.3245064 = fieldWeight in 3858, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.0625 = fieldNorm(doc=3858)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    Bibliographic utilities have been in existence for more than 40 years. From the beginning, they were designed to promote resource sharing among their members. The core of a bibliographic utility is the database of bibliographic records. The structure of the bibliographic record is based upon Machine Readable Cataloging (MARC). Other services have evolved from the utilities' bibliographic database.
    Source
    Encyclopedia of library and information sciences. 3rd ed. Ed.: M.J. Bates
  16. Durand, J.J.: Making your MARC (1997) 0.02
    0.02031583 = product of:
      0.04063166 = sum of:
        0.015956536 = weight(_text_:information in 871) [ClassicSimilarity], result of:
          0.015956536 = score(doc=871,freq=4.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.1920054 = fieldWeight in 871, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0546875 = fieldNorm(doc=871)
        0.024675125 = product of:
          0.04935025 = sum of:
            0.04935025 = weight(_text_:services in 871) [ClassicSimilarity], result of:
              0.04935025 = score(doc=871,freq=2.0), product of:
                0.1738033 = queryWeight, product of:
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.047340166 = queryNorm
                0.28394312 = fieldWeight in 871, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  3.6713707 = idf(docFreq=3057, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=871)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    Addresses some of the questions raised by school library media specialists but intended to help all those whose last cataloguing course was taken in library school before the technological revolution to make the most of the MARC record format. Covers necessary cataloguing tools and basic information needed to create an accurate MARC record, as well as successful additional information and some expectations of its future iuses. Emphasizes the importance of accurate MARC records if the online catalogue is to meet user needs, and be able to be merged with other catalogues. Also notes the MARC record's usefulness in streamlining activities such as circulation, use statistics, overdue notices, holding reports, bibliographies and inventories
    Source
    Journal of youth services in libraries. 10(1997) no.3, S.276-282
  17. Riva, P.: Mapping MARC 21 linking entry fields to FRBR and Tillett's taxonomy of bibliographic relationships (2004) 0.02
    0.020195961 = product of:
      0.080783844 = sum of:
        0.080783844 = sum of:
          0.042300213 = weight(_text_:services in 136) [ClassicSimilarity], result of:
            0.042300213 = score(doc=136,freq=2.0), product of:
              0.1738033 = queryWeight, product of:
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.047340166 = queryNorm
              0.2433798 = fieldWeight in 136, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.046875 = fieldNorm(doc=136)
          0.03848363 = weight(_text_:22 in 136) [ClassicSimilarity], result of:
            0.03848363 = score(doc=136,freq=2.0), product of:
              0.16577719 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.047340166 = queryNorm
              0.23214069 = fieldWeight in 136, 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=136)
      0.25 = coord(1/4)
    
    Date
    10. 9.2000 17:38:22
    Source
    Library resources and technical services. 48(2004) no.2, S.130-143
  18. Lee, S.; Jacob, E.K.: ¬An integrated approach to metadata interoperability : construction of a conceptual structure between MARC and FRBR (2011) 0.02
    0.020195961 = product of:
      0.080783844 = sum of:
        0.080783844 = sum of:
          0.042300213 = weight(_text_:services in 302) [ClassicSimilarity], result of:
            0.042300213 = score(doc=302,freq=2.0), product of:
              0.1738033 = queryWeight, product of:
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.047340166 = queryNorm
              0.2433798 = fieldWeight in 302, product of:
                1.4142135 = tf(freq=2.0), with freq of:
                  2.0 = termFreq=2.0
                3.6713707 = idf(docFreq=3057, maxDocs=44218)
                0.046875 = fieldNorm(doc=302)
          0.03848363 = weight(_text_:22 in 302) [ClassicSimilarity], result of:
            0.03848363 = score(doc=302,freq=2.0), product of:
              0.16577719 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.047340166 = queryNorm
              0.23214069 = fieldWeight in 302, 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=302)
      0.25 = coord(1/4)
    
    Date
    10. 9.2000 17:38:22
    Source
    Library resources and technical services. 55(2011) no.1, S.17-32
  19. Weber, L.B.: Reading formatting MARC AMC (1990) 0.02
    0.019275293 = product of:
      0.038550586 = sum of:
        0.012894828 = weight(_text_:information in 484) [ClassicSimilarity], result of:
          0.012894828 = score(doc=484,freq=2.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.1551638 = fieldWeight in 484, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0625 = fieldNorm(doc=484)
        0.025655756 = product of:
          0.05131151 = sum of:
            0.05131151 = weight(_text_:22 in 484) [ClassicSimilarity], result of:
              0.05131151 = score(doc=484,freq=2.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.30952093 = fieldWeight in 484, 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=484)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    This paper discusses how archivists use the MARC AMC format to exchange information about archival materials. The paper explains the modifications that MARC AMC introduced to the MARC bibliographic formats; gives examples of a record in generic USMARC AMC, RLIN AMC, and OCLC AMC; and considers the possible impact of format integration. The paper concludes with some thoughts about the changes that MARC AMC is causing in the archival profession.
    Date
    8. 1.2007 14:22:51
  20. Carvalho, J.R. de; Cordeiro, M.I.; Lopes, A.; Vieira, M.: Meta-information about MARC : an XML framework for validation, explanation and help systems (2004) 0.02
    0.01920266 = product of:
      0.03840532 = sum of:
        0.015956536 = weight(_text_:information in 2848) [ClassicSimilarity], result of:
          0.015956536 = score(doc=2848,freq=4.0), product of:
            0.08310462 = queryWeight, product of:
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.047340166 = queryNorm
            0.1920054 = fieldWeight in 2848, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              1.7554779 = idf(docFreq=20772, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2848)
        0.022448786 = product of:
          0.04489757 = sum of:
            0.04489757 = weight(_text_:22 in 2848) [ClassicSimilarity], result of:
              0.04489757 = score(doc=2848,freq=2.0), product of:
                0.16577719 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.047340166 = queryNorm
                0.2708308 = fieldWeight in 2848, 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=2848)
          0.5 = coord(1/2)
      0.5 = coord(2/4)
    
    Abstract
    This article proposes a schema for meta-information about MARC that can express at a fairly comprehensive level the syntactic and semantic aspects of MARC formats in XML, including not only rules but also all texts and examples that are conveyed by MARC documentation. It can be thought of as an XML version of the MARC or UNIMARC manuals, for both machine and human usage. The article explains how such a schema can be the central piece of a more complete framework, to be used in conjunction with "slim" record formats, providing a rich environment for the automated processing of bibliographic data.
    Source
    Library hi tech. 22(2004) no.2, S.131-137

Authors

Years

Languages

  • e 132
  • d 27
  • f 6
  • pl 1
  • sp 1
  • More… Less…

Types

  • a 141
  • m 14
  • el 8
  • s 8
  • n 3
  • x 3
  • b 2
  • ? 1
  • l 1
  • More… Less…