1 / 11

uPortal and DEMAND

uPortal and DEMAND. History - uPortal consortium started 12/99 as part of JA-SIG. Mission is to build an open architecture framework for a free university portal. - Demand (DEpartmental MANagers portal) is a prototype uPortal that will address that one constituency. Elements of a Portal.

kaethe
Download Presentation

uPortal and DEMAND

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. uPortal and DEMAND • History- uPortal consortium started 12/99 as part of JA-SIG. Mission is to build an open architecture framework for a free university portal.- Demand (DEpartmental MANagers portal) is a prototype uPortal that will address that one constituency An Overview of the Princeton University Web - DEMAND

  2. Elements of a Portal • Adaptive, Secure Framework • Customization • Personalization • Desktop Replacement An Overview of the Princeton University Web - DEMAND

  3. Portal Choices • Free (with strings) • Buy a tool • Build our own • Use a vertical (or verticals) • Consortium An Overview of the Princeton University Web - DEMAND

  4. uPortal and DEMAND • Rationale for method • Open architecture, no vendor lock-in, no purchased code. • Follow J2EE specs to insure scalability, platform independence • Write in java An Overview of the Princeton University Web - DEMAND

  5. uPortal and DEMAND • Initial implementation • Currently at version 1.5 • 1 ½ years An Overview of the Princeton University Web - DEMAND

  6. uPortal and DEMAND • Resources for uPortal • About 10 schools • one hired consulting group • total FTEs are approx. 5-6 • Resources for Demand - One customer, one technical person An Overview of the Princeton University Web - DEMAND

  7. uPortal and DEMAND • uPortal Project management • Technical project mgr and a ½ time project leader. Managed outside of Princeton. Group meets approx 1/mo. • Volunteers for roles through JA-SIG • Demand Project management • Follows P2k methodology. Customer lead and one programmer. An Overview of the Princeton University Web - DEMAND

  8. uPortal and DEMAND • Project maintenance – uPortal • Coordinated through JA-SIG • Source code at Univ. of Delaware • Project maintenance – Demand • framework will be maintained by ASIG • content? An Overview of the Princeton University Web - DEMAND

  9. uPortal and DEMAND • Project success- Not yet met all our goals - Have made considerable progress - Believe prototype (due in Aug) will be successful. An Overview of the Princeton University Web - DEMAND

  10. uPortal and DEMAND • Futures • We are forming a steering committee of departmental mgrs to define needs. This should be done for every constituency serviced by a university portal. • We need university policy regarding vendor specific vertical portals (such as PeopleSoft) vs a horizontal portal. An Overview of the Princeton University Web - DEMAND

  11. DEMAND An Overview of the Princeton University Web - DEMAND

More Related