web content management system n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Web Content Management System PowerPoint Presentation
Download Presentation
Web Content Management System

Loading in 2 Seconds...

play fullscreen
1 / 13

Web Content Management System - PowerPoint PPT Presentation


  • 166 Views
  • Uploaded on

Web Content Management System. Developing a System for Managing Web Content York Libraries Content Management System - Demo. Doug Fenwick Manager Application and Bibliographic Systems York University Libraries dfenwick@yorku.ca. Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

Web Content Management System


An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
    Presentation Transcript
    1. Web Content Management System • Developing a System for Managing Web Content • York Libraries Content Management System - Demo Doug Fenwick Manager Application and Bibliographic Systems York University Libraries dfenwick@yorku.ca Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia Tuan Nguyen Application Support Specialist York University Libraries tuan@yorku.ca 1

    2. Web Content Management • Three years ago a group was formed with the task of revising and improving the York Libraries website. This brief presentation will: • Identify the major problems • Define the objectives for improvement • Describe how an OpenSource “Content Management System” helped meet those objectives Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 5b

    3. Web Content Management • Problems identified with the Library website • Haphazard development • Lacked an organizational plan • Content created with several different HTML editors • Few layout standards - or not consistently applied • Navigation was inconsistent • Internal links to other pages • Link changes required manual effort – often missed • Lacked bread crumb trail • Lacked navigation bar • Frequent replication of information on several pages • Content change required manual effort to change all Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 2

    4. Web Content Management • Problems identified with the Library website • Administration of the website was insistent and confusing • Two servers: development and production • Rights to publish on the production server were limited to three individuals • Notified via Email • Often a delay of several days before content was updated • A large site with many pages, but lacked an overall schema • Where is it? What is it? • Who created it? • Last updated? Still valid? Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 3

    5. Web Content Management • Problems identifiedwith the Library website • Introduced MS FrontPage in an attempt to improve usability • Did reduce problems related to editor differences and encouraged more staff to create content • But introduced new problems • Software on installed on the workstation • Frequent updates • Required formal training sessions ($) • Easy to become creative – too creative • Standards declined further • Too Microsoft–centric Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 4

    6. Web Content Management • Problems identifiedwith the Library website • Lacked dynamic interface to eResource database • Static pages – alpha lists - updated daily • As the number of eJournals increased they became difficult to use • Lacked the ability to search for electronic resources • Needed a more informative and useful display of search results • Limited development possibilities Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 5

    7. Web Content Management • Having identified the problems the next step was to define our objectives for improving the management of the website and it’s content. • During this time we became aware of the term “Content Management System” which implied more than just Web page construction or a means of mapping large Web sites. • Instead it implied the breaking down of Web pages into smaller blocks of content which are stored in a database and can be used to dynamically build Web pages. • The concept of a discrete web page began to break down. • Some of the concepts and terminology inherent to Content Management are reflected in our objectives. Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 5b

    8. Web Content Management • Objectives for Improving the Management of Web Content • Reduce dependency upon desktop software • Only need a web browser • Easy to learn • Easy to enter content • Encourage concentration on content rather than “look” of pages • Simple WYSIWYG/HTML editor for entering content • Ability to import existing documents and images • Impose standards for consistent presentation • Style sheets • Custom templates • Objects which define type of content being entered Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 6

    9. Web Content Management • Objectives for Improving the Management of Web Content • Improve navigation • Navigation bar, bread crumbs, improved link management • Distribute responsibility and increase the number of content creators • Define Roles for individuals • (Content Entry / Editor / Publisher) • Flexible - broad or narrow interpretation • Workflows – assigning tasks by Role • Dynamic management of content • Content immediately updated when published • Reusable content blocks – to reduce replication • Life cycle (define duration that content is available) Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 7

    10. Web Content Management • Objectives for Improving the Management of Web Content • Version Control • Ability to roll back to a previous version of the page • Useful for sessional pages • Affordable • Buy or Build? Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 8

    11. Web Content Management • OpenSource Content Management System • Proprietary OpenSource • ArsDigita (ArsDigita Community System) • framework for development •  RedHat • Redhat Web Application Framework •  OpenSource Community: Byline - http://byline.objectweb.org/ • Components • Java • Java Server Pages (Apache/Tomcat) • Oracle or postgreSQL Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 9

    12. Web Content Management • Accomplished to date • May 2002 implementation – included revised Library website • Move all existing static pages into CMS • Integrated searching of eResource database • Dynamic display of search results with improved interface • Wrapper templates for ILS • Interface and template for subject specialists to create Subject Resource Guides Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 10

    13. Web Content Management • In Progress • Interface and template for an Information Literacy Course tool • Dynamic and customizable lists of recently acquired print and electronic resources • Generic tool for designing library surveys • Data retention • Data analysis tool Access 2004 - October 14, 15, 16 - Halifax, Nova Scotia 11