Home Healthcare Case Studies

A Major Hospital (Western USA), Web Content Management Tool

Project:

Web Content Management Tool

Executive Summary:

Solution

Architectural Overview of Custom Web Content Management Tool

• User Management: The WCM Tool has the ability to add, change or delete users. Users have User Ids, Names, Passwords, Email Addresses and Group Assignments.
• Group Assignments: Users may be assigned to one of two groups (User/Admin).
• Role-Based Access Privileges: The WCM Tool provides role-based security and access privileges:
• User Role: "User" level users are able to access the WCM Tool, add or edit content, but not move any new or edited content to the production website.
• Admin Role: "Admin" level users are able to access the WCM Tool, add or edit content, review work (new edited content) completed by users, as well as move approved pages to production.

WCM Tool Navigation/Environments

• WCM Menu: Users are able to navigate within the WCM Tool environment by using a menu. The menu is displayed upon successful logon to the WCM Tool.
• Data Environments: The WCM Tool supports three data environments: (1) an internal SQL Server database that stores all template data and web page data developed using the WCM Tool templates; (2) the staging area - where pages are generated from the web page generation engine; and (3) the production environment.

Web Page Templates (Programmer Maintained)

• Page Deletion: If a page is deleted, (part of the top menu or side menu,) the appropriate menu is updated.
• Web Page Content Editing: Users have the ability to edit a selected page, and to save the modified file for later review by a supervisor (Admin level user.)
• Page Preview: Users have the ability to preview the current page (being edited.)

Menu Editor

• Top Menu: An editor is provided for editing the top menu and any associated drop-down menus associated with the top-level choices.
• Side Menu: An editor is provided for the side menu and any associated drop-down menus associated with the top-level choices.

Page Generation Engine

• Specific Page Publication: A page generation engine is provided to move one page to the staging or production area from the WCM tool environment.
• Batch Publication of All Pages: Users have the ability to schedule a task to generate all pages afresh into the staging area from the tool.
• Page Migration to Production: Users have the ability to schedule a task to move all pages from the staging area to the production area.

Basic Workflow Management

• Pending-Approval Queue: Any page saved to the WCM Tool by any user is flagged for approval and added to a "queue" of other such pages.
• Page Review and Approval: "Admin" level users are able to access the workflow management area and review the list of pages that are pending review/approval; generate the page into the staging area after review (remove from queue); promote that page directly to production (a copy will be kept in the staging area also.)
• Page Approval and Publication: From the review page, the admin user is able to send an email to the regular user (author of the page), if the page cannot be approved. This provides a feedback mechanism from the approver to the content creator.
• Technical Environment: Front-end: MS Visual Studio (ASP, Visual Basic, VC++), HTML, XML; Back-end: Oracle 8i, SQL Loader, PL/SQL, XML.