Search (2 results, page 1 of 1)

  • × author_ss:"Taniguchi, S."
  • × theme_ss:"Metadaten"
  • × type_ss:"a"
  1. Taniguchi, S.: Recording evidence in bibliographic records and descriptive metadata (2005) 0.01 
    0.008627012 = product of:
  0.038821556 = sum of:
    0.022897845 = weight(_text_:of in 3565) [ClassicSimilarity], result of:
      0.022897845 = score(doc=3565,freq=26.0), product of:
        0.061262865 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.03917671 = queryNorm
        0.37376386 = fieldWeight in 3565, product of:
          5.0990195 = tf(freq=26.0), with freq of:
            26.0 = termFreq=26.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.046875 = fieldNorm(doc=3565)
    0.015923709 = product of:
      0.031847417 = sum of:
        0.031847417 = weight(_text_:22 in 3565) [ClassicSimilarity], result of:
          0.031847417 = score(doc=3565,freq=2.0), product of:
            0.13719016 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.03917671 = queryNorm
            0.23214069 = fieldWeight in 3565, 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=3565)
      0.5 = coord(1/2)
  0.22222222 = coord(2/9)
    Abstract
    In this article recording evidence for data values in addition to the values themselves in bibliographic records and descriptive metadata is proposed, with the aim of improving the expressiveness and reliability of those records and metadata. Recorded evidence indicates why and how data values are recorded for elements. Recording the history of changes in data values is also proposed, with the aim of reinforcing recorded evidence. First, evidence that can be recorded is categorized into classes: identifiers of rules or tasks, action descriptions of them, and input and output data of them. Dates of recording values and evidence are an additional class. Then, the relative usefulness of evidence classes and also levels (i.e., the record, data element, or data value level) to which an individual evidence class is applied, is examined. Second, examples that can be viewed as recorded evidence in existing bibliographic records and current cataloging rules are shown. Third, some examples of bibliographic records and descriptive metadata with notes of evidence are demonstrated. Fourth, ways of using recorded evidence are addressed.
    Date
    18. 6.2005 13:16:22
    Source
    Journal of the American Society for Information Science and Technology. 56(2005) no.8, S.872-882
  2. Taniguchi, S.: Understanding RDA as a DC application profile (2013) 0.00 
    0.0021037988 = product of:
  0.018934188 = sum of:
    0.018934188 = weight(_text_:of in 1906) [ClassicSimilarity], result of:
      0.018934188 = score(doc=1906,freq=10.0), product of:
        0.061262865 = queryWeight, product of:
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.03917671 = queryNorm
        0.3090647 = fieldWeight in 1906, product of:
          3.1622777 = tf(freq=10.0), with freq of:
            10.0 = termFreq=10.0
          1.5637573 = idf(docFreq=25162, maxDocs=44218)
          0.0625 = fieldNorm(doc=1906)
  0.11111111 = coord(1/9)
    Abstract
    The applicability of Dublin Core Application Profiles (DCAP) and the Singapore Framework for DCAPs to Resource Description and Access (RDA) were assessed. First, a draft RDA application profile is outlined, which reveals their applicability to RDA as a whole. Then, the current situation and issues involved in defining and specifying the RDA vocabularies, description structures, and syntaxes, all of which form the RDA application profile, are reviewed, for four levels of the RDA description structure; that is, the levels of aggregates and components of statements.

Years

Themes