UC Portal Workgroup
AGENDA
(TBD) November 2004
UCLA
Introductions
Genesis for the Workgroup
Description of the UCLA/UCSD joint portal project and its goals
Issues that Need Attention
What do
we expect a portal to do?
Differences between research,
instruction and administration's needs
What
about SAKAI Course Management?
Will it
line up with existing portals on campuses?
What do campuses need to do
with portals to better support UCOP's apps?
Can we still follow an open
source direction and use commercial portal products?
Multiple portals on a campus.
(How many is too many? How many is too few?)
Level set on portal projects on the campuses. Have each
project report briefly on:
Scope: size and nature of
audience, numbers of independent portals, etc.
Goals
Approach: technology/products
in use, funding approach
Current status
Goals for next 2 or 3 years
What would we like to accomplish together?
Sharing of content (what
content?)
Exchange of applications
(which applications?)
Others?
Implications:
Common taxonomy?
Content interchange standards (meta tagging, format, etc.)
Surfacing content from portal in another portal
Surfacing applications from one portal in another portal
Opportunities for hosting multiple portals in a shared, single infrastructure?
Identity Management/Directory/Authentication implications
Standards to explore (perhaps a brief background
presentation for each one)
JSR 168
WSRP
TEI
OASIS XML
word processing standards
others?
Pilot project(s)?
Try surfacing content from
Vignette CMS in someone else's uPortal?
Try hosting an application and
surfacing it in both Vignette and uPortal?
Process to refine a common
taxonomy (starting with UCLA/UCSD taxonomy)
Try hosting an independent
portal instance in an existing portal environment?
Wrap Up Plan for Next Steps