2021 Week 38 - Solution

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


The challenge this week took a look at what the best movie trilogies of all time were. This is off the back of Jenny's viz on Tableau Public so lets see how we can prepare the data to be visualised. 

Step 1 - Average, Highest & Rank Trilogies

Using the Films input table, we can start by calculating the average rating of each trilogy by using a FIXED LOD: 

Trilogy Average 


We can then repeat this same process to find the Max rating:

Trilogy Max 


Then finally we can rank the trilogies based on their average rating: 

Trilogy Rank


Note: There seems to be an error in the way that Prep is calculating this rank, so don't worry if your output is different!

Our table of data should now look like this: 


Step 2 - Trilogy Table

Before we combine the two tables together, we first need to remove the word 'trilogy' from each of the Trilogy field. This can be done easily by using an automatic split on the Trilogy field, removing the original Trilogy field and then renaming the split field to Trilogy. 

The table should now just be the trilogy name and ranking: 


We can now join this to our original data set by using Trilogy Rank = Trilogy Ranking:


Our joined table should look like this: 



Step 3 - Final Cleaning

There are some final clean ups that we need to do to prepare our data for the output. First we want to round the Average field to 1 decimal place: 

Trilogy Average
ROUND([Trilogy Average],1)

Then we can split the Number in Series field so that we have both the film order and total films in series. To do this we can again use an automatic split to split the number either side of the '/' into two separate columns.

The Split 1 field can be renamed to 'Film Order' and the Split 2 is our 'Total Films in Series' field. Finally we can remove the Number in Series field and then we are ready to output our data, which should look like this:


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