04-departments.md

---
title: "The Departments"
teaching: 25
exercises: 15
questions:
- "Question here"
objectives:
- "List the objectives"
keypoints:
- "List the key takeaways for the episode"
---

# 4. About `CO Departments`:gear:

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

* In a VO (Virtual Organization) deployment, `CO Departments`:gear: can be used to represent research groups.
* In an enterprise deployment, `CO Departments`:gear: 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`:gear: are visible to anyone within the `CO`:gear:, by logging into COmanage, though only `CO Administrators`:crown: may edit their information.

# Wrapping up

## Organizational model review

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

**Comparison Summary**

.  | COU | CO Department | CO Group
---|-----|---------------|---------
**Belongs To** | CO | CO; COU | CO; COU (for automatic groups only)
**Has Many** | CO Person Roles; CO Departments | |CO People (via CoGroupMember); CO Email List
**Hierarchical** | Yes | No ([CO-1523](https://bugs.internet2.edu/jira/browse/CO-1523)) | No ([CO-721](https://bugs.internet2.edu/jira/browse/CO-721))
**Object Type** | Structural Object | Primary Registry Object | Primary Registry Object
**Supported Attributes** | 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](/fig/ModelingPersonOrgRelationships.png) 

---

< TO BE UPDATED >

# Terminology & resources

## COmanage Objects :gear:

OBJECT | DESCRIPTION
------ | -----------
`CO Person`:gear: | the representation of a person in COmanage
`CO Group`:gear: | a specific COmanage organizational structure for representing certain collections of `CO Persons`:gear:

## Worksheets

WORKSHEET | DESCRIPTION
--------- | -----------
[Modeling Organization :memo:](/files/handouts/CO310-ModelingOrgs.pdf) | Planning sheet used in this lesson for understanding how the parts of the COmanage Organization fit together.
[CO Planning Worksheet :memo:](/files/handouts/CO320-01_COPlanningWorksheet.pdf) | Planning worksheet for creating your CO(s). Contains all of the configuration sections at a glance.

## Slides

To be included

---

NEXT SECTION: [2. The COU](/_episodes/02-cous.md)

LESSON OVERVIEW: [CO320 - Modeling Your Organization in COmanage](../index.md)

WORKSHOP OVERVIEW: [COmanage Workshop: Managing Identities & Collaborations](https://github.internet2.edu/lpaglione/COmg-trainingOverview/blob/master/README.md)