Access Anywhere: The JHSPH Portal Project

1
(No Transcript)
2
Access Anywhere The JHSPH Portal Project

• Ross McKenzie, Director
• Michelle Newman, Assistant Director
• Johns Hopkins University
• School of Public Health
• Office of Information Systems
• Baltimore, MD

CUMREC 2001 May 16, 2001
3
The Johns Hopkins School of Public Health

• Annual budget of 230m
• 950 full/part time faculty
• 1,500 students
• 21 international
• 2,500 staff
• 11,000 living alumni
• 30 live outside US

• Receives 27 of all research funds for US schools
  of public health
• Faculty pursue research in 40 countries
• Award 1/6 of all public health doctorates world
  wide

4
Growth of JHSPH Web
5
Watershed Event
6
Requirements

• Secure electronic collaborative environment.
• Completely web-based.
• Access from disparate geographical areas.
• Highly personalized.
• Single point of access.

7
Mission Statement
The JHSPH portal is an academic research tool
providing a personalized single point of access
for consolidating information from disparate
sources.
8
Selection Criteria

• No client software.
• Rapid development and deployment.
• We needed a fairly Quick Win!
• Willing to form a partnership.
• Established firm with a solid future.
• Compatible with industry standards.

9
Project Plan
10
Interviewing Users

• Faculty Senate Questionnaire Results
• Company logos appeared as advertising
• News considered not useful.
• Webmail Calendar a necessity.
• Taxonomy What does this mean?
• Document Management is not clear.
• Threaded Discussion/Chat limited use.

11
Interviewing Users

• 100 Personal Interviews
• What do you do?
• How comfortable are you when using your computer
  and browser?
• Encourage openness.
• Useful as an opportunity to talk with less vocal
  faculty.

12
Demo
13
Portal Categorization

• Benefit of Portal
• Many ways to present information.
• Challenge
• Finding the best way to present the information
  for the user and for future administration
  maintenance.

14
Portal Categorization

• Possible Solutions
• WebLinks
• Taxonomy
• Basic CDAs
• Complex CDAs (user customizable)
• Another Tab

15
Personalization

• User Perspective
• The ability to choose what you want to see and
  where you want to see it.
• Technical Perspective
• The ability to determine the users options.

16
Customization
17
Framework and Architecture
18
User Roles

• Managing Access through Roles without creating
  an administrative nightmare
• Faculty, Alumni, Students, Staff, External Users
• Departments
• Centers, Committees, Classes

19
User Interface Design

• Minimize company logos wherever possible.
• Search available at all times.
• Pay close attention to the use of pop-up windows
  and additional windows.
• Allow for single sign on.
• 2-column, 3-column, whatever!
• Use of tabs.

20
Application Integration

• Clinical Trials Data
• Forms
• Administrative Applications
• Student
• Financial
• Grants/Contracts

21
Rollout

• Training Classes One-on-one
• Paper Brochure
• Email
• Posters
• Portal Booth

22
Why Training?

• New applications (web calendar)
• Explain personalization
• Dual purpose (also to get buy-in!)
• Explain potential

23
Security Requirements

• Portal software
• had to fit into our current security architecture
  which is somewhat restrictive for an academic
  institution.
• must authenticate via LDAP.
• must work with certificates.
• must work with SSL.

24
Security Strategy
25
Project Costs
26
Lessons Learned

• Start interviews as soon as prototype is done!
• Dont use the word Taxonomy!
• Component creation - easier than anticipated.
• Training will be extensive!

27
Future

• Accessible from wireless Palm/CE devices (not the
  Palm VII 802.11b access)
• Develop a true e-learning environment to merge
  our distance and onsite students and to provide
  service to alumni.

28
Contact Info
Ross McKenzie rmckenzi_at_jhsph.edu Michelle
Newman mnewman_at_jhsph.edu http//portalinfo.jhs
ph.edu