Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
139 lines (96 sloc) 10.1 KB
title teaching exercises questions objectives keypoints workshopOverviewName workshopOverviewURL lessonOverviewName lessonOverviewURL previousEpisodeName previousEpisodeURL nextEpisodeName nextEpisodeURL
The Departments
25
15
Question here
List the objectives
List the key takeaways for the episode
COmanage Workshop: Managing Identities & Collaborations
CO320 - Modeling Your Organization in COmanage
../index.md
3. About Groups
/_episodes/03-groups.md

4. About CO Departments⚙️

CO Departments⚙️ are primary objects within COmanage, which means that they are intended to store representations of external objects (just like CO People⚙️). They can attach to either a CO⚙️ or a COU⚙️, and 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. CO Departments⚙️ can be used to support various use cases:

  • In a VO (Virtual Organization) deployment, CO Departments⚙️ can be used to represent research groups.
  • In an enterprise deployment, CO Departments⚙️ can be used to represent the University department hierarchy.

While there may typically be a one-to-one relationship between CO Departments and COUs, it is not strictly necessary. For example, a COU may be made up of members spanning two departments.

CO Departments⚙️ are visible to anyone within the CO⚙️, by logging into COmanage, though only CO Administrators👑 may edit their information.

Hands on - Create a CO Department⚙️

Interactive system activity

As with the other organizational units, there is a worksheet for modeling your departments, CO Department Planning Worksheet. Once you have explored the worksheet, we will implement a few departments within one of the COUs that you created

REQUIRED ROLE: CMP Administrator👑 OR CO Administrator👑

Sign into COmanage

  1. Using the credentials you specified as the CO Administrator👑, sign into the system.

  2. Navigate to your CO⚙️. If necessary, select your CO⚙️ by selecting Collaborations from the menu on the left, and then selecting your Collaboration.

Create a CO Department⚙️

  1. In the menu on the left, click on the Departments link to display the current list of CO Departments⚙️.

  2. Click the Add Department link above the table to create a new group. Fill in the form using the values that you included in the metadata section of your worksheet, and click the ADD button to add the CO Department⚙️. (NOTE: if you are specifying Leadership, Administrative or Support Groups, you will need to add them first.)

  3. Repeat this process for any other CO Groups⚙️ that you created worksheets for. Make at least one of these groups an Open group that anyone can join.

Add details to the CO Department⚙️

  1. From the list of CO Departments⚙️, prepare to edit one of the departments that you just created by clicking on the Edit button in the Actions column on the right. Here you can add information specific to the department to make it available to anyone within the CO⚙️. The list of things that can be included are

    • Identifiers
    • Email Addresses - for example, a general department email address
    • URLs - for example, the official website for the department
    • Telephone numbers - for example, the general number for the department
    • Addresses - physical addresses for the department

    Once you have made changed, click the SAVE button to save your changes.


Wrapping up

Organizational model review

You have learned about the structural elements that are used to model organizations within COmanage.

Comparison Summary

. CO⚙️ COU⚙️ CO Department⚙️ CO Group⚙️
Belongs To COmanage Platform CO CO; COU CO; COU (for automatic groups only)
Has Many COU; CO Group CO Person Roles; CO Departments CO People (via CoGroupMember); CO Email List
Hierarchical No Yes No No
Object Type Structural Object Structural Object Primary Registry Object Primary Registry Object
Supported Attributes None None Addresses; Email Addresses; Identifiers; Telephone Numbers; URLs; Leadership Group; Administrative Group; Support Group Open / Closed; Managers (via CoGroupMember); Email Addresses (via CoEmailList); Identifiers

Combining models - People & Organization

The following diagram summarizes the structures that we learned about during the last two lessons:

Model Diagram - People model and Organization model


Terminology & resources

COmanage Objects ⚙️

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 (this section)
. ****** CO310 - Modeling People in COmanage ****** .
CO Person The representation of a person in COmanage CO310-01
Organizational Identity Source Information about a person as obtained from an external source such as LDAP, netFORUM or ORCID CO310-02
Organizational 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

CO Person Roles 👑

ROLE DESCRIPTION Introduced in
CMP Administrators CMP Administrators are effectively super users, with the ability to perform almost all operations on the platform. CO320-01
CO Administrators CO⚙️ Administrators are super users within a CO. These individuals belong to the CO:admins group of the CO⚙️. CO320-01
System Administrators System Administrators have privileges that enable them to maintain the COmanage application. CO320-01
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⚙️. CO320-02

Worksheets 📝

WORKSHEET DESCRIPTION Introduced in
Modeling Organization Planning sheet used in this lesson for understanding how the parts of the COmanage Organization fit together CO320 (this lesson)
CO Planning Worksheet Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance CO320-01
COU Planning Worksheet Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance. CO320-02
CO Group Planning Worksheet Planning worksheet for creating your CO Group(s). Contains all of the configuration sections at a glance. CO320-03
CO Department Planning Worksheet Planning worksheet for creating your CO Group(s). Contains all of the configuration sections at a glance. CO320-04 (this section)
. ****** CO310 - Modeling People in COmanage ****** .
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 CO310

PREVIOUS SECTION: 3. About CO Groups


LESSON OVERVIEW: CO320 - Modeling Your Organization in COmanage

NEXT LESSON: CO330 - Linking to Systems Outside of COmanage

WORKSHOP OVERVIEW: COmanage Workshop: Managing Identities & Collaborations

You can’t perform that action at this time.