Search (6 results, page 1 of 1)

0.017612295 = product of:
  0.03522459 = sum of:
    0.03522459 = product of:
      0.07044918 = sum of:
        0.07044918 = weight(_text_:22 in 4950) [ClassicSimilarity], result of:
          0.07044918 = score(doc=4950,freq=2.0), product of:
            0.18208572 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05199731 = queryNorm
            0.38690117 = fieldWeight in 4950, 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=4950)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

30. 3.2003 11:06:22

0.014089836 = product of:
  0.028179672 = sum of:
    0.028179672 = product of:
      0.056359343 = sum of:
        0.056359343 = weight(_text_:22 in 1457) [ClassicSimilarity], result of:
          0.056359343 = score(doc=1457,freq=2.0), product of:
            0.18208572 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05199731 = queryNorm
            0.30952093 = fieldWeight in 1457, 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=1457)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

Seit dem 22. Februar 1999 ist das Resource Description Framework (RDF) als W3C-Empfehlung verfügbar. Doch was steckt hinter diesem Standard, der das Zeitalter des Semantischen Webs einläuten soll? Was RDF bedeutet, wozu man es einsetzt, welche Vorteile es gegenüber XML hat und wie man RDF anwendet, soll in diesem Artikel erläutert werden.

0.012328606 = product of:
  0.024657212 = sum of:
    0.024657212 = product of:
      0.049314424 = sum of:
        0.049314424 = weight(_text_:22 in 1461) [ClassicSimilarity], result of:
          0.049314424 = score(doc=1461,freq=2.0), product of:
            0.18208572 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05199731 = queryNorm
            0.2708308 = fieldWeight in 1461, 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=1461)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Date

30. 3.2003 10:50:22

0.012328606 = product of:
  0.024657212 = sum of:
    0.024657212 = product of:
      0.049314424 = sum of:
        0.049314424 = weight(_text_:22 in 2538) [ClassicSimilarity], result of:
          0.049314424 = score(doc=2538,freq=2.0), product of:
            0.18208572 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05199731 = 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.010567376 = product of:
  0.021134753 = sum of:
    0.021134753 = product of:
      0.042269506 = sum of:
        0.042269506 = weight(_text_:22 in 720) [ClassicSimilarity], result of:
          0.042269506 = score(doc=720,freq=2.0), product of:
            0.18208572 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05199731 = 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.007462248 = product of:
  0.014924496 = sum of:
    0.014924496 = product of:
      0.059697986 = sum of:
        0.059697986 = weight(_text_:authors in 3373) [ClassicSimilarity], result of:
          0.059697986 = score(doc=3373,freq=2.0), product of:
            0.23704608 = queryWeight, product of:
              4.558814 = idf(docFreq=1258, maxDocs=44218)
              0.05199731 = 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.