I originally included both folders and groups in the explore tree, but then updated it to display just folders, with a separate section for navigating just groups (My Groups). My thinking was that including groups and folders together make the tree unwieldy,
kind of like the Windows Explorer tree but with all the files as well as folders. But perhaps the number of groups per folder is not so large that this would necessarily be an issue. Our user tests should help point us in the right direction here.
On Dec 17, 2012, at 1:33 PM, Chris Hyzer wrote:
I think that is me (tech contact J )
I think the folders and groups should be in the explore tree with filters at the top for object type perhaps, or service, privileges, etc
We should go over each screen and idea on wed so we can discuss it all J
From: [mailto:] On
Behalf OfMichael Girgis
Sent: Monday, December 17, 2012 2:04 PM
To: Tom Barton
Cc: <>; Brenda Janish
Subject: Re: [grouper-dev] Lo-fi wireframes
Thanks for your feedback, Tom. I realize it's kind of tough to evaluate these wireframes over email without having some more explanation and context, so I'm counting on this week's call to talk through them a little more. I'd also like to ask for a volunteer
to be my go-to person for any specific technical questions I have as I develop the wireframes in more detail. I expect it might be a commitment of about an hour per week through the end of January. If anyone is up for it, please let me know.
To answer your questions:
1) Yes, that is an admittedly crude representation of a multi-step, wizard-like UI for adding people.
2) Your suggested change to the Assign Privileges step makes sense.
3) The N/A memberships are those people who have privileges for a group but are not members. For example, an ADMIN who is not a member. I'd definitely like to talk through this more with the group on Wednesday to ensure it's a sensible approach.
4) You mentioned adding a dropdown above the member list with possible actions. I have an "Update" dropdown which attempts to serve that purpose…might be better to talk through this on Wednesday.
5) Filter vs. search - Filter lets you show just *indirect* or *direct* members, for example, while the search lets you search for a specific string. So if you wanted to, you could filter for just direct members and browse that list (using the Filter), search
directly for a user named jsmith (using the Search), or first filter for direct members and then search that subset for jsmith.
6) Regarding the right column - there might be some redundancy in the right column with tasks that can be initiated in the middle column, but I believe that if all tasks were included in the dropdown, it could simply become too cluttered, so this is one way
to displace the clutter that most users won't regularly access. Of course, what's ultimately included in the dropdowns is up for debate. Furthermore, there will be some tasks which are possibly *dangerous* enough that you don't want them to be placed directly
next to more commonly used tasks. "Delete all members" is one example - I would suggest this is better relegated to a sidebar rather than a more regularly-accessed dropdown.
7) Your feedback regarding the Grouper-All subject makes sense.
On Dec 17, 2012, at 12:13 PM, Tom Barton wrote:
It would be great if you could give Michael & Brenda some feedback on the direction they are proposing for the new UI. Even a "looks good to me" is very helpful, and of course more specific questions or feedback is great too. Recall that we are trying to address
basic-to-intermediate users and tasks, leaving advanced tasks as-is in the current "admin UI", at least for grouper v2.2.
Michael & Brenda,
I have a couple of questions. On the Add People screen, is that a depiction of a "wizard-like" work flow, ie, the UI first presents *only* the "Find people" panel, and when Next is clicked the "Assign privileges" panel comes up, etc?
On the "Assign privileges" panel, I wondered whether we should have membership and privilege check boxes together. Membership only is the objective far more often than privilege assignment. I see that's at the top of the panel, but it seems less prominent than
the priv check boxes. I wonder if it should look more like this (please forgive crude attempt!):
[ 1 ] Find people > [ 2 ] Assign privileges
> [ 3 ] Review
[ ] Add Daniel Smith as a member
Privileges for this group
[ ] Admin [ ] Update
[ ] Read [ ] View
[ ] Opt-in [ ] Opt-out
That makes membership and priv assignment equally prominent. Might even have the Privileges stuff hidden by a +/- to expand collapse, with default collapsed. I suggest not having the group name in the membership check box text - they can be long, and it's in
the header area above, in large type I think. I also wondered about this organization of the privs themselves, grouping related ones together.
On the View a Group screen, what's the meaning of the N/A memberships? Also, I wonder if the "Show [drop down] entries" widget should move too the bottom, somewhere left of the paging controls. That would leave space at the top of the list for a heading element
above the check boxes of "Select" and to its right a [drop down] of the actions that are possible. I suppose those things like are delete, change membership start/end dates, import/export member list, view membership paths (if that even belongs in a basic/intermediate
interface). Finally, what's the difference between the Filter and the Search?
Is the right-hand column, for advanced tasks, a little redundant? I guess my question boils down to whether that task/action drop down in the header of the middle column covers everything that would go in the right column. Or are you really thinking that the
layou needs a right column for a future phase, ie, when the new UI begins to take on some of the advanced tasks that we'll leave only in the admin UI for v2.2?
Finally, there's a build-in Subject called Grouper-All which can be used to indicate "all current subjects, whatever those are". It is most often used to indicate that everyone should be able to View or Read a given group, without needing to list "everyone".
When Grouper-All is given a privilege like that, I wonder whether the Privileges for a given subject like Daniel Smith should show checked boxes for Read and View, but grey-out or otherwise indicating that they can't be unchecked just for Daniel.
On 12/13/2012 10:14 AM, Michael Girgis wrote:
Below, you'll find a link to a first pass at lo-fidelity wireframes for the Grouper 2.2 UI. A few notes before you take a look:
* These wireframes are only intended to convey the general direction I'm taking with the UI design and are clearly not fully spec'd or developed.
* Only a few key screens are represented here, related to the most common tasks of viewing/editing folders, groups and users.
* The first two pages simply describe the various page components in the three-column layout.
These wireframes will be used to validate that users can do the most basic tasks of navigating the site and finding and editing entities. So I'm mainly interested in higher-level feedback regarding the overall approach/layout, and less so the more granular
functionality which may not yet be fully developed. Please feel free to email me directly with feedback.
If you have a lot of feedback you'd like to share and you don't mind creating an account on yet another website, let me know and I'll create an account for you oncageapp.com
where you'll be able to add notes directly to the screenshots.
Thanks in advance for your feedback!