Search (7 results, page 1 of 1)

  • × author_ss:"McCallum, S.H."
  1. McCallum, S.H.: ¬An introduction to the Metadata Object Description Schema (MODS) (2004) 0.03
    0.028787265 = product of:
      0.05757453 = sum of:
        0.05757453 = sum of:
          0.007654148 = weight(_text_:a in 81) [ClassicSimilarity], result of:
            0.007654148 = score(doc=81,freq=4.0), product of:
              0.053105544 = queryWeight, product of:
                1.153047 = idf(docFreq=37942, maxDocs=44218)
                0.046056706 = queryNorm
              0.14413087 = fieldWeight in 81, product of:
                2.0 = tf(freq=4.0), with freq of:
                  4.0 = termFreq=4.0
                1.153047 = idf(docFreq=37942, maxDocs=44218)
                0.0625 = fieldNorm(doc=81)
          0.04992038 = weight(_text_:22 in 81) [ClassicSimilarity], result of:
            0.04992038 = score(doc=81,freq=2.0), product of:
              0.16128273 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.046056706 = queryNorm
              0.30952093 = fieldWeight in 81, 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=81)
      0.5 = coord(1/2)
    
    Abstract
    This paper provides an introduction to the Metadata Object Description Schema (MODS), a MARC21 compatible XML schema for descriptive metadata. It explains the requirements that the schema targets and the special features that differentiate it from MARC, such as user-oriented tags, regrouped data elements, linking, recursion, and accommodations for electronic resources.
    Source
    Library hi tech. 22(2004) no.1, S.82-88
    Type
    a
  2. McCallum, S.H.: Machine Readable Cataloging (MARC): 1975-2007 (2009) 0.02
    0.023258494 = product of:
      0.04651699 = sum of:
        0.04651699 = sum of:
          0.009076704 = weight(_text_:a in 3841) [ClassicSimilarity], result of:
            0.009076704 = score(doc=3841,freq=10.0), product of:
              0.053105544 = queryWeight, product of:
                1.153047 = idf(docFreq=37942, maxDocs=44218)
                0.046056706 = queryNorm
              0.1709182 = fieldWeight in 3841, product of:
                3.1622777 = tf(freq=10.0), with freq of:
                  10.0 = termFreq=10.0
                1.153047 = idf(docFreq=37942, maxDocs=44218)
                0.046875 = fieldNorm(doc=3841)
          0.037440285 = weight(_text_:22 in 3841) [ClassicSimilarity], result of:
            0.037440285 = score(doc=3841,freq=2.0), product of:
              0.16128273 = queryWeight, product of:
                3.5018296 = idf(docFreq=3622, maxDocs=44218)
                0.046056706 = 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)
    
    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
    Type
    a
  3. McCallum, S.H.: MARCXML sampler (2005) 0.00
    0.0029000505 = product of:
      0.005800101 = sum of:
        0.005800101 = product of:
          0.011600202 = sum of:
            0.011600202 = weight(_text_:a in 4361) [ClassicSimilarity], result of:
              0.011600202 = score(doc=4361,freq=12.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.21843673 = fieldWeight in 4361, product of:
                  3.4641016 = tf(freq=12.0), with freq of:
                    12.0 = termFreq=12.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=4361)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    At the IFLA conference in Glasgow, three years ago, the Information Technology Section organized a workshop on metadata. At that workshop MARCXML was presented, along with plans and expectations for its use. This paper is an update to that report. It reviews the development of an XML schema for MARC 21 and the MARCXML tool kit of transformations. The close relationship of MARCXML to the recent ISO standards work associated with MARC in XML is described. Sketches of interesting applications follow with uses that range from MARCXML as a switching format to a maintenance tool to a record communication format for new XML-based protocols.
    Footnote
    Vortrag, World Library and Information Congress: 71th IFLA General Conference and Council "Libraries - A voyage of discovery", August 14th - 18th 2005, Oslo, Norway.
    Type
    a
  4. McCallum, S.H.; Godwin, J.L.: Statistics on headings in the MARC file (1981) 0.00
    0.00270615 = product of:
      0.0054123 = sum of:
        0.0054123 = product of:
          0.0108246 = sum of:
            0.0108246 = weight(_text_:a in 4481) [ClassicSimilarity], result of:
              0.0108246 = score(doc=4481,freq=2.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.20383182 = fieldWeight in 4481, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.125 = fieldNorm(doc=4481)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Type
    a
  5. McCallum, S.H.: Preservation metadata standards for digital resources : what we have and what we need (2005) 0.00
    0.0024857575 = product of:
      0.004971515 = sum of:
        0.004971515 = product of:
          0.00994303 = sum of:
            0.00994303 = weight(_text_:a in 4353) [ClassicSimilarity], result of:
              0.00994303 = score(doc=4353,freq=12.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.18723148 = fieldWeight in 4353, product of:
                  3.4641016 = tf(freq=12.0), with freq of:
                    12.0 = termFreq=12.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046875 = fieldNorm(doc=4353)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    A key component for the successful preservation of digital resources is going to be the metadata that enables automated preservation processes to take place. The number of digital items will preclude human handling and the fact that these resources are electronic makes them logical for computer driven preservation activities. Over the last decade there have been a number of digital repository experiments that took different approaches, developed and used different data models, and generally moved our understanding forward. This paper reports on a recent initiative, PREMIS, that builds upon concepts and experience to date. It merits careful testing to see if the metadata identified can be used generally and become a foundation for more detailed metadata. And how much more will be needed for preservation activities? Initiatives for additional technical metadata and document format registries are also discussed.
    Footnote
    Vortrag, World Library and Information Congress: 71th IFLA General Conference and Council "Libraries - A voyage of discovery", August 14th - 18th 2005, Oslo, Norway.
    Type
    a
  6. McCallum, S.H.: Library of Congress metadata landscape (2003) 0.00
    0.0018909799 = product of:
      0.0037819599 = sum of:
        0.0037819599 = product of:
          0.0075639198 = sum of:
            0.0075639198 = weight(_text_:a in 1760) [ClassicSimilarity], result of:
              0.0075639198 = score(doc=1760,freq=10.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.14243183 = fieldWeight in 1760, product of:
                  3.1622777 = tf(freq=10.0), with freq of:
                    10.0 = termFreq=10.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=1760)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The Library of Congress (LC) has many of the same challenges as other libraries, especially large ones. LC has many different types of resources - books, journals, maps, music, manuscripts, audio, moving image, still image, artifacts, electronic - with large collections of each. Different levels of access are needed for this material: for some, collection level bibliographic description is adequate; for many, item level access is adequate; but for others, such as sound recordings, analytic, or sub unit access is highly desirable.The sizes of the LC collections are a major challenge - over 125 million non-electronic and over 3 million electronic items (and growing rapidly). And finally, electronic resources are presenting us with new issues - from metadata to preservation to storage to linking techniques. LC has tried to approach these challenges from a service perspective. Access must be successful for the end user, which mandates as much coherence and consistency in the metadata as possible and access systems that are easy to use. This paper focuses an the Library of Congress' perspective an metadata in the following three areas: (1) descriptive metadata in our current operations, (2) pathways that are developing that will support possible evolution in the future, and (3) broader metadata needs with digital material. The discussion is from a metadata element set and format point of view, not a cataloging data and cataloging rules view. Most acronyms used in this paper are expanded in an Appendix.
    Type
    a
  7. McCallum, S.H.: ¬A look at new information retrieval protocols : SRU, OpenSearch/A9, CQL, and XQuery (2006) 0.00
    0.001757696 = product of:
      0.003515392 = sum of:
        0.003515392 = product of:
          0.007030784 = sum of:
            0.007030784 = weight(_text_:a in 6108) [ClassicSimilarity], result of:
              0.007030784 = score(doc=6108,freq=6.0), product of:
                0.053105544 = queryWeight, product of:
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046056706 = queryNorm
                0.13239266 = fieldWeight in 6108, product of:
                  2.4494898 = tf(freq=6.0), with freq of:
                    6.0 = termFreq=6.0
                  1.153047 = idf(docFreq=37942, maxDocs=44218)
                  0.046875 = fieldNorm(doc=6108)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    Libraries have a large stake in search protocols because library systems are diverse yet library users need to access multiple sites without learning the search syntax of each site. This paper reviews and compares the relative advantages of several of the newest search protocols and query languages: Search via URL (SRU), OpenSearch, Contextual Query Language (CQL), and XQuery. The models for SRU and OpenSearch operations are described in order to explain differences in functionality - keyword search and simple data record return for OpenSearch and richer search with multiple format data return for SRU. The advantages of CQL are described along with possible complementary uses of the highly detailed and complex XQuery being developed for XML.
    Language
    a

Languages

Types