2020: Week 18


Due to the social distancing and isolation caused by Covid-19, all football games have been postponed across the majority of the world. Therefore to help fill the void, this week’s challenge is all about analysing football team line-ups and in-particular the Premier League games for Liverpool.

We start with a nicely formatted spreadsheet that includes the following:
  • Match Details - Including dates, teams, location and formation
  • Match Day Squad - 18 players broken down into Starting XI & Substitutes
    • Starting XI - the 11 players who started the game for Liverpool
    • Substitutes - the 7 players who started as a substitute for Liverpool
  • Substitution Information - Includes the Player On/Off and the Time
From this we want to answer some questions about the playing time of each of the players.

Requirements

  • Input Data
  • Update the headers for Match Details, Starting XI, Substitutes. Ideally this will be done without just renaming each individual header separately. Note, for substitutes the headers follow this pattern, where X is the substitute number:
    • SubX = Substitute Off, the player number who has left the field
    • SubX 1 = Substitute On, the player number who is entering the field
    • SubX 2 = Time of Substitute, the time in the match when the substitution occurred
  • Calculate whether or not the player was substituted on/off, what number substitute it was (1/2/3), and at what time in the match it happened. 
  • If a player was substituted in the 90th minute, then we count this as 1 appearance but 0 mins played, as we don't have information about additional time played in the match. 

Answer the following questions:
  • How many times has each player been in the squad? 
  • How many appearances has each player made?
  • What is their minute per games ratio? (This only includes games that they made an appearance in)

Output

  • 5 Fields:
    • In Squad
    • Player Name
    • Mins Played
    • Appearances
    • Mins per Game
  • 29 rows (30 incl. headers)

The full output can be found here for comparison. Don’t forget to fill the participation tracker and share your solutions using #PreppinData on Twitter.

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