2020: Week 7

As a little aside, Preppin' Data turns 1 year old on Thursday 13th February 2020. To celebrate the day, I just wanted to say thank you to a number of people who make this weekly challenge run:
  • Jonathan Allenby - my fellow Dr Prepper, who, without asking a question by a coffee machine in London, we'd never have a Prep based challenge. He's taken on a lot to keep this all running and providing great solution posts from day one
  • Tom Prowse - who is well on his way to becoming a Dr Prepper in his own right. Lots of great solution posts and filling the gaps for Jonathan and I when we need support - thank you. 
  • Jenny Martin - throwing up challenges, spotting issues and now providing video walkthroughs of the challenges at dataprepsolutions.com 
  • Bona Wang, Donna Coles, Jack Parry, Kate Brown and Rosario Gauna for finding errors and posing new challenges and generally encouraging Jonathan and I in the early days to keep us going.
Thank you all and hopefully we can keep coming up with great challenges as the Prep Development team (Rahim, Maraki, Zaheera and co) keep coming up with more great functionality. 
                                  ___________________________________________________

Enough of the thank you's, back to why you are here - Week 7's challenge. This week one of our supporters, Bona, and I have collaborated on an idea for a challenge around a common issue when processing data - counting something that no longer exists in the dataset. With GDPR and other consumer focused legislation becoming more prominent, customer records are disappearing rapidly once a customer leaves a business (for good reason). However, as an analyst, this makes certain tasks more challenging, like counting how many 'x' there were in a business at anyone time. 


For this challenge we are looking at employees who have left the business over time as well as understanding who still remain. 

Requirements

Current Employees

Reporting Dates

  • Input Data
  • Create a full list of employees
  • Create an end date for current employees that are yet to leave (use 1st March 2020) to help with calculations
  • Create a scaffold month that can have the Employee data joined on to it
  • Form your measures for analysis:
    • Count number of employees in employment by the company that month.
    • If the employee leaves in that month, remove them from the reporting within the month of leaving.
    • Avg Salary per employee per month
    • Total Salary paid by the company per month
  • Output the data

Output


One file:
  • 4 Columns:
    • Month
    • Total Monthly Salary
    • Avg Salary per Current Employees
    • Current Employees
  •  13 Rows (14 including Headers)
The outputs 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

2024: Week 1 - Prep Air's Flow Card

Image
Created by: Carl Allchin Welcome to a New Year of Preppin' Data challenges. For anyone new to the challenges then let us give you an overview how the weekly challenge works.  Each Wednesday the Preppin' crew (Jenny, myself or a guest contributor) drop a data set(s) that requires some reshaping and/or cleaning to get it ready for analysis.  You can use any tool or language you want to do the reshaping (we build the challenges in Tableau Prep but love seeing different tools being learnt / tried). Share your solution on LinkedIn, Twitter/X, GitHub or the Tableau Forums Fill out our tracker so you can monitor your progress and involvement The following Tuesday we will post a written solution in Tableau Prep (thanks Tom) and a video walkthrough too (thanks Jenny) As with each January for the last few years, we'll set a number of challenges aimed at beginners. This is a great way to learn a number of fundamental data preparation skills or a chance to learn a new tool — New Year&
Read more

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

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