Skip to Content.
Sympa Menu

comanage-dev - Re: [comanage-dev] Changing COs (CO-767 & CO-416)

Subject: COmanage Developers List

List archive

Re: [comanage-dev] Changing COs (CO-767 & CO-416)


Chronological Thread 
  • From: Scott Koranda <>
  • To: Arlen Johnson <>
  • Cc: comanage-dev <>
  • Subject: Re: [comanage-dev] Changing COs (CO-767 & CO-416)
  • Date: Sat, 22 Feb 2014 12:44:59 -0600

Hi,

On Fri, Feb 21, 2014 at 11:24 AM, Arlen Johnson
<>
wrote:
>> On 2/19/2014 6:41 PM, Benn Oshrin wrote:
>>
>>> 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?).
>
>
>
> If users could select their "default" CO, it might make this simpler.

For the LIGO use cases this could work well.

The large fraction of users will either be in one CO or will have a reasonable
default. Only a few (2?) would need to actively switch between COs/COUs
on a regular basis.

Thanks,

Scott

> If
> they are in only one CO, that's their default. If in multiple, they choose
> which will first appear when they log in. Perhaps "None - let me choose" is
> an option as well, which would end up presenting them with the global
> dashboard rather than the CO-specific dashboard.
>
> In either case, what I present for menuing is based on the CO in use
> (current or default). (And if "none - let me choose", they must first
> select their CO to use the menus...this option might only be of value to a
> platform admin.)
>
> On the other hand, you'd noted that you expect direct linking into the COs
> ...is that the common use case?



Archive powered by MHonArc 2.6.16.

Top of Page