Agenda

...

• Possible co-habitation solutions
• Action plan

Issues

...

• User populations that cross boundaries:
  • Student employees
  • Postdocs
  • Faculty
    *"Store fronts" and naming - how do people know which one to go to?
• Look-n-feel
• Governance in general
• Aggregating search results
• Announcements (double-entry)
• Calendar sharing
• Sharing of code, data & content
  • code update notifications
  • portlet sharing
  • user support

Proposed solutions

...

• Merge two portals into one (possibly with different "store fronts"):

...

• Shared database:
  • Common user lists, groups, announcements, channels, permissions store
  • Allows us to setup the two portals as backups for each other (possibly?)
  • SNAP would have to move to MySQL: a big job, but doable
• Somehow link the databases
• Setup data feeds (may only be possible in batch mode)
• Make AdCom code and libraries available with update notifications
• Make Student Portal code and libraries available with update notifications

Minutes

...

• Proposed action items:
  • By December, 2008:
    • 2 separate instances running
    • upgrade SNAP's code base to uPortal v 3.x
    •  discontinue support for IE6
    • reorganize content in SNAP, reduce the number of default tabs
    • enable portlets in SNAP
    • rename portals to ZotPortal
    • create a "store front" -- once a user authenticates, s/he will be redirected to the appropriate portal; for users who belong to more than one audience, the store-front will ask them which portal they prefer to go to and save their choice.   Both portal will provide ways to navigate from one to another
    • identify common tools: e.g. library, calendar, maps, safety, email, travel, etc.
  • Evaluate possibilities of merging by May, 2009