Search (4 results, page 1 of 1)

0.004527677 = product of:
  0.022638384 = sum of:
    0.022638384 = product of:
      0.04527677 = sum of:
        0.04527677 = weight(_text_:management in 2948) [ClassicSimilarity], result of:
          0.04527677 = score(doc=2948,freq=4.0), product of:
            0.14328322 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.042509552 = queryNorm
            0.31599492 = fieldWeight in 2948, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046875 = fieldNorm(doc=2948)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Abstract

RDA Resource Description and Access are guidelines for description and access to resources designed for digital environment and released, in its first version, in 2010. RDA is based on FRBR and its derived models, that focus on users' needs and on resources of any kind of content, medium and carrier. The paper discusses relevance of main features of RDA for the future role of libraries in the context of semantic web and metadata creation and exchange. The paper aims to highlight many consequences deriving from RDA being a content standard, and in particular the change from record management to data management, differences among the two functions realized by RDA (to identify and to relate entities) and functions realized by other standard such as MARC21 (to archive data) and ISB (to visualize data) and show how, as all these functions are necessary for the catalog, RDA needs to be integrated by other rules and standard and that these tools allow the fulfilment of the variation principle defined by S.R. Ranganathan.

0.004527677 = product of:
  0.022638384 = sum of:
    0.022638384 = product of:
      0.04527677 = sum of:
        0.04527677 = weight(_text_:management in 2956) [ClassicSimilarity], result of:
          0.04527677 = score(doc=2956,freq=4.0), product of:
            0.14328322 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.042509552 = queryNorm
            0.31599492 = fieldWeight in 2956, product of:
              2.0 = tf(freq=4.0), with freq of:
                4.0 = termFreq=4.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.046875 = fieldNorm(doc=2956)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Abstract

This paper discusses the progress that has been made to internationalize the management and development of RDA: Resource Description and Access. RDA has been designed for an international environment, and is used in a number of countries worldwide. The paper describes the impact that international adoption of RDA had on the arrangements for its governance, including a new structure for ensuring international participation. It discusses the progress that has been made to improve wider input into the processes for its development, including working groups, liaisons with related standards organizations, and cataloguing hackathons. The paper is based on desk research of published resources, including websites, blogs, and conference presentations. The paper concludes that the intention to internationalize RDA is serious and has made a good use of its opportunities, although threats to its success remain.

0.0034556747 = product of:
  0.017278373 = sum of:
    0.017278373 = product of:
      0.034556746 = sum of:
        0.034556746 = weight(_text_:22 in 2946) [ClassicSimilarity], result of:
          0.034556746 = score(doc=2946,freq=2.0), product of:
            0.14886121 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.042509552 = queryNorm
            0.23214069 = fieldWeight in 2946, 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=2946)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

Date

17. 5.2016 19:22:40

0.002667959 = product of:
  0.013339795 = sum of:
    0.013339795 = product of:
      0.02667959 = sum of:
        0.02667959 = weight(_text_:management in 3373) [ClassicSimilarity], result of:
          0.02667959 = score(doc=3373,freq=2.0), product of:
            0.14328322 = queryWeight, product of:
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.042509552 = queryNorm
            0.18620178 = fieldWeight in 3373, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.3706124 = idf(docFreq=4130, maxDocs=44218)
              0.0390625 = fieldNorm(doc=3373)
      0.5 = coord(1/2)
  0.2 = coord(1/5)

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.