Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin

...

  • Initial research
    • User interviews
      • What tasks do users perform most often? Do all users follow the same workflow to perform those tasks?
      • What are the pain points in the existing interface? What are the most frustrating tasks?
      • What do users wish they could do with the current interface but are unable to?
      • Where/when/how do users interact with Grouper?
      • How much functionality needs to be supported on small screens?
    • What's the true breakdown of expert vs intermediate users?
    • How much time, if any, should be spent testing the current interface against new users? existing users?
  • Gather requirements (concurrent with Initial Research)
    • Identify core functions
    • Identify existing functionality to be preserved
    • Identify new features requested by the community
      • Vote on new features?
    • Finalize list of new features and freeze requests
  • Low-fidelity wireframes - desktop and mobile
    • Initial sketching and low-fi electronic wireframe development
    • Test common tasks against wireframes
    • Rinse and repeat
  • High fidelity wireframes - desktop and mobile
    • Develop richer wireframes
    • Test common tasks against wireframes
    • Report results
  • Proof of concept of accessible widgets and write framework code (custom tags, common javascript etc)
    • Some of this could be done concurrently with steps outlined above
    • autocomplete
    • tree control
    • popup window
    • menu
    • layout (frame-like)
    • tooltips
  • Graphic Design
  • Development (iterative) (see the Developers Guide)
  • Testing

Key Tasks for User Testing

...

If you see an existing entry that reflects a concern or request that you share, please add your name and/or institution name to the Requester(s) cell.

