Hivanson Week 8 - Revision history

Hivanson: /* Methods */ reorder notes/obs

2024-03-14T06:24:09Z

‎Methods: reorder notes/obs

Hivanson: /* Methods */ note/obs

2024-03-14T06:23:44Z

‎Methods: note/obs

Hivanson: /* Results */ moving notes and obs

2024-03-14T06:20:46Z

‎Results: moving notes and obs

Hivanson: /* References */ added other refs

2024-03-14T05:40:22Z

‎References: added other refs

Hivanson: /* References */ added ref

2024-03-14T05:36:11Z

‎References: added ref

Hivanson: /* Acknowledgments */ acknowledgments

2024-03-14T05:19:48Z

‎Acknowledgments: acknowledgments

Hivanson: added titles for main title, acknowledgments, and references

2024-03-14T05:17:42Z

added titles for main title, acknowledgments, and references

Hivanson: /* Purpose */ a word

2024-03-14T05:07:37Z

‎Purpose: a word

Hivanson: /* Results */ notes and observations

2024-03-14T05:06:41Z

‎Results: notes and observations

Hivanson: /* Results */ added final database

2024-03-14T05:04:47Z

‎Results: added final database

@@ Line 9: / Line 9: @@
 #I attempted to set the relationships between my tables to match the schema provided by the FDA, but he two entity relationship diagrams provided on the FDA website contained some conflicting information. I matched the relationships as best I could according to the diagrams and according to common field names. See screenshot of my relationships below:[[Image:hivanson_week8_relationships.png|800px]]
 #I used SQL functions to query the database. See '''Results''' section.
-'''Notes and Observations''': SQL functions were tough to figure out at first, but eventually they all seemed pretty similar to one another. I would love to have more practice making more complex SQL queries.
+'''Notes and Observations''':
 Date columns were giving me issues; to resolve the issues upon importation: I changed the datatype from date/time to short text, and then after importing changed it back to date. This resolved the issue.
 ==='''Results'''===

@@ Line 9: / Line 9: @@
 #I attempted to set the relationships between my tables to match the schema provided by the FDA, but he two entity relationship diagrams provided on the FDA website contained some conflicting information. I matched the relationships as best I could according to the diagrams and according to common field names. See screenshot of my relationships below:[[Image:hivanson_week8_relationships.png|800px]]
 #I used SQL functions to query the database. See '''Results''' section.
 ==='''Results'''===

