Skip to content
Permalink
6797a3a265
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

COmg-CO320-modelOrg/_episodes/04-departments.md

Go to file
 
 
Cannot retrieve contributors at this time
4. About CO Departments:gear: Wrapping up Organizational model review Combining models - People & Organization Terminology & resources COmanage Objects ⚙️ Worksheets Slides
76 lines (50 sloc) 3.43 KB
Raw Blame
title teaching exercises questions objectives keypoints
The Departments
25
15
Question here
List the objectives
List the key takeaways for the episode

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:gear: 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.

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) | No (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

< TO BE UPDATED >

Terminology & resources

COmanage Objects ⚙️

OBJECT DESCRIPTION
CO Person⚙️ the representation of a person in COmanage
CO Group⚙️ a specific COmanage organizational structure for representing certain collections of CO Persons⚙️

Worksheets

WORKSHEET DESCRIPTION
Modeling Organization 📝 Planning sheet used in this lesson for understanding how the parts of the COmanage Organization fit together.
CO Planning Worksheet 📝 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

LESSON OVERVIEW: CO320 - Modeling Your Organization in COmanage

WORKSHOP OVERVIEW: COmanage Workshop: Managing Identities & Collaborations