1. Daphne Ogle, Fluid Design Lead, University of California, Berkeley Content Management Research

2. Overview Content management in our context Research project goals Draft Plan Discussion –Feedback on draft plan –Who can be involved? –How do we make it happen? –Timeline

3. Content Management Loosely defined as -- authoring, maintaining, organizing, viewing and sharing content...in this case digital content. Focus on USER’s definition of content in the respective products NOT “Content management System”

4. Research Project Goals Establish a comprehensive vision for Fluid Shared understanding of user’s concept of content management in respective applications Identify component candidates for helping users manage their content across uPortal, Moodle, Sakai & Kuali Comprehensive set of Personas defined and refined Create a long term vision of the UI architecture/conceptual model in Sakai

5. Problem Statement The Problem of: Heavy use of Resources tool in Sakai which has many usability problems UI grouped by function rather than activity –Clunky user experience for activities requiring users to move across tools (Sakai) and portlets (uPortal) We don’t understand well: –goals that users have regarding content –multiple paradigms (publishing, document management, file sharing, etc.) Diverse and distributed nature of open/community source development lends itself to tools being developed in silos.

6. Problem Statement - cont’d The impact of which is: A confusing and frustrating user experience Unclear how to implement content-related functionality Knowing how and when to integrate tools with resources is difficult Leading to: Lower adoption rate (long term use) Increased training & support costs Increased design and development time "Spaghetti" code

7. Problem Statement Cont’d Affects: All Users: students, faculty, teaching assistants, staff, researchers, training and support of systems, designers & developers of additional tools A successful solution would: Allow us to understand how users think about and engage with content Create views of data that make sense to users Define long term UI architectural vision for Sakai (ie. repository behind the scenes, content management activities happen in the context of the work) Identify candidate components Recommend experience integration needs and techniques between tools & portlets Communicate clear picture of above to community

8. The Plan Define vision / scope Recruit project team Need Analysis –Review existing requirements/research –Competitive analysis –Identify & recruit users –Contextual Inquiry: http://wiki.fluidproject.org/display/fluid/Contextual+Inquiry+Guidelines User Modeling –Personas –Scenarios –Other? Requirements & Design –Components –UI Architecture –Tool & Portlet UI integration strategies / suggestions More details at: http://wiki.fluidproject.org/display/fluid/Research+Project+Plan

9. Users - How many is reasonable? Regions –Canada, UK, Europe, South Africa, US Institution Type –Public, Private, Research focus, Community, On-line Institutional Roles –Instructors (variety of types), Teaching assistants, Students (undergrad, grad), Administrators (system, department, class), Researchers, Staff (project sites)

10. Possible Discussion Questions What’s the value in this project? Contextual Inquiry -- do we need expertise or can we teach/mentor other to do this practice? –We could do a class at uCamps. How do we do analysis and modeling of research in a distributed environment? How do we cover regional areas? How best to share out results with community as we go along -- show progress? Who can be involved? When? What kind of time? Where else should we recruit help (particularly for regional coverage)? Others?