← Older revision		Revision as of 06:20, 14 March 2024
Line 39:		Line 39:

	Question 9: The [https://www.accessdata.fda.gov/scripts/cder/daf/index.cfm search function on the FDA Drugs index] states that a user can "Search by Drug Name, Active Ingredient, or Application Number." Going through the list of queries that we used SQL to run, none can be run using the search function on the website. The FDA Drugs index does not allow search by form of drug (Query 1). The index does not allow a search to find a singular active ingredient (perhaps the search they are using is closer to <code>LIKE '<text>*'</code> than <code>= '<text>'</code>) and therefore cannot complete Query 2. Only one result is shown when searching the index for "Benadryl" while Query 3 using SQL retrieved 5 results. Endings and beginnings cannot be searched (Queries 4 and 8). Sponsor name cannot be searched (Query 7). These queries could not have been completed using the search function on the FDA Drugs index website alone, unless combing through and checking each listing for the desired characteristics (which is not a search).		Question 9: The [https://www.accessdata.fda.gov/scripts/cder/daf/index.cfm search function on the FDA Drugs index] states that a user can "Search by Drug Name, Active Ingredient, or Application Number." Going through the list of queries that we used SQL to run, none can be run using the search function on the website. The FDA Drugs index does not allow search by form of drug (Query 1). The index does not allow a search to find a singular active ingredient (perhaps the search they are using is closer to <code>LIKE '<text>*'</code> than <code>= '<text>'</code>) and therefore cannot complete Query 2. Only one result is shown when searching the index for "Benadryl" while Query 3 using SQL retrieved 5 results. Endings and beginnings cannot be searched (Queries 4 and 8). Sponsor name cannot be searched (Query 7). These queries could not have been completed using the search function on the FDA Drugs index website alone, unless combing through and checking each listing for the desired characteristics (which is not a search).
−
−	'''Notes and Observations''': SQL functions were tough to figure out at first, but eventually they all seemed pretty similar to one another. I would love to have more practice making more complex SQL queries.

	==='''Conclusion'''===		==='''Conclusion'''===

@@ Line 53: / Line 53: @@
 ==References==
 *LMU BioDB 2024. (2024). Week 8. Retrieved March 13, 2024, from https://xmlpipedb.cs.lmu.edu/biodb/spring2024/index.php/Week_8
 {{Template:Hivanson}}

← Older revision		Revision as of 05:36, 14 March 2024
Line 53:		Line 53:

	==References==		==References==
		+	*LMU BioDB 2024. (2024). Week 8. Retrieved March 13, 2024, from https://xmlpipedb.cs.lmu.edu/biodb/spring2024/index.php/Week_8
		+
	{{Template:Hivanson}}		{{Template:Hivanson}}

@@ Line 1: / Line 1: @@
 ==='''Purpose'''===
 Import public-access FDA drug database into Microsoft Access, then compare query capabilities using SQL on Access to those of the search function on the FDA Drug index.
@@ Line 44: / Line 45: @@
 By importing the FDA Drugs database to Microsoft Access, setting relationships between tables, and comparing searching using SQL functions to the search function on the FDA Drugs index website, we have learned the limitations of search functions provided by usual user interfaces, and have an understanding of how much can be done with SQL search functions. SQL allows for more flexibility and specificity in searching the FDA Drugs database than the FDA Drug Index search function provides.
 {{Template:Hivanson}}

← Older revision		Revision as of 05:06, 14 March 2024
Line 37:		Line 37:

	Question 9: The [https://www.accessdata.fda.gov/scripts/cder/daf/index.cfm search function on the FDA Drugs index] states that a user can "Search by Drug Name, Active Ingredient, or Application Number." Going through the list of queries that we used SQL to run, none can be run using the search function on the website. The FDA Drugs index does not allow search by form of drug (Query 1). The index does not allow a search to find a singular active ingredient (perhaps the search they are using is closer to <code>LIKE '<text>*'</code> than <code>= '<text>'</code>) and therefore cannot complete Query 2. Only one result is shown when searching the index for "Benadryl" while Query 3 using SQL retrieved 5 results. Endings and beginnings cannot be searched (Queries 4 and 8). Sponsor name cannot be searched (Query 7). These queries could not have been completed using the search function on the FDA Drugs index website alone, unless combing through and checking each listing for the desired characteristics (which is not a search).		Question 9: The [https://www.accessdata.fda.gov/scripts/cder/daf/index.cfm search function on the FDA Drugs index] states that a user can "Search by Drug Name, Active Ingredient, or Application Number." Going through the list of queries that we used SQL to run, none can be run using the search function on the website. The FDA Drugs index does not allow search by form of drug (Query 1). The index does not allow a search to find a singular active ingredient (perhaps the search they are using is closer to <code>LIKE '<text>*'</code> than <code>= '<text>'</code>) and therefore cannot complete Query 2. Only one result is shown when searching the index for "Benadryl" while Query 3 using SQL retrieved 5 results. Endings and beginnings cannot be searched (Queries 4 and 8). Sponsor name cannot be searched (Query 7). These queries could not have been completed using the search function on the FDA Drugs index website alone, unless combing through and checking each listing for the desired characteristics (which is not a search).
		+
		+	'''Notes and Observations''': SQL functions were tough to figure out at first, but eventually they all seemed pretty similar to one another. I would love to have more practice making more complex SQL queries.

	==='''Conclusion'''===		==='''Conclusion'''===

← Older revision		Revision as of 05:04, 14 March 2024
Line 9:		Line 9:

	==='''Results'''===		==='''Results'''===
		+
		+	[[Media:Hivanson_FDA_3.12.24.database.zip\|Download my competed database]]

	*Query 1: SELECT DrugName FROM Products WHERE form ='INJECTABLE;INTRAVENOUS, SUBCUTANEOUS';		*Query 1: SELECT DrugName FROM Products WHERE form ='INJECTABLE;INTRAVENOUS, SUBCUTANEOUS';