2023: Week 46 - Solution




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



Step 1 - Minutes Late

After inputting the data we want to remove any null values from the Arrival Time. We can do this by selecting the 'Null' value in the profile pane and then exclude.

We can then create the Scheduled Start Time and Arrival Time by combining the date with each of the time fields.

Scheduled Start Time
MAKEDATETIME([Date],[Scheduled Start Time])

Arrival Time
MAKEDATETIME([Date],[Arrival Time])

We can then remove the Date field and then calculate how late each student was by using a datediff calculation: 

Lateness
DATEDIFF('minute',[Scheduled Start Time],[Arrival Time])

At this stage our table should look like this: 



Step 2 - Output 1

At this stage we want to split the workflow into separate branches - one for each output.

In our first output we want to calculate the average lateness of students per weekday. We can calculate this using an aggregate step where we group by Day of Week and Avg Lateness: 



We can then rank the days based on the how late the avg is: 



Then split this into minutes and seconds:

Minutes Late
FLOOR([Lateness])

Seconds Late
ROUND(([Lateness]-[Minutes Late])*60)

We are then ready to output our first table: 



Step 3 - Output 2

For the second output we want to go back to the step where we calculated the 'lateness' and create a new branch.

Within this branch we can calculate whether a student was very late or not.

Very Late?
IF [Lateness]>5 THEN 1 ELSE 0 END

Using this field we can aggregate how many classes each student has attended and also how many they have been very late for. We can group by Student ID and then sum Number of Rows and Very Late?



From here we can rename the Number of Rows field to Number of Days Present and then calculate the % of total that they were very late.

% Days Very Late
ROUND(100*[Very Late?]/[Number of Days Present],1)

Then finally we can rank our table based on the % of very late days: 



Then our 2nd output should look like this: 


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