csuc2013 dlodge-final

21
Not Just for the Web: Cascade and Mass Email Messages Cascade User Conference September 17, 2013

Upload: hannonhill

Post on 15-May-2015

63 views

Category:

Technology


2 download

TRANSCRIPT

Page 1: Csuc2013 dlodge-final

Not Just for the Web:Cascade and Mass Email

MessagesCascade User Conference

September 17, 2013

Page 2: Csuc2013 dlodge-final

UCO Configuration Overview

WCMS(Cascade Server)

Staging(blasts-

preview.uco.local)

Production(blasts.uco.edu)

Page 3: Csuc2013 dlodge-final

Our Challenge

Distribution of Daily News

Daily newsletterStories submitted by the UCO communityCompiled by University RelationsEmailed to the UCO community

Page 4: Csuc2013 dlodge-final

Original Solution

Centralities Mark I

Born in 2001Hand typed daily in OutlookArchives in a shared Outlook folderHad to be sent before the close of business

Page 5: Csuc2013 dlodge-final

Centralities - 2001

Page 6: Csuc2013 dlodge-final

Original Solution

Centralities Mark II

Created in MS WordSent as HTML from WordAdded brandingRepeated typos due to Word->HTML

translationStill archived in Outlook folderStill sent before close of business

Page 7: Csuc2013 dlodge-final

Centralities - 2005

Page 8: Csuc2013 dlodge-final

Centralities - 2008

Page 9: Csuc2013 dlodge-final

Centralities - 2009

Page 10: Csuc2013 dlodge-final

Plan for a New Version

Centralities Mark III

User friendly creation and editing of messages

Queue for sending at any timeUniversity brandedAutomatically go out to multiple mailing listsOnline version and online archive

Page 11: Csuc2013 dlodge-final

User-Friendly Editing

Page 12: Csuc2013 dlodge-final

The Solution

Email Message Asset – The Message

Simple two-column HTML pageLeft column for a block of upcoming eventsRight column for contentBase URL setSimple workflow:

Edit -> Publish Preview -> Publish Production

“View on Website” link

Page 13: Csuc2013 dlodge-final

Workflow

Page 14: Csuc2013 dlodge-final

Centralities - 2013

Page 15: Csuc2013 dlodge-final

The Metafile

Email Message Asset – The Metafile

Uses the asset ID as a unique identifierContains:

Send Date and Time Path to the HTML file All information for email headers

XML-based

Page 16: Csuc2013 dlodge-final

The Metafile

Page 17: Csuc2013 dlodge-final

The Archive

Published nightlySimple jQuery-based script to filter the links

Page 18: Csuc2013 dlodge-final

The Solution

Production Server-Side Script

Rewrite URLs for hostname changeExtract email information from the MetafileCheck if already processedSend the emailFinal cleanup

Page 19: Csuc2013 dlodge-final

Lessons Learned

TimingHTML and XML files are not published instantaneously or simultaneously

Protect People from ThemselvesMore automation equals less chance of user error

Page 20: Csuc2013 dlodge-final

Future Plans

Revise the edit formPublish the archive from the WorkflowAdd loggingErrors emailed to our Service DeskExpand solution to other areas of campus

President’s Office Cabinet Notes

Page 21: Csuc2013 dlodge-final

David J. Lodge

405-974-2691

http://technology.uco.edu

[email protected]