2023: Week 20 - Dining Hall Debacle

Created by: Trea McElhone

At the Prep School, the lunch menu is extensive. However at the latest PTA (Parent Teacher Association) meeting some parents were grumbling about the range of dietary preferences offered by the school’s dining hall menu. They seemed to suggest that there aren’t enough vegetarian or vegan options for their kids, and they also complained that the vegan & vegetarian options offered are more expensive than the meat-based options. 


The principal was quick to reassure them that this was not the case - however perhaps too quick, as they had yet to check the stats! 


This is where you come in, as the PTA insisted on getting some fact based info and they want it pretty soon. As such, in this week's challenge, your task is to help the Prep School understand what percentage of meal options on its menu are vegan, vegetarian , or meat-based, as well as the average price for each meal type.

Input

Input 1: Meal Prices

Input 2: Nutritional Information

Requirements

  • Input both data sources from here

  • Group meal types 

    • Hint - veggie and vegetarian are the same type 

  • Join the data sets together so you have the meal type and price for each meal 

  • Remove the irrelevant fields

  • Aggregate the data by meal type and average their price

  • Calculate the percentage of total for each meal type 

    • Hint - this blog post is helpful for this step

  • Rename the fields to match the output data example 

  • Output the data as a CSV

Output


3 Fields 

  • Type 

  • Average Price 

  • Percent of Total 

3 rows (4 including headers)


You can download 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 @TreaMcElhone, @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