2020: Week 31 When PD met Workout Wednesday Again!

This challenge is a collaborative effort from Jenny, Carl and Lorna.

After the success of last year's Preppin' Data and Workout Wednesday live event, we decided a second meeting of the two challenges was a must. Although we can't be together physically in person, thank goodness we're able to host the event virtually!

Unfortunately, the Olympics that were due to take place in Japan this year weren't so lucky. Therefore, we chose to focus our challenge on looking back at historical Olympics data. Did you know this isn't the first Olympics to be cancelled?

Inputs

There are 3 inputs this week: 
  1. Host Countries (which you may recognise as the output from week 28's challenge, whose input came from Sports Viz Sunday) 

  2. The history of all the medallists for each Olympics (sourced from the Guardian and Wikipedia)

  3. A country codes lookup table.

Requirements

  • Input the data
  • Make sure every medal has both a Country and Country Code associated with it
  • Group together Canoe/Kayak and Canoeing Sports
  • Group together sensible Disciplines
  • Replace the word "metres"/"metre" in Events with an "m" abbreviation
  • Replace the word "kilometres" in Events with an "km" abbreviation
  • Change Sport from Swimming to Aquatics
  • Output cleaned Medallists Dataset
  • Aggregate to a row for each Event medal (i.e. we know longer need the Athlete names Level of Detail)
  • Create a table showing total Gold, Silver and Bronze medals from each country for each year
  • Output Country Medals Dataset
  • Using the Hosts dataset, create a field for the Host Country 
  • Change the United Kingdom to Great Britain
  • Output Host Cities Dataset

Outputs

There are 3 Outputs this week. You can download them all here if you didn't quite finish before we move onto the Workout Wednesday portion of the challenge.

1. Medallists Dataset
    9 columns; 33,203 rows
2. Country Medals Dataset
    5 columns; 1,242 rows
3. Host Cities Dataset
    9 columns; 28 rows
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, @JonathanAllenby & @TomProwse1

You can also post your solution on the brand new 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