1 / 15

my UMBC Redesign Project

my UMBC Redesign Project. Emedia Quarterly Meeting October 31, 2002. Overview. Background: Why Redesign? Proposed Process Discussion uPortal Demo. Why Redesign?. Like the web generally, higher ed sites are changing From “presence” to “experience”

sherlock_clovis
Télécharger la présentation

my UMBC Redesign Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. myUMBC Redesign Project Emedia Quarterly Meeting October 31, 2002

  2. Overview • Background: Why Redesign? • Proposed Process • Discussion • uPortal Demo

  3. Why Redesign? • Like the web generally, higher ed sites are changing • From “presence” to “experience” • How do we meet internal & external user needs with existing resources? • Distribution of Content Management • Change in technology presents opportunity to rethink myUMBC’s purpose and process.

  4. Changes in Higher Ed Sites • CASE Circle of Excellence Awards http://www.case.org/awards/alumni2002/award14.cfm • Fewer “institutional” sites seem to be winning awards • Trend is toward targeted sites focusing on personalization. • 3 of 4 “gold medal” sites didn’t exist five years ago. • 9 of all 14 medals focus on personalization • Why?

  5. From “Presence” to “Experience” • Past: Provide information • Content, navigation, infrequent updates • Focus is on designing a web “presence” • Present: Deliver services & functions • Online registration, pay online, online giving, etc. • Focus is on programming & technical engineering • Future: Build community & experience • Online Learning, SIGs, CMS, BLOGS • Focus is on targeted, personalized, frequently updated content

  6. What makes a good site? • If we’re moving toward building community, effectiveness ultimately depends on how a site addresses the information needs of its users AND sponsors. • In addition to target audiences (e.g., alumni, current students, faculty, staff, etc.), the stakeholders who support these groups need tools to help manage the content and information their users want.

  7. Proposed Process? • Fall: • Define myUMBC users, stakeholders & needs • Explore technology capabilities & portal best practices • Winter: • Define specifications for shared needs • Build and test functional prototype • Spring: • Refine development, consider pilot release • Prepare for launch (documentation, help, promotion) • Summer: • Launch • Milestones/Opportunities: PeopleSoft HR, Orientation

  8. Defining myUMBC Users • Who are myUMBC’s users or audiences? • What information do they need? • Who are the sponsors or stakeholders who support these users & needs? • What do stakeholders need to support their users?

  9. User Feedback Strategies • Focus groups • OIA Student Marketers (example) • OIT Help Desk (example) • Graduate Student Association (example) • Contextual Interviews • Site-based Surveys • Prototype Development & Testing • myUMBC Web Traffic Analysis

  10. Portal Best Practices • “The Power of Portals” Chronicle of H.E. • The GW Enterprise Portal Solution Educause 2002 Presentation • Charting a Smooth Course for Portal Development Educause Quarterly Article • Portal Fundamentals portalscommunity.com • Desirable Features & Priorities (draft)

  11. Portal Technology: Build or Buy? • Build: • Scarce resources for development AND maintenance. • Buy: • Vendor solutions (e.g., Blackboard, PeopleSoft). • Expensive, tied to vendor’s agenda

  12. Another Option: Share • Open Source: uPortal • Pros: • Cheap (free) • Access to other universities “brainpower.” • Cons: • Consistency of product support. • Customization depends on local knowledge.

  13. Uportal Demo Sites • California Technology Assistance Project (tutorial, guest acct.) • Denison University (different design, demo/guest login) • Illinois State University (good preview function) • Interactive Business Solutions (clean design, open layout) • Rutgers University (nice design, but light on content) • University of Kansas Medical Center (demo/guest login) • University of Delaware (good demo) Usability Note: a lot of uPortal sites say “Welcome Guest: Please Login,” but don’t provide any visible means of doing so. Must be a built-in preset developers didn’t turn off.

  14. Next Steps? • Opportunities • Honors Parents’ Assoc. Meeting (11/7) • OIT Town Hall with SGA (11/13) • Alumni Board Meeting (11/14) • John’s Web Content Development Class (January) • Brainstorming in smaller groups • Content & functional specifications • Programming & Design

  15. Contact: • John Fritz (fritz@umbc.edu or 410.455.6596) • This presentation is available at: • The UMBC Emedia Blackboard Site Or • http://www.umbc.edu/oit/myUMBC/myUMBCredesign.ppt

More Related