UW Enterprise Portal Evaluation Report to Sponsors 18 February 2010

Purpose “(to) evaluate and make a recommendation on a portal platform that could be used for all University populations and to propose a high-level implementation plan that would include research administration as an early pilot.”

Project Organization Project Planning/Leads Application Integration Community Expectations InfrastructurePortal Core User Interface Mobility

Drivers / Needs Improve the research management experience Integration of administrative systems and applications Integrate more UW information and services – leverage the community Tailored experience based on UW role(s)

An Enterprise Portal An integration platform that securely provides a central point for accessing, personalizing, and configuring information and applications appropriate to your role in the University. A standards-based integration and/or presentation platform.

High Level Requirements Consume identities and roles and groups Tailor presentation based on roles Easy to publish content User discovery and choice User layout control Provide themes Display current data, refresh on changes Unified notification system Admin forcing of some content Two factor authentication Display personalization Customizable authentication levels

Candidate Platforms uPortal Liferay Both open source, widely used in higher education, good support for standards, agnostic on database and app server.

Platform Recommendation Liferay Good documentation, more LDAP support, advanced UI for admins, support for development tools, clearly identified API, support for JSR-286 portlet standard, full-text search, Office/Sharepoint integration, integrated components Will require some custom work to integrate Shibboleth.

Long-Term Recommendation: Establish an Enterprise Portal Program Develop the foundation to support a long- term, sustainable enterprise portal program. Positions the UW to evolve its application and information aggregation strategies.

Elements of a Successful Program Community participation and governance Appropriate resourcing Processes for quality assurance, deploying new content, and content evaluation Data driven decisions on organization and content User interface and technical standards Ongoing technology renewal

Community Governance Resolve ambiguity Manage short and long term goals Mitigate conflict

Proposed Structure UW Tech GovernancePortal Working Group UX StandardsTech Standards

Ongoing Resources (in addition to community participation) 1 FTE Program Manager 2 FTE Software Engineers 1 FTE User Experience Designer 0.25 FTE Quality Assurance Engineer 0.25 Database Administrator FTE Support (student hourly).2 FTE Identity and Access Management engineering

Recommended Next Steps Perform proof-of-concept IAM Integration (2-3 weeks) Foundation Setting and Discovery (3-6 months) – Implement Governance Model – Implement Communication Plan – Portal Infrastructure Planning and Development Planning for Initial Release

Discussion Questions about platform or evaluation criteria? OK to proceed with next steps? What resources are required when? Who is the portal service manager/owner?

Resources Project Report: l/Report+Draft l/Report+Draft Project Web Site: l/Home l/Home Liferay Portal:

Acknowledgements Rupert Berk, Leman Chung, Dan Comden, David Cox, Jelena Curless, Jennifer Dobbelaere, Nathan Dors, Frank Fujimoto, Janice Granberg, Brad Greer, Alisa Hata, Chris Heiland, Gina Hills, Marcus Hirsch, Bob Hurt, Bob Jamieson, Jim Kresl, Jim Laney, Tom Lewis, Fang Lin, Ping Lo, Jim Loter, Erik Lundberg, Mark McNair, Todd Mildon, RL (Bob) Morgan, David Morton, Clara Nic Mhathuna, Paul Prestin, Gary Prohaska, Ammy Phuwanartnurak, Oren Sreebny, Mike Seibel, Scott Stephenson, Paul Schurr, Dan Trippel, Ann Testroet, Darcy Van Patten, Jennifer Ward, David Wall, James Werle, Charles Wesley, Sean Vaughan, Bill Yock