TritonLink UCSD's Student Portal
advertisement
TritonLink -UCSD’s Student Portal Beth Surrell Gabe Olszewski AACRAO Technology Conference Today’s discussion We had StudentLink, what’s next? So how do we get there? Project Goals StudentLink vs. TritonLink Phased rollout Web keeps changing We had StudentLink, what’s next? “Integrate all aspects of life at UCSD – academics, business services and student life” Student expectations Looking to web for services Simple, reliable, current Build community Find information in one place Administrative needs Enrollment growth Limited staff Early web development - silos Most web sites were about the organization Mission/Vision/Organization Services Content and Information is copy of printed brochures Transactions Look, Chart duplicated paper process feel, navigation unique to each site Portal service model Organize Target around services content to student needs and interests Business process reviewed as applications designed Transactions Campus integrated with content about policy events and news So how did we get here? Broad campus involvement required!! Student Built Affairs/Business Affairs Partnership on successful campus business portal Executive Committee Co-Directors Technical (Student Affairs & Technical) Team Stakeholders Committee Project goals - 2005 70-20-10 service model 70% online services 20% generalist 10% specialist Integrate Student Affairs websites in portal Move from department silos to service focus StudentLink vs. TritonLink 1996 technology New technology Transaction based Just in time information Minimal content Content rich Duplicate efforts Content manager Narrow campus focus Broad campus focus No search capability Google search Tools remain in familiar position Looking for content in StudentLink: Task: Student wants to change major. Use of Google search for content: Task: Student wants to change major. Gather campus input –Spring 04 Focus groups with Students, Faculty, Staff conducted by Marketing firm Direct interviews – provosts, student leaders Student Met survey with campus student affairs staff Design phase Implement portal infrastructure Developed look, content, and service plan Worked with Registrar for initial content – content within StudentLink TritonLink live! March 2005 Migrated StudentLink tools Registrar content integrated Comments Begin – user feedback work on new tools Usability testing - ongoing On-going development Single sign on -Shibboleth Personalization Evaluate Move new tool requests Student Affairs websites to content management system Integration with in-person staff service Use system for routine issues Use staff for exceptions Compliment system Don’t reproduce or contradict Refer to in-lobby terminals Use TritonLink jargon Explain information structure Capture feedback Capture common questions for FAQs Integration with physical facility Smaller issue than anticipated Strategic Does placement of kiosks lobby send right message for exceptions Ever-changing web New design for ucsd.edu Integrate TritonLink to new look Supported by new version of Vignette Questions? tritonlink.ucsd.edu Contacts: Beth Surrell – bsurrell@ucsd.edu Gabe Olszewski - golszewski@ucsd.edu Resources added for project Vignette Portal and Content Management software 3 year campus wide license $.5 million New staffing Editor and writer Portal programmer Two application programmers
