Class Journal Week 8 - Revision history

Asandle1: /* Andrew Sandler's Class Journal Entry */ added template

2024-03-14T20:53:14Z

‎Andrew Sandler's Class Journal Entry: added template

Hivanson: /* Hailey Ivanson */ removed an extraneous word

2024-03-14T06:20:02Z

‎Hailey Ivanson: removed an extraneous word

Hivanson: class journal entry.

2024-03-14T06:19:35Z

class journal entry.

Kmill104: /* Katie Miller */ fixing typo

2024-03-14T06:14:22Z

‎Katie Miller: fixing typo

Kmill104: answering questions

2024-03-14T06:13:48Z

answering questions

Nstojan1-new: added reflection answers

2024-03-14T04:47:09Z

added reflection answers

Msymond1: /* Dean Symonds */

2024-03-14T02:56:56Z

‎Dean Symonds

Msymond1: /* Dean Symonds */ answered the rest of the questions

2024-03-14T02:54:18Z

‎Dean Symonds: answered the rest of the questions

Msymond1: first 2 questions

2024-03-14T02:49:59Z

first 2 questions

Ckapla12: signature

2024-03-14T02:26:41Z

signature

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

	[[User:Asandle1\|Asandle1]] ([[User talk:Asandle1\|talk]])		[[User:Asandle1\|Asandle1]] ([[User talk:Asandle1\|talk]])
		+
		+	{{Template:Asandle1}}

@@ Line 3: / Line 3: @@
 #Importing the data and troubleshooting the occasional error messages made the most sense to me. The repetition was enjoyable, especially when I was able to solve my own issues.
 #I am not confident about how setting relationships should be done. I don't fully understand the relationship directionality, and had trouble interpreting the schema provided by the FDA.
-#I would love to learn more SQL functions to find the limits of what ca be done with this complex search function method. I liked using SQL and would love to look into a LinkedIn learning course or something similar that focuses on just SQL for Access.
+#I would love to learn more SQL functions to find the limits of what ca be done with this complex search method. I liked using SQL and would love to look into a LinkedIn learning course or something similar that focuses on just SQL for Access.
 [[User:Hivanson|Hivanson]] ([[User talk:Hivanson|talk]]) 23:19, 13 March 2024 (PDT)

← Older revision		Revision as of 06:19, 14 March 2024
Line 1:		Line 1:
		+	==[[User:Hivanson\|Hailey Ivanson]]==
		+	#Reading the first sentence in section 5.1 I got all excited because that's exactly what we did! Data importation from a specified source. If other data storage methods are similar to Access, I would know what I would be looking at if shown data being stored on a computer now that I've seen how the FDA Drugs database looks on my end when imported to Access.
		+	#Importing the data and troubleshooting the occasional error messages made the most sense to me. The repetition was enjoyable, especially when I was able to solve my own issues.
		+	#I am not confident about how setting relationships should be done. I don't fully understand the relationship directionality, and had trouble interpreting the schema provided by the FDA.
		+	#I would love to learn more SQL functions to find the limits of what ca be done with this complex search function method. I liked using SQL and would love to look into a LinkedIn learning course or something similar that focuses on just SQL for Access.
		+
		+	[[User:Hivanson\|Hivanson]] ([[User talk:Hivanson\|talk]]) 23:19, 13 March 2024 (PDT)
		+
	=[[User:Asandle1 \| Andrew Sandler]]'s Class Journal Entry=		=[[User:Asandle1 \| Andrew Sandler]]'s Class Journal Entry=
	# I feel that I do have a better understanding of how the data mentioned in the 5.1 article looks in its stored form.		# I feel that I do have a better understanding of how the data mentioned in the 5.1 article looks in its stored form.

@@ Line 44: / Line 44: @@
 ==Katie Miller==
 #Yes, I think I have a better understanding of the data mentioned in the article. Working with a relational database and defining relationships between the tables has given me a very basic insight on how relational databases operate. For very large databases like the ones in the article, I imagine there is a lot more tables and relationships that must be defined, but they likely operate in the same way as what I have seen.
