- Platform for Economic Inclusion
- Preference Editing Tools Design
- Fluid Infusion
- Design Handbook
- Social Justice Repair Kit
- BIG IDeA
We are iteratively engaged in user research to understand how users think about and manage their content around teaching, learning and research. This work ties into the UX Walkthroughs, which help us identify existing "pain points." Some of these will likely be well understood (and solution components can begin to be developed), but others will require more in depth understanding of why, what and how users need to work with content. This research can help us with that understanding.
Content management is being loosely defined as authoring, maintaining, organizing, viewing and sharing content...in this case digital content.
As we worked on the plan for this research and further tried to define content management in the context of Sakai, uPortal & Moodle, in the end we came to the conclusion that most of the use of these applications has to do with managing content...not in the sense of Content Management Systems but rather with specific goals in mind.
For Sakai and Moodle, both collaborative learning environments, the high level goal is to engage with content in a way to encourage teaching, learning and in Sakai's case, research. We can think of course material, assessments, research artifacts, email, announcements, etc. as content that is managed within a course and/or project site.
For uPortal, we are defining the content as both the portlets themselves and the content within the portlets. A user is concerned with which portlets they use and how they are configured to work together. They are also engaged with the specific content within each portlet.
In all cases, our current hypothesis is that many users think of the entire system as an application and such it should support their activities as such rather than expect them to work under the constraints of tools or portlets. They want to manage their content in the system as a whole and so expect to be able to seamlessly work with it across the system -- across sites in Sakai for instance.
The Problem of:
The impact of which is:
A successful solution would:
Note: The first round of the problem statement is focused on Sakai and specifically the Resources tool. We will either generalize it in future iterations or define separate statements for Moodle & uPortal.