Skip to end of metadata
Go to start of metadata

This is a draft in progress.

Discussion about preferences and permissions and what components might emerge.

Preferences & Permissions Definition

Definition

Problem/Pain

Problem description.

Scenarios

Sarah Windsor - Primary Persona
Scenarios to come.

Ed McClellan, Undergraduate
Scenarios to come.

Blue Sky Vision

Preferences & Permissions Component Ideas

Preferences Manager

  • Concierge - Personalizer, Customizer
  • Tool/Portlet editor/manager - difficult to see who will see the changes i make
  • Site-centric vs. User-centric preferences
  • Does the site know who I am, does it display my name? ("Welcome ...")
  • Customizing access keys - potential for conflict with browser shortcut keys
  • (U) No control over Personal Account, not associated with customization. User does not know what the system has identified.
  • Accessibility Preferences
    • Black on White / B-Y / Font Sizes
    • Access Keys

Permissions Manager

Summit Post-it Page

At the Fluid Summit, pain points represented on post-it notes were grouped into problem spaces (such as Feedback), then into (usually very high level) potential components such as the ones below. Each problem area was then rated as to whether it affected 1, 2, or 3/All of the Fluid applications (Sakai, uPortal, Moodle). Each potential component was then rated on the following matrix, which indicated how severe the pain point it helped solve was for users, as well as how frequently the pain point was encountered. It helped us determine how high a priority it was, with 1 being the highest priority and 3 being the lowest.

high severity

1

2a

low severity

2b

3

 

high frequency

low frequency