Csuc2013 dlodge-final

148 views
116 views

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
148
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Csuc2013 dlodge-final

  1. 1. Not Just for the Web: Cascade and Mass Email Messages Cascade User Conference September 17, 2013
  2. 2. UCO Configuration Overview WCMS (Cascade Server) Staging (blasts-preview.uco.local) Production (blasts.uco.edu)
  3. 3. Our Challenge Distribution of Daily News  Daily newsletter  Stories submitted by the UCO community  Compiled by University Relations  Emailed to the UCO community
  4. 4. 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
  5. 5. Centralities - 2001
  6. 6. 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
  7. 7. Centralities - 2005
  8. 8. Centralities - 2008
  9. 9. Centralities - 2009
  10. 10. 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
  11. 11. User-Friendly Editing
  12. 12. 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
  13. 13. Workflow
  14. 14. Centralities - 2013
  15. 15. 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
  16. 16. The Metafile
  17. 17. The Archive  Published nightly  Simple jQuery-based script to filter the links
  18. 18. 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
  19. 19. 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
  20. 20. 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
  21. 21. David J. Lodge 405-974-2691 http://technology.uco.edu dlodge@uco.edu

×