comanage-dev - Re: [comanage-dev] Action Items: COmanage-dev call 10-Dec-2010
Subject: COmanage Developers List
List archive
- From: heather flanagan <>
- To: CoMaNaGe-DeV List <>
- Subject: Re: [comanage-dev] Action Items: COmanage-dev call 10-Dec-2010
- Date: Mon, 13 Dec 2010 07:23:20 -0800
- 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=t7DNFbE+lwskceV+A1tO7P7zb9PAAjRHWokLpTWfeaLAEtMljCZWADBy3DNFTGnuxN +o8CivWRcb+VXmnxW3Rj9XbLLxU7IhZYU7PNFZnsd4ooF1bvv/YOvpz2bADh9vpbuBEm v/DUng7Itfuu7tAqBrzA+3dAqDINgsYgMz9Hc=
Hi all -
[AI] (Heather) will add questions about role transition to the assessment document.
I've created a new section within the assessment doc, moved a few questions in to it and added a few more. I'll continue to adjust this as I think of more or get feedback (hint, hint).
|| Users, guests, and contributors | _For Collaboration Coordinator/Site Administrators_ ||
| Who decides what services are given to whom, and when are those services provisioned/de-provisioned? | |
| What roles do people play within your CO? How consistent are the roles (e.g. researcher, administrator, assistant) across the CO, or do roles often blend? | |
| Who needs to be able to add people? Who is responsible for disambiguation within the registry? | |
| For each of the different types of people joining your VO, what is the invitation model? How are they added/invited/enrolled? | |
| How do you handle changes in affiliation (i.e. a postdoc at institution A becomes a faculty member at institution B, but expects to remain involved in the VO) | |
| What are your reporting requirements around the users in the VO? (i.e. real-time or batch reports for new users, FTE effort towards research for the VO) | |
-hf
- [comanage-dev] Action Items: COmanage-dev call 10-Dec-2010, Emily Eisbruch, 12/13/2010
- Re: [comanage-dev] Action Items: COmanage-dev call 10-Dec-2010, heather flanagan, 12/13/2010
Archive powered by MHonArc 2.6.16.