Portal Update

1
Portal Update

• ITSIG
• November, 23th , 2005

2
Release Overviews

• Plan is to proceed via a number of distinct
  releases
• Beta
• Beta (2)
• Pilot
• Production

3
Beta

• Objectives Stability of Portal framework and
  architecture
• Timeline Aug 31, 2005 - Oct 31, 2005 and now
  ongoing
• Exposures for Participants
• Unplanned service outages may occur
• Possible loss of configurations information and
  data.
• Access Restricted to a specific beta testers
  group.
• Content
• Limited content,
• Usability and accessibility not a primary focus.
• Success criteria
• Product is reliable, data and configuration
  information is safe.
• Outcome
• The success criteria still need to be met
• Patches from Unicon installed in early November
• Still need to be tested to have full confidence

4
Beta 2

• Objectives
• Continue testing the stability of the Academus
  Portal framework and the system architecture.
• Deliver single sign-on to key systems
• Expand user base (inclusiveness)
• Test appropriateness of the pushed tabs (Home,
  Academics, Campus, Resources)
• Enable Imagineering
• Timeline
• January, 2006 through February, 2006.

5
Beta 2 (contd)

• Exposures for Participants
• Unplanned service outages may occur
• User tab/channel configurations may be lost.
• User data in the Academus Bookmarks, Calendar and
  Notes channels may be lost
• Access
• wide range of faculty, staff, students
• Content
• Similar to what users see day one of pilot
• Success criteria
• No problems are detected that result in unplanned
  service outages and/or loss of user
  configurations and data.

6
Pilot

• Objectives
• Ongoing content development in support of the
  Universitys goals for the portal
• Final elements of design in place, feedback
  mechanisms.
• Timeline
• March, 2006 through Spring 2006
• Exposures for Participants
• Minimal, framework is production status.
• Access
• As broad a range and number of UofG and faculty,
  staff, students as possible.
• Success criteria
• Conforms to Guelphs accessibility requirements
• Resources in place to sustain the deployment
• Significant progress on usability

7
Production

• Objectives
• Regular content life cycle, gaining traction
• Timeline
• In place for summer, 2006.
• Exposures for Participants
• Minimal, framework is production status.
• Access
• Entire UofG faculty, staff, students
• Success criteria
• Portal is widely recognized as a key tool in
  supporting and enabling the mission of the
  University of Guelph.

8
Groups

• Groups will be defined from the
  organizational_status attribute in the central
  directory
• Faculty
• Staff
• Students
• Everyone else
• Further discussions on where to take this during
  the pilot

9
Major Tabs

• Home
• Calendar, Campus News
• Academics
• WebCT, WebAdvisor
• Resources
• WebMail, Briefcase, Bookmarks, Notes, Address
  Book
• Campus Life
• Discussion Forums, Launchpad
• New Tab