Skip to content
Open
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
67 changes: 66 additions & 1 deletion 02_activities/assignments/DC_Cohort/Assignment1.md
Original file line number Diff line number Diff line change
Expand Up @@ -106,6 +106,8 @@ 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)

![Farmers Market Logical Model](./images/Farmers Market Logical Model.PNG)

***

## Section 2:
Expand Down Expand Up @@ -209,5 +211,68 @@ Consider, for example, concepts of fariness, inequality, social structures, marg


```
Your thoughts...
Databases reflect the values and assumptions of the people who build them,

and those choices have consequences for the people they describe.

The article about Pakistan's national database illustrates this notion by defining

"family" through a patrilineal structure, as the database excluded women and children

who did not fit that mold. The database did not allow for an alternative or alternate

version of family structure. This kind of design is not unique to Pakistan and

appears in databases I encounter as well.


In healthcare, databases that store patient information often reflect narrow assumptions

about family structure too. Fields for "mother" and "father" leave no room for same-sex

parents, single parents, or non-traditional caregivers. In paediatric settings,

the question of who counts as a caregiver has direct implications for who gets included in

treatment decisions. When a database cannot represent a child's actual family structure,

it creates gaps in care.


In academic systems, similar issues arise. University databases categorize students by

enrollment status, citizenship, and program type, but not registered accomodation.

These categories determine access to funding, housing, and support services.

Students who fall outside standard categories, such as those requiring addition time to

compelte course work, face additional barriers if they may not have the opportunity to live

closer to campus given their enrollment status (ie., part-time). Anyone who deviates

from or needs additional support beyond a typial student template is harder to support.


In research, databases embed assumptions about who counts as a healthy control versus

a patient, what symptoms are worth measuring to find desired insights, and which populations

are worth or valuable to be studying given desired outcomes.These choices shape what gets discovered.

If a database is built around a narrow demographic, the findings derived from it will only reflect

that small sub popualtion, and be less generalizable to other populations. Databases therefore

guide what is normal to be studied given access of information, and this might not impact other

people who have more complex data collection features, impacting, in the end, what is studied.


Overall, when designing or working with data systems, I think it is worth asking who is already

in the database and who it was built to represent and who the database is leaving out to assess

how inclusive and generalizable the database itself is.

```
119 changes: 72 additions & 47 deletions 02_activities/assignments/DC_Cohort/assignment1.sql
Original file line number Diff line number Diff line change
Expand Up @@ -6,31 +6,29 @@
--SELECT
/* 1. Write a query that returns everything in the customer table. */
--QUERY 1




SELECT *
FROM customer;
--END QUERY


/* 2. Write a query that displays all of the columns and 10 rows from the customer table,
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


--WHERE
/* 1. Write a query that returns all customer purchases of product IDs 4 and 9.
Limit to 25 rows of output. */
--QUERY 3




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


Expand All @@ -42,10 +40,11 @@ filtered by customer IDs between 8 and 10 (inclusive) using either:
Limit to 25 rows of output.
*/
--QUERY 4




SELECT *,
quantity * cost_to_customer_per_qty AS price
FROM customer_purchases
WHERE customer_id BETWEEN 8 AND 10
LIMIT 25;
--END QUERY


Expand All @@ -55,21 +54,33 @@ Using the product table, write a query that outputs the product_id and product_n
columns and add a column called prod_qty_type_condensed that displays the word “unit”
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


/* 2. We want to flag all of the different types of pepper products that are sold at the market.
add a column to the previous query called pepper_flag that outputs a 1 if the product_name
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 LOWER(product_name) LIKE '%pepper%' THEN 1
ELSE 0
END AS pepper_flag
FROM product;
--END QUERY


Expand All @@ -78,10 +89,12 @@ contains the word “pepper” (regardless of capitalization), and otherwise out
vendor_id field they both have in common, and sorts the result by market_date, then vendor_name.
Limit to 24 rows of output. */
--QUERY 7




SELECT *
FROM vendor AS v
INNER JOIN vendor_booth_assignments AS vba
ON v.vendor_id = vba.vendor_id
ORDER BY vba.market_date, v.vendor_name
LIMIT 24;
--END QUERY


Expand All @@ -92,10 +105,10 @@ Limit to 24 rows of output. */
/* 1. Write a query that determines how many times each vendor has rented a booth
at the farmer’s market by counting the vendor booth assignments per vendor_id. */
--QUERY 8




SELECT vendor_id,
COUNT(*) AS booth_rentals
FROM vendor_booth_assignments
GROUP BY vendor_id;
--END QUERY


Expand All @@ -105,10 +118,16 @@ 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
c.customer_first_name,
c.customer_last_name,
SUM(cp.quantity * cp.cost_to_customer_per_qty) AS total_spent
FROM customer AS c
INNER JOIN customer_purchases AS cp
ON c.customer_id = cp.customer_id
GROUP BY c.customer_id, c.customer_last_name, c.customer_first_name
HAVING total_spent > 2000
ORDER BY c.customer_last_name, c.customer_first_name;
--END QUERY


Expand All @@ -124,10 +143,11 @@ When inserting the new vendor, you need to appropriately align the columns to be
VALUES(col1,col2,col3,col4,col5)
*/
--QUERY 10
CREATE TEMPORARY TABLE temp.new_vendor AS
SELECT * FROM vendor;




INSERT INTO temp.new_vendor
VALUES (10, 'Thomass Superfood Store', 'Fresh Focused', 'Thomas', 'Rosenthal');
--END QUERY


Expand All @@ -138,10 +158,12 @@ HINT: you might need to search for strfrtime modifers sqlite on the web to know
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 @@ -152,8 +174,11 @@ HINTS: you will need to AGGREGATE, GROUP BY, and filter...
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_to_customer_per_qty) 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.