Improving the CLE 1
Comments
Aug 14, 2008
Aug 14, 2008
Hi Gonzalo,
Great questions. Some things we have answers to, but haven't documented yet. Others are being discovered as we analyze the screens in more detail.
With the risk of losing documentation around the issues you've brought up (though I hope we don't), I'd like to suggest we get together in a call (possibly with the other UXI resources) to discuss each point in more detail.
I think that way we can comb through what has an answer and what needs one.
(edited)
I love the design, below some questions, some comments about possible gaps, uncertainty about scope/intentions.
1. Main Screen Templates
========================
1. Gateway Dashboard Screen
---------------------------
2-3. Assumes a) notion of internal membership, b) ability to create internal membership?
4-5. Assumes Sakai internal login (not CAS, etc, or mixed modes).
2. Dashboard Screen
-------------------
5. Widget list - categorization? How will a real list work?
6. Sites - How will a real list work?
3. Site Home Page Screen
------------------------
4. Site title bar - some sites titles cannot be customized under some circumstances/in some contexts
5-6-7. Sidebar? is this like a view/perspective?
4. Tool Screen (Ex: Site Settings)
----------------------------------
What is the purpose of the site id? Is this an editable field?
6. Widget
---------
State? What does minimize/close/move mean? For page view? For session? Forever?
2. Create a Site
================
2. Create a Site: Non-Course
----------------------------
Assumes course/not course site type distinction as only possibility
Assumes editable site title in all cases?
Missing some metadata
3. Create a Site: Course
-------------------------
Assumes non-provisioned course setup? No terms, etc.
Assumes editable title, etc.
3. Manage Site Settings
=======================
1. Site Home Page
-----------------
Note: Am on a site now, looks like the dashboard - site and dashboard need to be able to be adequately visually distinguished.
Sites have multiple owners, design assumes not
3. Site Settings - Members
--------------------------
Select All, Select All Visible are not the most common use cases. Other actions, other selection filters have a higher priority.
4. Site Settings - Members - Add Members
----------------------------------------
"For now, we will ask for user email addresses only, as this is most likely" - is this true?
5. Site Settings - Roles & Permissions - Modify Permissions
-----------------------------------------------------------
Aggregate idea may be overwhelming. Most people accept the defaults of each tool and leave it at that - at most will modify one tool. Leaving it in the tool makes better sense? I really like the design of the permissions grid.
6. Site Settings - Import/Export
--------------------------------
New sites can import content from old sites when being created- where is that functionality?
Functionality missing (tools, page order, groups, duplication, import from sites) or moved someplace else?
4. Edit Preferences
===================
2. Account Details
------------------
Assumes editable fields for institutional data, assumes internal login
4. Edit Look & Feel - Upload Logo
---------------------------------
Assumes that all site types can have own logos, assumes that sites can do without titles
5. Edit Look & Feel - Styles & Colors
-------------------------------------
Assumes that all sites can be changed in this manner (style, color scheme) - whereas it may be only certain types of sites only or none at all depending on the institutional context.
5. Add Tools
============
Some tools need configuration when added - where is that?
Some institutional contexts will disallow tool list editing, or rearranging?