2024: Week 26 - SuperBytes Customer Complaints Part 2

 Challenge by: Tobias Colmer

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

_____________________________________

After recovering from last week's data breach that targeted our Superbytes complaint data, more discrepancies within the data were discovered, such as complaints that took over 100 days to resolve being considered as timely. We need to fix this.

Input

The input for this challenge is the output from last week.

Requirements

  • Input the data
  • For Customer Complaints that are still In Progress, set the Date Resolved to today's date (for the output below this is set to 26th June 2024)
  • Create a Days to Resolve field for Complaints which are closed
  • Create a Days Open field for Complaints which are In Progress
  • Update the Timely Response field to correctly say whether it was Timely or Not, based on if the Date Resolved was less than 14 days
  • Create a parameter so a user can choose whether to output In Progress complaints or Closed complaints only
  • Output the data

Outputs

In Progress Complaints Output:

  • 13 fields
    • Complaint ID
    • Receipt Number
    • Customer ID
    • Date Received
    • Date Resolved
    • Days Open
    • Days to Resolve
    • Timely Response
    • Response to Customer
    • Issue Type
    • Product Category
    • Product ID
    • Complaint Description
  • 11 rows (12 including headers)

Completed Complaints Output:

  • 13 fields
    • Complaint ID
    • Receipt Number
    • Customer ID
    • Date Received
    • Date Resolved
    • Days Open
    • Days to Resolve
    • Timely Response
    • Response to Customer
    • Issue Type
    • Product Category
    • Product ID
    • Complaint Description
  • 42 rows (43 including headers)
You can view the outputs 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 u...
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