2021: Week 46 Book Shop Data Modelling

 Challenge by: Carl Allchin    

For any Tableau Desktop users, the relationship model being introduced in 2020.2 created a very different way of working with data. The aim of the new functionality was to remove the complexity of having to think about tying multiple data sets together. If you've worked with multiple data sets before, I'm sure you've stumbled across a time where the number of rows in your resulting data set formed by your joins has exploded to a large number from what you initially had. 

Relationships makes use of:

  • Smart Aggregations - avoid duplication of values that come from a join condition that links one row to many rows in the other data source
  • Conditional Joins - uses different types of joins depending on what the model assess that you are trying to do within your visualisation. 
This flexibility comes from Tableau creating a 'logical data model' that it then flexes. If you've created Joins and Unions before then you will have built a 'physical data model'. 

This all sounds great but when exploring data sets I've found that many people struggle to lock on to exactly what is going on in the data. You might not even have access to Tableau to make use of the relationship model. This leads us to this week's challenge where you will build the physical data model to help you understand what is happening in Tableau's main example data set for relationships, Bookshop. 

Input

One Excel workbook with 13 worksheets of data. 


Requirements

You aim is to build a data set that is one row per item sold for each order made at the Book Shop.
  • Input data
  • Union all the Sales data together to form one row per item in a sale
    • This is the granularity of the data set throughout the whole challenge (56,350 rows)
  • Join all other data sets in the workbook on to this data
    • Never let the number of rows change
      • You may need to disregard incomplete records or summarise useful data into a metric instead of including all the detail
  • Remove any duplicate fields
  • Remove the two fields created (in Prep at least) as the result of the Union:
    • Table Names
    • Sheet Names
  • Output your resulting single table

Output



38 Fields (calculations / aggregations in Italics):
  • Book ID
  • Sales Date
  • ISBN
  • Discount
  • Item ID
  • Order ID
  • First Name
  • Last Name
  • Birthday
  • Country of Residence
  • Hrs Writing per Day
  • Title 
  • Auth ID
  • Format
  • PubID
  • Publication Date
  • Pages
  • Print Run Size (k)
  • Price
  • Publishing House
  • City
  • State
  • Country
  • Year Established
  • Marketing Spend
  • Number of Awards (avg only)
  • Number of Months Checked Out
  • Total Checkouts
  • Genre
  • SeriesID
  • Volume Number
  • Staff Comment
  • Series Name
  • Planned Volumes
  • Book Tour Events
  • Average Rating
  • Number of Reviewers
  • Number of Reviews

56,350 rows (56,351 rows 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

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