350 likes | 473 Views
Content Management Systems Buy or Build. Ricky Rankin Queen’s University Gareth McAleese University of Ulster. Content Management System - Buy. The Queen’s Environment Problem to be Solved CMS Expectations The Implementation Path Where are we Next Steps. The Queen’s Environment.
E N D
Content Management Systems Buy or Build Ricky Rankin Queen’s University Gareth McAleese University of Ulster
Content Management System - Buy • The Queen’s Environment • Problem to be Solved • CMS Expectations • The Implementation Path • Where are we • Next Steps
The Queen’s Environment • Web Site • Combination of Intranet & Internet • Some information sourced from corporate databases • VLE/MLE/Portal • Developed in house • Database driven • Live links to corporate database systems
Code it yourself <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=windows-1252"> <META NAME="Generator" CONTENT="Microsoft Word 97"> <TITLE>QUB Equal Opportunities Unit - eou</TITLE> <META NAME="Template" CONTENT="C:\PROGRAM FILES\MICROSOFT OFFICE\OFFICE\html.dot"> </HEAD> <BODY LINK="#0000ff" VLINK="#800080"> <TABLE CELLSPACING=0 BORDER=0 CELLPADDING=0 WIDTH=100% height="431"> <TR> <TD colspan="5" VALIGN="MIDDLE" height="35" ><a href="http://www.qub.ac.uk/">QUB Home </a> </TD> </TR> <TR> <TD VALIGN="MIDDLE" height="35" colspan="2" > <div align="left"><img src="images/EOUhead.gif" align="left" ></div> </TD> <TD VALIGN="MIDDLE" height="35" colspan="3" width="585" > <div align="right"><img src="images/EOUhomepage.gif" width="110" height="29" > </div> </TD>
So what’s wrong with this • Information owner does not update page • The site’s a mess! • Our site is a laughing stock • Doesn’t look corporate or consistent • Can’t be good for business • Can’t find information • Patchwork of sites, inconsistent in presentation and navigation • Non compliance: usability; accessibility • The bloke who did it has left
The fix • outsource
So what’s wrong with this • Information owner does not update page • The site’s a mess! • Our site is a laughing stock • Doesn’t look corporate or consistent • Can’t be good for business • Can’t find information • Patchwork of sites, inconsistent in presentation and navigation • Non compliance: usability; accessibility • The bloke who did it has left
Dreamweaver Code <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <html LANG="EN-US"><!-- #BeginTemplate "/Templates/vcentre-default.dwt" --> <head> <!-- #BeginEditable "doctitle" --> <title>The Queen's Visitors' Centre - Welcome</title> <!-- #EndEditable --> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <STYLE TYPE="text/css"></STYLE> <link rel="stylesheet" href="menu_items/qub3.css"> <SCRIPT LANGUAGE="JavaScript" TYPE="text/javascript"> <!-- if(window.event + "" == "undefined") event = null; function HM_f_PopUp(){return false}; function HM_f_PopDown(){return false}; popUp = HM_f_PopUp; popDown = HM_f_PopDown; //-->
So what’s wrong with this • Information owner does not update page • The site’s a mess! • Our site is a laughing stock • Doesn’t look corporate or consistent • Can’t be good for business • Can’t find information • Patchwork of sites, inconsistent in presentation and navigation • Non compliance: usability; accessibility • The bloke who did it has left
So what’s wrong with this • Information owner does not update page • The site’s a mess! • Our site is a laughing stock • Doesn’t look corporate or consistent • Can’t be good for business • Can’t find information • Patchwork of sites, inconsistent in presentation and navigation • Non compliance: usability; accessibility • The bloke who did it has left
CMS Expectations • Internet Pages Initially • 100K pages reduced to < 300 • Control in Hands of Information Owners • WWW based • Office skills minimum requirement • Controlled Publishing Process • Define authors/contributor; moderator; administrators • Documents can be prepared prior to publication date with publication/remove/review/archive dates defined • Workflow • Navigation generated by System
CMS Expectations - continued • Corporate Style & Compliance with Legalisation • Define templates with protected areas • Enforce alt tags/metadata where appropriate • Resuse Content
CMS Expectations Tomorrow • Improve Publishing Process • Collection of information for Prospectus • Increase use eForms • Build Central Resources • Media libraries • Bio files • Doc library • Tackle the Intranet • Generic templates for units • Built in links to corporate systems to produce staff lists, course lists ….
The Process • Senior Management • It’s their WWW & message • Focus on Intrenet • Define functionality required • Linkage with legacy systems • Metadata • Accessibility • Research the market • 100+ alleged products • JISC documents • CMS mail lists • Vendor white papers
What’s out There - Costs • Open Source • Free • Needs configuration and building • Bargain Basement • <£5K • Limited functionality • Low End • <£30K • Mid Range • £30K - £100K • Top of Range • How much have you got
Sources of Information • Vendor WWW Sites white papers • JISC Paper http://www.jisc.ac.uk/uploaded_documents/tsw_01-02.pdf • CMS List http://www.cms-list.org/ • Useful Links http://www.steptwo.com.au/cm/vendors/list/index.html http://www.hartman-communicatie.nl/content/tools.htm
Current Position • System Selected • Templates being developed • Internet Site Converted to use CMS and Live end June
Next Steps • Develop Training • Expand Range of Templates Available • Develop Corporate Assets • Develop Intranet site based on CMS • Develop Generic School/Unit Sites
Things We Missed on the Way Through • Tracking • Spell Checking • Edit in situ