Content update

_episodes/02-generalFactors.md

@@ -12,18 +12,50 @@ keypoints:
 
 Review in broad strokes the factors that may affect how you model your organization, project or collaboration. Explore some real-world examples.
 
-## What are the most common factors for grouping people in your organization
+## How are COs modeled in COmanage?
+
+COmanage is a multi-tenet tool. This means that for each installation, one or more top-level groups can be expressed. These groups are called Collaborative Organizations or COs. Individuals are added to these fundamental groups (COs), but once there, the individuals can be included in multiple sub groups of the CO, called Collaboration Organization Units (or COUs.)
+
+### The COs
+
+ The term “Collaborative Organization” or CO to refer to 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. Some traits of these COs include:
+
+ * These individuals use a common workflow for adding collaborators.
+ * They share common policies for vetting the identities of collaborators.
+ * These COs may include individuals in a single organization, or individuals may be in multiple organizations, geographically different regions, or even work independently.
+
+COs can support one our more Collaborative Organization Units (COUs).
+
+### COUs
+
+"Collaborative Organizations Units" allow you to define an organizational structure within a CO. The reason that you would divide your CO into COUs are because there are differences across your CO that necessitates different policies in one or more of the following:
+
+* How individuals join and/or leave the group
+* There are different rules about how applications get provisioned or deprevisioned
+* The information stored or used about members of the group 
+
+These COUs may be recognized collaborators like departments, divisions, projects; or they may be related to the privileges that those in the group may have, for example, alumni or parents.
+
+If your collaboration–a single entity with common goals–has unique requirements among the different groups and/or departments regarding how participants will join those parts of your collaborations, then, you have a CO that contains COUs. If you have only one common set of policies that define how individuals are added or removed from the CO, then you do not have COU even though you may have groups for simple access control.
+
+
+other ph of your real organization. provide additional flexibility and control for 
+
+## What are the most common factors for modeling the groups of individuals in your organization
 
 There are many ways to group people in your organization. For tools like Membership Management Services, there are several common factors to consider:
 
 1. Where does the data about the person come from - also known as "Systems of Record"
 2. What are the conditions under which individuals gain or loose access to resources or services
 3. Logical groups like departments, projects, or teams
 
-## How does grouping work in COmanage
-
-COmanage is a multi-tenet tool. This means that for each installation, one or more top-level groups can be expressed. These groups are called Collaborative Organizations or COs. Individuals are added to these fundamental groups (COs), but once there, the individuals can be included in multiple sub groups of the CO, called Collaboration Organization Units (or COUs.)
 
 ## Consideration factors
 