{:=true} || Request name \\ || Description \\ || Category || Requester(s) \\ || | Use Spring MVC and Web-Flow \\ | Use same underlying technologies as Jasig CAS, thereby reducing skill sets necessary to deploy and customize a CAS-protected grouper installation. \\ | Backend | U Montreal | | HTML customization \\ | Use CSS themes (perhaps along the lines of csszengarden) and customizable JSP header and footer includes. \\ | Markup | U Penn \\ Cru (CCCI) \\ | | Internationalization (i18n) \\ | One language could be globally configured. Supporting multiple language would be better, but it's not a top priority. It could be detected from the browser (which is nice, but a default value would also work) but it has to be user-changeable using a drop-box or link of some kind since browser language might not be what the user prefers to see. | Backend | U Montreal \\ Cru (CCCI) \\ | | Display group relationships \\ | Visual display of groups impacting membership of a given group. Would illustrate subgroups and composite factors, perhaps expanded by levels. | UI | U Montreal | | Images of people in person picker | We would like a future Grouper UI to be able to display an image/photo of a subject (person) when choosing subjects to add as members of a group. \\ | UI | LIGO \\ \\ | | Why isn't subject a member search/display | Would be nice to have a way to search a group's membership and display why a particular subject is not a member of a group.  Example: given group x:y:allowed I'd lookup a subject and the UI would display that the subject is not a member of the group because of membership in x:y:deny or the subject is not a member of any groups which make up :allowed.  This would be very helpful for debugging a particular subject's membership issues when there are a lot of composite groups in play affecting the final group in question. | UI | U Chicago | | Roles/Permissions Area (Lite UI) \\ | Roles/Permissions work flow is somewhat complex and counter intuitive. The hierarchy graph and role/permissions display widgets are cool, but data entry flow could be improved. Maybe better documentation would be helpful. Are there any plans for this? | UI | UCLA | | Action Timer | Would be great when viewing details of a group to see when changes to a group will next be provisioned to downstream systems (or updated from external source) | UI/Backend | U Chicago \\ | | Mobile-Aware \\ | As mentioned in the architecture section above as a possibility, an interface optimized for use with mobile devices (smartphones and tablets) | UI | Stanford \\ Cru (CCCI) \\ | | Clone | Astem:AGroup exists including attributes and values, want to clone it to Bstem:BGroup with attribute names changing "namespace" from A to B. Users often want a new group that is "just like this existing group but different". | UI/Backend | LIGO | | Attribute handling at objects | It would be realy nice to handle attribute usage for groups, memberships and so on the page that handles the object. [See the UI being developed at Uppsala University|Grouper:Uppsala University Grouper Project Page]. | UI | Uppsala University \\ Cru (CCCI) \\ | | Metadata about provisioning \\ | Be able to attach built in attributes to identify on a UI where the group is used, and how long the provisioning takes (maybe range?) \\ | UI/Backend | Working group meeting \\ | | Encapsulated composites \\ | Would be nice if the UI treated include/exclude lists and require groups differently (maybe if they follow a naming convention) so the user doesnt need to know which group is the whitelist etc, the UI makes it easy.  Maybe this is in phase 2...  If looking at the full group the UI knows to edit the whitelist etc. \\ | UI | Steven C. \\ Chris \\ | | SSO to Grouper UI | Here at the University of Hawaii we also use CAS for authentication.  SSO to the Grouper UI would be very beneficial \\ | Backend | University of Hawaii (taken from comment below) \\ Cru (CCCI) | | Batch membership update from UI | Be able to easily assign multiple groups to a subject. Right now, there doesn't seem to be a way to manage membership from a subject point of view. Everything is done through the group page. It would be great if there was a may to manage membership from the subject info page. That way, we could easily add a single subject to multiple groups. It would be even better if there was a mechanism like the "Import members" from the Lite UI's group page where you can import a CSV file or imput members directly on screen. That could be used to list the groups in which we want to add a subject.  Also should be easy to remove multiple groups from a subject at once. | UI | U Montreal | | {color:#ff0000}Moved to "Guidelines".{color}\\   \\ -Hide complexity by default- | -Hide all of the "internal" attributes (such as ID, ID Path, UUID, etc.).  Only show the user-friendly names, paths, and descriptions.  The details will only become visible through a special setting.  The Lite UI does this now, and I think the entire UI should do this going forward.  I'd recommend that each user have a "profile" where they can set this kind of option globally... so that power users can always see the IDs, etc. but "normal" users will never be bothered by them.- | | Cru (CCCI) \\ | | -UX participation- \\ | -User eXperience professional can help with process to ensure good UI usability and workflow.- \\ | | U Chicago \\ | | GroupType Attributes | Add functionality for GroupType attributes to have a possible list of items a user can select. This will include showing a default value if one is presumed. There are of course cases in which a value needs to be supplied by the user, but there are many in which the possible answers are known and can be shown to the user for selection even if it is a boolean. To use the mailingList attributes as an example. The alias will need to be provided by the user. The allowAttachments and moderated are true/false questions. There can be a drop drown list to select true/false. A default value of say false can be specified in the metadata. For attributes that are lists of users, the user should be able to click on the attribute or an obvious button next to it to engage the selection process. | UI | UC Berkeley | {table-plus}
Wiki Markup
Advanced Tables - Table Plus
autonumber
true

Request name

Description

Category

Requester(s)

Use Spring MVC and Web-Flow

Use same underlying technologies as Jasig CAS, thereby reducing skill sets necessary to deploy and customize a CAS-protected grouper installation.

Backend

U Montreal

HTML customization

Use CSS themes (perhaps along the lines of csszengarden) and customizable JSP header and footer includes.

Markup

U Penn
Cru (CCCI)

Internationalization (i18n)

One language could be globally configured. Supporting multiple language would be better, but it's not a top priority. It could be detected from the browser (which is nice, but a default value would also work) but it has to be user-changeable using a drop-box or link of some kind since browser language might not be what the user prefers to see.

Backend

U Montreal
Cru (CCCI)

Display group relationships

Visual display of groups impacting membership of a given group. Would illustrate subgroups and composite factors, perhaps expanded by levels.

UI

U Montreal

Images of people in person picker

We would like a future Grouper UI to be able to display an image/photo of a subject (person) when choosing subjects to add as members of a group.

