University Portal Development

1
University Portal Development

• Kansas State University

2
Portal Theme Statement

• "The number of systems we cope with is a
  reflection of the tremendous depth and breadth of
  our institutions... Higher education needs a
  next-generation infrastructure that will allow
  our institutions to be user-centered, to
  establish and maintain life-long relationships
  with individuals, and to provide personalized,
  secure, seamless connections with all
  constituents."
•  

FOR MORE INFO...
The quote is from an article by Ed Lightfoot and
Weldon Ihrig in the Nov/Dec 2002 issue of
EDUCAUSE Review called "The Next-Generation
Infrastructure.
3
K-State Portal Approach

• Create a University Portal Development Task
  Force.
• Develop a Portal Prototype for K-State.
• Design a Portal Communication Strategy.
• Educate users through prototype demonstrations.
• Hold requirements definition meetings.
• Develop a Portal Project Plan.

4
Portal and the Integrated Information Initiative
Direct Software or Query Access
Technology (XML, CORBA, etc.) Users
University Data Bases Data Warehouse Courses Bo
oks/ Periodicals Research Papers Collections Vi
deo/Music Immersion/VR
A u t h e n t i c a t i o n
Direct Software or Query Access
Search Engine Metadata Network Servers
Students Faculty Alumni Citizens Clients Researche
rs Libraries Web Users Walk-ins
K-State Portal
Direct Software or Query Access
Authentication/Authorization
5
K-State Portal Task Force Organization

• Steering Committee
• Major University Stakeholders Project Sponsors.
• Technical Support Team
• Departmental Directors Technical Consultants.
• Project Development Team
• Web Development, Application Development DBA
  staff.
• Communication Team
• Central IT Support.

6
K-State Portal Prototype Goals

• Install Oracle Portal.
• Develop a Prototype with 2 application
  components.
• Understand content delivery mechanisms.
• Draft a Communication Plan.
• Draft an Enterprise Portal Project Plan.
• Learn about scalability, integration and
  migration requirements.
• Understand design, implementation, configuration
  and support issues.
• Review and gain approval.

7
Why a Prototype

• This is a Proof of Concept.
• Develop a working model to investigate and
  demonstrate the feasibility and functionality of
  Oracle Portal.
• Tool to educate the user community.
• Identify roles, responsibilities skills
  required.
• Gain an understanding of training, resource and
  time requirements.

8
Prototype Approach

• Contracted with Oracle Consulting.
• Total team immersion in project to complete with
  4 weeks of consulting time over an 8 week period.
• Long and intense development sessions with QA
  resulted in beneficial knowledge transfer for
  team members.
• Provides an environment to support continued
  research and discovery.

9
Prototype Development

• Technology Overview
• Oracle 9i Application Server, J2EE and web based
  development environment.
• Planning Requirements Definition
• Brainstormed and looked at other portals.
• Implementation
• Install configure Oracle Portal.
• Assigned roles, dealt with scenarios and
  developed solutions.
• Testing
• Final adjustments.

10
Where are we today?

• Prototype has been completed.
• Key demonstrations to major University
  stakeholders.
• Finalizing Communication Plan.
• Preparing for requirements analysis and
  definition.
• What does it look like today?

11
K-State Portal Prototype

• Demonstration http//portal.ksu.edu

12
Whats Next?

• Complete demonstrations to user community.
• Schedule requirements definitions meetings.
• Develop Portal Project Plan.
• Gain funding for appropriate staffing resources.

For more Information (coming soon)
http//www.ksu.edu/InfoTech/projects/portal
13
University Portal Development

• Questions?