Search (8 results, page 1 of 1)

0.027969502 = product of:
  0.083908506 = sum of:
    0.083908506 = weight(_text_:electronic in 4886) [ClassicSimilarity], result of:
      0.083908506 = score(doc=4886,freq=4.0), product of:
        0.19623034 = queryWeight, product of:
          3.9095051 = idf(docFreq=2409, maxDocs=44218)
          0.05019314 = queryNorm
        0.4276021 = fieldWeight in 4886, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.9095051 = idf(docFreq=2409, maxDocs=44218)
          0.0546875 = fieldNorm(doc=4886)
  0.33333334 = coord(1/3)

Abstract

Increasingly, XML applications are appearing on the World Wide Web, from e-commerce to information management. In the case of libraries and archives, XML enables more flexible information management and retrieval than using MARC or a relational database management system. Describes a project to explore the use of XML and the EAD, and the development of a prototype electronic finding aid. It focuses on the technical aspects, and reviews the options available and the choices made. This is done within the setting of a small- to medium-sized archive with minimal tools and resources.

0.015982574 = product of:
  0.04794772 = sum of:
    0.04794772 = weight(_text_:electronic in 3005) [ClassicSimilarity], result of:
      0.04794772 = score(doc=3005,freq=4.0), product of:
        0.19623034 = queryWeight, product of:
          3.9095051 = idf(docFreq=2409, maxDocs=44218)
          0.05019314 = queryNorm
        0.24434407 = fieldWeight in 3005, product of:
          2.0 = tf(freq=4.0), with freq of:
            4.0 = termFreq=4.0
          3.9095051 = idf(docFreq=2409, maxDocs=44218)
          0.03125 = fieldNorm(doc=3005)
  0.33333334 = coord(1/3)

Abstract

Using new communication technologies libraries must face continuously new questions, possibilities and expectations. This study discusses library-related aspects of our electronic era and how computer-related data formats affect bibliographic dataprocessing to give a summary of the most important results. First bibliographic formats for the exchange of bibliographic and related information in the machine-readable form between different types of computer systems were created more than 30 years ago. The evolution of information technologies leads to the improvement of computer systems. In addition to the development of computers and media types Internet has a great influence on data structure as well. Since the introduction of MARC bibliographic format, technology of data exchange between computers and between different computer systems has reached a very sophisticated stage and has contributed to the creation of new standards in this field. Today libraries work with this new infrastructure that induces many challenges. One of the most significant challenges is moving from a relatively homogenous bibliographic environment to a diverse one. Despite these challenges such changes are achievable and necessary to exploit possibilities of new metadata and technologies like the Internet and XML (Extensible Markup Language). XML is an open standard, a universal language for data on the Web. XML is nearly six-years-old standard designed for the description and computer-based management of (semi)-structured data and structured texts. XML gives developers the power to deliver structured data from a wide variety of applications and it is also an ideal format from server-to-server transfer of structured data. XML also isn't limited for Internet use and is an especially valuable tool in the field of library. In fact, XML's main strength - organizing information - makes it perfect for exchanging data between different systems. Tools that work with the XML can be used to process XML records without incurring additional costs associated with one's own software development. In addition, XML is also a suitable format for library web services. The Department of Computer-related Graphic Design and Library and Information Sciences of Debrecen University launched the BDML (Bibliographic Description Markup Language) development project in order to standardize bibliogrphic description with the help of XML.

0.014126732 = product of:
  0.042380195 = sum of:
    0.042380195 = weight(_text_:electronic in 3373) [ClassicSimilarity], result of:
      0.042380195 = score(doc=3373,freq=2.0), product of:
        0.19623034 = queryWeight, product of:
          3.9095051 = idf(docFreq=2409, maxDocs=44218)
          0.05019314 = queryNorm
        0.21597168 = fieldWeight in 3373, product of:
          1.4142135 = tf(freq=2.0), with freq of:
            2.0 = termFreq=2.0
          3.9095051 = idf(docFreq=2409, maxDocs=44218)
          0.0390625 = fieldNorm(doc=3373)
  0.33333334 = coord(1/3)

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.

0.011334131 = product of:
  0.03400239 = sum of:
    0.03400239 = product of:
      0.06800478 = sum of:
        0.06800478 = weight(_text_:22 in 4950) [ClassicSimilarity], result of:
          0.06800478 = score(doc=4950,freq=2.0), product of:
            0.17576782 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05019314 = 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.33333334 = coord(1/3)

Date

30. 3.2003 11:06:22

0.0090673035 = product of:
  0.02720191 = sum of:
    0.02720191 = product of:
      0.05440382 = sum of:
        0.05440382 = weight(_text_:22 in 1457) [ClassicSimilarity], result of:
          0.05440382 = score(doc=1457,freq=2.0), product of:
            0.17576782 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05019314 = 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.33333334 = coord(1/3)

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.00793389 = product of:
  0.023801671 = sum of:
    0.023801671 = product of:
      0.047603343 = sum of:
        0.047603343 = weight(_text_:22 in 1461) [ClassicSimilarity], result of:
          0.047603343 = score(doc=1461,freq=2.0), product of:
            0.17576782 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05019314 = 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.33333334 = coord(1/3)

Date

30. 3.2003 10:50:22

0.00793389 = product of:
  0.023801671 = sum of:
    0.023801671 = product of:
      0.047603343 = sum of:
        0.047603343 = weight(_text_:22 in 2538) [ClassicSimilarity], result of:
          0.047603343 = score(doc=2538,freq=2.0), product of:
            0.17576782 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05019314 = 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.33333334 = coord(1/3)

Date

14. 8.2004 10:39:22

0.0068004774 = product of:
  0.020401431 = sum of:
    0.020401431 = product of:
      0.040802862 = sum of:
        0.040802862 = weight(_text_:22 in 720) [ClassicSimilarity], result of:
          0.040802862 = score(doc=720,freq=2.0), product of:
            0.17576782 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.05019314 = 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.33333334 = coord(1/3)

Date

28. 1.2006 19:01:22