-**Will need to do an updated version of the [CO Requirements Assessment tool](https://spaces.at.internet2.edu/display/COmanage/CO+Requirements+Assessment)**
+**RESOURCE**: [COmanage Planning: Modeling your collaborative organization](/files/handouts/COmanage Planning_ Modeling your collaborative organization.pdf)
+
+Collaborations come in all sizes and levels of complexity. From complex virtual organizations that span multiple countries, to informal groups within a collaboration at a single campus, COmanage provides enough flexibility to support most types of collaborations.
+
+Depending on the size and complexity of your virtual organization, you need to consider how people should join the collaboration (e.g., the enrollment process), what applications they might need to accomplish their goals, and how they should be removed or expired at the end of their participation in the VO. The COmanage team has put together the resource above with questions that target several of the possible layers within a collaboration. While not all questions apply, by going through this assessment, you will learn more about your own processes and decide what is important for the platform.
+
+In modeling your collaborative organization, 

_episodes/04-yourModel.md

@@ -10,8 +10,56 @@ keypoints:
 - "List the key takeaways for the episode"
 ---
 
-Working collaboratively with others in the class, choose a model that you think would work for your situation.
+Working collaboratively with others in the class, choose a model that you think would work for your situation, and then implement it in COmanage.
 
-## Episode section
+# PICK YOUR MODEL
 
-... and content
+The steps to do this
+
+Use the [CO Worksheet](/files/handouts/COmanage Planning_ CO_Worksheet.pdf) to plan out your CO. 
+
+Work in pairs to discuss the choices that you made. Make adjustments in your plan as needed.
+
+# Then IMPLEMENT IT...
+
+## Create a CO
+
+![Interactive system activity](../assets/img/hands-on-keyboard.png)
+
+**REQUIRED ROLE**: Platform Administrator
+
+1. Sign into COmanage as a Platform Administrator. Once you sign in you will see a list of available collaborations. 
+2. Since you want to create a new CO, from the menu, select Platform > COs to display the CO Management Overview List.
+
+![Navigate to the CO Management Overview List](../fig/CO301-04_COMgmtList_2019-09-06.png)
+
+3. Click the "Add CO" link above the table on the right side to add a new CO.
+
+![CO management Overview list](../fig/CO301-04_COMgmtOverviewList_2019-09-06.png)
+
+4. Fill in the fields:
+  a. **The name of your CO.** This name will be displayed on lists and elsewhere. It is a good idea for this name to be descriptive, but relatively short.
+  b. **Description.** Write a short description of your CO. This description will be helpful for those who may not be familiar with your CO's name.
+  c. **Status.** There are three choices for the status:
+    * Active - you will select this one. Your CO will be immediately active upon its creation.
+    * Suspended - Useful if you do not want your CO to be active.
+    * Template - Useful if you want to create several COs based on the configuration from this one.
+
+## Configure your CO
+
+![Interactive system activity](../assets/img/hands-on-keyboard.png)
+
+### Settings
+
+The settings section for your CO enables you to configure the CO behavior. While there are several settings, we will only discuss the most common ones today. More details can be found on the [documentation page in the COmanage wiki](https://spaces.at.internet2.edu/display/COmanage/How+to+Configure+a+CO).
+
+**REQUIRED ROLE**: Platform Administrator | Collaboration (CO)Administrator
+
+
+1. From the Collaborations list page, click on the name of the Collaboration that you want to configure.
+2. In the CO menu, click on the "Configuration" link to see the list of customizations that you can make. Click on the first link, "CO Settings" to adjust the settings.
+
+![Navigate to COSettings Configuration > CO Settings](../assets/img/CO301-04_COSettings_2019-09-06.png)
+
+3. Using the values that you put in your [CO Worksheet](/files/handouts/COmanage Planning_ CO_Worksheet.pdf), adjust the settings for your CO.
+4. Click the `SAVE` button to save your work.

_episodes/05-generalCous.md

@@ -14,4 +14,5 @@ Learn about Collaboration Organization Units (COUs), and how they are used to ex
 
 ## Episode section
 
-... and content
+... and content
+

_episodes/08-advanced.md

@@ -16,4 +16,6 @@ During this section we will review advanced topics of interest to the class. Som
 
 ## Episode section
 
-... and content
+... and content
+
+COUs can be hierarchical; COUs can be directly a part of the CO, or can be a sub-part of another COU.

_includes/navbar.html

@@ -46,6 +46,7 @@
         </li>
   {% endif %}
 
+  <!-- remove extras section
   {% comment %} Show extras for lessons or if this is the main workshop-template repo (where they contain documentation). {% endcomment %}
   {% if site.kind == "lesson" %}
         <li class="dropdown">
@@ -57,23 +58,27 @@
             {% endfor %}
           </ul>
         </li>
-  {% endif %}
+  {% endif %} -->
 
   {% comment %} Always show license. {% endcomment %}
         <li><a href="{{ relative_root_path }}{% link LICENSE.md %}">License</a></li>
-  {% if page.source %}
-  {% if page.source == "Rmd" %}
-  <li><a href="{{repo_url}}/edit/{{ default_branch }}/{{page.path|replace: "_episodes", "_episodes_rmd" | replace: ".md", ".Rmd"}}" data-checker-ignore>Improve this page <span class="glyphicon glyphicon-pencil" aria-hidden="true"></span></a></li>
-  {% endif %}
-  {% else %}
-  <li><a href="{{repo_url}}/edit/{{ default_branch}}/{{page.path}}" data-checker-ignore>Improve this page <span class="glyphicon glyphicon-pencil" aria-hidden="true"></span></a></li>
-  {% endif %}
-      </ul>
+
+        <!-- Remove edit suggestion
+        {% if page.source %}
+        {% if page.source == "Rmd" %}
+        <li><a href="{{repo_url}}/edit/{{ default_branch }}/{{page.path|replace: "_episodes", "_episodes_rmd" | replace: ".md", ".Rmd"}}" data-checker-ignore>Improve this page <span class="glyphicon glyphicon-pencil" aria-hidden="true"></span></a></li>
+        {% endif %}
+        {% else %}
+        <li><a href="{{repo_url}}/edit/{{ default_branch}}/{{page.path}}" data-checker-ignore>Improve this page <span class="glyphicon glyphicon-pencil" aria-hidden="true"></span></a></li>
+        {% endif %}
+      </ul> -->
+
+      <!-- Remove site search
       <form class="navbar-form navbar-right" role="search" id="search" onsubmit="google_search(); return false;">
         <div class="form-group">
           <input type="text" id="google-search" placeholder="Search..." aria-label="Google site search">
         </div>
-      </form>
+      </form> -->
     </div>
   </div>
 </nav>

_layouts/base.html

@@ -45,12 +45,14 @@
     <div class="container">
       {% include navbar.html %}
 {{ content }}
+      <!-- Do not include a footer for now
       {% if site.kind == "workshop" %}
       {% include workshop_footer.html %}
       {% else %}
       {% include lesson_footer.html %}
-      {% endif %}
+      {% endif %} -->
     </div>
-    {% include javascript.html %}
+    <!-- Do not include page javascript - used for analytics...
+      {% include javascript.html %} -->
   </body>
 </html>