Emily Deere/Brett Pollack - UCSD Graduate Student Association

TRITONLINK EXECUTIVE COMMITTEE
MEETING
Friday October 29, 2010
PC WEST MARSHALL COLLEGE ROOM – LEVEL 2
(2:00 - 4:00 pm)
Members
Penny Rue, VC Student Affairs (Co-Chair)
Emily Deere, Exec. Director IT Applications, ACT System (Co-Chair)
John Baker, ACT/IT Applications/Acad/Apps/Manager
Bill Haid, Registrar, Admissions & Enrollment Services
Frank Powell, Academic Senate Chair of Division
Rick Nornholm, Director Technology/Admissions & Enrollment Services
Brett Pollak, Campus Web Manager
Barbara Sawrey, AVC Undergraduate Education
Beth Surrell, Director TritonLink Project
Jonathan Whitman, Director/Provost Muir College
Visitor:
Amini, Mojgan, ACT Director, Res Apps/User Experience
Student Representatives
Anish Bhayani, Undergraduate Student Representative
Manuel Ruidiaz, Graduate Student Representative
Members Absent:
Mae Brown, AVC Admissions & Enrollment Services
Jeff Gattas, Exec. Director University Communications & Public Affairs
Michelle Humphrey, Senior Director University Communications & Public Affairs
Gabriele Wienhausen, Associate Dean/Education, Div. of Biological Sciences
Our meeting started with general introductions of all the participants and a warm welcome to all including our new
Undergraduate Student representative Anish Bhayani.
I.
CWO – Campus Website Office Update – Emily Deere/Brett Pollack
Emily and Brett discussed the transition of the Campus Web Office to ACT. The purpose of the Campus
Web Office is to provide tools and services that integrate UC San Diego Web content so campus
information is more accessible to end users.
From a technical perspective, CWO now supports Blink, Current Students Web content, ucsd.edu, and
any website using the campus Web Content Management system. The CWO also supports MapLink,
Calendar Gateway, UCSD Mobile, and user interface design for all ACT web applications. The User
Interface technology stack can be leveraged by any campus department and can be accessed at:
http://uxt.ucsd.edu/
Emily Deere & Brett Pollak
NEW CWO STRUCTURE
1
Website UI
WebApp UI
UCSD Web
Consistency
2
Emily Deere
Brett Pollak
Allisa Becker
Greg Goldman
Jenny Chang*
Kyle Frost*
Mojgan Amini
Suki Chui
Flordelis Dimaano
Allan Kim
Nonie Kimpitak
Ike Lin
User Experience Technologies (UXT)
* Student Employees
3
Campus Web Office
Mission
The purpose of the Campus Web Office is to provide tools and services
that integrate UC San Diego Web content so campus information is
more accessible to end users.
Vision
The CWO accomplishes this through…
Offering a centralized content management system
Templates that reflect campus branding for websites and web
applications
Services & training to help UCSD departments and organizations get the
most out of these tools.
Mobile development
4
CWO Project Initiation
Business Owners
Academic Affairs, Chancellor’s Office, Student Affairs,
External & Business Affairs
Project Management
ACT-CWO
Technology
ACT ITI & ACT UX-T
5
Current Projects
Identify & train Blink content
owners in CMS
Over 60 people trained since June
Blink now relatively self sustaining
Online event form
registration framework
Mobile framework
TritonLink redesign Phase 2
CMS upgrade to version
6.7.2
Enhance Campus-wide
CMS Templates
Giving website redesign
RMP websites into Blink
Online Giving redesign
UI Design for new SSO
Migrate websites to CMS
6
2 Year CWO Roadmap
2010
Key:
Complete
In Process
Proposed
Ongoing
2011
UXT Project Design Requests
Migrate Websites to the CMS
Blink Operations
UXT UI Framework Support
Portal Services
UCPA Maintenance/Support
Transition
TritonLink & Current Students Redesign
TL
Phase 1
Financial Apps UI
Giving Website
Redesign
Mobile framework
Online
Giving UI
Apply mobile framework to Student Apps
Online Giving Redesign Phase 1 & 2
Lightweight Event Form Framework
Maplink Upgrades
(Security)
Timekeeping Roles
Screens
CMS utilities
Phase 1
CMS utilities Phase 2
Search Enhancements
Calendar Enhancements
Campus Website Refresh
CMS Sites Model
Enhance CMS Templates
CMS upgrade
Move RMP into Blink
1
I.
2
3
4
5
6
7
8
9
10
11
12
1
2
3
4
5
6
7
8
9
10
11
12
TritonLink Vision & Quick Wins Review.…………..….……. Beth
Surrell
Beth gave us a presentation that covered both Quick Wins and TritonLink Vision, please
see below.
II.
Calendar Gateway Update………………………………………Beth
Surrell
For the Calendar Gateway update, Beth showed and explained the website live on the
site. There was general discussion about the new tool and early adopters. She had an
action item to survey current calendar owners to see how it is working for them.
TritonLink
Follow up from June 2010 Quick Wins
What is TritonLink?
Vision for TritonLink 2.0
A mock-up of our concept
Project estimates
TritonLink Quick Wins
• Home page organization/enhancements (Completed)
– Order tools by type
– College/Departments more prominent
– Add shuttle schedule
– Links to calendars – events and academic
– Promote WebCT, WebMail, Port Triton
• Search improvements – TritonLink catalog created
• Navigation improvements – Tool tabs updated
• Library search widget (not completed)
• Double Duty pages (not completed)
• Footer changes (Completed)
What is TritonLink?
Go to www.ucsd.edu to “Current Students” or go to tritonlink.ucsd.edu
The intent of TritonLink is to
organize information by
topic—making it easier for
students to find UCSD
content and information.
TritonLink is a collection of
web pages in the campus
CMS which are branded
with the TritonLink logo.
A “TritonLink” branded page
is really no different than
any other page in the CMS.
It is a static Web page open
to anyone on the Internet.
MyTritonLink
MyTritonLink is a Web
application “behind”
campus SSO which
contains some
messaging specific to
the authenticated
student.
Penny Rue
Our Vision for TritonLink: Provide institutional functionality of what is typically
found in a student portal and provide an online environment enabling full
partnership and open participation by the entire UCSD community.
1. Better adoption of campus CMS use
• Reduce confusion: What pages are
TritonLink, what’s not?
• Remove the TritonLink brand from all CMS
pages.
2. Expand MyTritonLink’s role to become the
student portal.
• Entry is only through campus SSO
• Gateway to access all student tools
• Place for institutional messaging to students
• All pages/tools are MyTritonLink branded
John
Brett
Mojgan Rick
Nonie
Beth
3. Provide a student “Community” environment in MyTritonLink
• Provide the portal experience students expect
• Enable an on-line community for UCSD students
• Allow and encourage the development of UCSD-specific Portlets
• Provide high degree of personalization by individuals
Google’s portal
igoogle.com
Yahoo’s portal
my.yahoo.com
Microsoft’s portal
my.live.com
Today’s Portals have similar features:
• The user logs in with user/password (has an identity)
• A selectable theme
• Ability to create and name pages (tabs)
• Ability to Search, find, and add portlets
• Ability to organize and rearrange portlets
• Ability to “share” parts of their portal content
The majority of Web properties students use including Facebook, YouTube,
Flickr, MySpace, etc. allow personalization and control.
A student portal case study: Harvard
When Harvard rolled out a traditional student portal, students being disappointed in
the features and lack of personalization developed their own (Crimson Connect) using
a free hosted service. Crimson Connect not only has Harvard-specific portlets, but
leverages off an Ecosystem of thousands of other services like Yahoo, Facebook,
Amazon, MySpace, etc. that all can integrate into a student’s personalized page.
High-Level Estimates of Work
2) MyTritonLink Student Portal
1) “Current Student” CMS
Task
Resource
Effort
Task
ACT-UXT
5-10 days
Migrate content
ACT-CWO, ACTUXT, Student Affairs
20-25 days
URL redirector
ACT-UXT
5-7 days
Other Scripts
ACT-UXT
25-30days
QA
Roll-out
ACT-CWO,
Student Affairs
ACT-CWO,
ACT-UXT
5-10 days
Update Perl Apps
Parallel Work
Homepage
Resource
Update Java Apps
QA
Roll-out
Effort
ACT-ITAG,
ACT-UXT
ACT-ITAG,
ACT-UXT
ACT-ITAG,
ACT-CWO
Student Affairs
ACT-UXT,
ACT-ITAG
20-25 days
20-25 days
10-20 days
3-5 days
Total 3-6 months
1-2 days
Total 3-6 months
3) Community Tab
Task
Resource
Effort
Netvibes One-time setup
Vendor, ACT-UXT
$25k
Hosting & Maintenance
Vendor
$2k/month
QA
Student Affairs
Administration & Governance
Student Life
ongoing
Total
$25k +
$2k/month
Next Steps: Follow standard project lifecycle.
Scope document will clearly identity timeline and resources.
V.
Registrar Project Updates; E-Course, E-Grades, CUPID…………..Bill Haid
Update from Registrar’s Office
1. E-Course
a. Electronic workflow for Course Approval process
b. Project started July 2009
c. Requirements completed Fall 2009
d. In development Winter, Spring, Summer 2010
e. Currently in QA Testing; department staff involved
i. Econ, Math, Hist, Bio, MWP
f. Pilot launch Dec 2010; Seeking additional volunteer departments
g. General campus launch Feb 2011; Info sessions and training materials available in
January
h.
2. E-Grades
a.
b.
c.
d.
e.
f.
g.
Electronic submission of grades and grade changes
Requirements review completed Dec 2009
Project and funding approved April 2010
E-Grades development after E-Course.
Currently staffing project teams; Registrar, ACT, TL
Target pilot launch Spring 2011
Target general campus launch Fall 2011
3. CUPID (Create Unique Personal Identifiers)
a. Reconciliation of employee ID between PPS, ISIS, and IFIS
b. Program to automatically interface faculty information between ISIS and PPS for
instructional assignments.
c. Intended to improve data accuracy, faculty workload processes, classroom utilization
reporting, and other related academic activities for campus use
d. Moved to production Oct 21, 2010, targeted for completion Nov 2010
e. PPS to ISIS Interface (PII) now running each weekday
f. PII copies instructor information (EID, Status, DOB, mail code) from PPS to ISIS and
automatically creates PID for new instructors. (Instructor records will no longer be
created manually in ISIS.)
g. Departments are encouraged to expedite faculty information into PPS since instructors
will be attached to courses only if they are in PPS. Some coordination issues still to be
addressed.
h. This project a pre-requisite for E-Grades
i. Campus announcements will be forthcoming
VI. Student Systems Advisory Committee Update ….…... R. Nornholm/J. Baker
(Statistics taken from 6/4/2010 thru 10/28/2010)
Student System Advisory Committee (new/enhancements > 120 hours):
13 total requests: 1 new to be prioritized, 1 completed, 2 in work, and 9 in queue.
Major (requests >120 hours) non-SSAC efforts completed:
Direct Loans
UNEX ISIS-IFIS Interface changed to daily versus weekly and additional variance research tools
made available per Deloitte
CUPID
Academic Applications Response Team (enhancements < 120 hours):
29 total requests: 5 new, 3 completed
Footprints (FP) tickets (maintenance and mandates):
188 completed FP tickets (includes ISIS, SAM, TritonLink, and DARS)
11 closed trackers (TeamForge activities associated with FP tickets)
The next Student Systems Advisory Committee meeting is scheduled for November 19th.
The bottom line: Over the past four months we have accomplished quite a bit and, in an ongoing
manner, we have worked hard to stay ahead of planned/new and emergency/ad hoc requests for service.
To some extent, we have been successful in keeping our heads above water, but doing so is taking a toll
on the Academic Applications staff. Nonetheless, we want to do more! eCourse is getting ready to deliver
and eGrades development will ramp up immediately thereafter using many of the same programming
resources. We could easily find ourselves in the same position as we are currently resource-wise,
however, we made sure that the eGrades project included funding for a backfill contract programmer.
This person is already onboard and making good headway in terms of coming up to speed and addressing
several critical TritonLink maintenance and mandate items. Hopefully, this will allow me to use my more
experienced TritonLink programmers on TEC, SSAC, and AART requests without having to repeatedly
have them also working on emergency mandates