Abstract
This article describes the selection of a web content management system (CMS) at the Ohio State University Libraries. The author outlines the need for a CMS, describes the system requirements to support a large distributed content model and shares the CMS trial method used, which directly included content provider feedback side-by-side with the technical experts. The selected CMS is briefly described.
Highlights
■■ Literature ReviewContent and Workflow Management for Library Web Sites: Case Studies, a set of case studies edited by Holly Yu, a special issue of Library Hi Tech dedicated to content management, and other articles effectively outlined the need for libraries to move from static websites, dominated by HTML webpages, to dynamic database and content management system (CMS) driven websites.[1]
This article describes the selection of a web content management system (CMS) at the Ohio State University Libraries
Because of a combination of page editing practices learned with static HTML and a variety of skill with cascading style sheets (CSS), many pages lost the central control of the header, menu, and footer
Summary
Content and Workflow Management for Library Web Sites: Case Studies, a set of case studies edited by Holly Yu, a special issue of Library Hi Tech dedicated to content management, and other articles effectively outlined the need for libraries to move from static websites, dominated by HTML webpages, to dynamic database and CMS driven websites.[1]. Organization, must meet specific local requirements for functionality, and must include revision of the content management environment, meaning new roles for the people involved with the website.[4] Karen Coombs noted that “the implementation of a content management system dramatically changes the role of the web services staff” and requires training for the librarians and staff who are empowered to provide the content.[5] Another challenge was and continues to be a lack of a turn-key library CMS.[6] Several libraries that did a systematic requirements gathering process generally found that the readily available CMSs did not meet their requirements, and they ended up writing their own applications.[7] Building a CMS is not a project to take lightly, so only a select few libraries with dedicated in-house programming staff are able to take on such an endeavor.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
