title | teaching | exercises | questions | objectives | keypoints | workshopOverviewName | workshopOverviewURL | lessonOverviewName | lessonOverviewURL | previousEpisodeName | previousEpisodeURL | nextEpisodeName | nextEpisodeURL | |||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The structure of COmanage |
15 |
0 |
|
|
|
COmanage Workshop: Managing Identities & Collaborations |
CO101 - Workshop Intro & Getting to Know COmanage |
../index.md |
4. COmanage Capabilities |
/_episodes/04-capabilities.md |
5. How is COmanage structured?
People
OBJECT | DESCRIPTION | Introduced in |
---|---|---|
CO Person ⚙️ |
The representation of a person in COmanage | CO310-01 |
CO Group ⚙️ |
A specific COmanage organizational structure for representing certain collections of CO Persons ⚙️ |
CO320-03 |
Identity Source ⚙️ |
Information about a person as obtained from an external source such as LDAP, netFORUM or ORCID | CO310-02 |
Identity Source Records ⚙️ |
COmanage's cached value of the values at the source | CO310-02 |
CO Person Role ⚙️ |
The representation of a person's role in COmanage. This object describe the person's role with certain collections of people within your organization or collaboration. These objects are attached to ⚙️ CO Person objects; there may be any number of Roles. |
C0310-04 |
Organizations/ Collaborations - sub-units
OBJECT | DESCRIPTION | Introduced in |
---|---|---|
CO ⚙️ |
any formal or informal group of individuals that work collaboratively in a digital setting. They have a goal of a shared infrastructure that supports their collaborations so that the traditional limitations of localized applications may be overcome. | CO320-01 |
COU ⚙️ |
an organizational structure within a CO that differs in how individuals join and/or leave the group, how applications get provisioned or deprovisioned, who manages person membership and privileges in the group, or in the information stored or used about members of the group. | CO320-02 |
CO Group ⚙️ |
A specific COmanage organizational structure for representing certain collections of CO Persons ⚙️ |
CO320-03 |
CO Department ⚙️ |
A COmanage object that is used to model organizational departments. They can be used to store a number of attributes about the department, including telephone numbers, email addresses, URLs, identifiers, and the sets of people associated with specific responsibilities within the department. | CO320-04 |
Linking to Systems Outside of COmanage
OBJECT | DESCRIPTION | Introduced in |
---|---|---|
Identifier ⚙️ |
Objects that enable one to connect the information stored about people within the COmanage platform to representations of the same people in systems outside of COmanage | CO330-01 |
CO Service ⚙️ |
Services or applications that can be configured for CO Persons ⚙️ to have access to by participating in the organization or collaboration. |
CO330-02 |
Plugin ⚙️ |
Components that are used to easily customize and extend COmanage Registry functionality. | CO330-03 |
Provisioners ⚙️ |
Special Plugins that enable you to Provision to external systems using information stored within COmanage | CO350 |
PREVIOUS SECTION: 4. COmanage Capabilities
NEXT LESSON: CO201 - Installing COmanage Using Docker Images
LESSON OVERVIEW: CO101 - Workshop Intro & Getting to Know COmanage
WORKSHOP OVERVIEW: COmanage Workshop: Managing Identities & Collaborations