Search (3 results, page 1 of 1)

  • × author_ss:"Dean, R."
  1. O'Neill, E.T.; Childress, E.; Dean, R.; Kammerer, K.; Vizine-Goetz, D.; Chan, L.M.; El-Hoshy, L.: FAST: faceted application of subject terminology (2003) 0.05
    0.049570225 = product of:
      0.09914045 = sum of:
        0.09914045 = product of:
          0.29742134 = sum of:
            0.29742134 = weight(_text_:lcsh's in 3816) [ClassicSimilarity], result of:
              0.29742134 = score(doc=3816,freq=2.0), product of:
                0.5435469 = queryWeight, product of:
                  9.905128 = idf(docFreq=5, maxDocs=44218)
                  0.054875307 = queryNorm
                0.54718614 = fieldWeight in 3816, product of:
                  1.4142135 = tf(freq=2.0), with freq of:
                    2.0 = termFreq=2.0
                  9.905128 = idf(docFreq=5, maxDocs=44218)
                  0.0390625 = fieldNorm(doc=3816)
          0.33333334 = coord(1/3)
      0.5 = coord(1/2)
    
    Abstract
    The Library of Congress Subject Headings schema (LCSH) is by far the most commonly used and widely accepted subject vocabulary for general application. It is the de facto universal controlled vocabulary and has been a model for developing subject heading systems by many countries. However, LCSH's complex syntax and rules for constructing headings restrict its application by requiring highly skilled personnel and limit the effectiveness of automated authority control. Recent trends, driven to a large extent by the rapid growth of the Web, are forcing changes in bibliographic control systems to make them easier to use, understand, and apply, and subject headings are no exception. The purpose of adapting the LCSH with a simplified syntax to create FAST is to retain the very rich vocabulary of LCSH while making the schema easier to understand, control, apply, and use. The schema maintains upward compatibility with LCSH, and any valid set of LC subject headings can be converted to FAST headings.
  2. Colati, J.B.; Dean, R.; Maull, K.: Describing digital objects : a tale of compromises (2009) 0.04
    0.043138165 = product of:
      0.08627633 = sum of:
        0.08627633 = product of:
          0.17255266 = sum of:
            0.17255266 = weight(_text_:policy in 2983) [ClassicSimilarity], result of:
              0.17255266 = score(doc=2983,freq=4.0), product of:
                0.29423225 = queryWeight, product of:
                  5.361833 = idf(docFreq=563, maxDocs=44218)
                  0.054875307 = queryNorm
                0.5864505 = fieldWeight in 2983, product of:
                  2.0 = tf(freq=4.0), with freq of:
                    4.0 = termFreq=4.0
                  5.361833 = idf(docFreq=563, maxDocs=44218)
                  0.0546875 = fieldNorm(doc=2983)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Abstract
    The Alliance Digital Repository (ADR) is a consortial digital repository service developed by Colorado Alliance of Research Libraries (Alliance). This paper details how a standard descriptive metadata policy for repository records developed, and how that policy is currently being implemented. All digital objects in the ADR are required to have MODS and OAI-Dublin Core metadata that conform to certain minimum requirements. To help members meet the requirements, Alliance staff and the ADR Metadata Working Group, using tools available in the Fedora/Fez repository environment, have developed a customized set of core ADR material type templates in XSD form.
  3. O'Neill, E.T.; Chan, L.M.; Childress, E.; Dean, R.; El-Hoshy, L.M.; Vizine-Goetz, D.: Form subdivisions : their identification and use in LCSH (2001) 0.01
    0.011152269 = product of:
      0.022304539 = sum of:
        0.022304539 = product of:
          0.044609077 = sum of:
            0.044609077 = weight(_text_:22 in 2205) [ClassicSimilarity], result of:
              0.044609077 = score(doc=2205,freq=2.0), product of:
                0.19216397 = queryWeight, product of:
                  3.5018296 = idf(docFreq=3622, maxDocs=44218)
                  0.054875307 = queryNorm
                0.23214069 = fieldWeight in 2205, 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=2205)
          0.5 = coord(1/2)
      0.5 = coord(1/2)
    
    Date
    10. 9.2000 17:38:22