1 / 12

Portal Direction at UCB

Explore the key issues, features, requirements, and challenges in developing a student portal at the University of Colorado at Boulder, focusing on content management, single sign-on security, and integration of diverse data sources.

estherp
Download Presentation

Portal Direction at UCB

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Portal Direction at UCB Dennis M. Maloney University of Colorado at Boulder

  2. What Is a Portal • A gateway to web-based services • A hub integrating information sources • A home-base between web adventures • A single, personalized interface to all information resources in a secure, consistent and customizable manner enabling relationship management

  3. Student Portal - Key Issues • Content Management & Integration • Single Signon / Security/ Architecture • Directory Integration& Roles Definition • Multiple portals per campus per system • Transitive Authentication / Authorization?? • Calendar / Web-Email Integration • Application Integration – e.g., SIS

  4. Typical Student Portal Features • Authoritative place for information • Personalization of look and feel • Calendars, Schedules, Web-Email • Course Tool/Grade Book Integration • Chat, Bulletin Boards, News & IM • Online help & Search engines • Channelized Format

  5. Campus Portal Requirements • Institutional branding • Student-Centric • Authenticate student and determine role • Customize based on student’s role/status • Personalize to student’s preference • Integration of diverse data sources • Single sign-on • Open, extensible, robust architecture • Publish and subscribe interface is critical

  6. Infrastructure Required • Identity registry • Directory Services defines role • Directory Services stores preferences • Kerberos for authentication • Directory schema for calendar service • Content creation & update tools

  7. JA-Sig Tool Set – uPortal • “Free” solution • http://www.ja-sig.org • Collaborative H.E. Effort • Channel Framework & Content • Mellon Grant – “shrink-wrap” • Version 2.0 available in May 2001

  8. uPortal V 2.0 • Implementation Ready • Role-based Authentication • More Robust Security • Channel Content Publish/Subscribe tools • XML/XSL Channel Rendering • Channel Content Development

  9. Challenges • Define strategic portal vision and architecture • Portal development crosses departmental and data boundaries • Integration of data sources • Cultural shift for content & channel compliance

  10. Portal Timeframe • Student Portal mock-up by March 1 • Demonstrate proof of concept • Identify technical & cultural constraints • Test Portal “Content” Definition • Train development staff

  11. Portal Timeframe, Cont. • Student Portal alpha pilot by June • Directory enabled • Probably multiple logins • Limited in scope • Student Portal beta pilot by August • Limited in scope but fully functional • Begin assessment & redevelopment

  12. Next Steps • Continued development and deployment • Define portal architecture • Gauge “Portal Readiness” • Define content & publish guidelines • Create a portal working group for initial prototype project

More Related