2024: Week 25 - SuperBytes Customer Complaints

Challenge by: Tobias Colmer

We're continuing with DS43's challenges so over to Tobias to explain his first challenge. 

_____________________________________

This week Superbytes needs you to take a look at their complaints data, as an error was spotted in a recent data leak posted by rival supermarket WeakFloats: we need to check if their claims are true! They claim that:

we have no category field in our data clearly stating the category of products being complained about & that we were resolving complaints before we’d even received them!

Inputs

There are 2 inputs for this challenge:
  • The Complaints Data Table 

  • The Product Category Lookup Table 

Requirements

  • Input the dataInput the data
  • Split the Complaint Description field into:
    • Product ID
    • Issue Type
    • Complaint Description (the text the customer wrote to describe the complaint)
  • Extract the first 2 letters of the Product ID as this represents the Category Code
  • Use this Category Code to join on the Product Category from the lookup table
  • Filter the dataset to only contain rows where the Date Resolved happens after the Date Received
  • Remove unnecessary fields
  • Output the dataOutput the data

Output

  • 11 fields
    • Complaint ID
    • Receipt Number
    • Customer ID
    • Date Received
    • Date Resolved
    • Timely Response
    • Response to Customer
    • Issue Type
    • Product Category
    • Product ID
    • Complaint Description
  • 53 rows (54 including headers)
You can view the 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

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

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