-#2. Setting relationships between the tables made the most sense to me, as it was basically identifying which columns were present in multiple tables and then assigning that relationship. It made sense to me that if you had a question with two fields being looked at for the answers, even if one of the tables didn't have both fields the question was looking for, it could use its relationship with another table to find the final answers.
+#Setting relationships between the tables made the most sense to me, as it was basically identifying which columns were present in multiple tables and then assigning that relationship. It made sense to me that if you had a question with two fields being looked at for the answers, even if one of the tables didn't have both fields the question was looking for, it could use its relationship with another table to find the final answers.
-# I had some trouble with running queries in the SQL format. I often struggled with determining what exactly I was looking for and from where, and what I should put after SELECT, FROM, and WHERE.
+#I had some trouble with running queries in the SQL format. I often struggled with determining what exactly I was looking for and from where, and what I should put after SELECT, FROM, and WHERE.
 #I would like to learn more about other database tools in Microsoft Access, because I feel like there is a lot I still have to learn. I would also like to learn about other ways to create a database other than in Microsoft Access.
 [[User:Kmill104|Kmill104]] ([[User talk:Kmill104|talk]]) 23:13, 13 March 2024 (PDT)

← Older revision		Revision as of 06:13, 14 March 2024
Line 41:		Line 41:
	#I would like to know more about running queries and learn why different syntax is used in different types of situations especially when establishing relationships with two or more tables. I know that it is a powerful tool, however I don't think I understand when and how it could be used because I think that it could be a great tool to be able to use in daily life considering I have to keep track of all sorts of records for a number or horses.		#I would like to know more about running queries and learn why different syntax is used in different types of situations especially when establishing relationships with two or more tables. I know that it is a powerful tool, however I don't think I understand when and how it could be used because I think that it could be a great tool to be able to use in daily life considering I have to keep track of all sorts of records for a number or horses.
	[[User:Nstojan1-new\|Nstojan1-new]] ([[User talk:Nstojan1-new\|talk]]) 21:47, 13 March 2024 (PDT)		[[User:Nstojan1-new\|Nstojan1-new]] ([[User talk:Nstojan1-new\|talk]]) 21:47, 13 March 2024 (PDT)
		+
		+	==Katie Miller==
		+	#Yes, I think I have a better understanding of the data mentioned in the article. Working with a relational database and defining relationships between the tables has given me a very basic insight on how relational databases operate. For very large databases like the ones in the article, I imagine there is a lot more tables and relationships that must be defined, but they likely operate in the same way as what I have seen.
		+	#2. Setting relationships between the tables made the most sense to me, as it was basically identifying which columns were present in multiple tables and then assigning that relationship. It made sense to me that if you had a question with two fields being looked at for the answers, even if one of the tables didn't have both fields the question was looking for, it could use its relationship with another table to find the final answers.
		+	# I had some trouble with running queries in the SQL format. I often struggled with determining what exactly I was looking for and from where, and what I should put after SELECT, FROM, and WHERE.
		+	#I would like to learn more about other database tools in Microsoft Access, because I feel like there is a lot I still have to learn. I would also like to learn about other ways to create a database other than in Microsoft Access.
		+
		+	[[User:Kmill104\|Kmill104]] ([[User talk:Kmill104\|talk]]) 23:13, 13 March 2024 (PDT)

