University Portal Development Taskforce

1
University Portal Development Taskforce

• 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
University Portal Task Force Steering Committee

• Pat Bosco, Assoc. Vice President and Dean of
  Students
• David Rintoul, Assoc. Professor, Biology, Chair
  CITAC
• John Struve, Assoc. Vice President, Adm. and
  Finance
• Tweed Ross, Director of Instructional Support,
  FSCOT rep.
• John Streeter, Director, Information Systems
  Office
• Brad Sidener, Vice President, Alumni Association
• Roger Terry, Unit Coordinator, Info. and
  Educational Technology
• Marc Johnson, Dean of Agriculture

4
University Portal Task Force Technical Support

• Harvard Townsend, Director CNS
• David Hillier, Director, Data and Information
• Administration
• Rob Caffey, Director of Information Systems, DCE
• Diana Blake, Assoc. Director, ISO
• Lloyd Walker, Project Manager, DIA

5
University Portal Task Force Implementation
Support

• Janelle Corkill, Senior Web Specialist, CNS
• Neil Erdwien, Web Technology Manager, CNS
• Bryan Rall, Application Developer, DCE
• Rusty Taylor, Multimedia Director, ECC
• David Allen, Director of Digital Libraries

6
Portal Prototype Project

• Kansas State University

7
Portal Prototype ProjectSteering Committee

• Dr. Elizabeth Unger, Senior Technical Sponsor,
  VPAST
• Jane Rowlett, Project Sponsor, Office of the
  Provost
• Harvard Townsend, Director, CNS
• David Hillier, Director, DIA
• Rob Caffey, Director of Information Systems, DCE
• John Streeter, Director, ISO

8
Portal Prototype ProjectTeam Members

• Lloyd Walker, Project Manager
• Bryan Rall, Application Developer, DCE
• Scott Smith, Application Developer, DCE
• Janelle Corkill, Senior Web Specialist, CNS
• Susan Bale, Webmaster, Electronic Publishing, IET
• Jan Alexander, Data Modeler, DIA
• Nicki Habluetzel, Process Analyst, DIA
• Rusty Taylor, Multimedia Director, ECC
• Greg Girard, Database Administrator, ISO
• Mike Ediger, Systems Specialist, ISO

9
Portal Prototype ProjectMarketing Committee

• Rebecca Gould, Director, ITAC
• Anne Stark, Marketing Coordinator, DCE

10
Project Goals

• Install Oracle Portal.
• Develop a Prototype with 2 application
  components.
• Develop a Marketing Plan.
• Develop an Enterprise Portal Project Plan draft.
• Learn about scalability, integration and
  migration requirements.
• Understand design, implementation, configuration
  and support issues.

11
Why a Prototype

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

12
Project Approach

• Week 1 Introduction Overview
• Week 2 Planning
• Week 3 Development
• Week 4 Testing Closeout

13
Week 1

• Introduction with Oracle Consultant
• Overview of Oracle 9i Application Server and J2EE
• Enterprise Java Beans (EJB) 2.0
• Servlets 2.3
• JavaServer Pages (JSP) 1.2
• Web Services
• Java Connector Architecture, JCA 1.0
• Java Authentication and Authorization Service,
  JAAS 1.0.

14
Week 2

• Portal Planning
• Identify components
• Design and Layout
• Experimenting
• Brainstorming
• Looking at other portal sites
• Two distinct areas
• Framework look feel
• Portlets content

15
Week 2

• Identify Roles Responsibilities
• Application Server Administrator
• Portal Administrator
• Portal Page Developer
• Portlet/Application Developer

16
Week 3

• Development
• Framework
• Create Style Sheets
• Create Page Templates
• Create Public Navigation Page
• Create Authenticated Navigation Page
• Create Graphics
• Assign Roles Access Rights

17
Week 3

• Development
• Portlets
• KATS
• K-State Online
• Course Organizer
• Calendar
• Course Schedule
• Student Information
• Search
• Sign-on
• News, Weather Sports

18
Week 4

• Complete framework portlet development.
• Insert portlets and make adjustments for fit.
• Document what weve learned.
• Meeting to discuss scalability into a production
  environment.
• Conference call with UNC to discuss marketing.
• Conference call with Zentropy Partners to discuss
  Digital Library Interface.

19
Where are we today?

• prototype
• The creation of a working model to demonstrate
  feasibility and function. The prototype is later
  refined for inclusion in a final product.
• This is a work in progress and is only one
  example of what a portal could possibly look
  like.
• What does it look like today?

20
Like This
and this
21
Whats Next?

• Demonstration to Portal Prototype Steering
  Committee, Review and Approval.
• Exit Interview with Oracle consultant.
• Make any necessary adjustments.
• Plan demonstrations to user community
• Enterprise Portal Project Planning

For more Information (coming soon)
http//www.ksu.edu/InfoTech/projects/portal
22
Portal Prototype Project

• Questions?