Search (4 results, page 1 of 1)

0.011903835 = product of:
  0.02380767 = sum of:
    0.02380767 = product of:
      0.09523068 = sum of:
        0.09523068 = weight(_text_:authors in 1438) [ClassicSimilarity], result of:
          0.09523068 = score(doc=1438,freq=4.0), product of:
            0.22281978 = queryWeight, product of:
              4.558814 = idf(docFreq=1258, maxDocs=44218)
              0.0488767 = queryNorm
            0.42738882 = fieldWeight in 1438, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              4.558814 = idf(docFreq=1258, maxDocs=44218)
              0.046875 = fieldNorm(doc=1438)
      0.25 = coord(1/4)
  0.5 = coord(1/2)

Abstract

The authors, hoping to stimulate interest in XML (Extensible Markup Language) and explain its value to the library community, offer a fine introduction to the topic. The opening chapter defines XML as "a system for electronically tagging or marking up documents in order to label, organize, and categorize their content" and then goes on to describe its origins and fundamental building blocks. Subsequent chapters address related technologies, schema development, XML-based tools, and current and future library uses. The authors argue persuasively for increased XML use, emphasizing its advantages over HTML in flexibility, interoperability, extensibility, and internationalization. Information is detailed, deftly written, and supported by numerous examples. Readers without a technological bent may find the text daunting, but their perseverance will be richly rewarded. Particularly recommended for webmasters and those working in library information systems and technical services.

0.011588706 = product of:
  0.023177411 = sum of:
    0.023177411 = product of:
      0.046354823 = sum of:
        0.046354823 = weight(_text_:22 in 2538) [ClassicSimilarity], result of:
          0.046354823 = score(doc=2538,freq=2.0), product of:
            0.17115787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0488767 = queryNorm
            0.2708308 = fieldWeight in 2538, 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=2538)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

14. 8.2004 10:39:22

0.009933176 = product of:
  0.019866353 = sum of:
    0.019866353 = product of:
      0.039732706 = sum of:
        0.039732706 = weight(_text_:22 in 720) [ClassicSimilarity], result of:
          0.039732706 = score(doc=720,freq=2.0), product of:
            0.17115787 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.0488767 = queryNorm
            0.23214069 = fieldWeight in 720, 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=720)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

28. 1.2006 19:01:22

0.007014402 = product of:
  0.014028804 = sum of:
    0.014028804 = product of:
      0.056115218 = sum of:
        0.056115218 = weight(_text_:authors in 3373) [ClassicSimilarity], result of:
          0.056115218 = score(doc=3373,freq=2.0), product of:
            0.22281978 = queryWeight, product of:
              4.558814 = idf(docFreq=1258, maxDocs=44218)
              0.0488767 = queryNorm
            0.25184128 = fieldWeight in 3373, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              4.558814 = idf(docFreq=1258, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3373)
      0.25 = coord(1/4)
  0.5 = coord(1/2)

Abstract

A band of archivists and IT professionals at Harvard took on a project to convert nearly two million descriptions of archival collection components from marked-up text into the ArchivesSpace archival metadata management system. Starting in the mid-1990s, Harvard was an alpha implementer of EAD, an SGML (later XML) text markup language for electronic inventories, indexes, and finding aids that archivists use to wend their way through the sometimes quirky filing systems that bureaucracies establish for their records or the utter chaos in which some individuals keep their personal archives. These pathfinder documents, designed to cope with messy reality, can themselves be difficult to classify. Portions of them are rigorously structured, while other parts are narrative. Early documents predate the establishment of the standard; many feature idiosyncratic encoding that had been through several machine conversions, while others were freshly encoded and fairly consistent. In this paper, we will cover the practical and technical challenges involved in preparing a large (900MiB) corpus of XML for ingest into an open-source archival information system (ArchivesSpace). This case study will give an overview of the project, discuss problem discovery and problem solving, and address the technical challenges, analysis, solutions, and decisions and provide information on the tools produced and lessons learned. The authors of this piece are Kate Bowers, Collections Services Archivist for Metadata, Systems, and Standards at the Harvard University Archive, and Dave Mayo, a Digital Library Software Engineer for Harvard's Library and Technology Services. Kate was heavily involved in both metadata analysis and later problem solving, while Dave was the sole full-time developer assigned to the migration project.