← Older revision		Revision as of 04:47, 14 March 2024
Line 34:		Line 34:
	#I would like to know more about how these databases are used in my daily life, I am aware of how these databases exist in my daily life, through student Identification, song titles or IDs, but I am curious to know more about what it would mean if these databases did not exist in my daily life and how it would make it more difficult.		#I would like to know more about how these databases are used in my daily life, I am aware of how these databases exist in my daily life, through student Identification, song titles or IDs, but I am curious to know more about what it would mean if these databases did not exist in my daily life and how it would make it more difficult.
	[[User:Msymond1\|Msymond1]] ([[User talk:Msymond1\|talk]]) 19:56, 13 March 2024 (PDT)		[[User:Msymond1\|Msymond1]] ([[User talk:Msymond1\|talk]]) 19:56, 13 March 2024 (PDT)
		+
		+	==Natalija Stojanovic==
		+	#I definitely feel like I have a better understanding about the data mentioned in the 'What Is Code' reading is stored. In the beginning, it was hard to understand however the more I worked with the database, the more I understood about how information is searched and stored.
		+	#The part that made the most sense to me was inserting the tables and assigning the different field types based on the schema. Since the process was similar for all the tables, it was easy to repeat the process.
		+	#I am least confident about imputing the SLQ and running the queries to search for things. In the beginning I thought I understood what I was doing because the first 2 were straightforward. However, and they got more complicated and relationships had to be established it was more difficult to get them to work. It was difficult to understand what needed to be input for it to work, for example, for some we had to use the '=' and for some the word 'LIKE', I didn't understand when I had to use which one.
		+	#I would like to know more about running queries and learn why different syntax is used in different types of situations especially when establishing relationships with two or more tables. I know that it is a powerful tool, however I don't think I understand when and how it could be used because I think that it could be a great tool to be able to use in daily life considering I have to keep track of all sorts of records for a number or horses.
		+	[[User:Nstojan1-new\|Nstojan1-new]] ([[User talk:Nstojan1-new\|talk]]) 21:47, 13 March 2024 (PDT)

← Older revision		Revision as of 02:56, 14 March 2024
Line 33:		Line 33:
	#I feel the least confident about running queries to find certain things on the database. Because it required different syntax for each one, which many times was difficult to figure out what it must need, and it did not feel like there was a common pattern to be applied to all of the queries.		#I feel the least confident about running queries to find certain things on the database. Because it required different syntax for each one, which many times was difficult to figure out what it must need, and it did not feel like there was a common pattern to be applied to all of the queries.
	#I would like to know more about how these databases are used in my daily life, I am aware of how these databases exist in my daily life, through student Identification, song titles or IDs, but I am curious to know more about what it would mean if these databases did not exist in my daily life and how it would make it more difficult.		#I would like to know more about how these databases are used in my daily life, I am aware of how these databases exist in my daily life, through student Identification, song titles or IDs, but I am curious to know more about what it would mean if these databases did not exist in my daily life and how it would make it more difficult.
		+	[[User:Msymond1\|Msymond1]] ([[User talk:Msymond1\|talk]]) 19:56, 13 March 2024 (PDT)

@@ Line 30: / Line 30: @@
 ==Dean Symonds==
 #Yes, I do believe I have a better understanding of how the article mentions the data in section 5.1. Now that I have worked with a relational database, even though it was a rather simple one, I do believe I understand what it may look like more, and I can only imagine how extensive such databases must be for something such as Spotify because of all of the tables that the music must require, such as the artists, record company, release date, etc.
+#The part of the assignment that made the most sense to me is importing the tables and establishing the parameters for each variable, and establishing the relationships. If felt like something that could be repeated relatively easily and something that formed a rhythm after awhile.

← Older revision		Revision as of 02:49, 14 March 2024
Line 27:		Line 27:

	[[User:Ckapla12\|Ckapla12]] ([[User talk:Ckapla12\|talk]]) 19:26, 13 March 2024 (PDT)		[[User:Ckapla12\|Ckapla12]] ([[User talk:Ckapla12\|talk]]) 19:26, 13 March 2024 (PDT)
		+
		+	==Dean Symonds==
		+	#Yes, I do believe I have a better understanding of how the article mentions the data in section 5.1. Now that I have worked with a relational database, even though it was a rather simple one, I do believe I understand what it may look like more, and I can only imagine how extensive such databases must be for something such as Spotify because of all of the tables that the music must require, such as the artists, record company, release date, etc.
		+	#

← Older revision		Revision as of 02:26, 14 March 2024
Line 25:		Line 25:

	I would like to learn more about database design, query optimization techniques, and database management tools to improve the efficiency of creating relationships between tables and constructing queries.		I would like to learn more about database design, query optimization techniques, and database management tools to improve the efficiency of creating relationships between tables and constructing queries.
		+
		+	[[User:Ckapla12\|Ckapla12]] ([[User talk:Ckapla12\|talk]]) 19:26, 13 March 2024 (PDT)