Data
Best Practices for Data Analysts
1. Don’t make up and answer : be very sure of the answer you are giving it not verify to be certain
2. Dont publish or write something until you verify the results: Make sure you verify data before publishing it or writing something about it.
3. Be prepared for meetings and use your time effectively
4. Take note of everything that is in relationship to your objective.
5. aprovide detailed information about what you are presenting
Joining Data the Class Assessment
We told to simply find data on product subcategories.
What to be done:
We went ahead to create and click on query. After this we added our product table and product subcategory- it is what we are look for . We hit the product count to check the amount of data available which was 504 in total (the essence of this is to make sure we run a query that do not multiply our data hence given more than the data available).
Common Mistakes by New Data Analyst
1.Not spending enough time Up font to understand the data: look for what the field name , data types and Values
2.Not looking for duplicate data
3.Not doing preliminary math like sums , averages , and counts.
4.Not capturing record counts
5.Not documenting questions and follow-up answers.
6.Not verifying the numbers with some other method
7.Not asking questions out of fear
8.Not asking for documentation.
9.Not analyzing existing report.
Today in Data Analysis class
Joining Data in a single Table
Data structures that requires the joining of data always provide for how it will be done . For instance in excel it is called *Vlookup* while in data base it is called *queries*
In Queries there are different types of joins which are inner joins, left and right outer joint and cross joins. The type of join will determine the end result, so it important to understand them.
12.69 % of all global data comes from social media and approximately half a billion tweets are shared on X daily! DePIN and SocialFi have a strong future!
Continuation of practical Aspcet of Joining Data.
Inner join does not have arrow shape on either side of the join . When you change the line will change also . Like It was mentioned in the last class running this query on the existing example will only give us products that have been order . To get products that have not been order , we will need an left outer join. To do this I will go to click on left outer join on design view, right click and go to join properties .
My Day Analysis class today:
On the practical aspect of joining data
When you join data you are using the field of data that is the same in both tables and it the same data type . Sometimes they will named the same and sometimes they will be not.An example was given of a data field of product ID and Sales ID ; linking this together may give no results or limited results because sales ID and Product ID should not be linked .
