2023: Week 31 - HR Month - Filling in Missing IDs

Challenge by: Kelly Gilbert

Validated by: Abiramm Thavajothy

After a successful HR Month at the end of 2022, Kelly has returned with more real-life (fake data) challenges for us! Since Kelly's data prep tool of choice is Alteryx or Python, we also enlisted some help from colleagues at the Data School to ensure the logic works in Tableau Prep as well. Thanks for your help with this one Abi! Over to Kelly:

Over the next few challenges, we’ll be using fake employee data for a small network of distribution centers. The data is fake, but the challenges are based on real people analytics challenges.

In this challenge, we have two HR tables: one that contains the list of employees (with their name, DOB, etc.), and one that contains a monthly snapshot of which employees worked at each DC during the month.

We want to be able to join the two tables, but sometimes the employee_id is missing from one (or both!) of the tables. We do have a second ID (the guid), but sometimes that is missing as well! Fortunately, we have at least one of those IDs present for each record. 

The goal for this challenge is to fill in the missing IDs in both tables, so they can be joined later.

Note: throughout this month, you’ll see the abbreviations, “ee”, which is short for employee, and “DC” which is short for distribution center

Inputs

1. Employee Dimension Table (ee_dim_input.csv) 


2. Monthly Snapshot Table (ee_monthly_input.csv) 

Requirements

  • Input the data
  • Create a lookup table:
    • Find the unique employee_id / guid combinations in each table
    • Union the results together and remove any duplicates
    • Filter out any rows where one of the IDs is missing
  • Join the main table with the lookup table on employee_id (make sure to keep all records from the original table, whether or not they match)
  • If the guid is missing from the main table, replace it with the guid from the lookup table.
  • Join the result to the lookup table on guid (make sure to keep all records from the original table, whether or not they match)
  • If the employee_id is missing from the main table, replace it with the value from the lookup table
  • Repeat previous steps for both the employee table and the monthly table.
  • Make sure that there are no nulls in the employee_id and guid fields in both tables
  • Output the results (two files)

Outputs

1. The employee dimension table, with missing IDs filled (ee_table_v2.csv) 
  • 10 fields
    • employee_id
    • guid
    • first_name
    • last_name
    • date_of_birth
    • nationality
    • gender
    • email
    • hire_date
    • leave_date
  • 537 rows (538 including headers)
2. The monthly table, with missing IDs filled (ee_monthly_v2.csv) 
  • 6 fields
    • employee_id
    • guid
    • dc_nbr
    • month_end_date
    • hire_date
    • leave_date
  • 7,440 rows (7,441 including headers)
You can download the output from here.

After you finish the challenge make sure to fill in the participation tracker, then share your solution on Twitter using #PreppinData and tagging @kelly_gilbert, @AbirammT, @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