Csuc2013 dlodge-final
Upcoming SlideShare
Loading in...5

Csuc2013 dlodge-final






Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds



Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Csuc2013 dlodge-final Csuc2013 dlodge-final Presentation Transcript

  • Not Just for the Web: Cascade and Mass Email Messages Cascade User Conference September 17, 2013
  • UCO Configuration Overview WCMS (Cascade Server) Staging (blasts-preview.uco.local) Production (blasts.uco.edu)
  • Our Challenge Distribution of Daily News  Daily newsletter  Stories submitted by the UCO community  Compiled by University Relations  Emailed to the UCO community
  • Original Solution Centralities Mark I  Born in 2001  Hand typed daily in Outlook  Archives in a shared Outlook folder  Had to be sent before the close of business
  • Centralities - 2001
  • Original Solution Centralities Mark II  Created in MS Word  Sent as HTML from Word  Added branding  Repeated typos due to Word->HTML translation  Still archived in Outlook folder  Still sent before close of business
  • Centralities - 2005
  • Centralities - 2008
  • Centralities - 2009
  • Plan for a New Version Centralities Mark III  User friendly creation and editing of messages  Queue for sending at any time  University branded  Automatically go out to multiple mailing lists  Online version and online archive
  • User-Friendly Editing
  • The Solution Email Message Asset – The Message  Simple two-column HTML page  Left column for a block of upcoming events  Right column for content  Base URL set  Simple workflow: Edit -> Publish Preview -> Publish Production  “View on Website” link
  • Workflow
  • Centralities - 2013
  • The Metafile Email Message Asset – The Metafile  Uses the asset ID as a unique identifier  Contains:  Send Date and Time  Path to the HTML file  All information for email headers  XML-based
  • The Metafile
  • The Archive  Published nightly  Simple jQuery-based script to filter the links
  • The Solution Production Server-Side Script  Rewrite URLs for hostname change  Extract email information from the Metafile  Check if already processed  Send the email  Final cleanup
  • Lessons Learned  Timing HTML and XML files are not published instantaneously or simultaneously  Protect People from Themselves More automation equals less chance of user error
  • Future Plans  Revise the edit form  Publish the archive from the Workflow  Add logging  Errors emailed to our Service Desk  Expand solution to other areas of campus  President’s Office  Cabinet Notes
  • David J. Lodge 405-974-2691 http://technology.uco.edu dlodge@uco.edu