2022: Week 36 - Calendar Conundrum

Challenge by: Jared Flores

After beginner and intermediate months, it felt like time to give Carl a break! So here's a challenge submitted by Prep Star Jared:

As part of managing your store, you need to know which days you have coverage and which days you still need to schedule. When plugging your data into Tableau to create a calendar, you get this view because you’re missing dates:


Timeline Description automatically generated



We need to modify the data so that even dates with no coverage show in the view:

Diagram, timeline Description automatically generated

Input

  • Employees and their scheduled dates

Table Description automatically generated

 

Requirements

  • Input the data

  • The main challenge is to solve this using only employee_data input

  • Create a Calendar Table

    • Create a date range for the calendar

      • This should be dynamic to handle new data

      • The start of the range should be the based on the year of the earliest date

        • If earliest date is 06/01/2021, the start date should be 01/01/2021

      • The end of the range should be the last day of the year for the latest date in the data set

        • If the latest date is 06/01/2022, the end date should be 31/12/2022

    • Generate a row for every day between the start and end date to get a calendar table

  • Create a field containing the full name for each employee

  • Get a unique list of employees with their full name, first/last name fields, and employee id

  • Join the list to the calendar table

    • You should have a table with one row per employee per day

  • Join the new calendar table to the main table

    • One row per employee per day, even on days where the employee wasn’t scheduled

  • Create a flag if the employee was scheduled on the day

  • Handle any null values

  • Output the data

Output

A picture containing table Description automatically generated

 

  • 6 fields

    • Scheduled_date

    • Emp_id

    • Full_name

    • First_name

    • Last_name

    • Scheduled

  • 7300 rows (7301 including headers)

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 & @VizWhat

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