Skip to content

Commit

Permalink
Modifying Tidy data activity.Remove ER diagram activity
Browse files Browse the repository at this point in the history
  • Loading branch information
camilavargasp committed Oct 8, 2024
1 parent 64caec0 commit df90f99
Show file tree
Hide file tree
Showing 2 changed files with 30 additions and 32 deletions.
60 changes: 28 additions & 32 deletions materials/sections/intro-tidy-data.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -443,53 +443,49 @@ In the Cleaning & Wrangling chapter we will cover more best practices for cleani

## Activity

In groups of 3-4 we will do two activities that will help us put into practice the concepts of tidy data, identifying keys and structuring relational data.
<!-- In groups of 2-3 we will do two activities that will help us put into practice the concepts of tidy data, identifying keys and structuring relational data. -->

### Exercise 1:Identifying Tidy Data
<!-- ### Exercise 1:Identifying Tidy Data -->

::: callout-note
## Does the table follow the tidy data principles?

- Look at the tables on [this file](files/recognizing-tidy-data-activity.pdf) and determine if they follow the three tidy data principles.
If not, which ones aren't met?

- How would you wrangle the data to make it tidy?
Describe the steps you would take to tidy the data.
::: callout-tip
## Tidy data, keys and joins
- Get together in pairs or small groups
- Obtain materials from instructors including activity handout and blank paper(s).
- Follow instructions in activity handout.

- Sketch how would the tidy version look like.
:::

### Excersice 2: Relational Databases
<!-- ### Excersice 2: Relational Databases -->

::: callout-tip
## Prompt
<!-- ::: callout-tip -->
<!-- ## Prompt -->

> Our funding agency requires that we take surveys of individuals who complete our training courses so that we can report on the demographics of our trainees and how effective they find our courses to be.
:::
<!-- > Our funding agency requires that we take surveys of individuals who complete our training courses so that we can report on the demographics of our trainees and how effective they find our courses to be. -->
<!-- ::: -->

::: callout-note
## Design data collection tables
<!-- ::: callout-note -->
<!-- ## Design data collection tables -->

- In your small groups, design a set of tables that will capture information collected in a participant survey that would apply to many courses.
<!-- - In your small groups, design a set of tables that will capture information collected in a participant survey that would apply to many courses. -->

- Don't focus on designing a comprehensive set of questions for the survey, one or two simple questions would be sufficient (eg: "Did the course meet your expectations?", "What could be improved?", "To what degree did your knowledge increase?").
<!-- - Don't focus on designing a comprehensive set of questions for the survey, one or two simple questions would be sufficient (eg: "Did the course meet your expectations?", "What could be improved?", "To what degree did your knowledge increase?"). -->

- Include variables (columns) with basic set of information from the surveys and about the courses, such as the date of the course and name of the course, etc.
:::
<!-- - Include variables (columns) with basic set of information from the surveys and about the courses, such as the date of the course and name of the course, etc. -->
<!-- ::: -->

::: callout-note
## Create entity relationsip model
<!-- ::: callout-note -->
<!-- ## Create entity relationsip model -->

After you have thought about what kind of information you care collecting, let's break it down and build the entity-relationship model.
<!-- After you have thought about what kind of information you care collecting, let's break it down and build the entity-relationship model. -->

1. Identify the **entities** in the relational database and add each one in a box.
<!-- 1. Identify the **entities** in the relational database and add each one in a box. -->

2. Add **variables** for each entity.
<!-- 2. Add **variables** for each entity. -->

3. Identify the primary and foreign **keys** for those entities that relate to each other.
<!-- 3. Identify the primary and foreign **keys** for those entities that relate to each other. -->

4. Add "words" describing how each entity relates
<!-- 4. Add "words" describing how each entity relates -->

5. Add cardinality to every relationship in the diagram.
This mean, use the **EDR Crow's Foot** [Quick Reference](https://learning.nceas.ucsb.edu/2024-02-arctic/session_07.html#edr-crows-foot) to quantify how many items in an entity are related to another entity.
:::
<!-- 5. Add cardinality to every relationship in the diagram. -->
<!-- This mean, use the **EDR Crow's Foot** [Quick Reference](https://learning.nceas.ucsb.edu/2024-02-arctic/session_07.html#edr-crows-foot) to quantify how many items in an entity are related to another entity. -->
<!-- ::: -->
2 changes: 2 additions & 0 deletions materials/session_08.qmd
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,8 @@ title-block-banner: true
---




{{< include /sections/intro-tidy-data.qmd >}}

<!-- {{< include /sections/r-practice-tidy-data-joins.qmd >}} -->
Expand Down

0 comments on commit df90f99

Please sign in to comment.