Terminology and Reference
COmanage Objects and Terms
CO310 - Modeling People in COmanage
OBJECT | DESCRIPTION |
---|---|
CO Person |
The representation of a person in COmanage. |
Identity Source |
Information about a person as obtained from an external source such as LDAP, netFORUM or ORCID. |
Identity Source Records |
COmanage’s cached value of the values at the source. |
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. |
CO320 - Modeling Your Organization in COmanage
OBJECT | DESCRIPTION |
---|---|
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 |
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. |
CO Group |
A specific COmanage organizational structure for representing certain collections of CO Persons . |
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. |
CO330 - Linking to Systems Outside of COmanage
OBJECT | DESCRIPTION |
---|---|
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. |
CO Service |
Services or applications that can be configured for CO Persons to have access to by participating in the organization or collaboration. |
CO340 - Enrollment Workflows
TERM/ OJBECT | DESCRIPTION |
---|---|
Enrollment |
the process of bringing new CO Person records into COmanage. |
Petition |
the record of enrollment – it holds copies of the attributes that were provided at enrollment, even if the values are subsequently changed. History records are also maintained for the Petition, indicating such events as who approved it and when. |
Identity Matching |
During enrollment, it is possible that the person being enrolled is already in COmanage. Identity Matching is a process for identifying and linking the objects representing the person to avoid duplication an/or errors. |
Email Confirmation |
As part of the Enrollment Workflow the person being enrolled may need to confirm their email address by interacting with an email sent to that address. |
Account Linking |
refers to the management of links between existing Org Identities and CO Person records. Linking can happen automatically as part of an enrollment process. However, a CO Administrator can also manually adjust these links, usually to resolve enrollment issues. |
Petitioner |
Part of the Workflow Cast. The Petitioner executes the Enrollment Workflow, creating a Petition. The Petitioner could be a CO Administrator or COU Administrator, an existing CO Person associated with the CO, or a non-member with no existing affiliation to the CO. |
Enrollee |
Part of the Workflow Cast. The Enrollee is the subject of the Petition and will enrolled as a result of a successful Enrollment Workflow. Currently, an Enrollee only interacts with an Enrollment Workflow if the Flow requires the Enrollee to confirm their email address. |
Approver |
Part of the Workflow Cast. The Approver is one or more people who optionally reviews and approves (or denies) the Petition. If an Enrollment Workflow requires approval, the set of Approvers is determined by the approvers group of the Flow. |
CO350 - Provisioning
OBJECT | DESCRIPTION |
---|---|
Plugin |
Components that are used to easily customize and extend COmanage Registry functionality. |
Provisioners |
Special Plugins that enable you to Provision to external systems using information stored within COmanage. |
CO Person Roles
CO320 - Modeling Your Organization in COmanage
ROLE | DESCRIPTION |
---|---|
CMP Administrators |
CMP Administrators are effectively super users, with the ability to perform almost all operations on the platform. |
CO Administrators |
CO Administrators are super users within a CO. These individuals belong to the CO:admins group of the CO . |
System Administrators |
System Administrators have privileges that enable them to maintain the COmanage application. |
COU Administrators |
Individuals that have the ability to perform lifecycle management operations on the CO People who have CO Person Roles associated with the COU . |
Worksheets & Resources
CO201 - Installing COmanage Using Docker Images
WORKSHEET | DESCRIPTION |
---|---|
Workshop Reference | Reference sheet for the workshop. Use this worksheet to record your Virtual Machine number, the persona you will be using for the workshop. |
CO310 - Modeling People in COmanage
WORKSHEET | DESCRIPTION |
---|---|
Modeling People | Planning sheet used in this lesson for understanding how to model people in COmanage. This sheet is used to organize how specific people and their relationships would be expressed within COmanage |
CO320 - Modeling Your Organization in COmanage
WORKSHEET | DESCRIPTION |
---|---|
Modeling Organization | Guidelines for modeling your organization in COmanage |
CO Planning Worksheet | Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance |
COU Planning Worksheet | Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance |
CO Group Planning Worksheet | Planning worksheet for creating your CO Group(s). Contains all of the configuration sections at a glance |
CO Department Planning Worksheet | Planning worksheet for creating your CO Department(s). Contains all of the configuration sections at a glance |