addingslided in pdf to non-technical lessons

materials/sections/collaboration-social-data-policies.qmd

@@ -1,9 +1,40 @@
 
 ## Developing a Code of Conduct
 
+:::callout-note
+Find the presentation slides for this lesson [here](files/social-aspects-of-collaboration-slides.pdf)
+:::
+
+
 Whether you are joining a lab group or establishing a new collaboration, articulating a set of shared agreements about how people in the group will treat each other will help create the conditions for successful collaboration. If agreements or a code of conduct do not yet exist, invite a conversation among all members to create them. Co-creation of a code of conduct will foster collaboration and engagement as a process in and of itself, and is important to ensure all voices heard such that your code of conduct represents the perspectives of your community. If a code of conduct already exists, and your community will be a long-acting collaboration, you might consider revising the code of conduct. Having your group 'sign off' on the code of conduct, whether revised or not, supports adoption of the principles.
 
-When creating a code of conduct, consider both the behaviors you want to encourage and those that will not be tolerated. For example, the [Openscapes code of conduct](https://openscapes.org/code-of-conduct) includes Be respectful, honest, inclusive, accommodating, appreciative, and open to learning from everyone else. Do not attack, demean, disrupt, harass, or threaten others or encourage such behavior. 
+
+::: {.callout-caution icon="false"}
+## When developing a code of conduct, keep in mind:
+
+- Invite a conversation among all members to create grounding guidelines
+- Co-creation of a code of conduct will foster collaboration and engagement as a process in it self.
+- It is important to ensure all voices are heard
+- Things to consider
+    - Behaviors you want to encourage
+    - Behaviors that will not be tolerated
+
+:::
+
+For example, the [Openscapes code of conduct](https://openscapes.org/code-of-conduct) includes 
+
+- Be respectful
+- Be direct but professional
+- Be inclusive
+- Understand different perspectives
+- Appreciate and Accommodate Our Similarities and Differences
+- Lead by Example
+
+
+> **Understand Different Perspectives** <br>
+Our goal should not be to “win” every disagreement or argument. A more productive goal is to be open to ideas that make our own ideas better. Strive to be an example for inclusive thinking. “Winning” is when different perspectives make our work richer and stronger. ([openscapes.org](https://openscapes.org/code-of-conduct))
+
+
 
 Below are other example codes of conduct:
 
@@ -12,7 +43,7 @@ Below are other example codes of conduct:
 - [Arctic Data Center Code of Conduct](https://docs.google.com/document/d/1-eVjnwyLBAfg_f4DRIUVWnLeekgrzrz9wgbhnpOmuVE/edit)
 - [Mozilla Community Participation Guidelines](https://www.mozilla.org/en-US/about/governance/policies/participation/)
 - [Ecological Society of America Code of Conduct](https://www.esa.org/esa/code-of-conduct-for-esa-events/)
-- [Openscapes code of conduct](https://openscapes.org/code-of-conduct)
+
 
 
 ## Authorship and Credit Policies

materials/sections/collaboration-thinking-preferences.qmd

@@ -16,6 +16,10 @@ Step 1:
 
 ## About the Whole Brain Thinking System
 
+:::callout-note
+Find the presentation slides for this lesson [here](files/thinking-preferences.pdf)
+:::
+
 Everyone thinks differently. The way individuals think guides the way they work, and the way groups of individuals think guides how teams work. Understanding thinking preferences facilitates effective collaboration and team work.
 
 The Whole Brain Model, developed by Ned Herrmann, builds upon early conceptualizations of brain functioning. For example, the left and right hemispheres were thought to be associated with different types of information processing while our neocortex and limbic system would regulate different functions and behaviours.

materials/sections/geospatial-vector-analysis.qmd

@@ -412,12 +412,21 @@ ggmap_bbox_to_3857 <- function(map) {
 
 Next, we define the bounding box of interest, and use `get_stamenmap()` to get the basemap. Then we run our function defined above on the result of the `get_stamenmap()` call.
 
+```{r}
+#| echo: false
+
+register_stadiamaps("2d1ca8de-6538-4e1b-920f-05e96ecd95e6", write = TRUE)
+
+```
+
+
+
 ```{r}
 #| message: false
 #| warning: false
 
 bbox <- c(-170, 52,-130, 64) # this is roughly southern Alaska
-ak_map <- get_stamenmap(bbox, zoom = 4) # get base map
+ak_map <- get_stadiamap(bbox, zoom = 4) # get base map
 ak_map_3857 <- ggmap_bbox_to_3857(ak_map) # fix the bbox to be in EPSG:3857
 ```
 

materials/session_06.qmd

@@ -4,5 +4,6 @@ title-block-banner: true
 ---
 
 
+
 {{< include /sections/collaboration-social-data-policies.qmd >}}
 

materials/session_07.qmd

@@ -4,5 +4,6 @@ title-block-banner: true
 ---
 
 
+
 {{< include /sections/collaboration-thinking-preferences.qmd >}}
 

materials/session_10.qmd

@@ -4,5 +4,4 @@ title-block-banner: true
 ---
 
 
-
 {{< include /sections/geospatial-vector-analysis.qmd >}}