COmanage Developers List

[Benn Oshrin <>]

On 2/17/14 7:01 PM, Arlen Johnson wrote:
> The opportunity for a user to change COs explicitly, secondarily
> exposing the CO menus for that context is a departure from the current
> UI.  Entering into the context of a CO for management simplifies the UI
> and menus conceptually.
>
> Assuming we're all on board with this change (and I gather from our
> conversations that we are, but correct me if I'm wrong), the question
> arises: where do we allow a user to select the CO on which to work?  One
> possibility is shown in the screenshot below - allowing the user to
> change CO right next to the CO title itself.

On the one hand, I like it next to the CO title (seems intuitive), on 
the other hand it seems like visual clutter. My only alternative would 
be to put it in the black menu, but then we have the CO title there twice.

> Independent of where the selection is made, a couple of UI points arise
> from this:
>
>   * If a user exists in a single CO, they should just see that CO's
>     title, menu items, and no "change" menu.
>   * If a user exists in multiple COs, we can default them into one (e.g.
>     the first) or make them select one.  If we make them select a CO,
>     the "change" menu might read "select your collaborative
>     organization"   until they've done so.

Currently, there is no "entry point" into a CO, only the CMP 
(/registry). I think we need to allow something like /registry/co:2 to 
be a valid entry point (CO specific dashboard?).

We had the "select your CO" very early on. It was awful and led to a 
bunch of bad decisions (on our part). Maybe we can do better this time.

> If you have concerns with this approach, let me know.  Otherwise, I'll
> forge ahead.
>
> Note: no changes are being suggested for the existing "my account" menu
> which follows the model of "activity" --> "CO_1 ", "CO_2 ", ..."CO_n ".
> For an individual user, this seems a reasonable way to quickly manage
> their own account information.

Maybe, but it's also an extra hop when there's only one CO. Perhaps we 
can discuss some more.

Thanks,

-Benn-