Content Management System (CMS) - An overview

1. Content ManagementSystem (CMS)- An overview

2. Project Organisation

3. CMS Overview “To implement a content management infrastructure that captures, manages, leverages and distributes content in a collaborative fashion that minimizes the need for web authors to have significant technical skills in web design, implementation and publishing” Content Management System – Project Charter Version No. 0.4

4. CMS Objectives • Devolve content creation throughout the institution regardless of contributors’ skills • Provide security, governance and approval processes over content published on the web • Enable the creation, management, and usage of standardised metadata • Continue to support a diverse array of existing technology platforms • Consolidate the current technology environment wherever possible • Improve the quality of Monash web sites through the implementation of standards across presentation, metadata, governance, discovery, and navigation

7. Author Creates Content Approver checks Work CMS applies Metadata Not Approved Approved CMS publishes to the web servers Metadata sent to the Search Engine Available on the web A workflow with Metadata

8. Content Creation Aim: Simplify the processes of placing content on the web and obtaining approval to do so • Use templates to capture the content and to present it • Use workflow to simplify the upload, approve and publish processes • Embed Teamsite buttons in standard Microsoft applications if required

9. Processes Aim: Implement approval workflows and enable security such that only approved persons can publish to sites that are of importance to Monash

10. Metadata Aims: • Implement automated gathering of metadata with the ability of the authors and editors to correct if necessary • Appropriately store and manage metadata • Provide metadata to the search engine

11. Platforms/Environment Continue to support a diverse array of existing technology platforms Consolidate the current technology environment wherever possible Aims: • Implement processes that automate the capture of content from a variety of editing tools and simplify the presentation of that content • Enable the embedding of sophisticated content on web pages without requiring sophisticated web presentation skills from the author

12. Quality Aim: Improve the quality of Monash web sites • The implementation of standards across presentation, metadata, governance, and navigation will enhance quality • Ease of use will remove some of the barriers to quality • The dimensions of quality in this instance are accuracy, availability, discoverability, relevance, and timeliness of information

13. Quality - Actions • Accuracy: Enable an approval process to confirm the accuracy of the information • Availability: Ensure that the information is published, backed up, versioned, and restorable through automated Teamsite processes • Discoverability: Ensure that the information can be located through effective use of metadata driven searches • Relevance: Enable a process to ensure relevance through the use of approval processes • Timeliness of information: Simplify and automate the publication of web site information and enable removal of information through the use of automated “sunset” processes.

14. Implementation of TeamSite • Methods of content authoring • Use of standard content entry templates for html pages known as data capture templates • Use of web authoring applications for non-templated html pages • Use of Front-Office and TeamSite Briefcase for non-html pages

15. Front-Office and TeamSite briefcase • Front-Office is a TeamSite add-in to Microsoft Office that enables .doc, .ppt and .xls to be uploaded to the website directly from the desktop • TeamSite Briefcase is a TeamSite add-in to Window’s Explorer enabling any file type to uploaded to the website directly from the desktop