UI

LIGO

Why isn't subject a member search/display

Would be nice to have a way to search a group's membership and display why a particular subject is not a member of a group.  Example: given group x:y:allowed I'd lookup a subject and the UI would display that the subject is not a member of the group because of membership in x:y:deny or the subject is not a member of any groups which make up :allowed.  This would be very helpful for debugging a particular subject's membership issues when there are a lot of composite groups in play affecting the final group in question.

UI

U Chicago

Roles/Permissions Area (Lite UI)

Roles/Permissions work flow is somewhat complex and counter intuitive. The hierarchy graph and role/permissions display widgets are cool, but data entry flow could be improved. Maybe better documentation would be helpful. Are there any plans for this?

UI

UCLA

Action Timer

Would be great when viewing details of a group to see when changes to a group will next be provisioned to downstream systems (or updated from external source)

UI/Backend

U Chicago

Mobile-Aware

As mentioned in the architecture section above as a possibility, an interface optimized for use with mobile devices (smartphones and tablets)

UI

Stanford
Cru (CCCI)

Clone

Astem:AGroup exists including attributes and values, want to clone it to Bstem:BGroup with attribute names changing "namespace" from A to B. Users often want a new group that is "just like this existing group but different".

UI/Backend

LIGO

Attribute handling at objects

It would be realy nice to handle attribute usage for groups, memberships and so on the page that handles the object. See the UI being developed at Uppsala University.

UI

Uppsala University
Cru (CCCI)

Metadata about provisioning

Be able to attach built in attributes to identify on a UI where the group is used, and how long the provisioning takes (maybe range?)

UI/Backend

Working group meeting

Encapsulated composites

Would be nice if the UI treated include/exclude lists and require groups differently (maybe if they follow a naming convention) so the user doesnt need to know which group is the whitelist etc, the UI makes it easy.  Maybe this is in phase 2...  If looking at the full group the UI knows to edit the whitelist etc.

UI

Steven C.
Chris

SSO to Grouper UI

Here at the University of Hawaii we also use CAS for authentication.  SSO to the Grouper UI would be very beneficial

Backend

University of Hawaii (taken from comment below)
Cru (CCCI)

Batch membership update from UI

Be able to easily assign multiple groups to a subject. Right now, there doesn't seem to be a way to manage membership from a subject point of view. Everything is done through the group page. It would be great if there was a may to manage membership from the subject info page. That way, we could easily add a single subject to multiple groups. It would be even better if there was a mechanism like the "Import members" from the Lite UI's group page where you can import a CSV file or imput members directly on screen. That could be used to list the groups in which we want to add a subject.  Also should be easy to remove multiple groups from a subject at once.

UI

U Montreal

Moved to "Guidelines".
 
Hide complexity by default

Hide all of the "internal" attributes (such as ID, ID Path, UUID, etc.).  Only show the user-friendly names, paths, and descriptions.  The details will only become visible through a special setting.  The Lite UI does this now, and I think the entire UI should do this going forward.  I'd recommend that each user have a "profile" where they can set this kind of option globally... so that power users can always see the IDs, etc. but "normal" users will never be bothered by them.

 

Cru (CCCI)

UX participation

User eXperience professional can help with process to ensure good UI usability and workflow.

 

U Chicago

GroupType Attributes

Add functionality for GroupType attributes to have a possible list of items a user can select. This will include showing a default value if one is presumed. There are of course cases in which a value needs to be supplied by the user, but there are many in which the possible answers are known and can be shown to the user for selection even if it is a boolean. To use the mailingList attributes as an example. The alias will need to be provided by the user. The allowAttachments and moderated are true/false questions. There can be a drop drown list to select true/false. A default value of say false can be specified in the metadata. For attributes that are lists of users, the user should be able to click on the attribute or an obvious button next to it to engage the selection process.

UI

UC Berkeley

Input-Gathering Process

We'll aim to conduct the input gathering process as follows:

...