2022 Week 12 - Solution

Solution by Tom Prowse and you can download the workbook here.

This week take inspiration from the Gender Pay Gap Bot on Twitter, and take a look at historical data to get this into a nice, easy to understand structure.

Step 1 - Combine Files

The first step is to combine each of the different files from the different years. We have 5 different CSV files so we need to use the Wildcard Union within the Input step to stack these on top on one another.


After inputting all of the data files, we can then remove a lot of the fields that are included. We can remove fields straight from the input step by using the tick boxes on the right-hand side. 

We want to keep the following fields (these will be ticked): 

  • EmployerID
  • EmployerSize
  • DiffMedianHourlyPercent
  • File Paths
  • EmployerName
Our table should now look like this: 


Step 2 - Clean Report Year

Next we want to parse the year from each of the file names. After the wildcard union, Tableau Prep automatically creates the File Paths field which provides information about which input each of the rows come from. We can use this field to create a Year field for our data.

First, we want to split the data so that we only return the Year section at the end of the string. Fortunately, we can use the Automatic split to split the two years from the string into separate fields:


We can then rename the File Paths - Split 1 to Year, and then remove the File Path - Split 2 and File Paths fields so our data now looks like this:



Step 3 - Most Recent Report

To ensure we are including any companies that have changed their name, we now want to find out the latest year that each EmployerID had submitted a report. Therefore, we need to calculate the Max Year for each EmployerID by using a Fixed LOD calculation: 

Max Year 

Then we want to filter to return only where the Year = Max Year. This will only return the latest year that each EmployerID had submitted a report. 

At this stage we no longer need the Years, because we now have the latest name for each EmployerID, so we can keep only the EmployerName & EmployerID fields:


Then finally we can join this back to our original data set with an Inner Join where EmployerID = EmployerID


And then remove the duplicated EmployerID and the Employer Name from the original workflow - this will leave us with the updated company names.


Step 4 - Pay Gap Explainer

We now want to create a field that will help to explain the Pay Gap information in easy to understand English. 

As noted in the requirements there are a few different problems that might occur here. Therefore we follow these steps to create the string for each company:

1. Float Point Inaccuracies

String 

IF ABS([DiffMedianHourlyPercent])<10 THEN
LEFT(STR((CEILING(round(abs([DiffMedianHourlyPercent]),1)*100))/100),4)
ELSEIF ABS([DiffMedianHourlyPercent])<100 THEN
LEFT(STR((CEILING(round(abs([DiffMedianHourlyPercent]),1)*100))/100),5)
ELSE
LEFT(STR((CEILING(round(abs([DiffMedianHourlyPercent]),1)*100))/100),6)
END

This will ensure that the numbers are correct rounded to 2 decimals places.

2. Positive & Negatives

String  

IF RIGHT([String],1)='0' and LEN([String])>1
THEN LEFT([String],LEN([String])-1)
ELSE [String]
END

This will ensure that the positive and negatives are as we expect.

3. Correct Phrasing

IF [DiffMedianHourlyPercent]>0 THEN
"In this organisation, women's median hourly pay is "+[String]+"% lower than men's."

ELSEIF [DiffMedianHourlyPercent]<0 THEN
"In this organisation, women's median hourly pay is "+[String]+"% higher than men's."

ELSE "In this organisation, men's and women's median hourly pay is equal."
END

This creates the string for each of the three different options.

The final step of the challenge this week is to reorder the fields and then we are ready to output our data: 


You can download the full output here. 

After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @Datajedininja, @JennyMartinDS14 & @TomProwse1

You can also post your solution on the Tableau Forum where we have a Preppin' Data community page. Post your solutions and ask questions if you need any help! 


Popular posts from this blog

2023: Week 1 The Data Source Bank

Image
 Created by: Carl Allchin Welcome to a New Year of Preppin' Data. These are weekly exercises to help you learn and develop data preparation skills. We publish the challenges on a Wednesday and share a solution the following Tuesday. You can take the challenges whenever you want and we love to see your solutions. With data preparation, there is never just one way to complete the tasks so sharing your solutions will help others learn too. Share on Twitter, LinkedIn, the Tableau Forums or wherever you want to too. Tag Jenny Martin, Tom Prowse or myself or just use the #PreppinData to share your solutions.  The challenges are designed for learning Tableau Prep but we have a broad community who complete the challenges in R, Python, SQL, DBT, EasyMorph and many other tools. We love seeing people learn new tools so feel free to use whatever tools you want to complete the challenges.  A New Year means we start afresh so January's challenges will be focused on beginners. We will use dif
Read more

2023: Week 2 - International Bank Account Numbers

Image
Challenge By: Jenny Martin For week 2 of our beginner month, Data Source Bank has a requirement to construct International Bank Account Numbers (IBANs), even for Transactions taking place in the UK. We have all the information in separate fields, we just need to put it altogether in the following order: Inputs A list of the transactions, with information about the receiving bank account  A lookup table for the SWIFT Bank Codes  Requirements Input the data In the Transactions table, there is a Sort Code field which contains dashes. We need to remove these so just have a 6 digit string ( hint ) Use the SWIFT Bank Code lookup table to bring in additional information about the SWIFT code and Check Digits of the receiving bank account ( hint ) Add a field for the Country Code ( hint ) Hint: all these transactions take place in the UK so the Country Code should be GB Create the IBAN as above ( hint ) Hint: watch out for trying to combine sting fields with numeric fields - check data types Re
Read more

How to...Handle Free Text

Image
Free isn't always a good thing. In data, Free text is the example to state when proving that statements correct. However, lots of benefit can be gained from understanding data that has been entered in Free Text fields. What do we mean by Free Text? Free Text is the string based data that comes from allowing people to type answers in to systems and forms. The resulting data is normally stored within one column, with one answer per cell. As Free Text means the answer could be anything, this is what you get - absolutely anything. From expletives to slang, the words you will find in the data may be a challenge to interpret but the text is the closest way to collect the voice of your customer / employee. The Free Text field is likely to contain long, rambling sentences that can simply be analysed. If you count these fields, you are likely to have one of each entry each. Therefore, simply counting the entries will not provide anything meaningful to your analysis. The value is in
Read more