Skip to content
Closed
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 14 additions & 1 deletion 02_activities/assignments/DC_Cohort/Assignment1.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,8 +106,16 @@ Please do not pick the exact same tables that I have already diagrammed. For exa
- <img src="./images/01_farmers_market_conceptual_model.png" width="600">
- The column names can be found in a few spots (DB Schema window in the bottom right, the Database Structure tab in the main window by expanding each table entry, at the top of the Browse Data tab in the main window)

**Logical data model**:
- Table names: customer, customer_purchases.
- Relationship type: One-to-many.

<img src="./images/LDModel.png" width="600">

***



## Section 2:
You can start this section following *session 2*.

Expand Down Expand Up @@ -209,5 +217,10 @@ Consider, for example, concepts of fariness, inequality, social structures, marg


```
Your thoughts...
One example of how value systems are embedded in databases can be represented through healthcare and clinical research data which I encounter daily. In clinical research, databases are often designed around predefined categories such as sex, gender, race, ethnicity, and psychiatric diagnoses. Although these categories are important for standardizing data collection and facilitating analysis, they also reflect assumptions about how individuals should be classified. For example, restricting gender to binary categories can exclude individuals who do not identify within those categories.

Another important consideration is whose data is represented in the first place. Clinical research often involves eligibility criteria and recruitment procedures that may unintentionally exclude certain populations, such as individuals who face language barriers, have limited access to transportation, or cannot accommodate research visits during regular working hours. As a result, the data collected may not adequately represent the broader population, potentially limiting the generalizability of research findings. Standardization in data collection and database design does not necessarily equate fairness. For example, requiring every research participant to complete the same English-language questionnaires may appear standardized and fair. However, it can systematically underrepresent people in the population of interest who are not fluent in English.

Similar to the examples discussed in the article, these issues demonstrate that databases are not entirely neutral. Decisions about which information to collect, how to categorize individuals, and whose data to include reflect institutional priorities and social assumptions. Even when these decisions are made for practical or scientific reasons, they can reinforce existing inequalities if their broader implications are not taken into consideration.

```
116 changes: 99 additions & 17 deletions 02_activities/assignments/DC_Cohort/assignment1.sql
Original file line number Diff line number Diff line change
Expand Up @@ -7,8 +7,8 @@
/* 1. Write a query that returns everything in the customer table. */
--QUERY 1



SELECT *
FROM customer;

--END QUERY

Expand All @@ -17,8 +17,10 @@
sorted by customer_last_name, then customer_first_ name. */
--QUERY 2



SELECT *
FROM customer
ORDER BY customer_last_name, customer_first_name
LIMIT 10;

--END QUERY

Expand All @@ -28,8 +30,10 @@ sorted by customer_last_name, then customer_first_ name. */
Limit to 25 rows of output. */
--QUERY 3



SELECT *
FROM customer_purchases
WHERE product_id IN (4, 9)
LIMIT 25;

--END QUERY

Expand All @@ -43,8 +47,11 @@ Limit to 25 rows of output.
*/
--QUERY 4



SELECT *,
quantity * cost_per_quantity AS price
FROM customer_purchases
WHERE customer_id BETWEEN 8 AND 10
LIMIT 25;

--END QUERY

Expand All @@ -56,7 +63,14 @@ columns and add a column called prod_qty_type_condensed that displays the word
if the product_qty_type is “unit,” and otherwise displays the word “bulk.” */
--QUERY 5


SELECT
product_id,
product_name,
CASE
WHEN product_qty_type = 'unit' THEN 'unit'
ELSE 'bulk'
END AS prod_qty_type_condensed
FROM product;


--END QUERY
Expand All @@ -67,7 +81,18 @@ add a column to the previous query called pepper_flag that outputs a 1 if the pr
contains the word “pepper” (regardless of capitalization), and otherwise outputs 0. */
--QUERY 6


SELECT
product_id,
product_name,
CASE
WHEN product_qty_type = 'unit' THEN 'unit'
ELSE 'bulk'
END AS prod_qty_type_condensed,
CASE
WHEN product_name LIKE '%pepper%' THEN 1
ELSE 0
END AS pepper_flag
FROM product;


--END QUERY
Expand All @@ -79,8 +104,12 @@ vendor_id field they both have in common, and sorts the result by market_date, t
Limit to 24 rows of output. */
--QUERY 7



SELECT *
FROM vendor
INNER JOIN vendor_booth_assignments
ON vendor.vendor_id = vendor_booth_assignments.vendor_id
ORDER BY market_date, vendor_name
LIMIT 24;

--END QUERY

Expand All @@ -93,7 +122,10 @@ Limit to 24 rows of output. */
at the farmer’s market by counting the vendor booth assignments per vendor_id. */
--QUERY 8


SELECT vendor_id,
COUNT(*) AS booth_rental_count
FROM vendor_booth_assignments
GROUP BY vendor_id;


--END QUERY
Expand All @@ -106,7 +138,25 @@ of customers for them to give stickers to, sorted by last name, then first name.
HINT: This query requires you to join two tables, use an aggregate function, and use the HAVING keyword. */
--QUERY 9


SELECT
customer.customer_id,
customer.customer_first_name,
customer.customer_last_name,
SUM(customer_purchases.quantity *
customer_purchases.cost_per_quantity)
AS total_spent
FROM customer
INNER JOIN customer_purchases
ON customer.customer_id = customer_purchases.customer_id
GROUP BY
customer.customer_id,
customer.customer_first_name,
customer.customer_last_name
HAVING SUM(customer_purchases.quantity *
customer_purchases.cost_per_quantity) > 2000
ORDER BY
customer.customer_last_name,
customer.customer_first_name;


--END QUERY
Expand All @@ -125,6 +175,28 @@ VALUES(col1,col2,col3,col4,col5)
*/
--QUERY 10

--part 1: create temp TABLE

CREATE TABLE temp.new_vendor AS
SELECT *
FROM vendor;

--part 2: add new vendor

INSERT INTO temp.new_vendor (
vendor_id,
vendor_name,
vendor_type,
vendor_owner_first_name,
vendor_owner_last_name
)
VALUES (
10,
'Thomas Superfood Store',
'Fresh Focused',
'Thomas',
'Rosenthal'
);



Expand All @@ -139,8 +211,12 @@ and year are!
Limit to 25 rows of output. */
--QUERY 11



SELECT
customer_id,
strftime('%m', market_date) AS month,
strftime ('%Y', market_date) AS year
FROM customer_purchases
LIMIT 25;

--END QUERY

Expand All @@ -153,7 +229,13 @@ but remember, STRFTIME returns a STRING for your WHERE statement...
AND be sure you remove the LIMIT from the previous query before aggregating!! */
--QUERY 12


SELECT
customer_id,
SUM(quantity * cost_per_quantity) AS total_spent
FROM customer_purchases
WHERE strftime ('%m', market_date) = '04'
AND strftime ('%Y', market_date) = '2022'
GROUP BY customer_id;


--END QUERY
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading