• Complete pilot by end of spring 2002
• scope will be Current Students
• Allow for customization of content within the portal, possibly to include rearranging the data as well as color schemes.
• Include at least one WOW application
• Demo to VCU Administration, etc. the value and return on building the MyVCU Portal.
• Develop a white paper outlining the costs (hardware, people) and timeline to implement a full blown MyVCU Portal.

• Registration
• Financial Aid
• Student Billing
• Tax Information
• Parking
• WebMail
• Events Calendar
• My Library
• Select databases determined by a student's major (or faculty/staff department)
• You've Got Books determined by a student's major (or faculty/staff department)

• Single Login (or at least a VCU Standard for Single Login)
• Immediate log-in to My Library
• Ability to detect whether an individual is a graduate or undergraduate and set an appropriate profile of selected resources (the library page already has defined the profiles; this would automatically serve them up)
• Log-in for what are now stand-alone accounts (e.g., ILLiad, My Library Record, document delivery)

Questions to be answered

• How do we get them to use the portal once built?
• What do we built the MyVCU portal on? Uportal, Campus Pipeline, what?
• Is a portal important?

Minutes (October 2001 Meeting)

• We agreed to create the test environment using UPortal on Academic Technology's newly install Java Application Server and to Database Server.
• It was pointed out that Campus Pipeline was working with UPortal to develop module(s).
• While it was pointed out that the University may be doing something long term with Oracle, DB2 would be the database that was used for the initial VCU Portal development.
• Jim Yucha would look into Training Opportunities for UPortal Development.