/
Management Roundtable

Management Roundtable

Jun 14, 2005

Patty Gertz, Princeton

  • involved with JA-SIG from origin

  • portal strategy is not to have a portal - based on institution needs

Cornell

  • demo/demo guest login

Jonathan Markoff, Columbia

  • community/collaboration facilitation

  • enterprise portal started with Peoplesoft (HR, Payroll, benefits) rollout, expanding to students

    • SSO into Peoplesoft enabled through portal

  • looking at integrating with Sakai moving forward

Sarah Arnott, MUN

  • 2001 portal investigation

  • Banner school - SSO integrated into Banner

  • Small, student focused features and enhancements (e.g. student parking permit lottery)

Jason Shao, Rutgers

  • SSO introduced with myRutgers, tied to the portal

  • student focused gradual rollout, student service driven

  • webmail has been greatest initial draw

  • CAS & Webproxy has been a strong draw

Jameson, KUMC

  • uPortal 2.4.2

  • identity management was greatest deployment barrier

  • ePay advice/benefit service initial application, required by state of Kansas

  • Columbia announcement service helped reduce email clutter

  • Peoplesoft integration is a challange

Brian Samson, ASU

  • portal supports all affiliates, including applied students, acccepted students, etc.

  • 1 FTE, running uP 2.3.1

  • integration with messaging and other systems upcoming in fall as iframe

  • Blackboard integrated with SSO, would like to move to Sakai

  • WebDAV superuser used to pull info out of Exchange