Monday, November 2, 2009
Topic: The BLINK design process, content management system, dynamic navigation,
Participants: Penny White, Annie Krinsky, Sylvia Bass, Sonja Elson
UCSD hosts : Sydney Donahoe - Director Portal Services (ACT); Brett Pollak, Campus Web Manager; Allisa Becker, Operations Manager, Portal Services; Mojgan Amini, Director of Research Applications, User Experience.
Over lunch met with Jennifer Sturak, Managing Editor; Shelley Herron, Senior Analyst; Liz Morrison, Senior Writer.
A. BLINK overview - Sydney
1. In response to 1000 users' requests, Search field appears prominently on home page. Also placed above in banner section where the functionality is being re-worked. In future the people directory search will appear on left side, separately from standard Search fields.
2. Planning tool - SourceForge (similar to JIRA)
3. Toolbox will feature all personal tools such as My Blink. After old right column dashboards were removed, ( hated by ACT staff) there was an outcry from users who lost bookmarks. Solution = 'service available in browsers'
4. News - Users perceive there was more news on old BLINK whereas the opposite is true.
The rotating news pics have been paused by default.
5. Weekly Poll widget to use as quiz - (may purchase an application) will replace the Drive Time and Walk UCSD modules on right which are confusing to users as they also represent news which appears on the left
6. Users - 100,000 individuals per month in BLINK.
7. Widgets - Calendar (Google calendar), Maps, Updates . Shuttle tracks realtime position of bus.
8. Last Update info - placed near top of page.
9. Accessibility and Emergency info included in footer
10 Editors - Only SuperSMEs (subject matter experts) are allowed editing access.
B. Deployment, nuances, enhancements, work-arounds, and deployment of the Hannon Hill content management system - Brett Pollack
a. The Campus Web office provides brand consistency and compliance across all sites.
b. Cascade Server 5.7v - moving to 6.0 at end of 2009. Will be able to share data across websites and protect web data ...server redundancy.
c. Google Search appliance - each site has its own account;
d. Private content - CMS is separate from web server. . Password protected on web server side - have to log in to directory.
Use it with HT access .
c.
c.