Search (4 results, page 1 of 1)

0.006077728 = product of:
  0.024310911 = sum of:
    0.024310911 = product of:
      0.048621822 = sum of:
        0.048621822 = weight(_text_:services in 2972) [ClassicSimilarity], result of:
          0.048621822 = score(doc=2972,freq=2.0), product of:
            0.1712379 = queryWeight, product of:
              3.6713707 = idf(docFreq=3057, maxDocs=44218)
              0.04664141 = queryNorm
            0.28394312 = fieldWeight in 2972, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.6713707 = idf(docFreq=3057, maxDocs=44218)
              0.0546875 = fieldNorm(doc=2972)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

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.

0.0055293585 = product of:
  0.022117434 = sum of:
    0.022117434 = product of:
      0.04423487 = sum of:
        0.04423487 = weight(_text_:22 in 4198) [ClassicSimilarity], result of:
          0.04423487 = score(doc=4198,freq=2.0), product of:
            0.16333027 = queryWeight, product of:
              3.5018296 = idf(docFreq=3622, maxDocs=44218)
              0.04664141 = 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)
  0.25 = coord(1/4)

Date

22. 1.2011 14:23:07

0.004341234 = product of:
  0.017364936 = sum of:
    0.017364936 = product of:
      0.034729872 = sum of:
        0.034729872 = weight(_text_:services in 2586) [ClassicSimilarity], result of:
          0.034729872 = score(doc=2586,freq=2.0), product of:
            0.1712379 = queryWeight, product of:
              3.6713707 = idf(docFreq=3057, maxDocs=44218)
              0.04664141 = queryNorm
            0.2028165 = fieldWeight in 2586, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.6713707 = idf(docFreq=3057, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2586)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Content

Einführender Beitrag eines Themenheftes "Content management systems" mit den Beiträgen: Luwak: a content management solution (Matt Benzing) - LibData to LibCMS: One library's evolutionary pathway to a content management system (Paul F. Bramscher, John T. Butler) - Beyond HTML: Developing and re-imagining library web guides in a content management system (Doug Goans, Guy Leach, Teri M. Vogel) - CMS/CMS: content management system/change management strategies (Susan Goodwin, Nancy Burford, Martha Bedard, Esther Carrigan, Gale C. Hannigan) - Untangling a tangled web: a case study in choosing and implementing a CMS () - Building a local CMS at Kent State (Rick Wiggins, Jeph Remley, Tom Klingler) - Migrating a library's web site to a commercial CMS within a campus-wide implementation (Tom Kmetz, Ray Bailey) - Building a collection development CMS on a shoe-string (Regina Beach, Miqueas Dial) - Using web services to promote library-extension collaboration (Jerry Henzel, Barbara S. Hutchinson, Anne Thwaits) - Leveraging resources in a library gateway (Jerry V. Caswell) - Copyright in the networked world: copyright police (Michael Seadle)

0.004341234 = product of:
  0.017364936 = sum of:
    0.017364936 = product of:
      0.034729872 = sum of:
        0.034729872 = weight(_text_:services in 2601) [ClassicSimilarity], result of:
          0.034729872 = score(doc=2601,freq=2.0), product of:
            0.1712379 = queryWeight, product of:
              3.6713707 = idf(docFreq=3057, maxDocs=44218)
              0.04664141 = queryNorm
            0.2028165 = fieldWeight in 2601, product of:
              1.4142135 = tf(freq=2.0), with freq of:
                2.0 = termFreq=2.0
              3.6713707 = idf(docFreq=3057, maxDocs=44218)
              0.0390625 = fieldNorm(doc=2601)
      0.5 = coord(1/2)
  0.25 = coord(1/4)

Abstract

Purpose - The purpose of this paper is to report on the content management solution for 50 subject guides maintained by librarian subject specialists at the University of Nevada, Reno Libraries. Design/methodology/approach - The Web Development Librarian designed an SQL Server database to store subject guide content and wrote ASP.Net scripts to generate dynamic web pages. Subject specialists provided input throughout the process. Hands-on workshops were held the summer before the new guides were launched. Findings - The new method has successfully produced consistent but individually customized subject guides while greatly reducing maintenance time. Simple reports reveal the association between guides and licensed resources. Using the system to create course-specific guides would be a useful follow-up project. Skills learned in training workshops should be refreshed at regular intervals to boost confidence and introduce changes in the system. Practical implications - The advantages of centralizing content and separating it from presentation cannot be overstated. More consistency and less maintenance is just the beginning. Once accomplished, a library can incorporate Web 2.0 features into the application by repurposing the data or modifying the ASP.Net template. The now-organized data is clean and ready to migrate to web services or next-generation research guides when the time is right. Originality/value - This paper uniquely reports on an SQL Server, ASP.Net solution for managing subject guides. SQL Server includes data management features that increase application security and ASP.Net offers built-in functionality for manipulating and presenting data. Utmost attention was given to creating simple user interfaces that enable subject specialists to create complex web pages without coding HTML.