Skip to Content.
Sympa Menu

comanage-dev - Re: [comanage-dev] Multiple source institution use case?

Subject: COmanage Developers List

List archive

Re: [comanage-dev] Multiple source institution use case?


Chronological Thread 
  • From: heather flanagan <>
  • To: CoMaNaGe-DeV List <>
  • Subject: Re: [comanage-dev] Multiple source institution use case?
  • Date: Tue, 12 Oct 2010 17:10:44 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=YhGtW7Wya3Z4nhUk+H+RjXvPYe6/B7VSweWhhILhJbOnZdpplqTj7FXZozXkBACzxa VMk1VYBu+OoxJq9vcZAvbcEZmCBDyR6YdLpjIcIkRQSKsGRNmpppfzJ5w1rcJ/BlBUWt F+CHL2y//xTsP3oILSuwCJmjPrNLdnnWbAM2w=



On 10/12/2010 09:40 PM, Benn Oshrin wrote:
> The scenario of a person being affiliated with a source institution in
> order to have membership in a VO is well described.
>
> We've also discussed a person switching affiliation but wanting to
> maintain VO membership.  (eg: They were affiliated with Brown
> University, but are now affiliated with Blue University.)
>
> What about someone being multiply affiliated?  For example, they are
> part time faculty at Brown University and part time faculty at Blue
> University.  Does the VO need to know both of these affiliations, or
> is one sufficient?  If the former, why?
>
> -Benn-


Oh, nice scenario!  I think it's worth giving a quick shout out to our major VO to ask them if this is something that ever hits their radar.  It seems like very plausible scenario, but we may end up putting it aside for the moment.  Want me to add this to our Friday agenda?

-hf



Archive powered by MHonArc 2.6.16.

Top of Page