Janus Project Update

1. Janus Project Update Planning Group April 6, 2000

2. Agenda • What is the Janus project? • Status of the April edition • Planning for the September edition • Design/functionality overview • Discussion, input, questions Janus Project • Planning Group

3. Janus Project : <my.umich.edu> • The Web interface to U-M information, resources, and services • A new generation of Web applications • A CIO Office projectmanaged by the Planning Group Janus Project • Planning Group

4. Introduction : Current “Gateway” • Upside • Much viewed • High production values • Extensive content • Externally praised • Downside • Hard to find things • Passive “look and feel” • Incomplete • Structure tied to U-M organization • Internally criticized Janus Project • Planning Group

5. Introduction : Communities & Needs • Internal audiences • Faculty, students, and staff • Browse and search through internal information • Consistent navigation in “University cyberspace” • Convenient access to core applications • “Prospective” audiences • High school students, their parents, donors • University information • School and college program information • Materials for parents • Specific data and interests for prospective donors Janus Project • Planning Group

6. Introduction : Communities & Needs • Athletics, alumni, and hospital audiences • Athletic fans • Alumni seeking services • Patients seeking medical services • Other external audiences • Non-U-M researchers and colleagues • Other visitors Janus Project • Planning Group

7. Vision : Why Now ? • User needs and interest are high (the Internet is hot!) • A university’s web presence has become a measure of its quality • Institutional IT coordination at U-M enables greater cooperation • Web technology has progressed Janus Project • Planning Group

8. Vision : Results • A better Gateway • A portal for some audiences • Bring together many data sources (inside and outside university) • Integrated Web access to applications Janus Project • Planning Group

9. Vision : Deliver Value • Efficiency to individuals in audiences • Information sharing for schools, colleges, and departments • Perhaps provide graphical guidelines and templates • Perhaps e-commerce Janus Project • Planning Group

10. Plans : The “April Edition” of Janus • Four short-term goals • Prototype portal • Establish advisory teams • Improve U-M Gateway • Develop requirements for fall • Research and requirements • Conduct reviews and analyses with leadership and focus groups • Select information architecture approach Janus Project • Planning Group

11. Plans : The “April Edition” of Janus • Designing to users’ needs • Identity or brand • Content and information architecture • Navigation and browsing • Searching • User customization • Phased implementation with WebObjects • Front-end design • Back-end access to data sources • Integration of services • Customization and personalization Janus Project • Planning Group

12. Plans : University Participation • Faculty advisory groups — steering and advising • UM technical staff — research, design and implementation • Students — participation in design and evaluation Janus Project • Planning Group

13. Integration of services Bring information together Integrate information, resources, and services Add functionality Consistent presentation Consistent experience Easy to use Customize/personalize Deliver content based on your preferences Role-based and/or individual customization Security, accessibility, and self help Keeping it private Address special needs Get yourself out of trouble! Prototype Design Overview Janus Project • Planning Group

14. Any Questions ? Q and A Janus Project • Planning Group