|
Planning for a Standalone platform |
Expecting to be Embedded in a Portal |
---|---|---|
Single CO |
Probably a command-line oriented CO with an equal focus on person identity and tool availability |
Probably a CO with a more app-focused collaboration |
Multiple CO within the CMP |
Probably a CO that is acting more as a service provider to various groups than one focused on a single collaboration effort, where absolute control over branding is important |
Probably a CO that is acting as a service provider to a variety of collaborations that cannot share resources fully, but where the apps and services are still the focus of the collaboration |
Role |
Examples |
Create accounts |
Delete accounts |
Run partner tools (TeraGrid) |
Run local tools |
Access Community Data |
Add/Delete Community Data |
Add/Delete Groups |
Use Collaboration Tools (chat) |
Add/Delete User data |
Allocate Resources |
Request Resources |
Create CO Organization spaces |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Constrained user |
psuedo-anonymous, temporary, guest, possibly student, conference/tutorial specific accounts |
|
|
|
|
|
|
|
|
|
|
|
|
iPlant user |
identifiable user |
|
|
|
|
|
|
|
|
|
|
|
|
Steward |
community data steward, local tool owner |
|
|
|
|
|
|
|
|
|
|
|
|
Administrator |
Faculty, TA, Admin Asst. |
|
|
|
|
|
|
|
|
|
|
|
|
Developer |
tool developers/tool users (in Atmosphere), image creators |
|
|
|
|
|
|
|
|
|
|
|
|
Organization |
creating a CO, allocating resources to the CO |
|
|
|
|
|
|
|
|
|
|
|
|
Legend |
|
---|---|
|
not allowed |
|
allowed |
|
allowed but with limited scope |