Search (2 results, page 1 of 1)

0.092806555 = sum of:
  0.06354813 = product of:
    0.1906444 = sum of:
      0.1906444 = weight(_text_:objects in 4198) [ClassicSimilarity], result of:
        0.1906444 = score(doc=4198,freq=4.0), product of:
          0.3279419 = queryWeight, product of:
            5.315071 = idf(docFreq=590, maxDocs=44218)
            0.061700378 = queryNorm
          0.5813359 = fieldWeight in 4198, product of:
            2.0 = tf(freq=4.0), with freq of:
              4.0 = termFreq=4.0
            5.315071 = idf(docFreq=590, maxDocs=44218)
            0.0546875 = fieldNorm(doc=4198)
    0.33333334 = coord(1/3)
  0.029258423 = product of:
    0.058516845 = sum of:
      0.058516845 = weight(_text_:22 in 4198) [ClassicSimilarity], result of:
        0.058516845 = score(doc=4198,freq=2.0), product of:
          0.21606421 = queryWeight, product of:
            3.5018296 = idf(docFreq=3622, maxDocs=44218)
            0.061700378 = queryNorm
          0.2708308 = fieldWeight in 4198, 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=4198)
    0.5 = coord(1/2)

Abstract

Large, data-rich organizations have tremendously large collections of digital objects to be "repurposed," to respond quickly and economically to publishing, marketing, and information needs. Some management typically assume that a content management system, or some other technique such as OWL and RDF, will automatically address the workflow and technical issues associated with this reuse. Four case studies show that the sources of some roadblocks to agile repurposing are as much managerial and organizational as they are technical in nature. The review concludes with suggestions on how digital object repurposing can be integrated given these organizations' structures.

Date

22. 1.2011 14:23:07

0.016071463 = product of:
  0.032142926 = sum of:
    0.032142926 = product of:
      0.06428585 = sum of:
        0.06428585 = weight(_text_:work in 2972) [ClassicSimilarity], result of:
          0.06428585 = score(doc=2972,freq=2.0), product of:
            0.22646447 = queryWeight, product of:
              3.6703904 = idf(docFreq=3060, maxDocs=44218)
              0.061700378 = queryNorm
            0.28386727 = fieldWeight in 2972, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.6703904 = idf(docFreq=3060, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2972)
      0.5 = coord(1/2)
  0.5 = coord(1/2)

Abstract

After a review of the Kent State Libraries and Media Services Web site, a committee of librarians and staff gathered user feedback and developed a library-specific content management system (CMS) to make the move from a static HTML environment to database-driven design. This article focuses on the significant role of metadata in the CMS from the perspective of one of the site's architects and one of its content developers. This article includes figures and a biography for further reading. The work of the redesign was earlier described in a poster presentation for the 12th Annual ACRL conference.