no more paper, no more stamps: targeted mywsu communications
DESCRIPTION
No More Paper, No More Stamps: Targeted myWSU Communications. Jack Alilunas, Lavon Frazier October 20, 2004. 1. Overview of WSU. Research university 22,000+ students Four campuses Multiple learning centers Distance degree program. Spokane. ~DDP~. Pullman. Vancouver. Tri-Cities. - PowerPoint PPT PresentationTRANSCRIPT
1 1
No More Paper, No More Stamps:Targeted myWSU Communications
Jack Alilunas, Lavon FrazierOctober 20, 2004
2
Overview of WSUOverview of WSU Research university 22,000+ students Four campuses Multiple learning centers Distance degree program
3
PullmanTri-Cities
Vancouver
Spokane~DDP~
WSU Campus LocationsWSU Campus Locations
4
Presentation OutlinePresentation Outline Business Problem
Business Solution
Related Policies
Notices Demo
Technical Overview
Problems and Plans
5
Presentation OutlinePresentation Outline Business Problem
6
Business ProblemBusiness Problem
Better means of communication!
7
Business RequirementsBusiness Requirements
communicate information to specified audiences
enable faculty to communicatewith students in their classes
officially notify individuals ofstatus, etc.
Needed mechanism to:
8
More RequirementsMore Requirements
easier to maintain than mailing lists more secure than e-mail able to assure & track delivery less costly than USPS more timely delivery than USPS
or campus mail
Needed electronic communication mechanism that was:
9
OpportunityOpportunity
WSU was developing the myWSU web portal
as part of our vision for a “seamless, integrated, intuitive
information environment”
10
SolutionSolution
Targeted Notices Facility
in
myWSU
11
Presentation OutlinePresentation Outline Business Problem
Business Solution
12
Targeted Notices FacilityTargeted Notices Facility
Uses target recipient groups In secured portal web space Delivery based on WSU network-id Electronic, not paper and stamps Available for immediate delivery
13
Notices Information FlowNotices Information Flow
Notices-
SenderAuthorizations
-TargetGroups Manage
Subscriptions
View
Notices
Manage
Notices
Create
Notices
myWSUNoticeSender
myWSUNotice
RecipientDatabase
14
Sender AuthorizationsSender Authorizations Automatically authorized to classes Administrator authorized to subscription groups to own area Default authorization to individuals
15
Target GroupsTarget Groups Automatically populated
class enrollments Self-service subscriptions
role, campus, colleges, VP areas Administrator managed
President’s Cabinet
16
Targeting IndividualsTargeting Individuals Ad-hoc targeting
manual id entry data warehouse query results
Programmatic targeting notice feeds
17
Presentation OutlinePresentation Outline Business Problem
Business Solution
Related Policies
18
e-Correspondence Policye-Correspondence Policy
“Electronic correspondence shall be one of the authorized means of communication from Washington State University to students, faculty, staff, and other constituents.”
19
Appropriate SecurityAppropriate Security
“All University electronic correspondence that contain individually identifiable confidential or operational information must be sent via secure mechanisms that ensure message authenticity, confidentiality and integrity.”
20
Appropriate UseAppropriate Use
“University electronic correspondence may be used only to meet academic instruction, research, public service, and administrative needs of the University.”
21
Sender ResponsibilitySender Responsibility
“Note: to avoid the perception of myWSU notices as spam, it is essential for you to consider the needs of your audience, and that the targeting and frequency of your notices reflect such consideration.”
In help text:
22
Recipient ResponsibilityRecipient Responsibility “Just as they are responsible for any
printed correspondence that is delivered by non-electronic means, faculty, staff and students are responsible for all information sent to them via University- provided electronic correspondence delivery mechanisms. …that would be received and read in a timely fashion.”
23
Presentation OutlinePresentation Outline Business Problem
Business Solution
Related Policies
Notices Demo
24
Notice Recipient FunctionsNotice Recipient Functions Notices alert New notices list Notices in-box and viewer Campus announcements Subscriptions alert Manage subscriptions Subscriptions list
25
Notice Sender FunctionsNotice Sender Functions Create notices– three targeting methods– four notice styles– four handling options
Manage notices– search and display– delivery statistics– target additional recipients– change effective dates – stop further delivery
26
Presentation OutlinePresentation Outline Business Problem
Business Solution
Related Policies
Notices Demo
Technical Overview
27
Portal EnvironmentPortal Environment
OracleDB
Oracle 9i
Application
Server
Redhat Enterprise Linux, J2EE
OracleInternet
Directory
Oracle
Portal
httpF5 SSLAccelerator
https
28
Legacy Systems InterfaceLegacy Systems Interface
Legacy
Systems
Legacy: MVS, Natural, Adabas
Portal: Linux, Oracle
class sections
enrollments
LegacyDB
(Adabas)
PortalTrans.
(Adabas)
NoticesDB
(Oracle)
Synch
Process
SQL
Attunity
Connect
recipient groups
29
Legacy Systems InterfaceLegacy Systems Interface
RONet
Legacy: Windows Server 2003
RONetDB
(SQL Server)
PortalTrans.
(Adabas)
NoticesDB
(Oracle)
Synch
Process
OID(LDAP)
portal authorizations
notice authorizations
instructors, academic support staff
SQL
Attunity
Connect
Attunity
Connect
SQL
Portal: Linux,Oracle
30
Notice FeedsNotice Feeds
Any environment
Portal: Linux, Oracle
AnyDB
Batch or Online Process
OracleXML DB
Notice
Creation
XML, FTP
NoticesDB
(Oracle)
notices
recipients
Notice delivery
via myWSU
31
Presentation OutlinePresentation Outline Business Problem
Business Solution
Related Policies
Notices Demo
Technical Overview
Problems and Plans
32
Problems EncounteredProblems Encountered Huge developer learning curve Slow adoption by senders Lack of recipient awareness– ignoring subscriptions– not opening notices
System instability
33
Work in ProgressWork in Progress
Fully automated notice feeds Initial automatic subscriptions Ability to reply to a notice
34
Planned EnhancementsPlanned Enhancements
Distributed group administration Automated records retention Purge and archive functions Accessibility issues
